Got a weird issue where FS isn’t starting up correctly. Looking at the logs, it appears just to be attempting to restart SIP profiles (and failing), and that’s about it. There’s no socket for fs_cli, and a simple ‘systemctl restart’ fixes it. Anyone had something like this? I’ve tried fixing it with systemd after / requires, but it hasn’t helped. 

Here’s my .service file (not sure if this is the issue, I'd welcome any comments / better versions?)

[Unit]

Description=freeswitch

After=syslog.target network-online.target local-fs.target

[Service]

; service

Type=forking

PIDFile=/run/freeswitch/freeswitch.pid

PermissionsStartOnly=true

ExecStart=/usr/bin/freeswitch -ncwait -nonat

ExecStop=/usr/bin/fs_cli -x shutdown

TimeoutSec=45s

Restart=always

; exec

RuntimeDirectory=freeswitch

RuntimeDirectoryMode=0755

User=freeswitch

Group=freeswitch

LimitCORE=infinity

LimitNOFILE=100000

LimitNPROC=60000

;LimitSTACK=240

LimitRTPRIO=infinity

LimitRTTIME=7000000

IOSchedulingClass=realtime

IOSchedulingPriority=2

CPUSchedulingPolicy=rr

CPUSchedulingPriority=89

UMask=0007

[Install]

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org