Mid Day Reboots

[lazzara]

In the last month our Mitel 5000 has shut down to force reboot unexpectedly 7 times, and I'm at a loss for what may be the culprit. Call processing logs and memory diagnostics don't seem to tell the story, and all I can gather from the syslog is that there is a signal 15 command being sent, but not what is tripping that command. We haven't made any changes short of changing some user extensions for over 2 months, and so there doesn't appear to be anything new to have caused these issues.
Here are the syslog values from today.
Feb 27 11:17:02 NK-5200 kernel: imklog 3.18.6, log source = /proc/kmsg started.
Feb 27 11:17:02 NK-5200 rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="528" x-info="http://www.rsyslog.com"] restart
Feb 27 12:26:42 NK-5200 reboot: PID-21294: ROMD is called for reboot
Feb 27 12:26:42 NK-5200 pppd[1128]: Terminating on signal 15
Feb 27 12:26:42 NK-5200 pppd[1128]: Connection terminated.
Feb 27 12:26:43 NK-5200 rch_app: Last commands that were sent to MSP :
Feb 27 12:26:43 NK-5200 rch_app: #012Thu Feb 27 12:25:56 2020#012, target - 1, channel - 0x0046, command - 801c, <---
Feb 27 12:26:43 NK-5200 rch_app: params -  0000 0006 0000 0000 0000 005B

Here is the reported resets. The Scheduled Delayed are intentional, but all others were major productivity interruptions.
12:28 02-27 MAJOR RESET:  Major Reset From Software Watchdog Thread
13:32 02-26 MAJOR RESET:  Reset Due To Termination Signal
13:28 02-26 MAJOR RESET:  Major Reset From Software Watchdog Thread
04:03 02-26 MAJOR RESET:  Scheduled Delayed Major
17:47 02-21 MAJOR RESET:  Major Reset From Software Watchdog Thread
12:22 02-21 MAJOR RESET:  Major Reset From Software Watchdog Thread
04:03 02-19 MAJOR RESET:  Scheduled Delayed Major
14:46 02-18 MAJOR RESET:  Reset Due to Too Many Sequential Exceptions
04:03 02-12 MAJOR RESET:  Scheduled Delayed Major
04:09 02-05 MAJOR RESET:  Reset Due To Termination Signal


Thanks for  taking a look, and any help pointing in the right direction to move on troubleshooting is greatly appreciated.

[Tech Electronics]

Lazzara,

Download your Watchdog logs and look at those.

Thanks,

TE


Sent from my iPhone using Tapatalk

[acejavelin]

Like TE said, check the Watchdog logs... The watchdog process watches other processes and looks for errors, if they occur it schedules a reboot, and if they are major enough it reboots immediately.

This could be any number of issues, from a hardware failure to a database inconsistency. My first step in this is usually backup and run the DB Clean tool and see if the database has any errors, and if it does do a restore.