[asterisk-bugs] [JIRA] (ASTERISK-29098) pjsip: Crash in pjnath on cache timeout

Benjamin Keith Ford (JIRA) noreply at issues.asterisk.org
Wed Nov 4 12:30:15 CST 2020


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

Benjamin Keith Ford updated ASTERISK-29098:
-------------------------------------------

    Assignee: 钟明星
      Status: Waiting for Feedback  (was: Triage)

Unfortunately there's not really a way to reduce the size of the log files produced. If 10GB is too large, you could try just debug logs (not verbose), but ultimately both enabled would be best. As Kevin mentioned, we would probably just need the last portion of the logs. Do you have a log leading up to the crash? It can be compressed into something (like a tar file) and attached here if the file is too large.

> pjsip: Crash in pjnath on cache timeout
> ---------------------------------------
>
>                 Key: ASTERISK-29098
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29098
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 17.6.0, 17.8.0
>         Environment: centos 6.10
>            Reporter: 钟明星
>            Assignee: 钟明星
>              Labels: webrtc
>         Attachments: bt.txt, core.alast1-2020-09-26T15-00-47+0800-brief.txt, core.alast1-2020-09-26T15-00-47+0800-full.txt, core.alast1-2020-09-26T15-00-47+0800-info.txt, core.alast1-2020-09-26T15-00-47+0800-locks.txt, core.alast1-2020-09-26T15-00-47+0800-thread1.txt
>
>
> asterisk Frequency crash
> according to https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace



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



More information about the asterisk-bugs mailing list