asterisk crash 2.0.5 Segmentation fault (core dumped)

[billybobxm]

I just had asterisk crash on me and cause the time sync error in 2.0.5 here is what the screen log had when it crashed.

-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
== Manager 'sendcron' logged off from 127.0.0.1
Segmentation fault (core dumped)

any ideas about this?

[williamconley]

last time i had that was an iax configuration issue. unloaded modules one at a time ... iax was the culprit so i just took it out (wasn't using it). in the end, that box was rebuilt (client had no interest in finding out what was wrong with IAX, it was just a test box to see if the system would work ...).

There are ways to get the core dump to tell you which module caused the segmentation fault, and once you know the module ... either don't load it or delete its configuration file and reload it from scratch (yes, you can screw up the settings of IAX and cause a segmentation fault).

that being said: if you were to list your entire setup ... it would be a lot easier to say where your likely fault is (scratch setups are prone to this, as are hybrid systems where configuration files have been edited extensively ...). I've never had a segmentation fault in a vicidialnow or vicibox installed system IF the GUI is used for all configuration. (so far!)

this is a marvelous example of why it's a good idea to backup your configuration files regularly (!!! ahhh! take me back to last month!)

[billybobxm]

His is a vicibox install I am not using iax so I might pull that module out. How do I find out what module caused the fault? Where do I setup the log config?

[williamconley]

segmentation fault diagnosis is not within the "vicidial forum" realm. it's not hard, just technical. search for a method to read the "core.dump" files, that's what they're for.

logger.conf is in /etc/asterisk, instructions for its use are part of the asterisk package

vicidial logging is in server setup in GUI, but there are more indepth logging features available in the running scripts (instructions are IN the scripts and are generally modification of the cron jobs that start the scripts to cause them to start in debug or super debug mode).

vicidial logs are in /var/www/astguiclient

asterisk logs are in /var/www/asterisk (unless you tell asterisk to put them somewhere else ...)

happy hunting.

the first time i found it, BTW, i found it by "noload"ing modules in groups until i isolated iax. the next time i found it by reading the core.dump.

it depends on how grievous (and quick) the segmentation fault is. if the system cannot run, you can easily dump modules and attempt to start asterisk all afternoon or until it fires, the load modules unti it faults again. if it's running ... you have to be more analytical while allowing the agents to use the system.

oh: i also had one crash every time someone tried to register. turned out they were trying to register with SIP to an IAX account. which should just be impossible, but crashed the system instead. (once, two years and several versions of asterisk ago).

[boybawang]

check your hardware, could be a memory problem, I had this experience before, asterisk crashing due to seg fault and core dumps, we had to replace the memory and reinstall

[billybobxm]

all i had to do was restart asterisk and it was up and running, i didn't have to unload any modules or anything. I am going to look into reading the core dump but I guess I am thinking this could be memory related.

[williamconley]

you never rebooted before posting?

you're one of those guys! Ahhhh ...

Vicidial requires daily restart. You cannot run this like a "run it 24/8/356" linux server.

And if you have a "fault" of any sort, attempt a reboot to resolve the issue before posting. if the same problem recurs (after less than 24 hours), then it's a problem. otherwise a morning reboot resolves it means it isn't a problem.

that being said, if you DO dig down and find a flaw within an underlying app that can be patched and allow for a 6 month "no reboot" ... we'd all love to hear it.

[billybobxm]

I didn't need to reboot to fix the problem. Asterisk crashed so I restarted asterisk to fix the time sync error and get vicidial working again. I was simply posting the reason asterisk crashed and wanted to see if anyone else had the same issue with asterisk.

I do a daily reboot on the server but for the sake of getting the room running I only restarted asterisk since there was only another 20 minutes left to the shift and vicidial didn't have a problem with it.