[asterisk-bugs] [JIRA] (ASTERISK-28560) do_monitor Thread hangs on 99% cpu and doesn't respond

[Eike Maier (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eike Maier updated ASTERISK-28560:
----------------------------------

    Attachment: gdb_do_monitor_thread_hanging.txt

gdb Trace of the do_monitor thread when hanging on 99% CPU

> do_monitor Thread hangs on 99% cpu and doesn't respond
> ------------------------------------------------------
>
>                 Key: ASTERISK-28560
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28560
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Registration
>    Affects Versions: 13.29.0
>         Environment: CentOS 7.5, 2 Cores, 16GB RAM, Gigabit ethernet, XCP hosted VM
>            Reporter: Eike Maier
>         Attachments: gdb_do_monitor_thread_hanging.txt
>
>
> We have a small Asterisk PBX with about 50 to 70 extensions, 5 simult. calls and are using the queue app. 
> We're using some realtime functions like dynamic realtime for queue, queue member, queue log, moh and voicemail.
> Most of the other config files are used via static realtime. 
> When we're having some calls on our PBX and there are registers at the same time, sometimes the do_monitor thread of asterisk hangs on 99% CPU and doesn't respond to any input. The chan_sip module isn't doing anything after that. Most of the time, only a restart is solving this state.
> This state happens at least 2 times a day and is a bit annoying to reproduce.
> We're using a small modification, to ensure the sippeer table is updated, like via dynamic realtime, but this happens even without the modification.
> I have the output of core show locks and core show threads, a gdb trace could be done the next time, this happens.



--
This message was sent by Atlassian JIRA
(v6.2#6252)