Thread Info
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 5453 views
  • Users 0 members are here
Options
Suggested

SG105 lockup / crash

jamesharper

My SG105 with 17.0 Beta 2 on it just became completely unresponsive. No icmp or arp. I connected a serial console and nothing responded, indicating that there was a kernel crash in play. I didn't have a screen I could connect so I couldn't be sure.

In my experience sometimes Linux will log some kernel messages leading up to a crash. If this is the case, what logfile might I look in for this?

If it happens again I will look into hooking up a serial cable to a server to catch anything that happens.

Thanks

James

Parents Reply Children
  • in reply to jamesharper

    Hi James,

    Thank you for the feedback.

    Please share the syslog.log

  • in reply to deeptibhavsar

    Nothing interesting in there. Here is the relevant section

    Oct  9 17:15:13 (none) local0.info [ctipd][5433]: CEnginesContainer::UpdateSettings() - Updating
    Oct  9 17:15:13 (none) local0.info [ctipd][5433]: CEnginesContainer::UpdateSettings() - Updating
    Oct  9 18:15:08 (none) local0.info [ctipd][5433]: CIpRepCache::Save() - Saved to file /tmp/ctipd.cache_v6
    Oct  9 18:15:08 (none) local0.info [ctipd][5433]: CIpRepCache::Save() - Saved to file /tmp/ctipd.cache
    Oct  9 18:15:12 (none) local0.info ctasd[5899]: Save SenderID lists
    Oct  9 18:15:12 (none) local0.info ctasd[5899]: Save SenderId lists finished
    Oct  9 18:15:13 (none) local0.info [ctipd][5433]: CEnginesContainer::UpdateSettings() - Updating
    Oct  9 18:15:13 (none) local0.info [ctipd][5433]: CEnginesContainer::UpdateSettings() - Updating
    Oct  9 19:00:09 (none) syslog.info syslogd started: BusyBox v1.21.1
    Oct  9 19:00:09 (none) user.notice kernel: klogd started: BusyBox v1.21.1 (2017-10-03 18:43:19 UTC)
    Oct  9 19:00:09 (none) user.notice kernel: [    0.000000] Linux version 3.14.22-Aum (root@kar-nsgci-node-03) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #1 SM
    P Tue Oct 3 18:41:54 UTC 2017
    Oct  9 19:00:09 (none) user.info kernel: [    0.000000] e820: BIOS-provided physical RAM map:
    Oct  9 19:00:09 (none) user.info kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000099bff] usable
    Oct  9 19:00:09 (none) user.info kernel: [    0.000000] BIOS-e820: [mem 0x0000000000099c00-0x000000000009ffff] reserved
    Oct  9 19:00:09 (none) user.info kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    Oct  9 19:00:09 (none) user.info kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000799a6fff] usable

    the crash happened sometime after 18:15, and I powered cycled it around 19:00. No indication of a problem beforehand.

    I guess i'll just have to see if it happens again!

    James

Unfiltered HTML