<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 7, 2016 at 11:03 AM, Olivier <span dir="ltr"><<a href="mailto:oza.4h07@gmail.com" target="_blank">oza.4h07@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="gmail-h5">2016-09-06 14:37 GMT+02:00 George Joseph <span dir="ltr"><<a href="mailto:gjoseph@digium.com" target="_blank">gjoseph@digium.com</a>></span>:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span>On Tue, Sep 6, 2016 at 1:55 AM, Olivier <span dir="ltr"><<a href="mailto:oza.4h07@gmail.com" target="_blank">oza.4h07@gmail.com</a>></span> wrote:<br></span><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div dir="ltr"><div><div><div><div><div><div><div><div>Hello,<br><br></div><span>After testing <span>"pkill -SEGV -f /usr/sbin/asterisk" on Debian Jessie platform, I've got several questions :<br><br><br></span></span></div><span><span>1. When I issue a "cd /tmp; asterisk -cvvvvvvvvvvvg -U asterisk -G asterisk" command, and then issue a "pkill -SEGV asterisk" command,<br></span></span></div><span><span>I can read on Asterisk console:<br>*CLI> Segmentation error (core dumped)<br></span></span></div><span><span>(*) I translated into english the exact output I got.<br><br></span></span></div><span><div><span>I see a /tmp/core file exists.<br></span></div><div><span><br></span></div><span>My asterisk.conf includes:<br>full = verbose,notice,warning,error,d<wbr>ebug<br><br></span></span></div><span><span>After Asterisk's stop, my /var/log:asterisk/full doesn't include any mention to Segmentation error.<br></span></span></div><span><div><span>I cannot find anything in dmesg, /var/log/messages or /var/log/kern.log as I did when a real segmentation fault occurred on production system.<br></span></div><div><span><br></span></div><span>I would expect Asterisk to log something.<br></span></span></div><span><div><span>Is this expected behaviour ?<br></span></div></span></div></blockquote><div><br></div><div>Yes. Asterisk can't really log anything when it ends abruptly because of critical signals like SEGV and since it was user initiated, rather than an actual SEGV, there won't be a message in the kernel log buffer.</div><span><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div dir="ltr"><div><span><br><br>2. </span><span>When I issue a "cd /tmp; systemctl start asterisk" command, and then issue a "pkill
-SEGV asterisk" command,<br></span><span>I can read on Asterisk console:<br>Disconnected from Asterisk server<br>Asterisk cleanly ending (0).<br>Executing last minute cleanups<br><br></span></div><span></span><div><div><div><div><div><span>I cannot find any core file anyware.<br><br></span></div><div><span>File </span><span>/var/log:asterisk/full doesn't include any mention to Segmentation error.<br><br></span></div><div><span>Where should core file be created when Asterisk is run as a daemon by asterisk user and group ?<br></span></div><div><span>Is there a setting I can use to specify the directory used (so that we can make sure appropriate ownership is set) ?<br></span></div></div></div></div></div></div></blockquote><div><br></div></span><div>"$ sysctl kernel.core_pattern" will show you where core files are written. For Asterisk to produce the core file, it has to be started with the '-g' option so make sure your asterisk.service file is adding the option. </div><div><div><div><br></div></div></div></div></div></div></blockquote><div><br></div></div></div><div>My system shows:<br># ps aux | grep asteri<br>asterisk 429 7.3 2.4 59468 25088 ? Ssl 18:47 0:03 /usr/sbin/asterisk -U asterisk -G asterisk -g<br>...<br># sysctl kernel.core_pattern<br>kernel.core_pattern = core<br></div></div></div></div></blockquote><div><br></div><div>Since "core" is a relative file name, the file will be in whatever the working directory is for the process. You may have to hunt it down. For better debugging, you might want to set core_pattern to something like " /tmp/core-%e-%t". That way all core files will have a name like "/tmp/core-asterisk-1473164587.7705". "man core" should give you more info on constructing the file name.<br><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>Option -g is present.<br></div><div><br></div><div>So either, the "pkill -SEGV asterisk" command doesn't trigger any coredump "<span><span>Asterisk cleanly ending (0)",<br></span></span></div><div><span><span>either the core dump is not produced (find / -name "core.*" doesn't find anything) for some reason.<br></span></span></div><div><div class="gmail-h5"><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div><div></div><div><br></div></div></div></div></div></div></blockquote></div></div></div></div></div></blockquote></div>
</div></div>