Hi,
This is a shot in the wild, but you should check how memory-usage is for
ser.
turn the loglevel up, and look in /var/log/messages when this is
happening. it might happen that you are running out of shared memory.
I would also look at the nagios script for ser. This one you can modify
to make ser restart when it goes into a hang.
- Atle
* Weiter Leiter <bp4mls(a)googlemail.com> [060731 19:55]:
A monitoring app is good to have, but this won't
fix your problem. You
should get some pattern of events that trigger that state and ask for
developers help (if really needed and not some configuration error or broken
messages).
It could be that this behavior is just the most visible one among some other
service impending failures.
WL.
On 7/31/06, ram <talk2ram(a)gmail.com> wrote:
>
>Hi
>
>when i check the server is running
>iam able to see serctl moni, and serctl ps
>but the calls are not going, getting fast busy
>when i restart server, then i am able to make calls
>
>Moint does if the service down to restart
>but how do i check the calls are going out
>so restart services ?
>
>ram
>
>
>On 7/31/06, nick <nick(a)mobilia.it> wrote:
>>
>> ram wrote:
>> > Hi all
>> >
>> > Is any one here in the group used any call management software for SER
>>
>> >
>> > I have seen software for Asterisk hudlite, does any kind of software
>> for SER
>> >
>> > any one tested and report their experiences
>> >
>> > why iam asking is
>> >
>> > after Ser running some days
>> > i get this error in my syslog
>> >
>> > sl_reply_error used: I'm terribly sorry, server error occured (2/SL)
>> >
>> > that time my users not able to make call, i keep get fast busy, that
>> > time i need to reboot the Ser
>> > so calls again start going out side
>> >
>> > If any kind of monitoring software available or do automated job, when
>> > ever found that calls are not going
>> > then restart SER or some kind of solution should help the admin to
>> chek
>> > the logs, when the SER restarted.
>> >
>> > If not some one need to monitor constantly or wait for customer to
>> call
>> > to support \the calls are not going
>> >
>> > then we restart service will back the services, but i feel bad
>> practice,
>> > before customer realise some problem with
>> > server, the Admin able to fix the problem
>> >
>> > any suggestions will be appriciated.
>> >
>> > ram,
>> >
>> >
>> >
>> ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > Serusers mailing list
>> > Serusers(a)lists.iptel.org
>> >
http://lists.iptel.org/mailman/listinfo/serusers
>>
>> Run a cron job to check the logs every 5 minutes or so, and have it
>> restart the server if necessary..
>>
>> Monit can check to see if a server is up or down, but I don't know if
>> your server is up or down or if it's just locked up..
>>
>
>
>_______________________________________________
>Serusers mailing list
>Serusers(a)lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers
>
>
>
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers