Avaya S8300 embedded sip suddenly stops working

[lefthander]

Hi All,

We are using an Avaya S8300/G350, with cm 5.2.1 and also using its embedded sip server. After more than 3 years of use, suddenly the embedded sip server stopped working. With the statapp command, all services are up and running except the sip with output: SipServer 2/34 partially up. We already made a reboot/restart of the whole system, but still the same result. Also, the sip server web page cannot be accessed and displays the below details:

An error has occurred in the administration framework.
Failed to connect to the database.
Check the Host DB Password.
host: 127.0.0.1
Message: DB Error: connect failed.

Anybody who may have come across a solution to this one?

Regards,
Lefthander

 

[telcoguy]

You need specialist help to solve this.
This error has to do with a bug that causes the partition assigned to SES to run out of space.

According to Avaya:
Solution:
SES filesystem needs to be cleaned up, need to have SES ADE engaged for that.
However, the root cause is: this problem is caused by a CM bug which causes the watchdog process to stop,
which eventually causes SES's small partition to get full.
The CM bug causes a crond problem, which will cause "log rotation" not to function properly.
This causes the above issue.
Install latest CM 5.2.1 Service Pack (SP15 at time of occurrence) on the system.
To resolve please delete the old logs so that the space comes down and then restart the postgresql services,
if it doesn't come up please do reinitdb which will wipe out the SES database.
SES came up after reinit db.

 

[lefthander]

thanks telcoguy for the response...

is there a way to delete the log files via shell access?

 

[telcoguy]

You have a corrupted system, This is an Avaya job unfortunately.
Like mentioned above, "need to have SES ADE engaged for that" (application team)
I doubt you would have the required access rights.
Get in contact with Avaya, and mention you have an issue like described in SOLN231209.