I have followed the following FreePBX how-to on installing FreePBX 13 on CentOS 6.X. (Link omitted since I am a new user and will not allow me to post a link)
All is well and everything runs fine however every time I reboot the OS Asterisk 13 loads as root.root instead of asterisk.asterisk causing me to have to go into the CLI, shutdown Asterisk and then run “/usr/src/freepbx/start_asterisk start” in order for the UI to operate properly.
Could someone please assist me with how I can load Asterisk at boot as asterisk.asterisk instead of root.root?
Appears to be starting from /etc/init.d/asterisk at this point. I have looked through that script and do not seem to find a way to have it load as a different user then root.
I have now had the exact same issue - found several threads that sounded promising, but didn’t fix. Would love to hear what works for you. And if your Linux is rusty, mine is downright pathetic.
I’m also getting several alerts in the dashboard about modules not being owned by “asterisk”, despite the fact I’ve run the “fwconsole chown” command several times, as well as manually changed recursive permissions on the affected directories: File /etc/modprobe.d/dahdi.conf is not owned by asterisk File /etc/dahdi/modules is not owned by asterisk
If you dont plan on using DADHI just disable the module in connectivity on the module admin. Thats only used for physical hardware and not SIP. Fixed the errors for me because I didn’t compile the DADHI modules.
That was only an example - I had several that popped up. The built-in permissions repair didn’t correct (had to manually do it - very odd). The other odd one I’m seeing is “no conference room app”, yet the conference module is installed and the newer module is selected in Advanced Settings (the newer app_confbridge one).
However, I’ve dug around every place I know to trying to find what would make it start as ROOT each time and I’ve been unable to find it. I don’t even see where FPBX is starting in the first place, let alone Asterisk.
I will say, that is the one frustrating thing about the step-by-step instructions - they’re supposed to have a working system when complete, but I’m thinking there’s something missing we have to make some of these edits. I also had to edit some of the commands for the big set of “yum install” commands - several items were missed and I had to issue the install commands one by one. I’m thinking it’s the addition of a MAKE command in the middle of the string, but can’t be sure.
And as I was writing this, I blundered across something that works:
This stops Asterisk from auto-booting. Now you just have to issue a “fwconsole start” command on bootup:
vi /etc/rc.local
<at end of file put “fwconsole start”>
I have no doubt there’s a better (more proper) way to do it because I really wasn’t kidding about having weak linux skills - all of this was put together from other instruction-lettes, so I’m open to any “are you crazy” comments.
My only concern is, are there other services that should be run by “asterisk” that are also being run by root (such as, fail2ban)…