It seems to me that the restart is creating asterisk.pid in the "wrong" place. Try this - - find /|grep asterisk.pid This will tell you where the mislocated pid is being created and you can adjust the script accordingly. -- Danny Nicholas --
-----Original Message----- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Brian Sent: Wednesday, February 10, 2010 8:15 AM To: Ken Leland III Cc: asterisk-users@lists.digium.com Subject: Re: [asterisk-users] Unable to open pid file '/var/run/asterisk/asterisk.pid': No such file or directory On Wed, 2010-02-10 at 08:54 -0500, Ken Leland III wrote: > Brian, > > It could be that the ownership/permissions on the directory are not correct. > Are you running asterisk as asterisk:asterisk or root:root? > > Here is an article that lists the directories and what the ownership/permissions on each one should be: > > http://www.voip-info.org/wiki/view/Asterisk+non-root Thanks for that, but no - it runs as root, and root can create/access /var/run without any issues. I'm boggled... -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
