[Home]

Summary:ASTERISK-25206: No ability to control asterisk if permission failure on /var/run
Reporter:Scott Griepentrog (sgriepentrog)Labels:
Date Opened:2015-06-26 11:11:01Date Closed:
Priority:MinorRegression?
Status:Open/NewComponents:Core/General
Versions:SVN 11.18.0 13.4.0 Frequency of
Occurrence
Constant
Related
Issues:
Environment:Attachments:
Description:When starting asterisk as a non-root user, if the user does not have write permission to the /var/run/asterisk directory, asterisk will fail to write the asterisk.ctl and asterisk.pid files, but still be running in the background and servicing ports.

Asterisk -r will not function, and a script that checks the pid doesn't realize asterisk is running.  This scenario can lead to having multiple instances of asterisk running, with unexpected results.

Recommendation: change the startup code to consider a failure to write the .ctl or .pid file as a fatal error and exit.
Comments:By: Rusty Newton (rnewton) 2015-06-26 17:49:32.894-0500

I believe it has been this way forever. I'd be glad to see a change as I've certainly been confused by this in the past.