@henningw we have stuck to db_mode 0, so the issue no longer resurfaces. It is
still present, however, with db_mode 1.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
Hi @henningw - yes, I do. I saw a similar problem on the mailing list and we
are also using RDS - perhaps that's the issue (deadlock?). It looks like this
happens on a record delete for the dialog - looks like db_mode 0 resolves this
- so far instances with that option enabled have not
(gdb) bt n
#0 0x7fab34880860 in __errno_location@plt () from
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#1 0x7fab348bb589 in ?? () from
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#2 0x7fab348bb849 in ?? () from
/usr/lib/x86_64-linux-gnu/libmysqlclient.so.20
#3
strings /usr/lib/x86_64-linux-gnu/libcrypto.so | grep "^OpenSSL"
OpenSSLDie
OpenSSL_add_all_ciphers
OpenSSL_add_all_digests
OpenSSL 1.0.2n 7 Dec 2017
OpenSSL HMAC method
OpenSSL EC algorithm
OpenSSL RSA method
OpenSSL DSA method
OpenSSL ECDSA method
OpenSSL DH Method
OpenSSL X9.42 DH method
@miconda yes, I do have a machine where the issue is reproduced, where can I
email the information? If you could reply to that email with your public key
I'll add that right away as well.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
@miconda just wanted to follow up on this - dumping those records should show
us what the issue might be, how can that be inspected?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
@miconda what would be the best way to dump the kamailio uac memory segments to
see those records and compare with actual registrations?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
@henningw will do that instead, thanks!
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1895#issuecomment-487394400___
Kamailio (SER) - Development
Upping bounty to $250
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1895#issuecomment-487283380___
Kamailio (SER) - Development Mailing List
@miconda We got rid of the trunks/accounts causing 500 errors and auth failure,
yet are still seeing the leak in the kamailio process.
Any other way to troubleshoot this?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
@miconda ~2000 matches for "authentication failed for"
~2800 matches for "got sip response 500 while registering"
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
@kamailio-sync could you please clarify? Not sure I understand
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1895#issuecomment-484844338___
Kamailio
also doubling the bounty for this, hoping the community would help us get a
stable 5.1.7+
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@miconda what I meant is the non-expiring registration records stored in memory
As to the error messages, those are about it, everything else is repetitive and
the remaining logs consist of registrations, test calls, etc.
Perhaps there's a good way to export all shm data related to uac?
--
@miconda the number of records in uacreg is significantly less than that, that
makes me wonder if the hash table cleanup is to blame
```
Apr 16 00:05:37 ip-10-0-0-0 kamailio[12057]: ERROR: uac [uac_reg.c:913]:
uac_reg_tm_callback(): authentication failed for
Apr 16 00:05:37 ip-10-0-0-0
Posting a $100 bounty on this issue if anyone wants to take a look.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
We also have a test system with the issue reproduced if a closer look is needed
@miconda
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@miconda any other info I can gather that would help locate the issue here? The
issue is recurring.
Thank you
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Another occurence:
```
11(8342) ERROR: usrloc [ucontact.c:100]: new_ucontact(): no more shm memory
11(8342) ERROR: usrloc [urecord.c:149]: mem_insert_ucontact(): failed to create
new contact
11(8342) ERROR: usrloc [urecord.c:573]: insert_ucontact(): failed to insert
contact
11(8342) ERROR:
@miconda -m 2048 -M 16
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1895#issuecomment-474684038___
Kamailio (SER) - Development
### Description
Kamailio runs out of memory and stops processing requests.
```
ERROR: [core/tcp_main.c:973]: tcpconn_new(): mem. allocation failure
ERROR: [core/tcp_main.c:4042]: handle_new_connect(): tcpconn_new failed,
closing socket
ERROR: uac [uac_reg.c:533]: reg_ht_add(): no more shm
Hi Daniel!
I'm experiencing a similar issue and so I thought I'd bump this thread.
`
Aug 16 19:45:18 km2 kamailio[799]: CRITICAL: [pass_fd.c:277]:
receive_fd(): EOF on 17
Aug 16 19:45:18 km2 kamailio[767]: ALERT: [main.c:740]: handle_sigs():
child process 772 exited by a signal 11
Aug 16
22 matches
Mail list logo
