[asterisk-bugs] [JIRA] (ASTERISK-23219) Asterisk restarts with increasing LA

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-23219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214674#comment-214674 ] 

Matt Jordan commented on ASTERISK-23219:
----------------------------------------

This:

{noformat}
 [Jan 15 14:28:11] WARNING[13861] channel.c: Channel allocation failed: Refusing due to active shutdown
{noformat}

comes from this:

{noformat}
	/* If shutting down, don't allocate any new channels */
	if (shutting_down) {
		ast_log(LOG_WARNING, "Channel allocation failed: Refusing due to active shutdown\n");
		return NULL;
	}
{noformat}

The variable {{shutting_down}} is only set to a non-zero value if {{ast_begin_shutdown}} is called:

{noformat}
void ast_begin_shutdown(int hangup)
{
	shutting_down = 1;

	if (hangup) {
		ao2_callback(channels, OBJ_NODATA | OBJ_MULTIPLE, ast_channel_softhangup_cb, NULL);
	}
}
{noformat}

{{ast_begin_shutdown}} is only called from {{can_safely_quit}} in {{asterisk.c}}, which - for all intents and purposes - is the handler for someone shutting down your system. So no, it didn't crash (hence the lack of core file), and yes, someone did shut down your system :-)
                
> Asterisk restarts with increasing LA
> ------------------------------------
>
>                 Key: ASTERISK-23219
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23219
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.15.0
>         Environment: hardware: 2 CPU xeon E5649, 36GB RAM, CentOS release 6.2 (Final), kernel 2.6.32-220.13.1.el6.x86_64, 
> asterisk version is  1.8.15-cert2.
>            Reporter: Nikolay
>
> We have found out the problem with unexpected abnormal asterisk behaviour.
> Symtpomps: In a company there is a callcenter with asterisk as a PBX. Network connection is made by SIP protocol. Didfferent amount of calls can arive to the callcenter. Some days the call quantity can equal 750 calls
> simaltaneously, some days amount is 200 calls  simaltaneously (some of calls are on operators of a queue, some calls are queued and wait for operator - that is normal situation in callcenter).
> Suddenly new calls cannot be made - calling party hears busy. The current calls ger dropped. Load Average of the server immidiately increases from 1.6 to approx. 170. 
> In fulllog of asterisk we see next strings
> [Jan 15 14:28:11] WARNING[13861] channel.c: Channel allocation failed: Refusing due to active shutdown
> [Jan 15 14:28:11] WARNING[13861] chan_sip.c: Unable to allocate AST channel structure for SIP channel
> [Jan 15 14:28:11] NOTICE[13861] chan_sip.c: Unable to create/find SIP channel for this INVITE
> After that all calls are droppped, asterisk is automatically restarted (no system administrator gave command to restart it),  new calls are successfully established. 
> The coredump in /tmp directory was NOT created in this situation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira