Server rebooted unexpectedly and without log trace
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I was working at my desktop machine. My little server machine, media server, was playing the internet radio with Kodi. I went to the kitchen to put the dinner on the oven. On return, the media server had rebooted and was asking for login. There is no trace in the syslog: <1.5> 2021-01-23T21:15:03.643324+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) <3.6> 2021-01-23T21:16:56.732717+01:00 Isengard systemd 1 - - Started Daily Cleanup of Snapper Snapshots. <3.6> 2021-01-23T21:16:56.873624+01:00 Isengard dbus-daemon 1109 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.1048' (uid=0 pid=5447 comm="/usr/lib/snapper/systemd-helper --cleanup ") (using servicehelper) <3.6> 2021-01-23T21:16:57.131185+01:00 Isengard dbus-daemon 1109 - - [system] Successfully activated service 'org.opensuse.Snapper' <3.6> 2021-01-23T21:21:56.728956+01:00 Isengard systemd 1 - - Starting Cleanup of Temporary Directories... <3.5> 2021-01-23T21:21:56.875752+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/net-snmp.conf:1] Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordingly. <3.5> 2021-01-23T21:21:56.879004+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/radvd.conf:1] Line references path below legacy directory /var/run/, updating /var/run/radvd → /run/radvd; please update the tmpfiles.d/ drop-in file accordingly. <3.5> 2021-01-23T21:21:56.879901+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/samba.conf:1] Line references path below legacy directory /var/run/, updating /var/run/samba → /run/samba; please update the tmpfiles.d/ drop-in file accordingly. <3.5> 2021-01-23T21:21:56.883365+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/svnserve.conf:1] Line references path below legacy directory /var/run/, updating /var/run/svnserve → /run/svnserve; please update the tmpfiles.d/ drop-in file accordingly. <3.5> 2021-01-23T21:21:56.887213+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/tmp.conf:13] Duplicate line for path "/var/tmp", ignoring. <3.5> 2021-01-23T21:21:56.888626+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path "/var/lib", ignoring. <3.5> 2021-01-23T21:21:56.889240+01:00 Isengard systemd-tmpfiles 5561 - - [/usr/lib/tmpfiles.d/var.conf:23] Duplicate line for path "/var/spool", ignoring. <3.6> 2021-01-23T21:21:56.965040+01:00 Isengard systemd 1 - - Started Cleanup of Temporary Directories. <1.5> 2021-01-23T21:30:03.251921+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) <3.6> 2021-01-23T21:33:54.528052+01:00 Isengard smartd 1103 - - Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 41 to 46 <3.6> 2021-01-23T21:33:54.529239+01:00 Isengard smartd 1103 - - Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 41 to 46 <3.6> 2021-01-23T21:33:54.603175+01:00 Isengard smartd 1103 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 65 <3.6> 2021-01-23T21:33:54.603840+01:00 Isengard smartd 1103 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 34 to 35 <1.5> 2021-01-23T21:45:03.043504+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) 2021-01-23 22:06:23+01:00 - Booting the system now ================================================================================ Linux Isengard 5.3.18-lp152.60-default #1 SMP Tue Jan 12 23:10:31 UTC 2021 (9898712) x86_64 x86_64 x86_64 GNU/Linux <3.6> 2021-01-23T22:06:24.780509+01:00 Isengard systemd 1 - - systemd 234 running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 -IDN default-hierarchy=hybrid) <0.6> 2021-01-23T22:06:24.780976+01:00 Isengard kernel - - - [ 0.000000] microcode: microcode updated early to revision 0x411, date = 2019-04-23 <0.5> 2021-01-23T22:06:24.781721+01:00 Isengard kernel - - - [ 0.000000] Linux version 5.3.18-lp152.60-default (geeko@buildhost) (gcc version 7.5. ... Aside note: Kernel boot information is missing from syslog. New bug? Compare with leap 15.1 syslog: 2020-09-24 13:57:39+02:00 - Halting the system now =========================================== uptime: 13:57:39 up 82 days 15:43, 0 users, load average: 1.20, 1.30, 1.47 2020-09-24 20:48:11+02:00 - Booting the system now ================================================================================ Linux Isengard 4.12.14-lp151.28.67-default #1 SMP Fri Sep 4 15:23:21 UTC 2020 (2c5a14f) x86_64 x86_64 x86_64 GNU/Linux <0.6> 2020-09-24T20:48:12.560421+02:00 Isengard kernel - - - [ 0.000000] microcode: microcode updated early to revision 0x411, date = 2019-04-23 <0.5> 2020-09-24T20:48:12.560854+02:00 Isengard kernel - - - [ 0.000000] Linux version 4.12.14-lp151.28.67-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux) ) #1 SMP Fri Sep 4 15:23:21 UTC 2020 (2c5a14f) <0.6> 2020-09-24T20:48:12.560862+02:00 Isengard kernel - - - [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.14-lp151.28.67-default root=UUID=0d457df1-b43d-4587-aa5a-6c919bcbedb8 showopts resume=/dev/disk/by-label/Swap splash=verbose That would indicate a power failure, but the thing is on an UPS. I tested flipping the mains, for 5 seconds, and it survived. I was in the house, I would have noticed any power failure bigger than 0.1 second. A thermal event would be logged, and the machine is not loaded, anyway. Let's see if the journal has something: cer@Isengard:~> journalctl --list-boots - -9 6454520f76ef411aae4048bcad74bf29 Tue 2020-01-28 02:12:23 CET—Sun 2020-02-23 20:40:58 CET - -8 690c025a20e74949aa3b14a9920bc965 Sun 2020-02-23 20:41:43 CET—Sun 2020-04-12 19:41:11 CEST - -7 c931092ce6b742a0bcef0e0c789cc2d9 Sun 2020-04-12 19:41:55 CEST—Fri 2020-07-03 22:12:29 CEST - -6 d0d9dcc6f41d4d95bfb1bb7017fd89b9 Fri 2020-07-03 22:14:26 CEST—Thu 2020-09-24 13:59:17 CEST - -5 deddc3a843ba4ace9580e54614df5918 Thu 2020-09-24 20:46:37 CEST—Sat 2021-01-16 16:27:19 CET - -4 0078032ae9f446389daef4b9b1546184 Sat 2021-01-16 16:28:09 CET—Sat 2021-01-16 20:55:05 CET - -3 71982ddc703b49398aac561ae95a491f Sun 2021-01-17 10:12:08 CET—Sun 2021-01-17 21:01:44 CET - -2 ff6a60796ff94a26a514a8bff51fd3e0 Sun 2021-01-17 21:02:19 CET—Sat 2021-01-23 21:45:03 CET - -1 84c1f9d5c6c34fdbb83fe961e42bef1f Sat 2021-01-23 22:01:18 CET—Sat 2021-01-23 22:24:05 CET 0 ecd9e2c9fa9945e4ae57ef7e55938b36 Sat 2021-01-23 22:24:40 CET—Sat 2021-01-23 22:46:51 CET cer@Isengard:~> I need session 2, -2 Sun 2021-01-17 21:02:19 CET—Sat 2021-01-23 21:45:03 CET cer@Isengard:~> journalctl --boot=2 - -- Logs begin at Tue 2020-01-28 02:12:23 CET, end at Sat 2021-01-23 22:48:07 CET. -- No - then session 3? - -- Logs begin at Tue 2020-01-28 02:12:23 CET, end at Sat 2021-01-23 22:48:38 CET. -- No... wtf? cer@Isengard:~> journalctl --boot=ff6a60796ff94a26a514a8bff51fd3e0 - -- Logs begin at Tue 2020-01-28 02:12:23 CET, end at Sat 2021-01-23 22:48:38 CET. -- That's the whole journal, not number 2. Where is the journal number 2? Another bug in the journal? Ok, let's find the boot point by grepping the whole journal, old style Jan 23 21:16:57 Isengard dbus-daemon[1109]: [system] Successfully activated service 'org.opensuse.Snapper' Jan 23 21:21:56 Isengard systemd[1]: Starting Cleanup of Temporary Directories... Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/net-snmp.conf:1] Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordin> Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/radvd.conf:1] Line references path below legacy directory /var/run/, updating /var/run/radvd → /run/radvd; please update the tmpfiles.d/ drop-in file accordingly. Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/samba.conf:1] Line references path below legacy directory /var/run/, updating /var/run/samba → /run/samba; please update the tmpfiles.d/ drop-in file accordingly. Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/svnserve.conf:1] Line references path below legacy directory /var/run/, updating /var/run/svnserve → /run/svnserve; please update the tmpfiles.d/ drop-in file accordin> Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/tmp.conf:13] Duplicate line for path "/var/tmp", ignoring. Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path "/var/lib", ignoring. Jan 23 21:21:56 Isengard systemd-tmpfiles[5561]: [/usr/lib/tmpfiles.d/var.conf:23] Duplicate line for path "/var/spool", ignoring. Jan 23 21:21:56 Isengard systemd[1]: Started Cleanup of Temporary Directories. Jan 23 21:30:03 Isengard Sistema[5776]: Logging the current external IP= (omitted) Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 41 to 46 Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 41 to 46 Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 66 to 65 Jan 23 21:33:54 Isengard smartd[1103]: Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 34 to 35 Jan 23 21:45:03 Isengard Sistema[6157]: Logging the current external IP= (omitted) - -- Reboot -- Jan 23 22:01:18 Isengard kernel: microcode: microcode updated early to revision 0x411, date = 2019-04-23 Jan 23 22:01:18 Isengard kernel: Linux version 5.3.18-lp152.60-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP Tue Jan 12 23:10:31 UTC 2021 (9898712) Jan 23 22:01:18 Isengard kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-lp152.60-default root=UUID=0d457df1-b43d-4587-aa5a-6c919bcbedb8 showopts splash=verbose splash=silent resume=/dev/disk/by-label/Swap mitigations=auto quiet Jan 23 22:01:18 Isengard kernel: x86/fpu: x87 FPU will use FXSAVE Jan 23 22:01:18 Isengard kernel: BIOS-provided physical RAM map: Jan 23 22:01:18 Isengard kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000003efff] usable Jan 23 22:01:18 Isengard kernel: BIOS-e820: [mem 0x000000000003f000-0x000000000003ffff] ACPI NVS Same info, that is, no info about what caused the machine to reboot. Has been fully reliable since I bought it on 2016: 2016-11-27 23:38:32+01:00 - Booting the system now ================================================================================ Linux Isengard 4.4.27-2-default #1 SMP Thu Nov 3 14:59:54 UTC 2016 (5c21e7c) x86_64 x86_64 x86_64 GNU/Linux 2016-12-04 15:44:09+01:00 - Halting the system now =========================================== uptime: 15:44pm up 6 days 16:06, 0 users, load average: 0.66, 0.25, 0.14 But now it is running Leap 15.2 since 2021-01-17, that is, a week ago. It rebooted perhaps just at 22:00 - cronjob? I don't have, yet, any log entry on a Saturday at 22:00 with leap 15.2, the machine was upgraded from 15.1 to 15.2 just on past Saturday (with DVD). On previous 15.1, this is what happens normally: <1.5> 2021-01-09T21:30:03.324416+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) <1.5> 2021-01-09T21:45:05.372100+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) <3.6> 2021-01-09T21:48:37.584878+01:00 Isengard smartd 25710 - - Device: /dev/sda [SAT], SMART Usage Attribute: 189 Airflow_Temperature_Cel changed from 42 to 43 <3.6> 2021-01-09T21:48:37.586113+01:00 Isengard smartd 25710 - - Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 42 to 43 <3.6> 2021-01-09T21:48:37.640372+01:00 Isengard smartd 25710 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 67 to 66 <3.6> 2021-01-09T21:48:37.641443+01:00 Isengard smartd 25710 - - Device: /dev/disk/by-id/wwn-0x5000c5009399305f [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 33 to 34 <3.6> 2021-01-09T22:00:03.382980+01:00 Isengard systemd 1 - - Started Timeline of Snapper Snapshots. <3.6> 2021-01-09T22:00:03.514452+01:00 Isengard dbus-daemon 1186 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.16079' (uid=0 pid=23673 comm="/usr/lib/snapper/systemd-helper --timeline ") (using servicehelper) <3.6> 2021-01-09T22:00:03.775706+01:00 Isengard dbus-daemon 1186 - - [system] Successfully activated service 'org.opensuse.Snapper' <1.5> 2021-01-09T22:00:08.698222+01:00 Isengard Sistema - - - Logging the current external IP= (omitted) <9.6> 2021-01-09T22:15:01.744156+01:00 Isengard run-crons.daily - - - Considering my daily cron jobs. <9.6> 2021-01-09T22:15:01.885387+01:00 Isengard run-crons.daily - - - Adjusting permissions of Video directories I'll have to keep watching and see... - -- Cheers Carlos E. R. (from 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYAyj2hwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV5CYAoIQFFQZGRpCSsGwRl9bj jWgcgHdvAJ0TCi2Cbp5P5RkyBNJLKTzsNojWVw== =D6AM -----END PGP SIGNATURE-----
On 24/01/2021 09.56, David C. Rankin wrote:
On 1/23/21 4:31 PM, Carlos E. R. wrote:
I'll have to keep watching and see...
Do you have cats? (they have a way of screwing everything up...)
Heh, no, I don't have pets :-D Sometimes I have heard noises on the space below the roof tiles, probably rats. Fortunately, non have entered the house itself (I have baits for them (as sensors) and they are intact). -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 24/01/2021 06:24, Carlos E. R. wrote:
On 24/01/2021 09.56, David C. Rankin wrote:
On 1/23/21 4:31 PM, Carlos E. R. wrote:
I'll have to keep watching and see...
Do you have cats? (they have a way of screwing everything up...)
Heh, no, I don't have pets :-D
Sometimes I have heard noises on the space below the roof tiles, probably rats. Fortunately, non have entered the house itself (I have baits for them (as sensors) and they are intact).
At roof level it is more likely to be squirrels. One house I lived in suffered from this and the council have an 'exterminator' as part of 'public health' who explained this to me. Toronto is beset by racoons, who seem cure and cuddly and friendly and many people 'adopt them and feed them but they are a health hazard. They are too big to fit in the gaps under the eaves. It turned out the squirrels were getting in though a gap where the attached garage joined the house. The professional was good at spotting things like this. Yes, the squirrels can be a health hazard. Setting poisonous bait is not a good thing. having rotting corpses in the eves is definitely a health hazard. However I don't think squirrels will go for rat poison. Rats are voracious omnivores. -- “Reality is so complex, we must move away from dogma, whether it’s conspiracy theories or free-market,” -- James Glattfelder. http://jth.ch/jbg
On 24/01/2021 15.23, Anton Aylward wrote:
On 24/01/2021 06:24, Carlos E. R. wrote:
On 24/01/2021 09.56, David C. Rankin wrote:
On 1/23/21 4:31 PM, Carlos E. R. wrote:
I'll have to keep watching and see...
Do you have cats? (they have a way of screwing everything up...)
Heh, no, I don't have pets :-D
Sometimes I have heard noises on the space below the roof tiles, probably rats. Fortunately, non have entered the house itself (I have baits for them (as sensors) and they are intact).
At roof level it is more likely to be squirrels.
I've never seen any in this city. No, I don't think any animal crashed my machine. Even if I had an uninvited and unknown house guest, a key press causing a power off would be logged. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On Sun, 24 Jan 2021 15:44, Carlos E. R. <robin.listas@...> wrote:
On 24/01/2021 15.23, Anton Aylward wrote:
On 24/01/2021 06:24, Carlos E. R. wrote:
On 24/01/2021 09.56, David C. Rankin wrote:
On 1/23/21 4:31 PM, Carlos E. R. wrote:
I'll have to keep watching and see...
Do you have cats? (they have a way of screwing everything up...)
Heh, no, I don't have pets :-D
Sometimes I have heard noises on the space below the roof tiles, probably rats. Fortunately, non have entered the house itself (I have baits for them (as sensors) and they are intact).
At roof level it is more likely to be squirrels.
I've never seen any in this city.
No, I don't think any animal crashed my machine. Even if I had an uninvited and unknown house guest, a key press causing a power off would be logged.
I'm shooting into the blue here, so please bear with me: I've seen similar behavior in an environment with an unstable AC-power. With "unstable" I mean one or more (sine-)periods of serious undervoltage, e.g. for a nomial Voltage of 240Vrms a 2 period long (40ms @50Hz) drop to ca 50Vrms. Now, a good quality and amply dimensioned PSU just swallows such "brown-outs", but on a lesser quality, or driven at more than 80% nominal load a PSU can cut the "power-good" signal and thus causing a reboot (if configured to boot-on-power-on). A edison-glow-lamp and flourescent lamp would flicker, some LED lamp might, others might not. Monitoring such happenings is a pain in the but, and for most of us is would make no sense to invest in such equipment. A UPS is in most cases cheaper. Just my 2ct. - Yamaban.
On 24/01/2021 16.06, Yamaban wrote:
On Sun, 24 Jan 2021 15:44, Carlos E. R. <robin.listas@...> wrote:
...
I'm shooting into the blue here, so please bear with me:
Go ahead :-)
I've seen similar behavior in an environment with an unstable AC-power.
With "unstable" I mean one or more (sine-)periods of serious undervoltage, e.g. for a nomial Voltage of 240Vrms a 2 period long (40ms @50Hz) drop to ca 50Vrms.
Now, a good quality and amply dimensioned PSU just swallows such "brown-outs", but on a lesser quality, or driven at more than 80% nominal load a PSU can cut the "power-good" signal and thus causing a reboot (if configured to boot-on-power-on).
A edison-glow-lamp and flourescent lamp would flicker, some LED lamp might, others might not.
Monitoring such happenings is a pain in the but, and for most of us is would make no sense to invest in such equipment.
A UPS is in most cases cheaper.
Well, that machine is on an UPS. My desktop is on another UPS, and the router (another room) has yet a third UPS :-) What I haven't bothered to do is have some software monitoring the UPS (two of them have the port). I must get to do it. At the moment this happened I was at the kitchen, where I have an LG TV that is very sensitive to power fluctuations (bad design): switch something on or off, and the sound drops to zero for half a second. Something as dramatic as a real power glitch would crash that TV. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 1/24/21 6:23 AM, Anton Aylward wrote:
Sometimes I have heard noises on the space below the roof tiles, probably rats. Fortunately, non have entered the house itself (I have baits for them (as sensors) and they are intact).
At roof level it is more likely to be squirrels.
Here we have a species of non-native rat which lives in palm trees, and in building roofs. They're called Tree Rats, or Roof Rats. https://www.gardenzeus.com/rats-in-the-california-home/ I haven't seen any in/on the house, but saw one in a guava tree. They're smaller than regular rats. I've got traps in the attic just to be safe. Regards, Lew
Am Sat, 23 Jan 2021 23:31:53 +0100 (CET) schrieb "Carlos E. R." <robin.listas@telefonica.net>:
I'll have to keep watching and see...
If /proc/sys/kernel/panic is zero, keep watching. In case it has a non-zero value, configure kdump to capture future crashes. Good luck. Olaf
On 25/01/2021 09.12, Olaf Hering wrote:
Am Sat, 23 Jan 2021 23:31:53 +0100 (CET) schrieb "Carlos E. R." <robin.listas@telefonica.net>:
I'll have to keep watching and see...
If /proc/sys/kernel/panic is zero, keep watching.
In case it has a non-zero value, configure kdump to capture future crashes.
It is set to 90. What should I do with kdump? Where? I see in my backups that in 15.1 I had "/sbin/kdump", but the upgrade to 15.2 removed it. The same thing on this desktop machine. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <1632fff7-5ce8-2bc3-469e-df26ff3de21a@Telcontar.valinor> El 2021-01-23 a las 23:31 +0100, escribí:
Hi,
I was working at my desktop machine. My little server machine, media server, was playing the internet radio with Kodi. I went to the kitchen to put the dinner on the oven. On return, the media server had rebooted and was asking for login.
There is no trace in the syslog:
Just now, I noticed something unexpected in the log: <0.2> 2021-01-25T23:12:00.449044+01:00 Isengard kernel - - - [175645.133662] mce: CPU1: Core temperature above threshold, cpu clock throttled (total events = 124) <0.6> 2021-01-25T23:12:03.130449+01:00 Isengard kernel - - - [175647.818556] mce: CPU1: Core temperature/speed normal <0.6> 2021-01-25T23:12:03.130542+01:00 Isengard kernel - - - [175647.818567] mce: CPU0: Core temperature/speed normal This is not typical. The machine was running kodi, I was listening to a radio station over internet - same as the other day when it crashed. CPU load was low, but then I realized that the fans were not working. They are externally powered and the power supply had got loose in its socket. The case was also warm. CPU core temp was about 80, now it is down to 60..50°C. That could be the cause of the crash, but this machine when it gets hot it simply slows down. It is actually fanless, but I added external silent fans. And when it heats up, the event is logged. I have loaded it to full cpu for hours in the past with no issue, it just throttles down - or I use cpulimit to slow down those long processes. I will want to log the temps with a cronjob somehow. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYA9RURwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVm00An3FEzCrg4k9DI1cR8uTf MDXdlr3AAJ445ttly+KMC4HCjGyN+4DX1SLLvw== =/znP -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2021-01-23 at 23:31 +0100, Carlos E. R. wrote:
Hi,
I was working at my desktop machine. My little server machine, media server, was playing the internet radio with Kodi. I went to the kitchen to put the dinner on the oven. On return, the media server had rebooted and was asking for login.
There is no trace in the syslog:
...
I'll have to keep watching and see...
Another day I observed that the fans were not running (they are external) and the machine was too hot. I thought that was all. Well, just now it crashed while I was seated there. I had told kodi to play an internet radio (same as the other day). After few minutes the sound went into a loop. There was no response to keyboard. I tried to ssh-in, got: cer@Telcontar:~> ssh -X cer@isengard.valinor ssh: connect to host isengard.valinor port 22: No route to host I touched the machine, it was cold and the fans turning. The sound was still playing in a short loop. I waited a minute or so, then the machine rebooted on its own. Again, there is no indication on syslog: <1.5> 2021-02-02T10:30:03.574151+01:00 Isengard Sistema - - - Logging the current external IP= 83.53.59.39 <1.5> 2021-02-02T11:00:02.875404+01:00 Isengard Sistema - - - message repeated 2 times: [ Logging the current external IP= 83.53.59.39] <3.6> 2021-02-02T11:00:04.132961+01:00 Isengard systemd 1 - - Started Timeline of Snapper Snapshots. <3.6> 2021-02-02T11:00:04.264927+01:00 Isengard dbus-daemon 1102 - - [system] Activating service name='org.opensuse.Snapper' requested by ':1.1549' (uid=0 pid=10682 comm="/usr/lib/snapper/systemd-helper --timeline ") (using servicehelper) <3.6> 2021-02-02T11:00:04.522231+01:00 Isengard dbus-daemon 1102 - - [system] Successfully activated service 'org.opensuse.Snapper' <3.6> 2021-02-02T11:11:38.247462+01:00 Isengard named 2039 - - chase DS servers resolving '75.98.34.in-addr.arpa/DS/IN': 80.58.61.250#53 <3.6> 2021-02-02T11:11:40.287569+01:00 Isengard named 2039 - - network unreachable resolving '98.34.in-addr.arpa/NS/IN': 2001:13c7:7010::53#53 <3.6> 2021-02-02T11:11:40.288186+01:00 Isengard named 2039 - - network unreachable resolving '98.34.in-addr.arpa/NS/IN': 2001:dd8:6::101#53 <3.6> 2021-02-02T11:11:40.288559+01:00 Isengard named 2039 - - network unreachable resolving '98.34.in-addr.arpa/NS/IN': 2001:43f8:110::10#53 <3.6> 2021-02-02T11:11:40.288934+01:00 Isengard named 2039 - - network unreachable resolving '98.34.in-addr.arpa/NS/IN': 2001:500:87::87#53 <3.6> 2021-02-02T11:11:40.289276+01:00 Isengard named 2039 - - network unreachable resolving '98.34.in-addr.arpa/NS/IN': 2620:37:e000::53#53 <3.6> 2021-02-02T11:11:40.289665+01:00 Isengard named 2039 - - network unreachable resolving '98.34.in-addr.arpa/NS/IN': 2001:67c:e0::1#53 <3.6> 2021-02-02T11:11:40.745253+01:00 Isengard named 2039 - - network unreachable resolving '98.34.in-addr.arpa/NS/IN': 2001:4860:4802:32::66#53 <3.6> 2021-02-02T11:11:40.785168+01:00 Isengard named 2039 - - REFUSED unexpected RCODE resolving '98.34.in-addr.arpa/NS/IN': 216.239.32.102#53 <3.6> 2021-02-02T11:11:40.824647+01:00 Isengard named 2039 - - REFUSED unexpected RCODE resolving '98.34.in-addr.arpa/NS/IN': 216.239.34.102#53 <3.6> 2021-02-02T11:11:40.825925+01:00 Isengard named 2039 - - network unreachable resolving '98.34.in-addr.arpa/NS/IN': 2001:4860:4802:34::66#53 <3.6> 2021-02-02T11:11:40.827178+01:00 Isengard named 2039 - - network unreachable resolving '98.34.in-addr.arpa/NS/IN': 2001:4860:4802:36::66#53 <3.6> 2021-02-02T11:11:40.828380+01:00 Isengard named 2039 - - network unreachable resolving '98.34.in-addr.arpa/NS/IN': 2001:4860:4802:38::66#53 <3.6> 2021-02-02T11:11:40.902889+01:00 Isengard named 2039 - - REFUSED unexpected RCODE resolving '98.34.in-addr.arpa/NS/IN': 216.239.36.102#53 <3.6> 2021-02-02T11:11:40.952670+01:00 Isengard named 2039 - - REFUSED unexpected RCODE resolving '98.34.in-addr.arpa/NS/IN': 216.239.38.102#53 <3.6> 2021-02-02T11:11:40.970985+01:00 Isengard named 2039 - - validating 36.75.98.34.in-addr.arpa/PTR: no valid signature found <1.5> 2021-02-02T11:15:02.173180+01:00 Isengard Sistema - - - Logging the current external IP= 83.53.59.39 <3.6> 2021-02-02T11:18:47.397233+01:00 Isengard named 2039 - - timed out resolving 'prisa-us-eu.map.fastly.net/A/IN': 1.1.1.1#53 <3.6> 2021-02-02T11:18:47.404468+01:00 Isengard named 2039 - - timed out resolving 'prisa-us-eu.map.fastly.net/AAAA/IN': 1.1.1.1#53 2021-02-02 11:27:04+01:00 - Booting the system now ================================================================================ Linux Isengard 5.3.18-lp152.60-default #1 SMP Tue Jan 12 23:10:31 UTC 2021 (9898712) x86_64 x86_64 x86_64 GNU/Linux <0.6> 2021-02-02T11:27:07.046507+01:00 Isengard kernel - - - [ 0.000000] microcode: microcode updated early to revision 0x411, date = 2019-04-23 <0.5> 2021-02-02T11:27:07.046951+01:00 Isengard kernel - - - [ 0.000000] Linux version 5.3.18-lp152.60-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP Tue Jan 12 23:10:31 UTC 2021 (9898712) - -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYBktRRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV+ZsAoIcm5G1nq8csiCtC8dxm C7IEHNDNAJ46lXGaKF3jQcVFS4HJqdOx3XRVMQ== =Dqyi -----END PGP SIGNATURE-----
participants (6)
-
Anton Aylward -
Carlos E. R. -
David C. Rankin -
Lew Wolfgang -
Olaf Hering -
Yamaban