NEWS
[Solved] Question - Halt state and IOB behaviour
Hardware
7
Beiträge
2
Kommentatoren
1.1k
Aufrufe
2
Watching
-
(EDIT - in the end its not about IOB , its more about how logs are timestamped short time after boot)
Trying to setup HW configuration where also the loss of power will be reasonably safe to the SSD. When testing behavior of different ways of the shutdown and of the restarting I was really surprised when noted in the IOB log, that after shutdown the IOB firstly terminated everything (as I expected) however then roughly 1 minute after sigterm IOB started again. (doesnt matter whether the shutdown was made through GUI or by sudo shutdown, sudo shutdown -P).Im totally confused because I expected that ca 1 minute or more after shutdown the CPU does not work at all and no one application runs so that I can safely remove the power from the board. However in the log I see that it is not true.
Please see following section of the IOB log:
- At ca 16:40:18 I performed "sudo shutdown -P"
- At ca 16:41:01 I saw last blink of the SSD and the "power" was shut down (not really the power source but the GPIO PINS e.t.c. went into undefined state)
- At 16:42:36 I made a restart through GPIO3 pin
2024-01-27 16:40:18.328 - info: backitup.0 (2040) cleaned everything up... 2024-01-27 16:40:18.321 - info: host.pi4IobPnl received SIGTERM 2024-01-27 16:40:18.324 - info: admin.0 (1529) terminating http server on port 8081 2024-01-27 16:40:18.352 - info: host.pi4IobPnl stopInstance system.adapter.admin.0 (force=false, process=true) 2024-01-27 16:40:18.390 - info: host.pi4IobPnl stopInstance system.adapter.javascript.0 (force=false, process=true) 2024-01-27 16:40:18.399 - info: host.pi4IobPnl stopInstance system.adapter.history.0 (force=false, process=false) 2024-01-27 16:40:18.400 - info: host.pi4IobPnl stopInstance system.adapter.discovery.0 (force=false, process=true) 2024-01-27 16:40:18.420 - info: host.pi4IobPnl stopInstance system.adapter.backitup.0 (force=false, process=true) 2024-01-27 16:40:18.421 - info: host.pi4IobPnl stopInstance system.adapter.ebus.0 (force=false, process=false) 2024-01-27 16:40:18.422 - info: host.pi4IobPnl stopInstance system.adapter.valuetrackerovertime.0 (force=false, process=false) 2024-01-27 16:40:18.494 - info: javascript.0 (1806) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.501 - info: discovery.0 (1921) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.498 - info: admin.0 (1529) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.509 - info: discovery.0 (1921) terminating 2024-01-27 16:40:18.508 - info: backitup.0 (2040) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.512 - info: discovery.0 (1921) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.531 - info: javascript.0 (1806) terminating 2024-01-27 16:40:18.536 - info: backitup.0 (2040) terminating 2024-01-27 16:40:18.541 - info: host.pi4IobPnl stopInstance system.adapter.admin.0 send kill signal 2024-01-27 16:40:18.547 - info: admin.0 (1529) terminating 2024-01-27 16:40:18.548 - info: host.pi4IobPnl stopInstance system.adapter.javascript.0 send kill signal 2024-01-27 16:40:18.549 - info: host.pi4IobPnl stopInstance system.adapter.discovery.0 send kill signal 2024-01-27 16:40:18.554 - info: host.pi4IobPnl stopInstance system.adapter.backitup.0 send kill signal 2024-01-27 16:40:18.551 - info: javascript.0 (1806) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.550 - info: backitup.0 (2040) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.553 - info: admin.0 (1529) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.836 - info: discovery.0 (1921) terminating 2024-01-27 16:40:18.836 - info: javascript.0 (1806) terminating 2024-01-27 16:40:18.848 - info: backitup.0 (2040) terminating 2024-01-27 16:40:18.869 - info: admin.0 (1529) terminating 2024-01-27 16:40:19.228 - info: host.pi4IobPnl instance system.adapter.discovery.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.266 - info: host.pi4IobPnl instance system.adapter.backitup.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.281 - info: host.pi4IobPnl instance system.adapter.admin.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.321 - info: host.pi4IobPnl instance system.adapter.javascript.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.322 - info: host.pi4IobPnl All instances are stopped. 2024-01-27 16:40:19.505 - info: host.pi4IobPnl terminated 2024-01-27 16:41:15.975 - info: host.pi4IobPnl iobroker.js-controller version 5.0.17 js-controller starting 2024-01-27 16:41:15.984 - info: host.pi4IobPnl Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-01-27 16:41:15.985 - info: host.pi4IobPnl hostname: pi4IobPnl, node: v18.19.0 2024-01-27 16:41:15.986 - info: host.pi4IobPnl ip addresses: 10.0.3.121 fe80::c9b8:7f3d:e204:7d2f 2024-01-27 16:41:17.956 - info: host.pi4IobPnl connected to Objects and States 2024-01-27 16:41:18.003 - info: host.pi4IobPnl added notifications configuration of host 2024-01-27 16:41:19.138 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.nodeCurrent" 2024-01-27 16:41:19.144 - info: host.pi4IobPnl 7 instances found 2024-01-27 16:41:19.172 - info: host.pi4IobPnl starting 4 instances 2024-01-27 16:41:19.325 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.nodeNewest" 2024-01-27 16:41:19.339 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.nodeNewestNext" 2024-01-27 16:41:19.351 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.npmCurrent" 2024-01-27 16:41:19.370 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.npmNewest" 2024-01-27 16:41:19.393 - info: host.pi4IobPnl instance system.adapter.admin.0 started with pid 1502 2024-01-27 16:41:19.411 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.npmNewestNext" 2024-01-27 16:41:19.470 - info: host.pi4IobPnl Some obsolete host states deleted. 2024-01-27 16:41:23.248 - info: host.pi4IobPnl instance system.adapter.javascript.0 started with pid 1790 2024-01-27 16:41:25.189 - info: admin.0 (1502) starting. Version 6.12.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:25.261 - info: admin.0 (1502) requesting all objects 2024-01-27 16:41:26.091 - info: admin.0 (1502) received all objects 2024-01-27 16:41:26.908 - info: admin.0 (1502) Request actual repository... 2024-01-27 16:41:27.072 - info: admin.0 (1502) socket.io server listening on port 8081 2024-01-27 16:41:27.083 - info: admin.0 (1502) http server listening on port 8081 2024-01-27 16:41:27.084 - info: admin.0 (1502) Use link "http://127.0.0.1:8081" to configure. 2024-01-27 16:41:27.508 - info: host.pi4IobPnl Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2024-01-27 16:41:27.563 - info: host.pi4IobPnl instance system.adapter.discovery.0 started with pid 2180 2024-01-27 16:41:29.324 - info: javascript.0 (1790) starting. Version 7.1.6 in /opt/iobroker/node_modules/iobroker.javascript, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:29.867 - info: javascript.0 (1790) requesting all states 2024-01-27 16:41:29.870 - info: javascript.0 (1790) requesting all objects 2024-01-27 16:41:30.189 - info: javascript.0 (1790) received all states 2024-01-27 16:41:30.403 - info: javascript.0 (1790) received all objects 2024-01-27 16:41:31.226 - info: host.pi4IobPnl instance system.adapter.backitup.0 started with pid 2392 2024-01-27 16:41:31.258 - info: discovery.0 (2180) starting. Version 4.2.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:32.354 - info: admin.0 (1502) Repository received successfully. 2024-01-27 16:41:34.198 - info: backitup.0 (2392) starting. Version 2.9.8 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:34.312 - info: backitup.0 (2392) [iobroker] backup will be activated at 02:48 every 1 day(s) 2024-01-27 16:45:17.316 - info: admin.0 (1502) failed connection to socket.io from ::ffff:10.0.3.121: Passport was not initialized 2024-01-27 16:45:45.067 - info: admin.0 (1502) ==> Connected system.user.admin from ::ffff:10.0.3.121In the log I can see that within ca 1sec the IOB succesfuly terminated itself (16:40:19.505). However within no more than 1 minute the IOB started again (16:41:15.975) and finished its preparation within some 15 seconds (16:41:34.312) which was still ca 1 minute before I woke-up theRPI through GPIO3. After my restarting of the RPI the IOB only waited for me to log-in to the admin webpage.
Is this behaviour during the HALT state normal?
(Note - I firstly discovered this having the PiJuice Hat installed. This hat provides a battery backup. However even after taking the hat down the RPI behaves this strange way. And the log is from using the RPI without the hat)
RPI 4B 8GB, fresh installation of Bookworm,
fresh installation of IOBroker v. 6.12.0
Node.js: v18.19.0
NPM: 10.2.3
js-controller: 5.0.17
only few basic adapters installed
Instead of SD card Im using SSD connected through Axagon adapter to USB. -
(EDIT - in the end its not about IOB , its more about how logs are timestamped short time after boot)
Trying to setup HW configuration where also the loss of power will be reasonably safe to the SSD. When testing behavior of different ways of the shutdown and of the restarting I was really surprised when noted in the IOB log, that after shutdown the IOB firstly terminated everything (as I expected) however then roughly 1 minute after sigterm IOB started again. (doesnt matter whether the shutdown was made through GUI or by sudo shutdown, sudo shutdown -P).Im totally confused because I expected that ca 1 minute or more after shutdown the CPU does not work at all and no one application runs so that I can safely remove the power from the board. However in the log I see that it is not true.
Please see following section of the IOB log:
- At ca 16:40:18 I performed "sudo shutdown -P"
- At ca 16:41:01 I saw last blink of the SSD and the "power" was shut down (not really the power source but the GPIO PINS e.t.c. went into undefined state)
- At 16:42:36 I made a restart through GPIO3 pin
2024-01-27 16:40:18.328 - info: backitup.0 (2040) cleaned everything up... 2024-01-27 16:40:18.321 - info: host.pi4IobPnl received SIGTERM 2024-01-27 16:40:18.324 - info: admin.0 (1529) terminating http server on port 8081 2024-01-27 16:40:18.352 - info: host.pi4IobPnl stopInstance system.adapter.admin.0 (force=false, process=true) 2024-01-27 16:40:18.390 - info: host.pi4IobPnl stopInstance system.adapter.javascript.0 (force=false, process=true) 2024-01-27 16:40:18.399 - info: host.pi4IobPnl stopInstance system.adapter.history.0 (force=false, process=false) 2024-01-27 16:40:18.400 - info: host.pi4IobPnl stopInstance system.adapter.discovery.0 (force=false, process=true) 2024-01-27 16:40:18.420 - info: host.pi4IobPnl stopInstance system.adapter.backitup.0 (force=false, process=true) 2024-01-27 16:40:18.421 - info: host.pi4IobPnl stopInstance system.adapter.ebus.0 (force=false, process=false) 2024-01-27 16:40:18.422 - info: host.pi4IobPnl stopInstance system.adapter.valuetrackerovertime.0 (force=false, process=false) 2024-01-27 16:40:18.494 - info: javascript.0 (1806) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.501 - info: discovery.0 (1921) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.498 - info: admin.0 (1529) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.509 - info: discovery.0 (1921) terminating 2024-01-27 16:40:18.508 - info: backitup.0 (2040) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.512 - info: discovery.0 (1921) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.531 - info: javascript.0 (1806) terminating 2024-01-27 16:40:18.536 - info: backitup.0 (2040) terminating 2024-01-27 16:40:18.541 - info: host.pi4IobPnl stopInstance system.adapter.admin.0 send kill signal 2024-01-27 16:40:18.547 - info: admin.0 (1529) terminating 2024-01-27 16:40:18.548 - info: host.pi4IobPnl stopInstance system.adapter.javascript.0 send kill signal 2024-01-27 16:40:18.549 - info: host.pi4IobPnl stopInstance system.adapter.discovery.0 send kill signal 2024-01-27 16:40:18.554 - info: host.pi4IobPnl stopInstance system.adapter.backitup.0 send kill signal 2024-01-27 16:40:18.551 - info: javascript.0 (1806) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.550 - info: backitup.0 (2040) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.553 - info: admin.0 (1529) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.836 - info: discovery.0 (1921) terminating 2024-01-27 16:40:18.836 - info: javascript.0 (1806) terminating 2024-01-27 16:40:18.848 - info: backitup.0 (2040) terminating 2024-01-27 16:40:18.869 - info: admin.0 (1529) terminating 2024-01-27 16:40:19.228 - info: host.pi4IobPnl instance system.adapter.discovery.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.266 - info: host.pi4IobPnl instance system.adapter.backitup.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.281 - info: host.pi4IobPnl instance system.adapter.admin.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.321 - info: host.pi4IobPnl instance system.adapter.javascript.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.322 - info: host.pi4IobPnl All instances are stopped. 2024-01-27 16:40:19.505 - info: host.pi4IobPnl terminated 2024-01-27 16:41:15.975 - info: host.pi4IobPnl iobroker.js-controller version 5.0.17 js-controller starting 2024-01-27 16:41:15.984 - info: host.pi4IobPnl Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-01-27 16:41:15.985 - info: host.pi4IobPnl hostname: pi4IobPnl, node: v18.19.0 2024-01-27 16:41:15.986 - info: host.pi4IobPnl ip addresses: 10.0.3.121 fe80::c9b8:7f3d:e204:7d2f 2024-01-27 16:41:17.956 - info: host.pi4IobPnl connected to Objects and States 2024-01-27 16:41:18.003 - info: host.pi4IobPnl added notifications configuration of host 2024-01-27 16:41:19.138 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.nodeCurrent" 2024-01-27 16:41:19.144 - info: host.pi4IobPnl 7 instances found 2024-01-27 16:41:19.172 - info: host.pi4IobPnl starting 4 instances 2024-01-27 16:41:19.325 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.nodeNewest" 2024-01-27 16:41:19.339 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.nodeNewestNext" 2024-01-27 16:41:19.351 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.npmCurrent" 2024-01-27 16:41:19.370 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.npmNewest" 2024-01-27 16:41:19.393 - info: host.pi4IobPnl instance system.adapter.admin.0 started with pid 1502 2024-01-27 16:41:19.411 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.npmNewestNext" 2024-01-27 16:41:19.470 - info: host.pi4IobPnl Some obsolete host states deleted. 2024-01-27 16:41:23.248 - info: host.pi4IobPnl instance system.adapter.javascript.0 started with pid 1790 2024-01-27 16:41:25.189 - info: admin.0 (1502) starting. Version 6.12.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:25.261 - info: admin.0 (1502) requesting all objects 2024-01-27 16:41:26.091 - info: admin.0 (1502) received all objects 2024-01-27 16:41:26.908 - info: admin.0 (1502) Request actual repository... 2024-01-27 16:41:27.072 - info: admin.0 (1502) socket.io server listening on port 8081 2024-01-27 16:41:27.083 - info: admin.0 (1502) http server listening on port 8081 2024-01-27 16:41:27.084 - info: admin.0 (1502) Use link "http://127.0.0.1:8081" to configure. 2024-01-27 16:41:27.508 - info: host.pi4IobPnl Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2024-01-27 16:41:27.563 - info: host.pi4IobPnl instance system.adapter.discovery.0 started with pid 2180 2024-01-27 16:41:29.324 - info: javascript.0 (1790) starting. Version 7.1.6 in /opt/iobroker/node_modules/iobroker.javascript, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:29.867 - info: javascript.0 (1790) requesting all states 2024-01-27 16:41:29.870 - info: javascript.0 (1790) requesting all objects 2024-01-27 16:41:30.189 - info: javascript.0 (1790) received all states 2024-01-27 16:41:30.403 - info: javascript.0 (1790) received all objects 2024-01-27 16:41:31.226 - info: host.pi4IobPnl instance system.adapter.backitup.0 started with pid 2392 2024-01-27 16:41:31.258 - info: discovery.0 (2180) starting. Version 4.2.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:32.354 - info: admin.0 (1502) Repository received successfully. 2024-01-27 16:41:34.198 - info: backitup.0 (2392) starting. Version 2.9.8 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:34.312 - info: backitup.0 (2392) [iobroker] backup will be activated at 02:48 every 1 day(s) 2024-01-27 16:45:17.316 - info: admin.0 (1502) failed connection to socket.io from ::ffff:10.0.3.121: Passport was not initialized 2024-01-27 16:45:45.067 - info: admin.0 (1502) ==> Connected system.user.admin from ::ffff:10.0.3.121In the log I can see that within ca 1sec the IOB succesfuly terminated itself (16:40:19.505). However within no more than 1 minute the IOB started again (16:41:15.975) and finished its preparation within some 15 seconds (16:41:34.312) which was still ca 1 minute before I woke-up theRPI through GPIO3. After my restarting of the RPI the IOB only waited for me to log-in to the admin webpage.
Is this behaviour during the HALT state normal?
(Note - I firstly discovered this having the PiJuice Hat installed. This hat provides a battery backup. However even after taking the hat down the RPI behaves this strange way. And the log is from using the RPI without the hat)
RPI 4B 8GB, fresh installation of Bookworm,
fresh installation of IOBroker v. 6.12.0
Node.js: v18.19.0
NPM: 10.2.3
js-controller: 5.0.17
only few basic adapters installed
Instead of SD card Im using SSD connected through Axagon adapter to USB.@cjoe What about syslog?
sudo journalctl --since "2024-01-27 16:40:18" --until "2024-01-27 16:45"? -
@cjoe What about syslog?
sudo journalctl --since "2024-01-27 16:40:18" --until "2024-01-27 16:45"?@iobnordlicht said in Question - Halt state and IOB behaviour:
sudo journalctl --since "2024-01-27 16:40:18" --until "2024-01-27 16:45"
Here it is, I cut it just few lines after the boot: (Let me know if I shall give here even the long rest of log after the boot)
Jan 27 16:40:18 pi4xyzxyz systemd-logind[600]: System is powering down. Jan 27 16:40:18 pi4xyzxyz systemd-logind[600]: The system will power off now! Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping session-2.scope - Session 2 of User pi... Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping session-3.scope - Session 3 of User pi... Jan 27 16:40:18 pi4xyzxyz systemd[1]: Removed slice system-bthelper.slice - Slice /system/bthelper. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Removed slice system-modprobe.slice - Slice /system/modprobe. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped target bluetooth.target - Bluetooth Support. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped target rpc_pipefs.target. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped target sound.target - Sound Card. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped target timers.target - Timer Units. Jan 27 16:40:18 pi4xyzxyz systemd[1]: apt-daily-upgrade.timer: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped apt-daily-upgrade.timer - Daily apt upgrade and clean activities. Jan 27 16:40:18 pi4xyzxyz systemd[1]: apt-daily.timer: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped apt-daily.timer - Daily apt download activities. Jan 27 16:40:18 pi4xyzxyz systemd[1]: dpkg-db-backup.timer: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped dpkg-db-backup.timer - Daily dpkg database backup timer. Jan 27 16:40:18 pi4xyzxyz systemd[1]: e2scrub_all.timer: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems. Jan 27 16:40:18 pi4xyzxyz systemd[1]: fstrim.timer: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped fstrim.timer - Discard unused blocks once a week. Jan 27 16:40:18 pi4xyzxyz systemd[1]: logrotate.timer: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped logrotate.timer - Daily rotation of log files. Jan 27 16:40:18 pi4xyzxyz systemd[1]: man-db.timer: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped man-db.timer - Daily man-db regeneration. Jan 27 16:40:18 pi4xyzxyz systemd[1]: systemd-tmpfiles-clean.timer: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped target time-set.target - System Time Set. Jan 27 16:40:18 pi4xyzxyz systemd[1]: systemd-rfkill.socket: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Closed systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Unmounting run-rpc_pipefs.mount - RPC Pipe File System... Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping alsa-restore.service - Save/Restore Sound Card State... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Terminating Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping bluetooth.service - Bluetooth service... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/ldac Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping colord.service - Manage, Install and Generate Color Profiles... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSink/aptx_hd Jan 27 16:40:18 pi4xyzxyz systemd[1]: rpi-display-backlight.service - Turns off Raspberry Pi display backlight on shutdown/reboot was skipped because of an unmet condition check (ConditionPathIsDirectory=/proc/device-tree/rpi_backlight). Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_hd Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping rtkit-daemon.service - RealtimeKit Scheduling Policy Service... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSink/aptx Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping systemd-random-seed.service - Load/Save Random Seed... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped target getty.target - Login Prompts. Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSink/sbc Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping ModemManager.service - Modem Manager... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/sbc Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping accounts-daemon.service - Accounts Service... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSink/sbc_xq Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping cron.service - Regular background program processing daemon... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/sbc_xq Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping cups-browsed.service - Make remote CUPS printers available locally... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_1 Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping dphys-swapfile.service - dphys-swapfile - set up, mount/unmount, and delete a swap file... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_0 Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping getty@tty1.service - Getty on tty1... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/faststream Jan 27 16:40:18 pi4xyzxyz systemd[1]: glamor-test.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/faststream_duplex Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped glamor-test.service - Check for glamor. Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSink/opus_05 Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping iobroker.service - ioBroker Server... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/opus_05 Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping lightdm.service - Light Display Manager... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSink/opus_05_duplex Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping pijuice.service - PiJuice status service... Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Endpoint unregistered: sender=:1.31 path=/MediaEndpoint/A2DPSource/opus_05_duplex Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping raspi-config.service - LSB: Switch to ondemand cpu governor (unless shift key is pressed)... Jan 27 16:40:18 pi4xyzxyz ModemManager[697]: <info> caught signal, shutting down... Jan 27 16:40:18 pi4xyzxyz systemd[1]: rp1-test.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz vncserver[78791]: See https://www.realvnc.com for information on VNC. Jan 27 16:40:18 pi4xyzxyz vncserver[78791]: To start an instance of VNC Server in Virtual Mode, run the following command: Jan 27 16:40:18 pi4xyzxyz vncserver[78791]: vncserver-virtual Jan 27 16:40:18 pi4xyzxyz vncserver[78791]: To start the VNC Server in Virtual Mode daemon, run the following command as Jan 27 16:40:18 pi4xyzxyz vncserver[78791]: root: Jan 27 16:40:18 pi4xyzxyz vncserver[78791]: /etc/vnc/vncservice start vncserver-virtuald Jan 27 16:40:18 pi4xyzxyz vncserver[78791]: To start VNC Server in Service Mode, run the following command as root: Jan 27 16:40:18 pi4xyzxyz vncserver[78791]: /etc/vnc/vncservice start vncserver-x11-serviced Jan 27 16:40:18 pi4xyzxyz vncserver[78791]: To start VNC Server in User Mode, run the following command: Jan 27 16:40:18 pi4xyzxyz vncserver[78791]: vncserver-x11 Jan 27 16:40:18 pi4xyzxyz vncserver-x11[804]: Connections: disconnected: 10.0.3.115::63962 (TCP) ([ServerShutdown] VNC Server exited) Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped rp1-test.service - Check for RP1 displays for Xorg. Jan 27 16:40:18 pi4xyzxyz systemd[1]: rpi-eeprom-update.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped rpi-eeprom-update.service - Check for Raspberry Pi EEPROM updates. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping ssh.service - OpenBSD Secure Shell server... Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping triggerhappy.service - triggerhappy global hotkey daemon... Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping udisks2.service - Disk Manager... Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping vncserver-x11-serviced.service - VNC Server in Service Mode daemon... Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping vncvirtualdesktop.service... Jan 27 16:40:18 pi4xyzxyz lightdm[1212]: pam_unix(lightdm-autologin:session): session closed for user pi Jan 27 16:40:18 pi4xyzxyz sshd[847]: Received signal 15; terminating. Jan 27 16:40:18 pi4xyzxyz systemd[1]: accounts-daemon.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped accounts-daemon.service - Accounts Service. Jan 27 16:40:18 pi4xyzxyz systemd[1]: cron.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped cron.service - Regular background program processing daemon. Jan 27 16:40:18 pi4xyzxyz systemd[1]: rtkit-daemon.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped rtkit-daemon.service - RealtimeKit Scheduling Policy Service. Jan 27 16:40:18 pi4xyzxyz systemd[1]: ssh.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server. Jan 27 16:40:18 pi4xyzxyz systemd[1]: getty@tty1.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped getty@tty1.service - Getty on tty1. Jan 27 16:40:18 pi4xyzxyz systemd[1]: colord.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped colord.service - Manage, Install and Generate Color Profiles. Jan 27 16:40:18 pi4xyzxyz polkitd[580]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.32, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus) Jan 27 16:40:18 pi4xyzxyz systemd[1]: run-rpc_pipefs.mount: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Unmounted run-rpc_pipefs.mount - RPC Pipe File System. Jan 27 16:40:18 pi4xyzxyz systemd[1]: vncvirtualdesktop.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped vncvirtualdesktop.service. Jan 27 16:40:18 pi4xyzxyz systemd[1]: session-3.scope: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped session-3.scope - Session 3 of User pi. Jan 27 16:40:18 pi4xyzxyz vncserver-x11-serviced[1433]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Jan 27 16:40:18 pi4xyzxyz vncserver-x11-serviced[1433]: after 77503 requests (77503 known processed) with 0 events remaining. Jan 27 16:40:18 pi4xyzxyz vncserver-x11-serviced[1482]: X connection to :0 broken (explicit kill or server shutdown). Jan 27 16:40:18 pi4xyzxyz vncserver-x11-serviced[1508]: vncserverui: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Jan 27 16:40:18 pi4xyzxyz ModemManager[697]: <info> ModemManager is shut down Jan 27 16:40:18 pi4xyzxyz NetworkManager[649]: <info> [1706370018.4854] modem-manager: ModemManager no longer available Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.16' (uid=0 pid=780 comm="/usr/sbin/cupsd -l") Jan 27 16:40:18 pi4xyzxyz udisksd[611]: udisks daemon version 2.9.4 exiting Jan 27 16:40:18 pi4xyzxyz systemd[793]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz systemd[793]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.Profile1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.31" (uid=1000 pid=990 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.Profile1.Error.NotImplemented" requested_reply="0" destination=":1.12" (uid=0 pid=761 comm="/usr/libexec/bluetooth/bluetoothd") Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Stopping SDP server Jan 27 16:40:18 pi4xyzxyz bluetoothd[761]: Exit Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.31' (uid=1000 pid=990 comm="/usr/bin/wireplumber") Jan 27 16:40:18 pi4xyzxyz systemd[1]: var-swap.swap: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Deactivated swap var-swap.swap - /var/swap. Jan 27 16:40:18 pi4xyzxyz systemd[1]: triggerhappy.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped triggerhappy.service - triggerhappy global hotkey daemon. Jan 27 16:40:18 pi4xyzxyz systemd[1]: udisks2.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped udisks2.service - Disk Manager. Jan 27 16:40:18 pi4xyzxyz systemd[1]: ModemManager.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped ModemManager.service - Modem Manager. Jan 27 16:40:18 pi4xyzxyz systemd-logind[600]: Session 3 logged out. Waiting for processes to exit. Jan 27 16:40:18 pi4xyzxyz systemd[1]: bluetooth.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped bluetooth.service - Bluetooth service. Jan 27 16:40:18 pi4xyzxyz systemd[1]: alsa-restore.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped alsa-restore.service - Save/Restore Sound Card State. Jan 27 16:40:18 pi4xyzxyz systemd[1]: systemd-random-seed.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped systemd-random-seed.service - Load/Save Random Seed. Jan 27 16:40:18 pi4xyzxyz systemd[1]: dphys-swapfile.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped dphys-swapfile.service - dphys-swapfile - set up, mount/unmount, and delete a swap file. Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Activation via systemd failed for unit 'colord.service': Refusing activation, D-Bus is shutting down. Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Refusing activation, D-Bus is shutting down. Jan 27 16:40:18 pi4xyzxyz vncserver-x11[804]: session ended: user pi Jan 27 16:40:18 pi4xyzxyz vncserver-x11[804]: FdIo: setHandler: [System-32] write: Broken pipe (32) Jan 27 16:40:18 pi4xyzxyz vncserver-x11[804]: ServerManager: Server stopped Jan 27 16:40:18 pi4xyzxyz systemd[1]: raspi-config.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped raspi-config.service - LSB: Switch to ondemand cpu governor (unless shift key is pressed). Jan 27 16:40:18 pi4xyzxyz systemd[1]: vncserver-x11-serviced.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped vncserver-x11-serviced.service - VNC Server in Service Mode daemon. Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.31' (uid=1000 pid=990 comm="/usr/bin/wireplumber") Jan 27 16:40:18 pi4xyzxyz systemd[1]: vncserver-x11-serviced.service: Consumed 1min 12.824s CPU time. Jan 27 16:40:18 pi4xyzxyz dbus-daemon[567]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Refusing activation, D-Bus is shutting down. Jan 27 16:40:18 pi4xyzxyz systemd[1]: cups-browsed.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped cups-browsed.service - Make remote CUPS printers available locally. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Removed slice system-getty.slice - Slice /system/getty. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping avahi-daemon.service - Avahi mDNS/DNS-SD Stack... Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping cups.service - CUPS Scheduler... Jan 27 16:40:18 pi4xyzxyz systemd[1]: plymouth-quit-wait.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped plymouth-quit-wait.service - Hold until boot process finishes up. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping polkit.service - Authorization Manager... Jan 27 16:40:18 pi4xyzxyz systemd[1]: rc-local.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz avahi-daemon[564]: Got SIGTERM, quitting. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped rc-local.service - /etc/rc.local Compatibility. Jan 27 16:40:18 pi4xyzxyz avahi-daemon[564]: Leaving mDNS multicast group on interface eth1.IPv6 with address xyzxyzxyz. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped target network-online.target - Network is Online. Jan 27 16:40:18 pi4xyzxyz avahi-daemon[564]: Leaving mDNS multicast group on interface eth1.IPv4 with address 10.0.3.121. Jan 27 16:40:18 pi4xyzxyz systemd[1]: NetworkManager-wait-online.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz avahi-daemon[564]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped NetworkManager-wait-online.service - Network Manager Wait Online. Jan 27 16:40:18 pi4xyzxyz avahi-daemon[564]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Jan 27 16:40:18 pi4xyzxyz avahi-daemon[564]: avahi-daemon 0.8 exiting. Jan 27 16:40:18 pi4xyzxyz systemd[1]: avahi-daemon.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped avahi-daemon.service - Avahi mDNS/DNS-SD Stack. Jan 27 16:40:18 pi4xyzxyz systemd[1]: session-2.scope: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped session-2.scope - Session 2 of User pi. Jan 27 16:40:18 pi4xyzxyz systemd[1]: session-2.scope: Consumed 4min 13.353s CPU time. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping systemd-logind.service - User Login Management... Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping user@1000.service - User Manager for UID 1000... Jan 27 16:40:18 pi4xyzxyz systemd[1]: polkit.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped polkit.service - Authorization Manager. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Activating special unit exit.target... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped target default.target - Main User Target. Jan 27 16:40:18 pi4xyzxyz systemd[1]: polkit.service: Consumed 1.043s CPU time. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping dbus.service - D-Bus User Message Bus... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping dconf.service - User preferences database... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping gnome-keyring-daemon.service - GNOME Keyring daemon... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping gvfs-afc-volume-monitor.service - Virtual filesystem service - Apple File Conduit monitor... Jan 27 16:40:18 pi4xyzxyz org.freedesktop.secrets[4824]: discover_other_daemon: 1 Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping gvfs-daemon.service - Virtual filesystem service... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping gvfs-goa-volume-monitor.service - Virtual filesystem service - GNOME Online Accounts monitor... Jan 27 16:40:18 pi4xyzxyz systemd[1]: cups.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping gvfs-gphoto2-volume-monitor.service - Virtual filesystem service - digital camera monitor... Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped cups.service - CUPS Scheduler. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping gvfs-metadata.service - Virtual filesystem metadata service... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping gvfs-mtp-volume-monitor.service - Virtual filesystem service - Media Transfer Protocol monitor... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk device monitor... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping pipewire-pulse.service - PipeWire PulseAudio... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping xdg-desktop-portal.service - Portal service... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping xdg-document-portal.service - flatpak document portal service... Jan 27 16:40:18 pi4xyzxyz systemd-logind[600]: Removed session 3. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping xdg-permission-store.service - sandboxed app permission store... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped gvfs-afc-volume-monitor.service - Virtual filesystem service - Apple File Conduit monitor. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped pipewire-pulse.service - PipeWire PulseAudio. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped gnome-keyring-daemon.service - GNOME Keyring daemon. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped dconf.service - User preferences database. Jan 27 16:40:18 pi4xyzxyz systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Unmounted run-user-1000-gvfs.mount - /run/user/1000/gvfs. Jan 27 16:40:18 pi4xyzxyz systemd[1]: run-user-1000-doc.mount: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Unmounted run-user-1000-doc.mount - /run/user/1000/doc. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk device monitor. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped dbus.service - D-Bus User Message Bus. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped gvfs-gphoto2-volume-monitor.service - Virtual filesystem service - digital camera monitor. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped gvfs-goa-volume-monitor.service - Virtual filesystem service - GNOME Online Accounts monitor. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped gvfs-mtp-volume-monitor.service - Virtual filesystem service - Media Transfer Protocol monitor. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped xdg-desktop-portal.service - Portal service. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped xdg-document-portal.service - flatpak document portal service. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped xdg-permission-store.service - sandboxed app permission store. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped gvfs-metadata.service - Virtual filesystem metadata service. Jan 27 16:40:18 pi4xyzxyz systemd[1]: systemd-logind.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped gvfs-daemon.service - Virtual filesystem service. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped systemd-logind.service - User Login Management. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping wireplumber.service - Multimedia Service Session Manager... Jan 27 16:40:18 pi4xyzxyz wireplumber[990]: stopped by signal: Terminated Jan 27 16:40:18 pi4xyzxyz wireplumber[990]: disconnected from pipewire Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped wireplumber.service - Multimedia Service Session Manager. Jan 27 16:40:18 pi4xyzxyz systemd[793]: wireplumber.service: Consumed 8.445s CPU time. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopping pipewire.service - PipeWire Multimedia Service... Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped pipewire.service - PipeWire Multimedia Service. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Removed slice session.slice - User Core Session Slice. Jan 27 16:40:18 pi4xyzxyz systemd[793]: session.slice: Consumed 10.446s CPU time. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped target basic.target - Basic System. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped target paths.target - Paths. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped target sockets.target - Sockets. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Stopped target timers.target - Timers. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Closed dbus.socket - D-Bus User Message Bus Socket. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Closed dirmngr.socket - GnuPG network certificate management daemon. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Closed gcr-ssh-agent.socket - GCR ssh-agent wrapper. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Closed gnome-keyring-daemon.socket - GNOME Keyring daemon. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers). Jan 27 16:40:18 pi4xyzxyz systemd[793]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted). Jan 27 16:40:18 pi4xyzxyz systemd[793]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation). Jan 27 16:40:18 pi4xyzxyz systemd[793]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Closed pipewire-pulse.socket - PipeWire PulseAudio. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Closed pipewire.socket - PipeWire Multimedia System Socket. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Closed pk-debconf-helper.socket - debconf communication socket. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Removed slice app.slice - User Application Slice. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Reached target shutdown.target - Shutdown. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Finished systemd-exit.service - Exit the Session. Jan 27 16:40:18 pi4xyzxyz systemd[793]: Reached target exit.target - Exit the Session. Jan 27 16:40:18 pi4xyzxyz systemd[1]: user@1000.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped user@1000.service - User Manager for UID 1000. Jan 27 16:40:18 pi4xyzxyz systemd[1]: user@1000.service: Consumed 11.252s CPU time. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopping user-runtime-dir@1000.service - User Runtime Directory /run/user/1000... Jan 27 16:40:18 pi4xyzxyz systemd[1]: run-user-1000.mount: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Unmounted run-user-1000.mount - /run/user/1000. Jan 27 16:40:18 pi4xyzxyz systemd[1]: user-runtime-dir@1000.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped user-runtime-dir@1000.service - User Runtime Directory /run/user/1000. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Removed slice user-1000.slice - User Slice of UID 1000. Jan 27 16:40:18 pi4xyzxyz systemd[1]: user-1000.slice: Consumed 4min 24.958s CPU time. Jan 27 16:40:18 pi4xyzxyz systemd[1]: lightdm.service: Deactivated successfully. Jan 27 16:40:18 pi4xyzxyz systemd[1]: Stopped lightdm.service - Light Display Manager. Jan 27 16:40:18 pi4xyzxyz systemd[1]: lightdm.service: Consumed 1min 13.449s CPU time. Jan 27 16:40:19 pi4xyzxyz systemd[1]: Starting plymouth-poweroff.service - Show Plymouth Power Off Screen... Jan 27 16:40:19 pi4xyzxyz systemd[1]: Stopping systemd-user-sessions.service - Permit User Sessions... Jan 27 16:40:19 pi4xyzxyz systemd[1]: Received SIGRTMIN+20 from PID 78837 (plymouthd). Jan 27 16:40:19 pi4xyzxyz systemd[1]: systemd-user-sessions.service: Deactivated successfully. Jan 27 16:40:19 pi4xyzxyz systemd[1]: Stopped systemd-user-sessions.service - Permit User Sessions. Jan 27 16:40:19 pi4xyzxyz systemd[1]: Stopped target nss-user-lookup.target - User and Group Name Lookups. Jan 27 16:40:19 pi4xyzxyz systemd[1]: Stopped target remote-fs.target - Remote File Systems. Jan 27 16:40:19 pi4xyzxyz systemd[1]: Stopped target remote-fs-pre.target - Preparation for Remote File Systems. Jan 27 16:40:19 pi4xyzxyz systemd[1]: Stopped target nfs-client.target - NFS client services. Jan 27 16:40:19 pi4xyzxyz systemd[1]: Started plymouth-poweroff.service - Show Plymouth Power Off Screen. Jan 27 16:40:19 pi4xyzxyz systemd[1]: plymouth-switch-root-initramfs.service - Tell Plymouth To Jump To initramfs was skipped because of an unmet condition check (ConditionPathExists=/run/initramfs/bin/sh). Jan 27 16:40:19 pi4xyzxyz bash[781]: ================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped] Jan 27 16:40:19 pi4xyzxyz bash[781]: ================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging] Jan 27 16:40:19 pi4xyzxyz bash[781]: ================================== > LOG REDIRECT system.adapter.javascript.0 => false [Process stopped] Jan 27 16:40:19 pi4xyzxyz bash[781]: ================================== > LOG REDIRECT system.adapter.javascript.0 => false [system.adapter.javascript.0.logging] Jan 27 16:40:20 pi4xyzxyz systemd[1]: iobroker.service: Main process exited, code=exited, status=1/FAILURE Jan 27 16:40:20 pi4xyzxyz systemd[1]: iobroker.service: Failed with result 'exit-code'. Jan 27 16:40:20 pi4xyzxyz systemd[1]: Stopped iobroker.service - ioBroker Server. Jan 27 16:40:20 pi4xyzxyz systemd[1]: iobroker.service: Consumed 2min 12.992s CPU time. Jan 27 16:40:23 pi4xyzxyz sudo[78931]: pijuice : PWD=/var/lib/pijuice ; USER=root ; COMMAND=/bin/systemctl list-jobs Jan 27 16:40:23 pi4xyzxyz sudo[78931]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1002) Jan 27 16:40:23 pi4xyzxyz sudo[78931]: pam_unix(sudo:session): session closed for user root Jan 27 16:40:23 pi4xyzxyz systemd[1]: pijuice.service: Deactivated successfully. Jan 27 16:40:23 pi4xyzxyz systemd[1]: Stopped pijuice.service - PiJuice status service. Jan 27 16:40:23 pi4xyzxyz systemd[1]: pijuice.service: Consumed 2.288s CPU time. Jan 27 16:40:59 pi4xyzxyz systemd[1]: wayvnc.service: State 'stop-sigterm' timed out. Killing. Jan 27 16:40:59 pi4xyzxyz systemd[1]: wayvnc.service: Killing process 77762 (sh) with signal SIGKILL. Jan 27 16:40:59 pi4xyzxyz systemd[1]: wayvnc.service: Killing process 79619 (sleep) with signal SIGKILL. Jan 27 16:40:59 pi4xyzxyz systemd[1]: wayvnc.service: Failed with result 'exit-code'. Jan 27 16:40:59 pi4xyzxyz systemd[1]: Stopped wayvnc.service - VNC Server. Jan 27 16:40:59 pi4xyzxyz systemd[1]: wayvnc.service: Consumed 5.046s CPU time. Jan 27 16:40:59 pi4xyzxyz systemd[1]: Stopped target network.target - Network. Jan 27 16:40:59 pi4xyzxyz systemd[1]: Stopping NetworkManager.service - Network Manager... Jan 27 16:40:59 pi4xyzxyz NetworkManager[649]: <info> [1706370059.9180] caught SIGTERM, shutting down normally. Jan 27 16:40:59 pi4xyzxyz systemd[1]: Stopping networking.service - Raise network interfaces... Jan 27 16:40:59 pi4xyzxyz systemd[1]: Stopping wpa_supplicant.service - WPA supplicant... Jan 27 16:40:59 pi4xyzxyz wpa_supplicant[657]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all Jan 27 16:40:59 pi4xyzxyz NetworkManager[649]: <info> [1706370059.9464] dhcp4 (eth1): canceled DHCP transaction Jan 27 16:40:59 pi4xyzxyz NetworkManager[649]: <info> [1706370059.9465] dhcp4 (eth1): activation: beginning transaction (timeout in 45 seconds) Jan 27 16:40:59 pi4xyzxyz NetworkManager[649]: <info> [1706370059.9466] dhcp4 (eth1): state changed no lease Jan 27 16:40:59 pi4xyzxyz NetworkManager[649]: <info> [1706370059.9480] manager: NetworkManager state is now CONNECTED_SITE Jan 27 16:40:59 pi4xyzxyz NetworkManager[649]: <info> [1706370059.9493] device (wlan0): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed') Jan 27 16:40:59 pi4xyzxyz dbus-daemon[567]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=649 comm="/usr/sbin/NetworkManager --no-daemon") Jan 27 16:40:59 pi4xyzxyz dbus-daemon[567]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down. Jan 27 16:41:00 pi4xyzxyz wpa_supplicant[657]: p2p-dev-wlan0: CTRL-EVENT-DSCP-POLICY clear_all Jan 27 16:41:00 pi4xyzxyz wpa_supplicant[657]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0 Jan 27 16:41:00 pi4xyzxyz NetworkManager[649]: <info> [1706370060.4860] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'removed', sys-iface-state: 'removed') Jan 27 16:41:00 pi4xyzxyz dbus-daemon[567]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=649 comm="/usr/sbin/NetworkManager --no-daemon") Jan 27 16:41:00 pi4xyzxyz dbus-daemon[567]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down. Jan 27 16:41:00 pi4xyzxyz wpa_supplicant[657]: p2p-dev-wlan0: CTRL-EVENT-TERMINATING Jan 27 16:41:00 pi4xyzxyz wpa_supplicant[657]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all Jan 27 16:41:00 pi4xyzxyz NetworkManager[649]: <info> [1706370060.5104] exiting (success) Jan 27 16:41:00 pi4xyzxyz systemd[1]: networking.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped networking.service - Raise network interfaces. Jan 27 16:41:00 pi4xyzxyz systemd[1]: NetworkManager.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped NetworkManager.service - Network Manager. Jan 27 16:41:00 pi4xyzxyz systemd[1]: NetworkManager.service: Consumed 2.106s CPU time. Jan 27 16:41:00 pi4xyzxyz wpa_supplicant[657]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all Jan 27 16:41:00 pi4xyzxyz wpa_supplicant[657]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Jan 27 16:41:00 pi4xyzxyz wpa_supplicant[657]: wlan0: CTRL-EVENT-TERMINATING Jan 27 16:41:00 pi4xyzxyz systemd[1]: wpa_supplicant.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped wpa_supplicant.service - WPA supplicant. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopping dbus.service - D-Bus System Message Bus... Jan 27 16:41:00 pi4xyzxyz systemd[1]: dbus.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped dbus.service - D-Bus System Message Bus. Jan 27 16:41:00 pi4xyzxyz systemd[1]: dbus.service: Consumed 2.398s CPU time. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped target basic.target - Basic System. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-ask-password-plymouth.path: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped target paths.target - Path Units. Jan 27 16:41:00 pi4xyzxyz systemd[1]: cups.path: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped cups.path - CUPS Scheduler. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped target slices.target - Slice Units. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Removed slice user.slice - User and Session Slice. Jan 27 16:41:00 pi4xyzxyz systemd[1]: user.slice: Consumed 4min 24.958s CPU time. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped target sockets.target - Socket Units. Jan 27 16:41:00 pi4xyzxyz systemd[1]: avahi-daemon.socket: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Closed avahi-daemon.socket - Avahi mDNS/DNS-SD Stack Activation Socket. Jan 27 16:41:00 pi4xyzxyz systemd[1]: cups.socket: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Closed cups.socket - CUPS Scheduler. Jan 27 16:41:00 pi4xyzxyz systemd[1]: dbus.socket: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Closed dbus.socket - D-Bus System Message Bus Socket. Jan 27 16:41:00 pi4xyzxyz systemd[1]: triggerhappy.socket: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Closed triggerhappy.socket. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped target sysinit.target - System Initialization. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped target cryptsetup.target - Local Encrypted Volumes. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-ask-password-wall.path: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped target integritysetup.target - Local Integrity Protected Volumes. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped target swap.target - Swaps. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped target veritysetup.target - Local Verity Protected Volumes. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopping fake-hwclock.service - Restore / save the current clock... Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopping systemd-binfmt.service - Set Up Additional Binary Formats... Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-sysctl.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-sysctl.service - Apply Kernel Variables. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-modules-load.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-modules-load.service - Load Kernel Modules. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopping systemd-timesyncd.service - Network Time Synchronization... Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopping systemd-update-utmp.service - Record System Boot/Shutdown in UTMP... Jan 27 16:41:00 pi4xyzxyz systemd[1]: run-credentials-systemd\x2dsysctl.service.mount: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Unmounted run-credentials-systemd\x2dsysctl.service.mount - /run/credentials/systemd-sysctl.service. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-timesyncd.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-timesyncd.service - Network Time Synchronization. Jan 27 16:41:00 pi4xyzxyz systemd[1]: fake-hwclock.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped fake-hwclock.service - Restore / save the current clock. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-binfmt.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-binfmt.service - Set Up Additional Binary Formats. Jan 27 16:41:00 pi4xyzxyz systemd[1]: proc-sys-fs-binfmt_misc.automount: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Unset automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point. Jan 27 16:41:00 pi4xyzxyz systemd[1]: proc-sys-fs-binfmt_misc.mount: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-update-utmp.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-update-utmp.service - Record System Boot/Shutdown in UTMP. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-tmpfiles-setup.service - Create Volatile Files and Directories. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped target local-fs.target - Local File Systems. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Unmounting boot-firmware.mount - /boot/firmware... Jan 27 16:41:00 pi4xyzxyz systemd[1]: Unmounting run-credentials-systemd\x2dsysusers.service.mount - /run/credentials/systemd-sysusers.service... Jan 27 16:41:00 pi4xyzxyz systemd[1]: Unmounting run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount - /run/credentials/systemd-tmpfiles-setup.service... Jan 27 16:41:00 pi4xyzxyz systemd[1]: Unmounting run-credentials-systemd\x2dtmpfiles\x2dsetup\x2ddev.service.mount - /run/credentials/systemd-tmpfiles-setup-dev.service... Jan 27 16:41:00 pi4xyzxyz umount[79646]: umount: /run/credentials/systemd-tmpfiles-setup.service: no mount point specified. Jan 27 16:41:00 pi4xyzxyz systemd[1]: run-credentials-systemd\x2dsysusers.service.mount: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Unmounted run-credentials-systemd\x2dsysusers.service.mount - /run/credentials/systemd-sysusers.service. Jan 27 16:41:00 pi4xyzxyz systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Mount process exited, code=exited, status=32/n/a Jan 27 16:41:00 pi4xyzxyz systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Failed with result 'exit-code'. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Unmounted run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount - /run/credentials/systemd-tmpfiles-setup.service. Jan 27 16:41:00 pi4xyzxyz systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup\x2ddev.service.mount: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Unmounted run-credentials-systemd\x2dtmpfiles\x2dsetup\x2ddev.service.mount - /run/credentials/systemd-tmpfiles-setup-dev.service. Jan 27 16:41:00 pi4xyzxyz systemd[1]: boot-firmware.mount: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Unmounted boot-firmware.mount - /boot/firmware. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Reached target umount.target - Unmount All Filesystems. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-fsck@dev-disk-by\x2dpartuuid-870ea24b\x2d01.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-fsck@dev-disk-by\x2dpartuuid-870ea24b\x2d01.service - File System Check on /dev/disk/by-partuuid/870ea24b-01. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Removed slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped target local-fs-pre.target - Preparation for Local File Systems. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-sysusers.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-sysusers.service - Create System Users. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-remount-fs.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Stopped systemd-remount-fs.service - Remount Root and Kernel File Systems. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Reached target shutdown.target - System Shutdown. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Reached target final.target - Late Shutdown Services. Jan 27 16:41:00 pi4xyzxyz systemd[1]: systemd-poweroff.service: Deactivated successfully. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Finished systemd-poweroff.service - System Power Off. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Reached target poweroff.target - System Power Off. Jan 27 16:41:00 pi4xyzxyz systemd[1]: Shutting down. Jan 27 16:41:00 pi4xyzxyz systemd-shutdown[1]: Syncing filesystems and block devices. Jan 27 16:41:00 pi4xyzxyz systemd-shutdown[1]: Sending SIGTERM to remaining processes... Jan 27 16:41:00 pi4xyzxyz systemd-journald[278]: Received SIGTERM from PID 1 (systemd-shutdow). Jan 27 16:41:00 pi4xyzxyz systemd-journald[278]: Journal stopped -- Boot 4d19456ddcxyzxyz89f4697fc7969ac0 -- Jan 27 16:41:00 pi4xyzxyz kernel: Booting Linux on physical CPU 0x0000000000 [0x410fd083] Jan 27 16:41:00 pi4xyzxyz kernel: Linux version 6.1.0-rpi7-rpi-v8 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) Jan 27 16:41:00 pi4xyzxyz kernel: random: crng init done Jan 27 16:41:00 pi4xyzxyz kernel: Machine model: Raspberry Pi 4 Model B Rev 1.5 Jan 27 16:41:00 pi4xyzxyz kernel: efi: UEFI not found. Jan 27 16:41:00 pi4xyzxyz kernel: Reserved memory: created CMA memory pool at 0x000000000dc00000, size 512 MiB Jan 27 16:41:00 pi4xyzxyz kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool -
(EDIT - in the end its not about IOB , its more about how logs are timestamped short time after boot)
Trying to setup HW configuration where also the loss of power will be reasonably safe to the SSD. When testing behavior of different ways of the shutdown and of the restarting I was really surprised when noted in the IOB log, that after shutdown the IOB firstly terminated everything (as I expected) however then roughly 1 minute after sigterm IOB started again. (doesnt matter whether the shutdown was made through GUI or by sudo shutdown, sudo shutdown -P).Im totally confused because I expected that ca 1 minute or more after shutdown the CPU does not work at all and no one application runs so that I can safely remove the power from the board. However in the log I see that it is not true.
Please see following section of the IOB log:
- At ca 16:40:18 I performed "sudo shutdown -P"
- At ca 16:41:01 I saw last blink of the SSD and the "power" was shut down (not really the power source but the GPIO PINS e.t.c. went into undefined state)
- At 16:42:36 I made a restart through GPIO3 pin
2024-01-27 16:40:18.328 - info: backitup.0 (2040) cleaned everything up... 2024-01-27 16:40:18.321 - info: host.pi4IobPnl received SIGTERM 2024-01-27 16:40:18.324 - info: admin.0 (1529) terminating http server on port 8081 2024-01-27 16:40:18.352 - info: host.pi4IobPnl stopInstance system.adapter.admin.0 (force=false, process=true) 2024-01-27 16:40:18.390 - info: host.pi4IobPnl stopInstance system.adapter.javascript.0 (force=false, process=true) 2024-01-27 16:40:18.399 - info: host.pi4IobPnl stopInstance system.adapter.history.0 (force=false, process=false) 2024-01-27 16:40:18.400 - info: host.pi4IobPnl stopInstance system.adapter.discovery.0 (force=false, process=true) 2024-01-27 16:40:18.420 - info: host.pi4IobPnl stopInstance system.adapter.backitup.0 (force=false, process=true) 2024-01-27 16:40:18.421 - info: host.pi4IobPnl stopInstance system.adapter.ebus.0 (force=false, process=false) 2024-01-27 16:40:18.422 - info: host.pi4IobPnl stopInstance system.adapter.valuetrackerovertime.0 (force=false, process=false) 2024-01-27 16:40:18.494 - info: javascript.0 (1806) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.501 - info: discovery.0 (1921) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.498 - info: admin.0 (1529) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.509 - info: discovery.0 (1921) terminating 2024-01-27 16:40:18.508 - info: backitup.0 (2040) Got terminate signal TERMINATE_YOURSELF 2024-01-27 16:40:18.512 - info: discovery.0 (1921) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.531 - info: javascript.0 (1806) terminating 2024-01-27 16:40:18.536 - info: backitup.0 (2040) terminating 2024-01-27 16:40:18.541 - info: host.pi4IobPnl stopInstance system.adapter.admin.0 send kill signal 2024-01-27 16:40:18.547 - info: admin.0 (1529) terminating 2024-01-27 16:40:18.548 - info: host.pi4IobPnl stopInstance system.adapter.javascript.0 send kill signal 2024-01-27 16:40:18.549 - info: host.pi4IobPnl stopInstance system.adapter.discovery.0 send kill signal 2024-01-27 16:40:18.554 - info: host.pi4IobPnl stopInstance system.adapter.backitup.0 send kill signal 2024-01-27 16:40:18.551 - info: javascript.0 (1806) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.550 - info: backitup.0 (2040) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.553 - info: admin.0 (1529) Terminated (NO_ERROR): Without reason 2024-01-27 16:40:18.836 - info: discovery.0 (1921) terminating 2024-01-27 16:40:18.836 - info: javascript.0 (1806) terminating 2024-01-27 16:40:18.848 - info: backitup.0 (2040) terminating 2024-01-27 16:40:18.869 - info: admin.0 (1529) terminating 2024-01-27 16:40:19.228 - info: host.pi4IobPnl instance system.adapter.discovery.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.266 - info: host.pi4IobPnl instance system.adapter.backitup.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.281 - info: host.pi4IobPnl instance system.adapter.admin.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.321 - info: host.pi4IobPnl instance system.adapter.javascript.0 terminated with code 0 (NO_ERROR) 2024-01-27 16:40:19.322 - info: host.pi4IobPnl All instances are stopped. 2024-01-27 16:40:19.505 - info: host.pi4IobPnl terminated 2024-01-27 16:41:15.975 - info: host.pi4IobPnl iobroker.js-controller version 5.0.17 js-controller starting 2024-01-27 16:41:15.984 - info: host.pi4IobPnl Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-01-27 16:41:15.985 - info: host.pi4IobPnl hostname: pi4IobPnl, node: v18.19.0 2024-01-27 16:41:15.986 - info: host.pi4IobPnl ip addresses: 10.0.3.121 fe80::c9b8:7f3d:e204:7d2f 2024-01-27 16:41:17.956 - info: host.pi4IobPnl connected to Objects and States 2024-01-27 16:41:18.003 - info: host.pi4IobPnl added notifications configuration of host 2024-01-27 16:41:19.138 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.nodeCurrent" 2024-01-27 16:41:19.144 - info: host.pi4IobPnl 7 instances found 2024-01-27 16:41:19.172 - info: host.pi4IobPnl starting 4 instances 2024-01-27 16:41:19.325 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.nodeNewest" 2024-01-27 16:41:19.339 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.nodeNewestNext" 2024-01-27 16:41:19.351 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.npmCurrent" 2024-01-27 16:41:19.370 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.npmNewest" 2024-01-27 16:41:19.393 - info: host.pi4IobPnl instance system.adapter.admin.0 started with pid 1502 2024-01-27 16:41:19.411 - info: host.pi4IobPnl Delete state "system.host.pi4IobPnl.versions.npmNewestNext" 2024-01-27 16:41:19.470 - info: host.pi4IobPnl Some obsolete host states deleted. 2024-01-27 16:41:23.248 - info: host.pi4IobPnl instance system.adapter.javascript.0 started with pid 1790 2024-01-27 16:41:25.189 - info: admin.0 (1502) starting. Version 6.12.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:25.261 - info: admin.0 (1502) requesting all objects 2024-01-27 16:41:26.091 - info: admin.0 (1502) received all objects 2024-01-27 16:41:26.908 - info: admin.0 (1502) Request actual repository... 2024-01-27 16:41:27.072 - info: admin.0 (1502) socket.io server listening on port 8081 2024-01-27 16:41:27.083 - info: admin.0 (1502) http server listening on port 8081 2024-01-27 16:41:27.084 - info: admin.0 (1502) Use link "http://127.0.0.1:8081" to configure. 2024-01-27 16:41:27.508 - info: host.pi4IobPnl Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2024-01-27 16:41:27.563 - info: host.pi4IobPnl instance system.adapter.discovery.0 started with pid 2180 2024-01-27 16:41:29.324 - info: javascript.0 (1790) starting. Version 7.1.6 in /opt/iobroker/node_modules/iobroker.javascript, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:29.867 - info: javascript.0 (1790) requesting all states 2024-01-27 16:41:29.870 - info: javascript.0 (1790) requesting all objects 2024-01-27 16:41:30.189 - info: javascript.0 (1790) received all states 2024-01-27 16:41:30.403 - info: javascript.0 (1790) received all objects 2024-01-27 16:41:31.226 - info: host.pi4IobPnl instance system.adapter.backitup.0 started with pid 2392 2024-01-27 16:41:31.258 - info: discovery.0 (2180) starting. Version 4.2.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:32.354 - info: admin.0 (1502) Repository received successfully. 2024-01-27 16:41:34.198 - info: backitup.0 (2392) starting. Version 2.9.8 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.19.0, js-controller: 5.0.17 2024-01-27 16:41:34.312 - info: backitup.0 (2392) [iobroker] backup will be activated at 02:48 every 1 day(s) 2024-01-27 16:45:17.316 - info: admin.0 (1502) failed connection to socket.io from ::ffff:10.0.3.121: Passport was not initialized 2024-01-27 16:45:45.067 - info: admin.0 (1502) ==> Connected system.user.admin from ::ffff:10.0.3.121In the log I can see that within ca 1sec the IOB succesfuly terminated itself (16:40:19.505). However within no more than 1 minute the IOB started again (16:41:15.975) and finished its preparation within some 15 seconds (16:41:34.312) which was still ca 1 minute before I woke-up theRPI through GPIO3. After my restarting of the RPI the IOB only waited for me to log-in to the admin webpage.
Is this behaviour during the HALT state normal?
(Note - I firstly discovered this having the PiJuice Hat installed. This hat provides a battery backup. However even after taking the hat down the RPI behaves this strange way. And the log is from using the RPI without the hat)
RPI 4B 8GB, fresh installation of Bookworm,
fresh installation of IOBroker v. 6.12.0
Node.js: v18.19.0
NPM: 10.2.3
js-controller: 5.0.17
only few basic adapters installed
Instead of SD card Im using SSD connected through Axagon adapter to USB.@cjoe Well it might be simple - probably the RPI shuts down fully like expected hower after a boot the internal clock takes its time from some of the logs because it has no info about present time from the web yet. Then in the logs the wrong time continues to be recorded until the RPI is able contacting a time server and synchronize its clock. At this moment the time recorded in the logs skips few minutes and now continues to be recorded properly:
Jan 27 16:41:25 pi4xyzxyz systemd[1]: Started colord.service - Manage, Install and Generate Color Profiles. Jan 27 16:41:27 pi4xyzxyz bash[793]: Send diag info: {"uuid":"xyzxyzxyz","language":"en","country":"xyzxyz","hosts":[{"version":"5.0.17","platform":"Javascript/Node.js","type":"linux"}],"node":"v18.19.0","arch":"arm64","docker":false,"adapters":{"admin":{"version":"6.12.0","platform":"Javascript/Node.js"},"discovery":{"version":"4.2.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.9.8","platform":"Javascript/Node.js"},"ebus":{"version":"3.2.4","platform":"Javascript/Node.js"},"javascript":{"version":"7.1.6","platform":"Javascript/Node.js"},"valuetrackerovertime":{"version":"1.0.1","platform":"Javascript/Node.js"},"history":{"version":"3.0.1","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":7,"compactMode":false,"noCompactInstances":0,"model":"Cortex-A72","cpus":4,"mem":8189632512,"ostype":"Linux","city":"xyz"} Jan 27 16:41:28 pi4xyzxyz PackageKit[1734]: refresh-cache transaction /100_ecddaada from uid 1000 finished with success after 6882ms Jan 27 16:41:33 pi4xyzxyz systemd[1]: systemd-fsckd.service: Deactivated successfully. Jan 27 16:43:23 pi4xyzxyz systemd-timesyncd[529]: Contacted time server 77.48.28.248:123 (2.debian.pool.ntp.org). Jan 27 16:43:23 pi4xyzxyz systemd-timesyncd[529]: Initial clock synchronization to Sat 2024-01-27 16:43:23.331684 CET. Jan 27 16:43:25 pi4xyzxyz PackageKit[1734]: get-updates transaction /101_dceeaaea from uid 1000 finished with success after 7737ms Jan 27 16:43:25 pi4xyzxyz systemd[1]: systemd-hostnamed.service: Deactivated successfully. Jan 27 16:43:27 pi4xyzxyz sudo[1333]: pam_unix(sudo:session): session closed for user pijuice Jan 27 16:43:29 pi4xyzxyz vncserver-x11[816]: Connections: disconnected: 10.0.3.115::64218 (TCP) ([ViewerClosed] VNC Viewer closed) Jan 27 16:43:29 pi4xyzxyz vncserver-x11[816]: session ended: user pi Jan 27 16:44:27 pi4xyzxyz vncserver-x11[816]: Connections: connected: 10.0.3.115::64220 (TCP) -
@cjoe Well it might be simple - probably the RPI shuts down fully like expected hower after a boot the internal clock takes its time from some of the logs because it has no info about present time from the web yet. Then in the logs the wrong time continues to be recorded until the RPI is able contacting a time server and synchronize its clock. At this moment the time recorded in the logs skips few minutes and now continues to be recorded properly:
Jan 27 16:41:25 pi4xyzxyz systemd[1]: Started colord.service - Manage, Install and Generate Color Profiles. Jan 27 16:41:27 pi4xyzxyz bash[793]: Send diag info: {"uuid":"xyzxyzxyz","language":"en","country":"xyzxyz","hosts":[{"version":"5.0.17","platform":"Javascript/Node.js","type":"linux"}],"node":"v18.19.0","arch":"arm64","docker":false,"adapters":{"admin":{"version":"6.12.0","platform":"Javascript/Node.js"},"discovery":{"version":"4.2.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.9.8","platform":"Javascript/Node.js"},"ebus":{"version":"3.2.4","platform":"Javascript/Node.js"},"javascript":{"version":"7.1.6","platform":"Javascript/Node.js"},"valuetrackerovertime":{"version":"1.0.1","platform":"Javascript/Node.js"},"history":{"version":"3.0.1","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":7,"compactMode":false,"noCompactInstances":0,"model":"Cortex-A72","cpus":4,"mem":8189632512,"ostype":"Linux","city":"xyz"} Jan 27 16:41:28 pi4xyzxyz PackageKit[1734]: refresh-cache transaction /100_ecddaada from uid 1000 finished with success after 6882ms Jan 27 16:41:33 pi4xyzxyz systemd[1]: systemd-fsckd.service: Deactivated successfully. Jan 27 16:43:23 pi4xyzxyz systemd-timesyncd[529]: Contacted time server 77.48.28.248:123 (2.debian.pool.ntp.org). Jan 27 16:43:23 pi4xyzxyz systemd-timesyncd[529]: Initial clock synchronization to Sat 2024-01-27 16:43:23.331684 CET. Jan 27 16:43:25 pi4xyzxyz PackageKit[1734]: get-updates transaction /101_dceeaaea from uid 1000 finished with success after 7737ms Jan 27 16:43:25 pi4xyzxyz systemd[1]: systemd-hostnamed.service: Deactivated successfully. Jan 27 16:43:27 pi4xyzxyz sudo[1333]: pam_unix(sudo:session): session closed for user pijuice Jan 27 16:43:29 pi4xyzxyz vncserver-x11[816]: Connections: disconnected: 10.0.3.115::64218 (TCP) ([ViewerClosed] VNC Viewer closed) Jan 27 16:43:29 pi4xyzxyz vncserver-x11[816]: session ended: user pi Jan 27 16:44:27 pi4xyzxyz vncserver-x11[816]: Connections: connected: 10.0.3.115::64220 (TCP)Yes, would also consider this as no problem. Your system clearly rebooted according to journal.
-
Yes, would also consider this as no problem. Your system clearly rebooted according to journal.
@iobnordlicht said in Question - Halt state and IOB behaviour:
Yes, would also consider this as no problem. Your system clearly rebooted according to journal.
Thank you for confirmation.
My concern wasn't about proper rebooting but more about proper shutdown and to be sure when I can switch-off the power supply safely.
Now I learned that I cannot trust the time values in any log until the RPI synchronizes its clock from web (or from RTC). Or more exactly that if I need to know exactly what when happened around boot I must correct the time data after boot till the moment of clock synchronization by simply adding the difference.Shall I delete this my topic? Or shall I rename it ? Please suggest
-
@iobnordlicht said in Question - Halt state and IOB behaviour:
Yes, would also consider this as no problem. Your system clearly rebooted according to journal.
Thank you for confirmation.
My concern wasn't about proper rebooting but more about proper shutdown and to be sure when I can switch-off the power supply safely.
Now I learned that I cannot trust the time values in any log until the RPI synchronizes its clock from web (or from RTC). Or more exactly that if I need to know exactly what when happened around boot I must correct the time data after boot till the moment of clock synchronization by simply adding the difference.Shall I delete this my topic? Or shall I rename it ? Please suggest
@cjoe Keep it for the next... me personally, I would add [solved] to the title, whatever suites you... :spock-hand:
Support us
786
Online32.5k
Benutzer81.6k
Themen1.3m
Beiträge