I fixed this issue by adding “mysql.service” to the “After” line in the freeswitch.service systemd configuration file.
Quick question, regarding this PID path file (I read some answers here on this thread about that)
My monitrc file includes this path:
— FreeSWITCH ----
check process freeswitch with pidfile /var/run/freeswitch/freeswitch.pid
then the systemd file states:
[Service]
; service
Type=forking
PIDFile=/run/freeswitch/freeswitch.pid
Environment=“DAEMON_OPTS=-nonat”
Environment=“USER=freeswitch”
Environment=“GROUP=freeswitch”
EnvironmentFile=-/etc/default/freeswitch
ExecStartPre=/bin/chown -R ${USER}:${GROUP} /var/lib/freeswitch /var/log/freeswitch /etc/freeswitch />usr/share/freeswitch /var/run/freeswitch
ExecStart=/usr/bin/freeswitch -u ${USER} -g ${GROUP} -ncwait ${DAEMON_OPTS}
TimeoutSec=45s
Restart=always
No matter if I change that path in the systemd config file to /var/run/freeswitch/freeswitch.pid I still see (after rebooting) 2 PID files (one inside “/var/run/freeswitch/” directory, and the other under “/run/freeswitch/” directory). Is this a normal behavior -and I have to be leave it as it is- or is it some kind of duplicated process running for same freeswitch installation ? (I’m not a Linux expert, just curious how this works, and trying to minimize any impact to this platform performance)
What is the correct path to the PID file to set in both files (systemd and monirc) ?
