Arch Linux

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Random Reboot....why?

I have a music streamer, a Salkstream III running Arch Linux OS v 6.18.7 (running "headless").  The only thing I use it for is running Roon Server.  I leave it powered on all the time unless I need to shut down or reboot for a particular reason.  I've not had any issues while using the music streamer.

Recently, I noticed it rebooted randomly, then did it again several days later.  Both times the streamer wasn't being used.  After some research (I'm a complete newbie at Linux), I found how to see the logs leading up to the reboot by running  journalctl -b -1 -r.  I cannot tell if something in the log tells me why it is rebooting itself (I don't understand most of it).

I hope I'm not asking too much for someone to look through this log to see if it explains why my streamer is rebooting itself.  BTW, my apologies if I'm not posting the log correctly on the forum.  I tried googling how to correctly post a log, but I don't understand the instructions.  If there is something else I should post, please let me know (with exact newbie instructions how to do so).

PS - I did some research, and if I understand correctly, the "...Unknown udp packet received from 192.168.50.12:62096..." error is being caused by one of our iPads and isn't unusual and shouldn't cause problems (at least according to Google, lol).

Thanks!

Feb 14 15:41:49 splayer systemd-logind[367]: System is rebooting.
Feb 14 15:41:49 splayer systemd-logind[367]: The system will reboot now!
Feb 14 15:41:49 splayer systemd[1]: Started Authorization Manager.
Feb 14 15:41:49 splayer polkitd[515038]: Started polkitd version 127
Feb 14 15:41:49 splayer systemd[1]: Starting Authorization Manager...
Feb 14 15:35:09 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 15:25:08 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 15:15:07 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 15:05:06 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 14:55:05 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 14:45:04 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 14:35:03 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 14:25:02 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 14:15:01 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 14:05:00 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 13:54:59 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 13:44:57 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 13:34:56 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 13:24:55 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 13:14:54 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 13:04:53 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 12:54:52 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 12:44:51 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 12:34:50 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 12:24:49 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 12:14:48 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 12:04:47 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 11:54:46 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 11:44:45 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 11:44:11 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:62096
Feb 14 11:44:11 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:55543
Feb 14 11:39:21 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:50536
Feb 14 11:39:21 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:52402
Feb 14 11:34:44 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 11:24:43 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 11:14:41 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 11:04:40 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 10:54:39 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 10:44:38 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 10:34:37 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 10:32:56 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:56094
Feb 14 10:32:55 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:61344
Feb 14 10:24:36 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 10:14:35 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 10:06:20 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:53375
Feb 14 10:06:20 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:64269
Feb 14 10:04:34 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 09:54:33 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 09:44:32 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 09:43:12 splayer systemd[1]: Finished Daily man-db regeneration.
Feb 14 09:43:12 splayer systemd[1]: man-db.service: Deactivated successfully.
Feb 14 09:43:08 splayer systemd[1]: Starting Daily man-db regeneration...
Feb 14 09:43:08 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 09:39:22 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 09:34:31 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 09:24:30 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 09:14:29 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 09:04:28 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 08:54:27 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 08:44:26 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 08:34:25 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 08:24:24 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 08:14:23 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 08:04:22 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 07:54:20 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 07:44:19 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 07:34:18 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 07:24:17 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 07:14:16 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 07:09:02 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:62158
Feb 14 07:09:02 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:61168
Feb 14 07:04:15 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 07:01:21 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:52802
Feb 14 07:01:21 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:60143
Feb 14 06:54:14 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 06:44:13 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 06:34:12 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 06:24:11 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 06:14:10 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 06:05:29 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:57616
Feb 14 06:05:29 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:59990
Feb 14 06:04:09 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 06:00:25 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:56117
Feb 14 06:00:25 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:60694
Feb 14 06:00:23 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:62340
Feb 14 06:00:23 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:54409
Feb 14 05:57:44 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:53297
Feb 14 05:57:44 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:65495
Feb 14 05:54:08 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 05:51:25 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:54787
Feb 14 05:51:25 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:65440
Feb 14 05:44:07 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 05:35:08 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:59231
Feb 14 05:35:08 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:60749
Feb 14 05:34:06 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 05:24:05 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 05:14:04 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 05:04:03 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:54:02 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:44:01 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:38:26 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:62603
Feb 14 04:38:26 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:52831
Feb 14 04:33:59 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:23:58 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:13:57 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:03:56 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:53:55 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:43:54 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:33:53 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:23:52 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:13:51 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:03:50 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:53:49 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:43:48 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:33:47 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:23:46 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:13:45 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:03:44 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:53:42 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:43:41 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:33:40 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:23:39 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:13:38 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:03:37 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:53:36 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:43:35 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:35:12 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 00:34:39 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 00:33:34 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:30:22 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 00:27:42 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 00:23:56 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 00:23:34 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:14:27 splayer systemd[1]: Finished Rotate log files.
Feb 14 00:14:27 splayer systemd[1]: logrotate.service: Deactivated successfully.
Feb 14 00:14:27 splayer systemd[1]: Starting Rotate log files...
Feb 14 00:13:33 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:03:32 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:00:07 splayer systemd[1]: shadow.service: Deactivated successfully.
Feb 14 00:00:07 splayer systemd[1]: Started Verify integrity of password and group files.
Feb 13 23:59:48 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 13 23:53:31 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 23:49:04 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 13 23:46:23 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 13 23:43:29 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 23:33:28 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 23:32:57 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 13 23:30:49 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 13 23:23:27 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 23:16:52 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 13 23:13:26 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 23:03:25 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 22:53:49 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 13 22:53:24 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 22:53:17 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 13 22:43:23 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 22:33:22 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 22:28:38 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 13 22:23:21 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 22:13:20 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 22:03:19 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 21:53:18 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 21:43:17 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 21:33:16 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 21:23:15 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 21:13:14 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 21:03:13 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 20:53:12 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 20:43:11 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 20:33:09 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 20:23:08 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 20:13:07 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 20:03:06 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 19:53:05 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 19:51:05 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:62544
Feb 13 19:51:04 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:54904
Feb 13 19:43:04 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 19:33:03 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 19:23:02 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 19:13:01 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 19:03:00 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 18:52:59 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 18:42:58 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 18:32:57 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 13 18:30:06 splayer systemd[1]: Finished Cleanup of Temporary Directories.
Feb 13 18:30:06 splayer systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Feb 13 18:30:05 splayer systemd[1]: Starting Cleanup of Temporary Directories...
Feb 14 06:44:13 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 06:34:12 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 06:24:11 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 06:14:10 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 06:05:29 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:57616
Feb 14 06:05:29 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:59990
Feb 14 06:04:09 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 06:00:25 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:56117
Feb 14 06:00:25 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:60694
Feb 14 06:00:23 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:62340
Feb 14 06:00:23 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:54409
Feb 14 05:57:44 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:53297
Feb 14 05:57:44 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:65495
Feb 14 05:54:08 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 05:51:25 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:54787
Feb 14 05:51:25 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:65440
Feb 14 05:44:07 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 05:35:08 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:59231
Feb 14 05:35:08 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:60749
Feb 14 05:34:06 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 05:24:05 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 05:14:04 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 05:04:03 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:54:02 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:44:01 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:38:26 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:62603
Feb 14 04:38:26 splayer minidlnad[605]: minissdp.c:773: warn: Unknown udp packet received from 192.168.50.12:52831
Feb 14 04:33:59 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:23:58 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:13:57 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 04:03:56 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:53:55 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:43:54 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:33:53 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:23:52 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:13:51 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 03:03:50 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:53:49 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:43:48 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:33:47 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:23:46 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:13:45 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 02:03:44 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:53:42 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:43:41 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:33:40 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:23:39 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:13:38 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 01:03:37 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:53:36 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:43:35 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:35:12 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 00:34:39 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 00:33:34 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:30:22 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 00:27:42 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 00:23:56 splayer systemd-resolved[281]: Clock change detected. Flushing caches.
Feb 14 00:23:34 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:14:27 splayer systemd[1]: Finished Rotate log files.
Feb 14 00:14:27 splayer systemd[1]: logrotate.service: Deactivated successfully.
Feb 14 00:14:27 splayer systemd[1]: Starting Rotate log files...
Feb 14 00:13:33 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:03:32 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 00:00:07 splayer systemd[1]: shadow.service: Deactivated successfully.

Last edited by Saturn94 (2026-02-15 01:41:17)

schard

Forum Moderator

From: Hannover

Registered: 2016-05-06

Posts: 2,521

Website

Re: Random Reboot....why?

Mod note: Please use Code-Tags to format code snippets and log output. Please edit your post in this regard.

---

Inofficial first vice president of the Rust Evangelism Strike Force

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

Mod note: Please use Code-Tags to format code snippets and log output. Please edit your post in this regard.

EDIT:  I didn't know what you meant, so tried to look it up.  Did I edit my post correctly?  I'm doing my best as a complete newbie.

Last edited by Saturn94 (2026-02-15 01:43:52)

loqs

Member

Registered: 2014-03-06

Posts: 18,781

Re: Random Reboot....why?

On the reboot issue nothing in the journal output you have posted indicates the system is going to reboot.  The next place to look normally would be a QR code on the display but that is not available on your headless system.  What kernel is the system running?  I mean linux, linux-zen, linux-hardened etc.?

Last edited by loqs (2026-02-15 01:44:21)

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

On the reboot issue nothing in the journal output you have posted indicates the system is going to reboot.  The next place to look normally would be a QR code on the display but that is not available on your headless system.  What kernel is the system running?  I mean linux, linux-zen, linux-hardened etc.?

Is this what you mean?

6.18.7-arch1-1

I'm having to look up what command lines to type to find this information.  I came across this as well;

Linux version 6.18.7-arch1-1 (linux@archlinux) (gcc (GCC) 15.2.1 20260103, GNU ld (GNU Binutils) 2.45.1) #1 SMP PREEMPT_DYNAMIC Sat, 24 Jan 2026 00:47:39 +0000

Does any of this help?  If there is a different command line I should be using to find the info you are looking for, please let me know.

Last edited by Saturn94 (2026-02-15 01:53:18)

loqs

Member

Registered: 2014-03-06

Posts: 18,781

Re: Random Reboot....why?

Linux version 6.18.7-arch1-1 (linux@archlinux) (gcc (GCC) 15.2.1 20260103, GNU ld (GNU Binutils) 2.45.1) #1 SMP PREEMPT_DYNAMIC Sat, 24 Jan 2026 00:47:39 +0000

Is Arch's standard linux kernel from the linux package although it is a bit out of data. I was wondering if you were running linux-hardened which will reboot on issues that linux will only warn about. Can you reproduce the issue with the latest kernel 6.18.9.arch1-2?

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

Linux version 6.18.7-arch1-1 (linux@archlinux) (gcc (GCC) 15.2.1 20260103, GNU ld (GNU Binutils) 2.45.1) #1 SMP PREEMPT_DYNAMIC Sat, 24 Jan 2026 00:47:39 +0000

Is Arch's standard linux kernel from the linux package although it is a bit out of data. I was wondering if you were running linux-hardened which will reboot on issues that linux will only warn about. Can you reproduce the issue with the latest kernel 6.18.9.arch1-2?

Does the kernel not get updated when I update the OS?  I last updated the OS Feb 6, 2026 using the command "pacman -Syu".  Is there something else I should be doing to update the kernel (btw, I have no idea what a kernel is, lol).

BTW, I am unable to force the issue to occur.  It has just happened on its own twice since Feb 6th without any interaction from me.  I wasn't using the streamer at the time though it is aways powered on.

It's entirely possible this has been happening for some time and I've never noticed.  On Feb 6th, I just happened to be sitting next to one of my Roon's endpoints and noticed it lost connection temporarily with Roon.  Looking into possible causes led me to the discovery that Archlinux was rebooting on its own.

Last edited by Saturn94 (2026-02-15 02:12:21)

loqs

Member

Registered: 2014-03-06

Posts: 18,781

Re: Random Reboot....why?

Does the kernel not get updated when I update the OS?  I last updated the OS Feb 6, 2026 using the command "pacman -Syu".

Yes and no. On your system the kernel is provided by the linux package.  The linux package itself will be updated by `pacman -Syu` provided the mirror it was being updated from was up to date.  What is the output of `pacman -Q linux`?  With the kernel there is an additional step it needs to be copied to where ever your system's boot mechanism expects to find it commonly under /boot.  This should happen automatically but it depends on the system being configured correctly.

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

Does the kernel not get updated when I update the OS?  I last updated the OS Feb 6, 2026 using the command "pacman -Syu".

Yes and no. On your system the kernel is provided by the linux package.  The linux package itself will be updated by `pacman -Syu` provided the mirror it was being updated from was up to date.  What is the output of `pacman -Q linux`?  With the kernel there is an additional step it needs to be copied to where ever your system's boot mechanism expects to find it commonly under /boot.  This should happen automatically but it depends on the system being configured correctly.

If it matters, I do use the Mirror List updater tool to copy the first 5 sites listed to my etc > pacman.d > mirrorlist file before I run an update (usually once a month).  These are the options I select on the Mirror List updater tool:
Country:  United States
Protocol:  https
IP Version:  IPv4, IPv6
Use Mirror Status is checked

To answer your question, "pacman -Q linux" outputs "linux 6.18.7.arch1-1"

Last edited by Saturn94 (2026-02-15 02:34:00)

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

Does the kernel not get updated when I update the OS?  I last updated the OS Feb 6, 2026 using the command "pacman -Syu".

Yes and no. On your system the kernel is provided by the linux package.  The linux package itself will be updated by `pacman -Syu` provided the mirror it was being updated from was up to date.  What is the output of `pacman -Q linux`?  With the kernel there is an additional step it needs to be copied to where ever your system's boot mechanism expects to find it commonly under /boot.  This should happen automatically but it depends on the system being configured correctly.

I went ahead and ran "pacman -Syu" to update again.

Now when I run "pacman -Q linux", it outputs "linux 6.18.9.arch1-2".

Running 'uname -a" outputs "Linux splayer 6.18.9-arch1-2 #1 SMP PREEMPT_DYNAMIC Mon, 09 Feb 2026 17:16:33 +0"

Am I correct that this means I'm now running the latest kernel?

Last edited by Saturn94 (2026-02-15 04:46:26)

5hridhyan

Member

From: Asia

Registered: 2025-12-25

Posts: 282

Re: Random Reboot....why?

Regarding your `random reboots`
your logs show a 'clean' reboot (meaning the system was told to restart, not that it crashed or lost power). To find out what triggered it, could you check the logs for the login manager from that previous session/such reboot?

journalctl -u systemd-logind -b -1

We are looking for a line that says 'ordered by UID'. Also, since it happens when you aren't using it, it's worth checking if any scheduled tasks are running:

systemctl list-timers

Edit
Yes as of now it is the latest kernel.
first paste those outputs and also better share full journal logs for such reboots/behavior...

journalctl -b -1 | curl -F 'file=@-' https://0x0.st

(this uploads the log from the previous boot and gives you a link to share here. If you need to go further back, use -b -2, -b -3, etc)

Last edited by 5hridhyan (2026-02-15 05:29:43)

---

Keep your virtue sharpened in a kingdom of carrion, and the throne they offer will be built from your ribs.

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

Regarding your `random reboots`
your logs show a 'clean' reboot (meaning the system was told to restart, not that it crashed or lost power). To find out what triggered it, could you check the logs for the login manager from that previous session/such reboot?

journalctl -u systemd-logind -b -1

We are looking for a line that says 'ordered by UID'. Also, since it happens when you aren't using it, it's worth checking if any scheduled tasks are running:

systemctl list-timers

Edit
Yes as of now it is the latest kernel.

0 ✓ splayer ~ $ journalctl -u systemd-logind -b -2
Feb 10 18:15:18 splayer systemd[1]: Starting User Login Management...
Feb 10 18:15:18 splayer systemd-logind[367]: New seat seat0.
Feb 10 18:15:18 splayer systemd-logind[367]: Watching system buttons on /dev/input/event1 (Power Button)
Feb 10 18:15:18 splayer systemd-logind[367]: Watching system buttons on /dev/input/event0 (Power Button)
Feb 10 18:15:18 splayer systemd[1]: Started User Login Management.
Feb 10 19:40:36 splayer systemd-logind[367]: New session '1' of user 'root' with class 'user' and type 'tty'.
Feb 10 19:40:36 splayer systemd-logind[367]: New session '2' of user 'root' with class 'manager-early' and type 'unspecified'.
Feb 10 19:44:39 splayer systemd-logind[367]: Session 1 logged out. Waiting for processes to exit.
Feb 10 19:44:39 splayer systemd-logind[367]: Removed session 1.
Feb 10 19:44:49 splayer systemd-logind[367]: Removed session 2.
Feb 10 23:10:31 splayer systemd-logind[367]: New session '3' of user 'root' with class 'user' and type 'tty'.
Feb 10 23:10:31 splayer systemd-logind[367]: New session '4' of user 'root' with class 'manager-early' and type 'unspecified'.
Feb 10 23:11:01 splayer systemd-logind[367]: Session 3 logged out. Waiting for processes to exit.
Feb 10 23:11:01 splayer systemd-logind[367]: Removed session 3.
Feb 10 23:11:12 splayer systemd-logind[367]: Removed session 4.
Feb 10 23:35:17 splayer systemd-logind[367]: New session '5' of user 'root' with class 'user' and type 'tty'.
Feb 10 23:35:17 splayer systemd-logind[367]: New session '6' of user 'root' with class 'manager-early' and type 'unspecified'.
Feb 10 23:35:45 splayer systemd-logind[367]: Session 5 logged out. Waiting for processes to exit.
Feb 10 23:35:45 splayer systemd-logind[367]: Removed session 5.
Feb 10 23:35:55 splayer systemd-logind[367]: Removed session 6.
Feb 14 15:41:49 splayer systemd-logind[367]: The system will reboot now!
Feb 14 15:41:49 splayer systemd-logind[367]: System is rebooting.
Feb 14 15:41:49 splayer systemd[1]: Stopping User Login Management...
Feb 14 15:41:49 splayer systemd[1]: systemd-logind.service: Deactivated successfully.
Feb 14 15:41:49 splayer systemd[1]: Stopped User Login Management.
0 ✓ splayer ~ $

I don't see a line above that mentions "UID".

0 ✓ splayer ~ $ systemctl list-timers
NEXT                          LEFT LAST                           PASSED UNIT                             ACTIVATES
Sun 2026-02-15 00:22:46 EST  10min Sat 2026-02-14 00:14:27 EST         - logrotate.timer                  logrotate.service
Sun 2026-02-15 00:40:01 EST  27min Sat 2026-02-14 09:43:08 EST         - man-db.timer                     man-db.service
Sun 2026-02-15 23:44:53 EST    23h Sat 2026-02-14 23:44:53 EST 27min ago systemd-tmpfiles-clean.timer     systemd-tmpfiles-clean.service
Mon 2026-02-16 00:00:00 EST    23h Sun 2026-02-15 00:00:03 EST 12min ago shadow.timer                     shadow.service
Fri 2026-02-20 12:37:56 EST 5 days Tue 2026-02-10 21:43:39 EST         - archlinux-keyring-wkd-sync.timer archlinux-keyring-wkd-sync.service

5 timers listed.
Pass --all to see loaded but inactive timers, too.
0 ✓ splayer ~ $

Does the above show anything useful?

5hridhyan

Member

From: Asia

Registered: 2025-12-25

Posts: 282

Re: Random Reboot....why?

the logs confirm it was a "clean" reboot, but interestingly, no specific user or software process is recorded as having asked for it. Usually, if a user types the command, we see a "UID" mentioned.
Because that line is missing, we should look at two possibilities:

- Physical Trigger: Does the device have a physical power/reset button? Is it possible it's being bumped, or is there a "Wake on LAN" or "Power on AC loss" setting in the BIOS that might be misbehaving?
-Kernel/System level: Since the logind output is a bit sparse, we need the "full picture" from the kernel.
Could you please run this command and share the link it gives you? It will show us the full system activity leading up to that exact second on Feb 14.

journalctl -b -2 | curl -F 'file=@-' https://0x0.st

(Note: I used -b -2 because your previous output showed the Feb 14 event was 2 boots ago).
yes for that specific reboot/behavior.

Last edited by 5hridhyan (2026-02-15 05:37:58)

---

Keep your virtue sharpened in a kingdom of carrion, and the throne they offer will be built from your ribs.

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

Regarding your `random reboots`
your logs show a 'clean' reboot (meaning the system was told to restart, not that it crashed or lost power). To find out what triggered it, could you check the logs for the login manager from that previous session/such reboot?

journalctl -u systemd-logind -b -1

We are looking for a line that says 'ordered by UID'. Also, since it happens when you aren't using it, it's worth checking if any scheduled tasks are running:

systemctl list-timers

Edit
Yes as of now it is the latest kernel.
first paste those outputs and also better share full journal logs for such reboots/behavior...

journalctl -b -1 | curl -F 'file=@-' https://0x0.st

(this uploads the log from the previous boot and gives you a link to share here. If you need to go further back, use -b -2, -b -3, etc)

I think adding -2 shows the logs including when the last random reboot occurred earlier today (Feb 14th) up until I rebooted this evening (Feb 14th after updating the OS to 6.18.9 arch1-2).  It goes back to Feb 10th when I last shut down and rebooted.

This is my first attempt posting a log this way.  Please let me know if it worked correctly or not, or if you need additional logs (the first random reboot I noticed occurred Feb 6th).

https://0x0.st/PBev.txt

Thank you!

Last edited by Saturn94 (2026-02-15 05:38:51)

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

the logs confirm it was a "clean" reboot, but interestingly, no specific user or software process is recorded as having asked for it. Usually, if a user types the command, we see a "UID" mentioned.
Because that line is missing, we should look at two possibilities:

- Physical Trigger: Does the device have a physical power/reset button? Is it possible it's being bumped, or is there a "Wake on LAN" or "Power on AC loss" setting in the BIOS that might be misbehaving?
-Kernel/System level: Since the logind output is a bit sparse, we need the "full picture" from the kernel.
Could you please run this command and share the link it gives you? It will show us the full system activity leading up to that exact second on Feb 14.

journalctl -b -2 | curl -F 'file=@-' https://0x0.st

(Note: I used -b -2 because your previous output showed the Feb 14 event was 2 boots ago).
yes for that specific reboot/behavior.

I posted the log you requested in my above post.  Please let me know if it isn't the correct log.

The device does have a physical power button, but its location is between the side external heat fins, so it's extremely unlikely to be accidentally pressed, not to mention no one was near it when the random reboots occurred.  As far as I know, the device is not set to "Wake on LAN" or "Power on AC loss" (if there is a power outage, it does not power back on automatically).  If necessary, I could try to hook up a keyboard and TV via HDMI and see if I can access the BIOS settings to see what it says (I'll have to research how to do that).

Last edited by Saturn94 (2026-02-15 05:53:10)

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

the logs confirm it was a "clean" reboot, but interestingly, no specific user or software process is recorded as having asked for it. Usually, if a user types the command, we see a "UID" mentioned...

Is it possible Roonserver could be doing something to cause the reboot, but not show in the logs?  Roonserver is the only software I run on this machine.

PS - It's getting late here (1:09am), so I'm going to come back to this in the morning.

Thank you!

Last edited by Saturn94 (2026-02-15 06:10:29)

5hridhyan

Member

From: Asia

Registered: 2025-12-25

Posts: 282

Re: Random Reboot....why?

To answer your Roon question: it’s extremely unlikely Roon itself triggered a reboot. If it did, the logs would show a specific request.

and from The  logs I didn't see hardware errors (MCE), thermal spikes, etc I say it’s all clean. There are some minor database and network errors, but nothing that would cause a system-wide restart.
and the fact that it’s a clean reboot with no user ID (UID) really points toward a low-level trigger, like a minor power fluctuation or a firmware safety reset.

Don’t worry about the BIOS or connecting a display for now. Run the new kernel (6.18.9) and watch it for a week. Most of these 'ghost' reboots are fixed by the stability improvements in newer kernels I guess...

Let us know if it stays stable or if the `ghost` comes back! Get some rest.

Last edited by 5hridhyan (2026-02-15 08:03:36)

---

Keep your virtue sharpened in a kingdom of carrion, and the throne they offer will be built from your ribs.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 73,157

Re: Random Reboot....why?

Feb 14 15:35:09 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 15:41:49 splayer systemd[1]: Starting Authorization Manager...
Feb 14 15:41:49 splayer polkitd[515038]: Started polkitd version 127
Feb 14 15:41:49 splayer systemd[1]: Started Authorization Manager.
Feb 14 15:41:49 splayer systemd-logind[367]: The system will reboot now!
Feb 14 15:41:49 splayer systemd-logind[367]: System is rebooting.

That's a controlled and deliberate reboot and apparently it required polkit for privilege authentication.

Feb 10 18:15:08 splayer systemd[1]: Created slice User and Session Slice.
Feb 10 19:40:35 splayer sshd-session[9080]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 19:40:36 splayer systemd-logind[367]: New session '1' of user 'root' with class 'user' and type 'tty'.
Feb 10 19:40:36 splayer (systemd)[9098]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 19:40:36 splayer systemd-logind[367]: New session '2' of user 'root' with class 'manager-early' and type 'unspecified'.
Feb 10 19:40:36 splayer systemd[1]: Started Session 1 of User root.
Feb 10 19:44:39 splayer sshd-session[9080]: pam_unix(sshd:session): session closed for user root
Feb 10 19:44:39 splayer systemd-logind[367]: Session 1 logged out. Waiting for processes to exit.
Feb 10 19:44:39 splayer systemd-logind[367]: Removed session 1.
Feb 10 19:44:49 splayer systemd-logind[367]: Removed session 2.
Feb 10 19:44:49 splayer (sd-pam)[9102]: pam_unix(systemd-user:session): session closed for user root
Feb 10 23:10:31 splayer sshd-session[28689]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 23:10:31 splayer systemd-logind[367]: New session '3' of user 'root' with class 'user' and type 'tty'.
Feb 10 23:10:31 splayer (systemd)[28711]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 23:10:31 splayer systemd-logind[367]: New session '4' of user 'root' with class 'manager-early' and type 'unspecified'.
Feb 10 23:10:31 splayer systemd[1]: Started Session 3 of User root.
Feb 10 23:11:01 splayer sshd-session[28689]: pam_unix(sshd:session): session closed for user root
Feb 10 23:11:01 splayer systemd-logind[367]: Session 3 logged out. Waiting for processes to exit.
Feb 10 23:11:01 splayer systemd-logind[367]: Removed session 3.
Feb 10 23:11:12 splayer systemd-logind[367]: Removed session 4.
Feb 10 23:11:12 splayer (sd-pam)[28715]: pam_unix(systemd-user:session): session closed for user root
Feb 10 23:35:16 splayer sshd-session[31099]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 23:35:17 splayer systemd-logind[367]: New session '5' of user 'root' with class 'user' and type 'tty'.
Feb 10 23:35:17 splayer (systemd)[31117]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 23:35:17 splayer systemd-logind[367]: New session '6' of user 'root' with class 'manager-early' and type 'unspecified'.
Feb 10 23:35:17 splayer systemd[1]: Started Session 5 of User root.
Feb 10 23:35:45 splayer sshd-session[31099]: pam_unix(sshd:session): session closed for user root
Feb 10 23:35:45 splayer systemd-logind[367]: Session 5 logged out. Waiting for processes to exit.
Feb 10 23:35:45 splayer systemd-logind[367]: Removed session 5.
Feb 10 23:35:55 splayer systemd-logind[367]: Removed session 6.
Feb 10 23:35:55 splayer (sd-pam)[31120]: pam_unix(systemd-user:session): session closed for user root
Feb 14 15:41:50 splayer systemd[1]: Removed slice User and Session Slice.

doesn't seem to come from an interactive session, there doesn't seem to be a cron daemon and the logged systemd timers look unsuspicious.

=> https://wiki.archlinux.org/title/Polkit … ng/logging

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

To answer your Roon question: it’s extremely unlikely Roon itself triggered a reboot. If it did, the logs would show a specific request.

and from The  logs I didn't see hardware errors (MCE), thermal spikes, etc I say it’s all clean. There are some minor database and network errors, but nothing that would cause a system-wide restart.
and the fact that it’s a clean reboot with no user ID (UID) really points toward a low-level trigger, like a minor power fluctuation or a firmware safety reset.

Don’t worry about the BIOS or connecting a display for now. Run the new kernel (6.18.9) and watch it for a week. Most of these 'ghost' reboots are fixed by the stability improvements in newer kernels I guess...

Let us know if it stays stable or if the `ghost` comes back! Get some rest.

Thank you.

Speaking of the hardware, I bought the Salkstream in June 2016.  It has a 2tb internal HDD and two external USB HDDs connected for backups (one connected at all times and the other only when performing a backup).  The internal HDD failed in November 2020 and was replaced with a new 2tb HDD.  The case is fanless and uses an external power supply (power brick?).  If the power supply were going bad, wouldn’t the Salkstream just shut down if power dropped too low?

A few days ago, I shut down, disconnected the power supply, and opened up the Salk to see if it needed cleaning.  There was surprisingly little dust inside considering I haven’t opened the case since replacing the internal HDD in late 2020.  I blew out what dust was inside and reseated the two RAM sticks (4gb each) just to make sure they have a good connection.

I noticed on the motherboard there is a button battery.  What is it for?  It’s just over 9.5 years old at this point.  If it’s getting weak, could it be causing the ghost reboots?

As you suggested, I’ll monitor it and see if any ghost reboots occur again.  Here’s hoping the OS update fixed whatever it is.

EDIT:  I looked up about the motherboard battery.  This is what Google says about signs it needs replacing;

A failing CMOS battery, typically a CR2032 coin cell on the motherboard, causes the computer to lose BIOS settings, resulting in incorrect system time/date, CMOS Checksum errors, and boot failures. Other common signs include the computer asking for F1/setup input on boot, erratic behavior, or hardware not being detected properly.
Key Signs of a Dying CMOS Battery
Incorrect Time and Date: The system clock resets to a default date (e.g., Jan 1, 2000) or displays the wrong time every time the computer is powered on.
BIOS/UEFI Reset: Custom BIOS settings, such as boot order or overclocking configurations, revert to default settings upon every reboot.
Boot Errors: Messages like "CMOS Read Error," "CMOS Battery Failure," or "CMOS Checksum Error" appear during startup.
Failure to Boot: The computer may not start at all, or it may get stuck in a boot loop, often accompanied by unusual beeping sounds.
Driver/Hardware Issues: Frequent issues with hardware detection, such as network adapters failing to connect or drivers disappearing.
Longer Boot Times: The system takes longer to POST (Power-On Self-Test).

Best I can tell, I’m not experiencing any of those symptoms, so I guess the battery is fine (the Salkstream is very rarely ever disconnected from the power supply).

Last edited by Saturn94 (2026-02-15 19:06:23)

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

Feb 14 15:35:09 splayer dhcpcd[404]: enp2s0: requesting DHCPv6 information
Feb 14 15:41:49 splayer systemd[1]: Starting Authorization Manager...
Feb 14 15:41:49 splayer polkitd[515038]: Started polkitd version 127
Feb 14 15:41:49 splayer systemd[1]: Started Authorization Manager.
Feb 14 15:41:49 splayer systemd-logind[367]: The system will reboot now!
Feb 14 15:41:49 splayer systemd-logind[367]: System is rebooting.

That's a controlled and deliberate reboot and apparently it required polkit for privilege authentication.

Feb 10 18:15:08 splayer systemd[1]: Created slice User and Session Slice.
Feb 10 19:40:35 splayer sshd-session[9080]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 19:40:36 splayer systemd-logind[367]: New session '1' of user 'root' with class 'user' and type 'tty'.
Feb 10 19:40:36 splayer (systemd)[9098]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 19:40:36 splayer systemd-logind[367]: New session '2' of user 'root' with class 'manager-early' and type 'unspecified'.
Feb 10 19:40:36 splayer systemd[1]: Started Session 1 of User root.
Feb 10 19:44:39 splayer sshd-session[9080]: pam_unix(sshd:session): session closed for user root
Feb 10 19:44:39 splayer systemd-logind[367]: Session 1 logged out. Waiting for processes to exit.
Feb 10 19:44:39 splayer systemd-logind[367]: Removed session 1.
Feb 10 19:44:49 splayer systemd-logind[367]: Removed session 2.
Feb 10 19:44:49 splayer (sd-pam)[9102]: pam_unix(systemd-user:session): session closed for user root
Feb 10 23:10:31 splayer sshd-session[28689]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 23:10:31 splayer systemd-logind[367]: New session '3' of user 'root' with class 'user' and type 'tty'.
Feb 10 23:10:31 splayer (systemd)[28711]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 23:10:31 splayer systemd-logind[367]: New session '4' of user 'root' with class 'manager-early' and type 'unspecified'.
Feb 10 23:10:31 splayer systemd[1]: Started Session 3 of User root.
Feb 10 23:11:01 splayer sshd-session[28689]: pam_unix(sshd:session): session closed for user root
Feb 10 23:11:01 splayer systemd-logind[367]: Session 3 logged out. Waiting for processes to exit.
Feb 10 23:11:01 splayer systemd-logind[367]: Removed session 3.
Feb 10 23:11:12 splayer systemd-logind[367]: Removed session 4.
Feb 10 23:11:12 splayer (sd-pam)[28715]: pam_unix(systemd-user:session): session closed for user root
Feb 10 23:35:16 splayer sshd-session[31099]: pam_unix(sshd:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 23:35:17 splayer systemd-logind[367]: New session '5' of user 'root' with class 'user' and type 'tty'.
Feb 10 23:35:17 splayer (systemd)[31117]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Feb 10 23:35:17 splayer systemd-logind[367]: New session '6' of user 'root' with class 'manager-early' and type 'unspecified'.
Feb 10 23:35:17 splayer systemd[1]: Started Session 5 of User root.
Feb 10 23:35:45 splayer sshd-session[31099]: pam_unix(sshd:session): session closed for user root
Feb 10 23:35:45 splayer systemd-logind[367]: Session 5 logged out. Waiting for processes to exit.
Feb 10 23:35:45 splayer systemd-logind[367]: Removed session 5.
Feb 10 23:35:55 splayer systemd-logind[367]: Removed session 6.
Feb 10 23:35:55 splayer (sd-pam)[31120]: pam_unix(systemd-user:session): session closed for user root
Feb 14 15:41:50 splayer systemd[1]: Removed slice User and Session Slice.

doesn't seem to come from an interactive session, there doesn't seem to be a cron daemon and the logged systemd timers look unsuspicious.

=> https://wiki.archlinux.org/title/Polkit … ng/logging

Thank you for taking a look.  I guess it’s good news that everything looks normal, other than still not knowing what is triggering the “ghost” reboots.

5hridhyan

Member

From: Asia

Registered: 2025-12-25

Posts: 282

Re: Random Reboot....why?

I noticed on the motherboard there is a button battery.  What is it for?  It’s just over 9.5 years old at this point.  If it’s getting weak, could it be causing the ghost reboots?

its CMOS and it's responsible for time and date and settings in the BIOS when the board is unplugged, "9.5" years, its "aged" it can cause settings resets, but random runtime reboots are uncommon from a weak CMOS battery.

Speaking of the hardware, I bought the Salkstream in June 2016.  It has a 2tb internal HDD and two external USB HDDs connected for backups (one connected at all times and the other only when performing a backup).  The internal HDD failed in November 2020 and was replaced with a new 2tb HDD.  The case is fanless and uses an external power supply (power brick?).  If the power supply were going bad, wouldn’t the Salkstream just shut down if power dropped too low?

not necessarily die or shutdown always... as they age, the capacitors can leak voltage "noise." If the motherboard feels a ripple, it might trigger a soft-reset for "protection" they typically have OVP/UVPs, but not sure in this case until tested with diff brick/unit but from your polkit logs its unlikely, a ripple doesn't asks “Hello polkit, may I request a structured reboot?"
Stick to the plan of monitoring for a week on the new kernel and see if it holds up.

Last edited by 5hridhyan (2026-02-15 19:30:23)

---

Keep your virtue sharpened in a kingdom of carrion, and the throne they offer will be built from your ribs.

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

I noticed on the motherboard there is a button battery.  What is it for?  It’s just over 9.5 years old at this point.  If it’s getting weak, could it be causing the ghost reboots?

its CMOS and it's responsible for time and date and settings in the BIOS when the board is unplugged, "9.5" years, its "aged" it can cause settings resets, but random runtime reboots are uncommon from a weak CMOS battery.

Speaking of the hardware, I bought the Salkstream in June 2016.  It has a 2tb internal HDD and two external USB HDDs connected for backups (one connected at all times and the other only when performing a backup).  The internal HDD failed in November 2020 and was replaced with a new 2tb HDD.  The case is fanless and uses an external power supply (power brick?).  If the power supply were going bad, wouldn’t the Salkstream just shut down if power dropped too low?

not necessarily die or shutdown always... as they age, the capacitors can leak voltage "noise." If the motherboard feels a ripple, it might trigger a soft-reset for "protection" they typically have OVP/UVPs, but not sure in this case until tested with diff brick/unit but from your polkit logs its unlikely, a ripple doesn't asks “Hello polkit, may I request a structured reboot?"
Stick to the plan of monitoring for a week on the new kernel and see if it holds up.

Thank you for the explanation.

I did some research on checking the cmos, and found how to run “sensors” to check the battery voltage (vbat).  The vbat voltage looks fine, so the battery appears to be good.  Is there anything else in the sensors output that looks concerning?

root@splayer ~ $ sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +35.0°C  (high = +79.0°C, crit = +85.0°C)
Core 0:        +34.0°C  (high = +79.0°C, crit = +85.0°C)
Core 1:        +32.0°C  (high = +79.0°C, crit = +85.0°C)

nct6776-isa-0290
Adapter: ISA adapter
Vcore:         872.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:           176.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:            3.36 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:           3.34 V  (min =  +2.98 V, max =  +3.63 V)
in4:           512.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:             1.89 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:             1.70 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:            3.44 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:            3.33 V  (min =  +2.70 V, max =  +3.63 V)
fan1:             0 RPM  (min =    0 RPM)
fan2:             0 RPM  (min =    0 RPM)
fan3:             0 RPM  (min =    0 RPM)
fan4:             0 RPM  (min =    0 RPM)
fan5:             0 RPM  (min =    0 RPM)
SYSTIN:         +37.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
CPUTIN:         -59.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN:         -14.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
PECI Agent 0:   +34.0°C  (high = +80.0°C, hyst = +75.0°C)
                         (crit = +85.0°C)
PCH_CHIP_TEMP:   +0.0°C  
PCH_CPU_TEMP:    +0.0°C  
PCH_MCH_TEMP:    +0.0°C  
pwm1:               82%  (mode = pwm)
pwm2:               82%  (mode = pwm)
pwm3:              128%  (mode = pwm)
intrusion0:    OK
intrusion1:    OK
beep_enable:   disabled

root@splayer

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 73,157

Re: Random Reboot....why?

An empty CMOS battery will not cause spurious reboots and certainly not w/ the symptoms/journal you posted.
If you follow the wiki link I posted, it explains how to log polkit - maybe that gets us a hint what (or at least which user) is triggering this.
As a stopgap, some paragraph below also shows how to block these permissions in polkit (so the reboot request will be denied, you can still "sudo reboot")

On a formal note, please avoid bloating the thread with pointless full-quotes of previous posts, thanks.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Saturn94

Member

Registered: 2026-02-11

Posts: 34

Re: Random Reboot....why?

Seth, thank you for clarifying that the cmos battery isn’t the issue.

I took a look at the link you posted, and must admit much of it went over my head.  I think for now I’ll stick with the plan to just wait and see if the ghost reboots continue.  If they do, I’ll see if I can figure out how to set up the logs mentioned in the link.

My apologies for the full quotes.  I’m still learning how to use this forum and haven’t yet figured out how to respond to a particular post without quoting.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 73,157

Re: Random Reboot....why?

My apologies for the full quotes.

No worries.

haven’t yet figured out how to respond to a particular post without quoting.

You can't nor have to - if you want to reference something specifically you can just quote that.

On topic:
Adding the two files are restarting polkit (or rebooting…) would do - the invocation gets logged into the system journal.
But since there's no (active) session only root or members of the wheel group should™ be able to reboot - you could see what processes fall into that category.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc