Hi Landry,

I'll try to debug it using debug-asterisk package. If I understand you right, 
should I remove original asterisk-18.3.0 package first and install debug-* one?

System load is about 0.4  0.3  0.3 according to top command. It is modern 
system with 8c/16t AMD 4750U. 98% resources are free.

But it can be old problem from this thread 
https://marc.info/?l=openbsd-bugs&m=158413759801240&w=2 system stuttering. 
Stuttering appeared on all machines I have before, and problem might be with 
OpenBSD's scheduler, but not found. Martin Pieuchot checked scheduler's code 
and didn't find anything which can cause the problem. On latest AMD 4750U 
machine stuttering minimally present too, which can possible cause some 
packages to crash.

During 6.7- to 6.9- I see that Python cause huge stuttering when some python 
program is run.

On modern CPU stuttering is not so obvious, but can affect on user-space 
programs behavior I suppose.

Martin

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, May 21, 2021 7:30 AM, Landry Breuil <[email protected]> wrote:

> Le Fri, May 21, 2021 at 06:56:15AM +0000, Martin a écrit :
>
> > Hi Stuart,
> > I'm having trouble with asterisk 18.3.0 from packages. Sometimes it crashes 
> > during runtime. Especially if SIP client reregisters from different 
> > locations (subnet).
>
> interestingly, i had asterisk 18.4.0 dying yesterday night, also on 6.9.
>
> safe_asterisk[91037]: Asterisk ended with exit status 139
> safe_asterisk[91037]: Asterisk exited on signal 11.
> safe_asterisk[91037]: Automatically restarting Asterisk.
>
> but at the same time influxdb was also badly crashing/spouting go debug
> msgs in syslog, so maybe that's related to system load.
>
> sadly i dunno if asterisk generated a coredump somewhere, and if so, where..
>
> > Could you recommend runtime debug procedure to find out what happened with 
> > it?
>
> the port has DEBUG_PACKAGES set, so install the debug symbols with
> pkg_add -d asterisk, restart the service, and when it crashes collect
> the trace with gdb from ports.
>
> also looking at its logs might help.. i dont have anything special in my
> logs.
>
> Landry


Reply via email to