-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recording crash #881
Comments
seems the error isn't always the same.. Nov 25 09:25:55 proxy1 kernel: rtpengine-recor[24317] general protection ip:3ee165eac4 sp:7fd291b55b00 error:0 in libglib-2.0.so.0.2800.8[3ee1600000+115000] Nov 25 10:24:04 proxy1 kernel: rtpengine-recor[26825]: segfault at 6ebc ip 000000000040d085 sp 00007fa84cfeeb80 error 4 in rtpengine-recording[400000+16000] Nov 25 10:43:26 proxy1 kernel: rtpengine-recor[29242] general protection ip:3edf27b93c sp:7f55af1cbba8 error:0 in libc-2.12.so[3edf200000+18b000] |
Open the core dump in gdb and post the output of If you're using a Debian packaged build, make sure the debug package is installed first. |
can you refresh me where is the dump file ? |
Really depends on your system, under systemd try /var/lib/systemd/coredump/ |
centos 6 and i don't find any coredump directory on the system. |
Can't help with CentOS unfortunately |
Syntax to start gdb is |
Core was generated by `/usr/sbin/rtpengine-recording --config-file=/etc/rtpengine-recording.conf --pid'. |
And the rest of the backtrace? Also which version is this? |
#0 0x0000003ee165eac4 in g_slice_alloc () from /lib64/libglib-2.0.so.0 [root@proxy1 tmp]# /usr/sbin/rtpengine-recording -v |
Looks like some sort of memory corruption issue. Are you able to run this through valgrind? Something like
|
==20322== Memcheck, a memory error detector |
Ah you have to add --foreground to the options |
valgrind --leak-check=full /usr/sbin/rtpengine-recording --config-file=/etc/rtpengine-recording.conf |
Don't really need the leak check, just keep an eye on reported errors like invalid reads or writes. |
Okay but i have to output on a file ? |
Depends on how much output you get. If it's too much for your terminal, you can write to a file with --log-file=... |
strange no crash anymore when launched with G_SLICE=always-malloc valgrind /usr/sbin/rtpengine-recording ... |
Maybe an issue with the glib slice allocator then. Try again with |
glib2.x86_64 2.28.8-10.el6 |
I have added the G_SLICE in init script and since then no crash anymore.... start() { |
Might be a problem with your glib then. Try looking for an updated package |
Hello,
The RTP Recording crash after 20 minutes of operation :)
I get this log in the syslog 👍
proxy1 kernel: rtpengine-recor[24317] general protection ip:3ee165eac4 sp:7fd291b55b00 error:0 in libglib-2.0.so.0.2800.8[3ee1600000+115000]
Can you help me to find the dump file and extract root cause ?
Thanks
The text was updated successfully, but these errors were encountered: