[Spce-user] found sems had stopped

[Theo]

Ok there are indeed core files there "core.sems.sig6.24219" so clearly
something is crashing then... now to find out what.

On Fri, Feb 13, 2015 at 10:26 AM, Theo <axessofficetheo at gmail.com> wrote:

> Hi
>
> Thanks for that. I had already looked at sems.log and dmesg - nothing
> there that I can see at all?
>
> I am unsure what to do with /var/cores?
>
> - Monit - sure, but we're not ready for the PRO version :-) - I guess can
> just put that on ourselves in that case? or simply run a script that does
> the same?
>
> On Fri, Feb 13, 2015 at 10:13 AM, Victor Seva <vseva at sipwise.com> wrote:
>
>> On 02/13/2015 08:15 AM, Theo wrote:
>> > Hi all
>> >
>> > Calls were failing on our platform - I found sems had stopped running.
>> > Starting it fixed the issue - however I would like to find out why it
>> > was not running. I have not been able to find anything in the logs, but
>> > I may be looking in the wrong place. Where would I look for any clues?
>>
>> /var/log/ngcp/sems.log
>>
>> If sems crashed:
>>
>> /var/log/dmesg
>> /var/cores/
>>
>> > Secondly - to avoid this in future, would it be safe to run some cron
>> > job that checks the status of the various services and starts them if
>> > found not running and send an alert email when this happens and run it
>> > every couple of minutes.
>>
>> Implemented in PRO through monit
>>
>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20150213/51a37b9a/attachment-0001.html>