Signaling Server's /var directory is at 100%

[mszodiac]

Hello everyone! Our CS1000's signaling server's /var directory is at 100% full. Being at 100% full, we've seen our VoIP calls go down unexpectedly, and Element Manager becoming unresponsive.

We do not have the root password (unfortunately). Is there another way to clear/delete files off of /var directory just with the admin credential?

Your soonest reply is extremely appreciated!

 

[janaya]

I think you can do it with the admin2 password. If you don't have them,, the instructions to change are in the NTP. Also somewhere in the /var is a log folder and it sounds like you may have some logs to remove.

John Anaya
Amdocs Inc.
ACSS/ACIS - CS1000 Rls 7.5/Call Pilot 5
ACSS/ACIS - SME - IP Office 8.0
APSS/APDS - Avaya UC Services

Public Profile

http://www.linkedin.com/pub/john-anaya/25/1b9/a9b/

 

[mszodiac]

I've tried deleting the files using admin2. However, if I show the permissions on the directories, it shows "rw --r nortel" only. I'm confused because as far as I know, nortel account was removed from Release 7.5.

 

[monkey101]

You can log into the ss using admin2 and use the freeDiskSpace command. That will clean up alot of stuff. I never backup the logs when doing this.

 

[bignose21]

You can reset the root password also with the install media, also in NTP (Security Fundamentals)

 

[mszodiac]

Thanks for your replies! I'm hesitant to reset the root password because the NTP says the BIOS must be a minimum 18 or it can crash the system AND I've crashed a system before doing this. It's really a catch 22 since. I do not know the root password and cannot run the command to confirm the BIOS level. I'll be trying this on the lab system today, so hopefully it will work this time.

 

[mszodiac]

I tried the password recovery but I get the error "Error: Cannot define device for /partition" Does anyone know why this is?

 

[davejohnh]

There is a patch that can be applied to this to stop it happening again, but you'll need to clear the directory files first. We had it happen twice in the space of a fortnight on 2 different systems