It’s a permissions problem most likely.
systemd should start FS as root, FS creates any directories and files that it needs, increases runtime priority, and claims ports, then FS drops its own privileges to those specified by the –u and –g switches.
It’s worth checking the ownership and permissions of the files and directories that FS has already created (such as freeswitch.pid) to avoid further gnashing of teeth.
If you are using systemd, you control processes with the ‘systemctl’ command, not ‘service’. Systemd has the ability to restart FS if it crashes and other useful things so I recommend getting up to speed on it as it seems to be quite robust.
Hope this helps.
Bote
From: rick.jarvis@magicmail.mooo.com
Sent: Monday, 19 October, 2015 17:14
Subject: Re: [Freeswitch-users] systemd
Nothing in /var/log/freeswitch/freeswitch.log
Results of running it at command line below. I’ve tried running it with ‘c’ instead of ‘ncwait’ as well, but it complains about the pid
root@voice:/etc/systemd/system# /usr/bin/freeswitch -u freeswitch -g freeswitch -ncwait -nonat -rp
1349 Backgrounding.
FreeSWITCH[1348] Error starting system! pid:1349
root@voice:/etc/systemd/system# /usr/bin/freeswitch -u freeswitch -g freeswitch -c -nonat -rp
Cannot open pid file /var/run/freeswitch/freeswitch.pid.