On 10/21/24 10:44, Samuel Sieb wrote:
On 10/21/24 3:05 AM, ToddAndMargo via users wrote:
On 10/20/24 23:09, Samuel Sieb wrote:
On 10/20/24 11:05 PM, ToddAndMargo via users wrote:
On 10/20/24 22:45, Samuel Sieb wrote:
On 10/20/24 7:42 PM, ToddAndMargo via users wrote:
On 10/20/24 19:22, Samuel Sieb wrote:
dnf system-upgrade log
If it finds anything, you can run it again with the (I assume)
number and get the logs.
I am not sure I understand:
# dnf system-upgrade log
The following boots appear to contain offline transaction logs:
1 / 86dede181d25447f94a9457c2ec80d11: 2024-10-20 05:11:05 39→41
2 / b73afb7abf49472fb3b50eed305c07c8: 2024-10-21 01:51:45 39→41
Where do I find these things?
Two of them? That's interesting.
Try "dnf system-upgrade log 1" and then 2.
# dnf system-upgrade log 1
Unknown argument "1" for command "log". Add "--help" for more
information about the arguments.
You could look in the man page. :-) (man dnf-system-upgrade)
dnf system-upgrade log --number=1
It shows a ton of things being upgraded. 31157 lines!
Oct 19 22:41:54 rn6.rent-a-nerd.local systemd-shutdown[1]: Syncing
filesystems >
Oct 19 22:41:54 rn6.rent-a-nerd.local systemd-shutdown[1]: Sending
SIGTERM to r>
Oct 19 22:41:54 rn6.rent-a-nerd.local systemd-journald[78730]:
Received SIGTERM>
Oct 19 22:41:54 rn6.rent-a-nerd.local systemd-journald[78730]: Journal
stopped
lines 31135-31157/31157 (END)
To F40 packages?
What about log 2?
Well, it is a lot shorter. Only 1768 lines. I see no
dnf anything.
Log 2 what my second attempt to upgrade. The reboot
went off, then it almost instantly rebooted again and
went back to 39
Oct 20 18:52:14 rn6.rent-a-nerd.local audit[1]: SERVICE_START pid=1
uid=0 auid=4294967295 ses=4294967295 su>
Oct 20 18:52:14 rn6.rent-a-nerd.local audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 sub>
Oct 20 18:52:14 rn6.rent-a-nerd.local systemd[1]: Finished
systemd-reboot.service - System Reboot.
Oct 20 18:52:14 rn6.rent-a-nerd.local systemd[1]: Reached target
reboot.target - System Reboot.
Oct 20 18:52:14 rn6.rent-a-nerd.local systemd[1]: Shutting down.
Oct 20 18:52:14 rn6.rent-a-nerd.local audit: BPF prog-id=61 op=UNLOAD
Oct 20 18:52:14 rn6.rent-a-nerd.local audit: BPF prog-id=60 op=UNLOAD
Oct 20 18:52:14 rn6.rent-a-nerd.local audit: BPF prog-id=57 op=UNLOAD
Oct 20 18:52:14 rn6.rent-a-nerd.local audit: BPF prog-id=56 op=UNLOAD
Oct 20 18:52:14 rn6.rent-a-nerd.local audit: BPF prog-id=53 op=UNLOAD
Oct 20 18:52:14 rn6.rent-a-nerd.local audit: BPF prog-id=55 op=UNLOAD
Oct 20 18:52:14 rn6.rent-a-nerd.local audit: BPF prog-id=54 op=UNLOAD
Oct 20 18:52:14 rn6.rent-a-nerd.local audit: BPF prog-id=52 op=UNLOAD
Oct 20 18:52:14 rn6.rent-a-nerd.local systemd-shutdown[1]: Syncing
filesystems and block devices.
Oct 20 18:52:14 rn6.rent-a-nerd.local systemd-shutdown[1]: Sending
SIGTERM to remaining processes...
Oct 20 18:52:14 rn6.rent-a-nerd.local systemd-journald[935]: Received
SIGTERM from PID 1 (systemd-shutdow).
Oct 20 18:52:14 rn6.rent-a-nerd.local systemd-journald[935]: Journal stopped
lines 1746-1768/1768 (END)
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
