Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

R6 System Reboots! 2

Status
Not open for further replies.
djuplift

djuplift

IS-IT--Management
Jan 9, 2008
573
US
Getting random reboots and I cant seem to pin down why.

I have several traces with the reboots in them If any one has the time to take a look at the logs here is the zip file download link: any help would be greatly appreciated.

ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
JNCIA-EX
JNCIA-ER
JNCIA-FWV
Convergence+
 
Sort by date Sort by votes
The IPO may be losing contact with the SD Card
 
Upvote 0 Downvote
That would cause reboots? What would be the indication of this?

ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
JNCIA-EX
JNCIA-ER
JNCIA-FWV
Convergence+
 
Upvote 0 Downvote
Only two out of three shows a reboot but one is whit a call to a group ? and the other while some one calls voicemail.
Do you use announcement on the group ?
If yes then it could be possible that the SD card is the problem.
Stop the card and start it from SSA.
See if it helps, if it does then make a backupp of the card and format it with Manager or SSA.
Then recreate it with manager and use the backup to put back messages files etc etc

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

 
Upvote 0 Downvote
It cant be the SD card this is a v1 cabinet I should have mentioned that before.

ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
JNCIA-EX
JNCIA-ER
JNCIA-FWV
Convergence+
 
Upvote 0 Downvote
To clarify it is an IP500 V1 cabinet and was upgraded to R6 last week the problems started the following business day.

The voice mail service has failed on us a few times as well since the upgrade, after setting the service to restart after a failure we have not had any more noticeable failures I will have to check the logs to see if has been failing/restarting.

ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
JNCIA-EX
JNCIA-ER
JNCIA-FWV
Convergence+
 
Upvote 0 Downvote
Indeed do you mind telling me a little more about that CQ?

ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
JNCIA-EX
JNCIA-ER
JNCIA-FWV
Convergence+
 
Upvote 0 Downvote
Are there any older digital phones on the system? Had a system go into reboot cycle and it turned out it was on older 4424D+ causing the issue. Unplugged the phone and all reboots stopped.
 
Upvote 0 Downvote
Finally "CQ40206 - System Restart Every 3-4 days" again very vague, you should be able to click a CQ and bring up more detailed info really, as some don't help at all :)

ACSS (SME)
APSS (SME)

 
Upvote 0 Downvote
In your trace I see this:

72528063mS PRN: WARNING:
72528064mS PRN: Buffer pool 3 dropped below 898 - free 1098
72528064mS PRN:
72528103mS PRN: .+Buffer usage in pool 3, No. 1 user = f01f7780 f03b862c, 6172 buffers
72528103mS PRN: .+Buffer usage in pool 3, No. 2 user = f00b24f0 f01d69e4, 5999 buffers
72528104mS PRN: .+Buffer usage in pool 3, No. 3 user = f00b24f0 f01d6c34, 1999 buffers
72528104mS PRN: .+Buffer usage in pool 3, No. 4 user = 0 0, 1069 buffers
72528104mS PRN: .+Buffer usage in pool 3, No. 5 user = f01d633c f01d6c34, 390 buffers
72528104mS PRN: .+Buffer usage in pool 3, No. 6 user = f01d633c f01d69e4, 184 buffers
72528104mS PRN: .+Buffer usage in pool 3, No. 7 user = f03b75d4 f02d86a8, 49 buffers
72528104mS PRN: .+Buffer usage in pool 3, No. 8 user = f01a97e0 f01a9a54, 31 buffers
72528105mS PRN: .+Buffer usage in pool 3, No. 9 user = f01e94a0 f01a8dcc, 31 buffers
72528105mS PRN: .+Buffer usage in pool 3, No. 10 user = f04efd40 f04f29e8, 9 buffers
72528159mS PRN: .+Buffer usage in pool 3, No. 1 Ident = 32 , 6177 buffers
72528160mS PRN: .+Buffer usage in pool 3, No. 2 Ident = 0 , 5919 buffers
72528160mS PRN: .+Buffer usage in pool 3, No. 3 Ident = ff , 1358 buffers
72528160mS PRN: .+Buffer usage in pool 3, No. 4 Ident = 8 , 1275 buffers
72528160mS PRN: .+Buffer usage in pool 3, No. 5 Ident = a5 , 1073 buffers
72528160mS PRN: .+Buffer usage in pool 3, No. 6 Ident = 2c , 17 buffers
72528160mS PRN: .+Buffer usage in pool 3, No. 7 Ident = 30 , 10 buffers
72528161mS PRN: .+Buffer usage in pool 3, No. 8 Ident = 31 , 8 buffers

and there is this CQ out "CQ40260 - Memory leak with buffer pools 1 and 2 lead to system restart" maybe it effects pool 3 too :)

ACSS (SME)
APSS (SME)

 
Upvote 0 Downvote
They are "call parking" and I see a parked call timing out before every reboot, however when we tested this we could not recreate the issue... Anyone know when we are to expect a the next maintenance patch?

Would it be worth the time to take the system back to 5.0.18 until the patch is released?

ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
JNCIA-EX
JNCIA-ER
JNCIA-FWV
Convergence+
 
Upvote 0 Downvote
I would do, I have the latest release on test now so it will be next month it get released I imagine, the park does proceed this 14259440mS PRN: .FATAL TLB Data address=00003104 d=5 pc=f01f70e8 f01f7208 f032fccc f033009c f03301b0 f038ad70 IP 500 6.0(8)

And there are a quite few TLB errors in the system according to those traces :)

ACSS (SME)
APSS (SME)

 
Upvote 0 Downvote
So we have a memory leak and a call park problem awesome!!


ACA - Implement IP Office
ACS - Implement IP Office
ACSS - SMEC (IP Office)
JNCIA-EX
JNCIA-ER
JNCIA-FWV
Convergence+
 
Upvote 0 Downvote
I had a buffer problem too but only one time.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

 
Upvote 0 Downvote
I have a 500v1 and have had it just randomly reboot 3-4 times now since upgrading to 6.0. My alarm email tells me that the system has restarted from power fail. Power hasn't failed as this is on UPS in a rack with a lot of servers and the IPO is the only one that has this "power failure". Unfortunately I haven't had a monitor trace running at the time. Just happened again this morning. I will start monitor now and let it run until it happens again.
 
Upvote 0 Downvote
Maybe your power supply is dying ?


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

 
Upvote 0 Downvote
Wouldn't that be affecting the other devices plugged into it though? None of the servers, switches or firewalls are having any issues.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

William C290
  • Solved
System Alarm 1
Replies
3
Views
260
John Tel
John Tel
vtt2019
  • Locked
  • Question
System Status - No PING
Replies
2
Views
308
AJA7
AJA7
DTGMI
  • Locked
  • Question
Updating H323 R6 SW on J179
Replies
2
Views
133
gwebster
gwebster
N
  • Locked
  • Question
System not running system SD primary software after non-mergeable SIP Trunk changes 5
Replies
12
Views
1K
derfloh
derfloh
PhonesTech
  • Locked
  • Question
Avaya IP office Reboots with Avaya Workplace apps
Replies
5
Views
192
vfotineas
vfotineas

Part and Inventory Search

Sponsor

Back
Top