Hey Everyone, I've been running a version of the CVS without issue until late last week when suddenly Asterisk would randomly hit 99% CPU and stop registering my DIDs.
If I stop Asterisk with a 'stop now' and restart Asterisk all is well... for a bit. So far I have deducted the following. Happens randomly during day and night - not at present times nor frequency Happens when no calls are present (it is a very low usage test box) If console is left open with high verbosity no errors are reported, CPU usage just climbs to 99% and the DIDs die - I only know because of Nagios and the DIDs ring busy. 'top' clearly lists Asterisk as the CPU hog. both 'uptime' and 'top' confirm the usage and the culprit. The server is at a data centre and is hardly used. It is only used for Asterisk. I have looked at all the other logs and cannot find any thing else creating entries - mail, messages, boot, anything. As I said the server does very little so it would be easy to see other entries. The Asterisk logs show nothing out of the ordinary. The machine does not have any digium hardware in it, it uses SIP for inbound and IAX for outbound. Basic calling card and voicemail functions. I can move to a newer CVS but that seems like new variables... I know this one was working and still works on a local test box using the providers. I am mainly looking to find the best way to see where Asterisk is getting stuck (some type of loop?) J _______________________________________________ Asterisk-Users mailing list [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
