[rbak-nsp] Process like pppd,sshd,inetd crashing frequently

Larry Jones ljones at mta-telco.com
Fri Jan 28 00:08:06 EST 2011 

I just upgraded my nine SE800s to 6.2.1.6 this week.
The prior 6.2.1.x releases were very buggy from my experience

From: Navin Nepali [mailto:navin_n at yahoo.com]
Sent: Thursday, January 27, 2011 7:51 PM
To: redback-nsp at puck.nether.net; Larry Jones
Subject: RE: [rbak-nsp] Process like pppd,sshd,inetd crashing frequently


Currently i am running Redback Networks SmartEdge OS Version SEOS-6.2.1.2-Release

Thanks

--- On Fri, 1/28/11, Larry Jones <ljones at mta-telco.com> wrote:

From: Larry Jones <ljones at mta-telco.com>
Subject: RE: [rbak-nsp] Process like pppd,sshd,inetd crashing frequently
To: "Navin Nepali" <navin_n at yahoo.com>, "redback-nsp at puck.nether.net" <redback-nsp at puck.nether.net>
Date: Friday, January 28, 2011, 10:18 AM

I’ve seen things like this in the past. What release are you  running?



From: redback-nsp-bounces at puck.nether.net [mailto:redback-nsp-bounces at puck.nether.net] On Behalf Of Navin Nepali
Sent: Thursday, January 27, 2011 7:38 PM
To: redback-nsp at puck.nether.net
Subject: [rbak-nsp] Process like pppd,sshd,inetd crashing frequently



Hello!



Strangely last night my SE800 start behaving abnormally. The process like statd, aaad,pppd,sshd, inetd etc started crashing frequently. I reloaded the system, after that for some period of time the system was normal but again the process started crashing.



Right now I have switched XCRP3 card to the standby one and it seems ok till now.



Can sshd cause these problem? I mean due to excessive ssh connection request?..for now i have disabled sshd service to check.



In the log, i see the message like this:

[ntc]NT-SE800#show log
Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/3114]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/3351]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/3464]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/3529]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/3698]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/4715]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/4798]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/4923]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/4925]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/5033]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/5707]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/5816]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/5858]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/5957]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/6131]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/6225]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/6229]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/6235]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 04:49:56: %LOG-6-SEC_ACTIVE: Jan 28 04:49:56: [0002]: [3/1:1023:63/6/2/6955]: %ISM-6-INFO: [ism2_cct_reg_timer_clear] Forcing
 SUB_SESS_DOWN_CPLT

Jan 28 05:04:04: %LOG-6-SEC_ACTIVE: Jan 28 05:04:04: [255/22:1:27/6/2/11745]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_P
USH_SUB_FINAL_ACCT  cib ptr = 0x426f5d80  flags = 40

Jan 28 05:04:04: %LOG-6-SEC_ACTIVE: Jan 28 05:04:04: [255/22:1:27/6/2/9585]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_PU
SH_SUB_FINAL_ACCT  cib ptr = 0x42fe2dbc  flags = 40

Jan 28 05:04:04: %LOG-6-SEC_ACTIVE: Jan 28 05:04:04: [255/22:1:27/6/2/1237]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_PU
SH_SUB_FINAL_ACCT  cib ptr = 0x42fe22b8  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/14590]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_P
USH_SUB_FINAL_ACCT  cib ptr = 0x42fe25c4  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/14574]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_P
USH_SUB_FINAL_ACCT  cib ptr = 0x42fe2d08  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/14401]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_P
USH_SUB_FINAL_ACCT  cib ptr = 0x42fe2ba0  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/14346]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_P
USH_SUB_FINAL_ACCT  cib ptr = 0x42fe29c0  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/14284]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_P
USH_SUB_FINAL_ACCT  cib ptr = 0x42fe281c  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/6798]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_PU
SH_SUB_FINAL_ACCT  cib ptr = 0x42fe2498  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/5465]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_PU
SH_SUB_FINAL_ACCT  cib ptr = 0x42fe2420  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/5223]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_PU
SH_SUB_FINAL_ACCT  cib ptr = 0x42fe23a8  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/4193]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_PU
SH_SUB_FINAL_ACCT  cib ptr = 0x42fe2ee8  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/4027]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_PU
SH_SUB_FINAL_ACCT  cib ptr = 0x42fe2d80  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/4001]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_PU
SH_SUB_FINAL_ACCT  cib ptr = 0x42fe2984  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/3544]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_PU
SH_SUB_FINAL_ACCT  cib ptr = 0x42fe2eac  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/3439]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_PU
SH_SUB_FINAL_ACCT  cib ptr = 0x42fe2150  flags = 40

Jan 28 05:04:05: %LOG-6-SEC_ACTIVE: Jan 28 05:04:05: [3/1:1023:63/6/2/3219]: %STAT-3-ERR_MEM: Bad circuit was created by CCRT_PPA_PU
SH_SUB_FINAL_ACCT  cib ptr = 0x42fe2f60  flags = 40







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20110128/13e3db14/attachment-0001.html>

More information about the redback-nsp mailing list