CM server perform by itself a reboot

Doc ID    SOLN215368
Version:    1.0
Status:    Published
Published date:    05 Sep 2013
Author:   
Juan Gabriel Ayala Cedillo
 

Details

system rebooted approx 11:15 EST - rqst for reason
init@Fox-server1> uptime
11:48:28 up 21 min, 2 users, load average: 0.03, 0.04, 0.05init@Fox-server1> restartcause
RESTART CAUSES for Fox-server1
Cause Action Escalated Mode Time
Initialized 4 (RELOAD) no Active 05/21 12:01
Initialized 4 (RELOAD) no Active 05/21 13:33
Craft Request 4 (RELOAD) no Active 05/21 14:21
Craft Request 4 (RELOAD) no Active 05/21 14:22
Initialized 4 (RELOAD) no Active 05/21 14:27
Initialized 4 (RELOAD) no Active 05/21 14:47
Initialized 4 (RELOAD) no Active 06/03 14:19
Craft Request 4 (RELOAD) no Active 06/03 14:31
Craft Request 4 (RELOAD) no Active 06/03 14:38
Initialized 4 (RELOAD) no Active 06/04 15:46
Initialized 4 (RELOAD) no Active 06/17 13:07
Software Request 1 (WARM) no Active 03/08 13:44
Initialized 4 (RELOAD) no Active 11/28 11:30

init@Fox-server1> swversion

Operating system: Linux 2.6.11-AV24 i686 i686

Built: Oct 4 15:33 2007

Contains: 00.0.825.4

CM Reports as: R015x.00.0.825.4

CM Release String: S8500-015-00.0.825.4

UPDATES:

Update ID Status Type Update description

------------------------------- ------------ ------- ---------------------------

00.0.825.4-15467 activated cold patch 15467 for 00.0.825.4

Platform/Security ID Status Type Update description

------------------------------- ------------ ------- ---------------------------

PLAT-rhel4-1000 activated hot SSP 1-pcre security update

　

CM Translation Saved: 2012-11-29 01:00:15

CM License Installed: 2008-08-15 11:06:51

CM Memory Config: Standard

Problem Clarification

system rebooted approx 11:15 EST - rqst for reason

Cause

Unknown CM server logs previous to reboot it doens´t contains logs in around 10 hours previous to outage.

Logs

root@S8500> more 2012-1126-114804.log  >>> It is the file log previous to 11:30 yesterday >>>
20121127:012030523:23904691:hmm(9645):MED:[CM5_proc_err: pro=7171,err=200,seq=39 951,da1=85(0x55),da2=0(0x0)]  >> Last log 2012 Nov 27 at 01:20 hours >>
 
root@S8500> more 2012-1128-112921.log  >> It is immediate next file log >>>
20121128:112922611:100:LIC(9497):HIGH:[doReq: ValidLicense for appId 0 failed 00  >>> It is the reboot process by itself >>

Solution

CM version so old 5.0.0.825.4 unable to escalate with T4 action recommende upgrade to Cm 5.2.1.016.4 path 19880 after Cm 5.0.0.X until CM 5.2.1. thera are sevreal CM fixes in sense to prevent some CM server reboots induced by PBX by itself.


Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy