> I will try to get it in the evening.
Unfortunately dnf.log ends at the moment when the packages are started to be updated (doing a separate "dnf update" session I don't see anything during the update process itself, only before and after):
Transaction Summary
================================================================================
Install 146 Packages
Upgrade 3172 Packages
Remove 6 Packages
Downgrade 9 Packages
2017-10-17T18:28:37Z INFO Total size: 3.0 G
2017-10-17T18:28:37Z INFO Downloading Packages:
2017-10-17T18:28:37Z SUBDEBUG Call: RPMPayload._end_cb: (<dnf.repo.RPMPayload object at 0x7fca047ba5c0>, 1, 'Already downloaded'), {}
(...)
2017-10-17T18:28:38Z SUBDEBUG Call: RPMPayload._end_cb: (<dnf.repo.RPMPayload object at 0x7fca0451d940>, 1, 'Already downloaded'), {}
2017-10-17T18:28:38Z SUBDEBUG Call: RPMPayload._end_cb: (<dnf.repo.RPMPayload object at 0x7fca0451d978>, 1, 'Already downloaded'), {}
2017-10-17T18:28:47Z INFO Running transaction check
2017-10-17T18:28:51Z INFO Transaction check succeeded.
2017-10-17T18:28:51Z INFO Running transaction test
2017-10-17T18:28:59Z INFO Transaction test succeeded.
2017-10-17T18:28:59Z DDEBUG timer: transaction test: 7137 ms
2017-10-17T18:28:59Z INFO Running transaction
2017-10-17T18:29:01Z DDEBUG RPM transaction start.
(here stars another session started manually from chroot)
2017-10-18T01:31:01Z INFO --- logging initialized ---
2017-10-18T01:31:01Z DDEBUG timer: config: 12 ms
2017-10-18T01:31:01Z DEBUG Loaded plugins: builddep, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restar
ting, playground, repoclosure, repograph, repomanage, reposync, system-upgrade
2017-10-18T01:31:01Z DEBUG DNF version: 2.7.3
(...)
The system journal from the session with dnf upgrade after reboot terminates unexpectedly:
Oct 17 20:27:55 foobar systemd[1]: Reached target System Initialization.
Oct 17 20:27:55 foobar kernel: audit: type=1130 audit(1508264875.449:92): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/s
Oct 17 20:27:55 foobar systemd[1]: Starting System Upgrade using DNF...
Oct 17 20:27:55 foobar systemd[1]: Started Updates device firmware whilst offline.
Oct 17 20:27:55 foobar audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fwupd-offline-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?
Oct 17 20:27:55 foobar systemd[1]: Listening on D-Bus System Message Bus Socket.
Oct 17 20:27:55 foobar systemd[1]: Starting Update the operating system whilst offline...
Oct 17 20:27:55 foobar pk-offline-update[807]: another framework set up the trigger
Oct 17 20:27:55 foobar systemd[1]: Started Update the operating system whilst offline.
Oct 17 20:27:55 foobar audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=packagekit-offline-update comm="systemd" exe="/usr/lib/systemd/systemd" hostn
Oct 17 20:27:55 foobar audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=packagekit-offline-update comm="systemd" exe="/usr/lib/systemd/systemd" hostna
Oct 17 20:27:55 foobar audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fwupd-offline-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?
Oct 17 20:27:56 foobar systemd[1]: Received SIGRTMIN+20 from PID 362 (plymouthd).
Oct 17 20:27:58 foobar audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
Oct 17 20:27:58 foobar systemd[1]: Received SIGRTMIN+20 from PID 362 (plymouthd).
Oct 17 20:27:59 foobar dnf[805]: Last metadata expiration check: 0:18:43 ago on Tue 17 Oct 2017 08:09:16 PM CEST.
Oct 17 20:27:59 foobar system-python[805]: Starting system upgrade. This will take a while.
Oct 17 20:28:19 foobar dnf[805]: Dependencies resolved.
(...)
Oct 17 20:37:00 foobar dnf[805]: Upgrading : pygtk2-codegen-2.24.0-18.fc27.x86_64 1368/6548
Oct 17 20:37:00 foobar dnf[805]: Running scriptlet: glibc-headers-2.26-8.fc27.x86_64 1369/6548
Oct 17 20:37:01 foobar dnf[805]: Upgrading : glibc-headers-2.26-8.fc27.x86_64 1369/6548
Oct 17 20:37:01 foobar dnf[805]: Upgrading : glibc-devel-2.26-8.fc27.x86_64 1370/6548
(... end ...)
I left the computer alone during the operation and it was shut down when I came back. My system suffers from 100% CPU used by kworker: https://bugzilla.redhat.com/show_bug.cgi?id=1115658#c4 (there is open bug, but I cannot find it right now). It might got overheat and did emergency shutdown (I haven't seen that before, thus). It was very hot and I see in that log:
Oct 17 20:33:34 foobar kernel: CPU1: Core temperature above threshold, cpu clock throttled (total events = 1)
Therefore, I suspect it wasn't a system-upgrade issue, just unexpected shutdown. Nevertheless, using that accident I would like to set a procedure to behave in that situation in the future (it might happen occasionally).
Marcin
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
