ims_ipsec_pcscf crashes after the call #2970
Comments
miconda
changed the title
|
Colleagues, there is an opportunity to give a hint why it crashes ims_ipsec_pcscf ? |
|
Thanks for the report, can you install maybe kamailio debug symbols (e.g. from packages) and do the backtrace again? The initial one is missing any detailed information. |
|
Thanks for the answer! Did I understand correctly that I need to install "kamailio-dbg"? I installed Kamailio via "apt install" from the repository. |
|
kamailio-dbg should do the trick |
I apologize, but the packages cannot install kamailio-dbg on Debian, the repositories do not have any kamailio-dbg, kamailio-debbug, kamailio-dbg. Maybe I need to include from the debbig module parameters https://www.kamailio.org/docs/modules/devel/modules/debugger.html? |
|
At least in the kamailio debian repository they are there: root@sbct1: # apt-cache policy kamailio-dbg |
|
If you're using the packages from official Debian repo try adding following
to your sources list
deb http://deb.debian.org/debian-debug bullseye main
…On Tue, Dec 28, 2021, 15:00 Henning Westerholt ***@***.***> wrote:
At least in the kamailio debian repository they are there:
***@***.***: # apt-cache policy kamailio-dbg
kamailio-dbg:
Installiert: (keine)
Installationskandidat: 5.5.3+bpo11
Versionstabelle:
5.5.3+bpo11 500
500 http://deb.kamailio.org/kamailio55 bullseye/main amd64 Packages
—
Reply to this email directly, view it on GitHub
<#2970 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABO7UZO7MWDJEOVSWZFXL5TUTG7HRANCNFSM5JZDNT7Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
_______________________________________________
Kamailio (SER) - Development Mailing List
***@***.***
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
|
|
Thanks for the tips. The old core is gone, but the new one. |
|
Updated Kamailio to: |
|
It looks like the second core dump back trace was from another child that stopped because of an error in another child. Do you have only this core dump, or are there others? If more, try to find the one with the process ID from the first log file output related to the crash. |
|
Sorry, wrong core |
|
Can this bt help with the concept of the problem? Or is it better to take the dump again, attach the log and bt? |
|
Hello, it crashed during the processing of an 183 message. Crashed function was fill_contact(..) in frame 0. You could investigate the passed data in this function to see why it crashed. Another idea would be to look to the SIP message that was processed to see if there was something unusual in it. |
|
Hi Eugeniy,
You need to install debug symbols as Henning mentioned and provide the
backtrace with symbols to investigate. If possible provide P-cscf logs and
Wireshark trace.
BR Aleksandar Yosifov
…On Tue, Dec 28, 2021 at 2:52 PM Eugeniy ***@***.***> wrote:
Colleagues, there is an opportunity to give a hint why it crashes
ims_ipsec_pcscf ?
—
Reply to this email directly, view it on GitHub
<#2970 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABO7UZO5JE2IPFKDMH4ESLLUTGXFNANCNFSM5JZDNT7Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
_______________________________________________
Kamailio (SER) - Development Mailing List
***@***.***
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
|
|
@alexyosifov If I do not misread it, I think the second backtrace was already done with debug symbols installed. |
Hi, Aleksandar. In the archive in the attachment a new dump, log and bt with debug symbols |
Hey! |
|
It seems that problem is not in contact parsing. I think that object are in some failed state In core dump we have what it seems to be a valid Contact field We have normal pointer to parsed object but object itself contains garbage. This is why no parsing is performed and this check passes. If we take I am not much into this code and unfortunately I am unable to find where this values are set. Are messages reused or created from scratch each time? The |
|
Friends, do you have any ideas about the problem? |
|
This issue is stale because it has been open 6 weeks with no activity. Remove stale label or comment or this will be closed in 2 weeks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Hi, I am a junior with Kamailio, if I show you where I am wrong, I will. Often during a call between two sip clients (located on the same subnet with pcscf) Kamailio P-CSCF crashes with a core dump. But sometimes the call goes through normally, I can’t see why this is happening.
Troubleshooting
Reproduction
It is reproduced often, the error is most likely somewhere with me.
Debugging Data
Log Messages
SIP Traffic
pcscf_dump.zip
Possible Solutions
Additional Information
kamailio -vkamailio_cfg.zip
kamailio_log.zip
The text was updated successfully, but these errors were encountered: