Summary:	ASTERISK-25516: Too many objects of the specified type (PJ_ETOOMANY). Failed to send Request msg OPTIONS.
Reporter:	Dmitriy Serov (Demon)	Labels:
Date Opened:	2015-11-02 06:41:25.000-0600	Date Closed:	2017-07-26 14:23:27
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Resources/res_pjsip
Versions:	13.6.0	Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) 2016_01_14__14_08_07.backtrace-threads.txt ( 1) 2016_01_14__14_08_07.full.tail.txt ( 2) 2016_01_14__14_10_07.backtrace-threads.txt ( 3) 2016_01_14__14_10_07.full.tail.txt
Description:	Periodically have trouble connecting via TLS. Restart the entire server temporarily helps to solve this problem. Could be wrong, but to version 13.6 (maybe 13.5) to this problem has not been noticed. In logs: {noformat} [2015-11-02 15:14:50] VERBOSE[32360] res_pjsip/pjsip_configuration.c: Endpoint nikomi is now Unreachable [2015-11-02 15:14:50] WARNING[27501] pjsip:     tsx0x7fca10935 .Failed to send Request msg OPTIONS/cseq=39950 (tdta0x7fc9ac3898c0)! err=70010 (Too many objects of the specified type (PJ_ETOOMANY)) [2015-11-02 15:14:50] ERROR[27501] res_pjsip.c: Error 70010 'Too many objects of the specified type (PJ_ETOOMANY)' sending OPTIONS request to endpoint <unknown> [2015-11-02 15:14:50] ERROR[27501] astobj2.c: bad magic number for object 0x7fca110bc878. Object is likely destroyed. [2015-11-02 15:14:50] ERROR[27501] astobj2.c: bad magic number for object 0x7fca110bc878. Object is likely destroyed. [2015-11-02 15:14:50] WARNING[16669] res_pjsip_pubsub.c: No registered subscribe handler for event call-info [2015-11-02 15:14:51] VERBOSE[15690] res_pjsip/pjsip_configuration.c: Contact 17382/2fde01cd8fa187d013d5d6f5ad16edc1 has been deleted [2015-11-02 15:14:51] VERBOSE[26128] res_pjsip_registrar.c: Added contact 'sip:17382@87.255.225.137:5060' to AOR '17382' with expiration of 5 seconds [2015-11-02 15:14:51] VERBOSE[15690] res_pjsip/pjsip_configuration.c: Contact 17382/2fde01cd8fa187d013d5d6f5ad16edc1 has been created {noformat} After the reboot, the following occurs: {noformat} [2015-11-02 15:27:50] VERBOSE[25161] res_pjsip/pjsip_configuration.c: Contact mihey/d8f385c654ff72c10a100ae41e7d8ea7 has been deleted [2015-11-02 15:27:50] VERBOSE[25152] res_pjsip_registrar.c: Added contact 'sip:mihey@195.39.210.75:26478;transport=TCP;rinstance=b28be0f6f6c0ba96' to AOR 'mihey' with expiration of 60 seconds [2015-11-02 15:27:50] VERBOSE[25161] res_pjsip/pjsip_configuration.c: Contact mihey/d8f385c654ff72c10a100ae41e7d8ea7 has been created [2015-11-02 15:27:51] VERBOSE[25161] res_pjsip/pjsip_configuration.c: Contact mihey/d8f385c654ff72c10a100ae41e7d8ea7 is now Reachable.  RTT: 80.545 msec [2015-11-02 15:27:51] ERROR[25158] pjsip:       tcpc0x7f540847 TCP connect() error: Connection refused [code=120111] [2015-11-02 15:27:51] WARNING[25158] pjsip:     tsx0x7f5408615 Failed to send Request msg OPTIONS/cseq=30258 (tdta0x7f53f8090750)! err=120111 (Connection refused) [2015-11-02 15:27:52] VERBOSE[25161] res_pjsip/pjsip_configuration.c: Contact kamilla926/03e7ac3c4d70f9f04ca28f3efb1cd684 has been deleted [2015-11-02 15:27:52] VERBOSE[25161] res_pjsip/pjsip_configuration.c: Endpoint kamilla926 is now Unreachable [2015-11-02 15:27:53] VERBOSE[25161] res_pjsip/pjsip_configuration.c: Contact pogudim/872d9943e36305857031e5941b6e696c is now Reachable.  RTT: 196.643 msec [2015-11-02 15:27:53] VERBOSE[25161] res_pjsip/pjsip_configuration.c: Endpoint pogudim is now Reachable [2015-11-02 15:27:53] VERBOSE[25203] res_pjsip/pjsip_configuration.c: Contact 17378/8844fcebe28526d84816c03c0e44bc1e has been deleted [2015-11-02 15:27:53] VERBOSE[25152] res_pjsip_registrar.c: Added contact 'sip:17378@87.255.225.137:5060' to AOR '17378' with expiration of 5 seconds {noformat} Assumption: Constant "Connection refused" overwhelms the limited list in PJProject.
Comments:	By: Asterisk Team (asteriskteam) 2015-11-02 06:41:27.003-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Rusty Newton (rnewton) 2015-11-04 18:52:38.233-0600 Can you describe more about the environment in which this happens? How many channels are up and of what types? How much traffic until this issue occurs? Can you provide some examples of the pjsip configuration and call flow? By: Asterisk Team (asteriskteam) 2015-11-19 12:00:22.178-0600 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Dmitriy Serov (Demon) 2016-01-14 06:14:21.848-0600 Two segfaults. (Second after restart, of course, through 2 minutes). [2016-01-14 14:05:28] WARNING[6309] pjsip:        tsx0x359e728 .Failed to send Request msg OPTIONS/cseq=9501 (tdta0x6d1e1e0)! err=70010 (Too many objects of the specified type (PJ_ETOOMANY)) [2016-01-14 14:05:28] ERROR[6309] res_pjsip.c: Error 70010 'Too many objects of the specified type (PJ_ETOOMANY)' sending OPTIONS request to endpoint <unknown> [2016-01-14 14:09:38] WARNING[22845] pjsip:     tsx0x7fbbec062 .Failed to send Request msg OPTIONS/cseq=20465 (tdta0x7fbbe8267130)! err=70010 (Too many objects of the specified type (PJ_ETOOMANY)) [2016-01-14 14:09:38] ERROR[22845] res_pjsip.c: Error 70010 'Too many objects of the specified type (PJ_ETOOMANY)' sending OPTIONS request to endpoint <unknown> By: Oleksandr Natalenko (post-factum) 2016-05-18 12:08:59.008-0500 Got the same issue with Asterisk 13.9.1 + TLS trunk (SIPNET). There are 6 UDP trunks and 1 TLS, and only TLS suffers from this issue. pjproject is of version 2.4.5. Here is my pjsip.conf: https://gist.github.com/9d0b3f4af449e700f1f5646c09ad0fe3. TLS variant of SIPNET trunk that fails with the error posted above is located at lines 128–146. Please reopen the ticket. By: Joshua C. Colp (jcolp) 2016-05-18 12:15:26.220-0500 [~post-factum] Only the original reporter can reopen this issue, please create a new issue. By: Dmitriy Serov (Demon) 2016-05-18 12:26:40.959-0500 I can't find how to reopen issue I'll reopen it as soon as know how to do this By: Asterisk Team (asteriskteam) 2016-05-18 12:26:41.150-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Rusty Newton (rnewton) 2016-06-17 15:42:45.889-0500 [~Ares] please attach your configuration to the ticket (and make it clear that it is your configuration). Can you provide a step by step description on how to reproduce the failure? Or does it fail randomly for you ? By: Rusty Newton (rnewton) 2017-07-25 17:23:24.868-0500 Dmitriy can you verify whether this issue occurs in the most recent 13, 14 or Master? We have fixed a lot of issues since 13.6 and I'm wondering if this has been resolved since we haven't seen any more reports on this one. By: Dmitriy Serov (Demon) 2017-07-26 02:30:03.519-0500 Guess that bug was fixed. Log doesn't contain "PJ_ETOOMANY". Where is no troubles with PJSIP+TLS By: Rusty Newton (rnewton) 2017-07-26 14:23:27.675-0500 Thanks. Closing this out as "cannot reproduce". If someone encounters the issue in a more recent version, please open a new issue with fresh/recent debug and configuration.