Rate of OpenSER’s (212.249.15.4) internal errors
Emin Gabrielyan
2007-06-12
It seems that after introduction of forced restarts every 4 hours (by Christian Lathion), the operation of the OpenSER SIP server at 212.249.15.4 is stabilized:
openser2:~/aa# cat /root/openser_restart.sh
#!/bin/sh
/etc/init.d/openser restart
echo "`date` OpenSER restarted" >> /var/log/openser_restart.log
echo "`date` OpenSER restarted" >> /var/log/ser.log
openser2:~/aa#
openser2:~/aa# cat /var/log/openser_restart.log
Mon Jun 11 12:01:03 CEST 2007 OpenSER restarted
Mon Jun 11 16:01:03 CEST 2007 OpenSER restarted
Mon Jun 11 20:01:04 CEST 2007 OpenSER restarted
Tue Jun 12 00:01:04 CEST 2007 OpenSER restarted
Tue Jun 12 04:01:04 CEST 2007 OpenSER restarted
Tue Jun 12 08:01:03 CEST 2007 OpenSER restarted
Tue Jun 12 12:01:04 CEST 2007 OpenSER restarted
openser2:~/aa#
Here is the histogram of the number of hourly errors for the past 7 days (in the logarithmic scale):
The chart represents total 203’065 fatal errors. The log of first 1000 errors is provided [log]. Such errors signify that the SIP server is seriously damaged and almost all calls are lost. The current configuration file of OpenSER is here [cfg].
Starting from 2007-06-11 (Monday), we see on the chart seven short histograms. Each of these short histograms represents 29 initialization records logged at each restart of OpenSER. These histograms appear every 4 hour according to crontab:
openser2:~/aa# crontab -l
# m h dom mon dow command
01 */4 * * * /root/openser_restart.sh
openser2:~/aa#
The same chart in non-logarithmic scale:
The text [txt] and excel [xls] files contain the commands required for computation of the shown charts.
* * *