Got that, it’s this in the service file:

[Unit]
Description=freeswitch
After=network-online.target

On 28 Jun 2017, at 20:51, Ken Rice <krice@freeswitch.org> wrote:

Try changing it so that FreeSWITCH depends on the network to be full up before it’ll start in the system setup. Theres a way to do that but the data eludes me at this time
 
From: FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Rick Jarvis
Sent: Wednesday, June 28, 2017 2:49 PM
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Subject: Re: [Freeswitch-users] FS service issues (systemd)
 
Thanks Jason. 
 

Indeed, fresh install of deb 8.8 and FS 1.6, and exactly the same behaviour. Needs a manual ‘systemctl restart freeswitch’ to get it into life. Quite annoying, especially as it was ok before… not quite sure what’s changed.

On 28 Jun 2017, at 20:26, Jason Komar <jkomar@jbox.ca> wrote:
 
I had this happen on one particular FS box and no matter what I tried I could not get FS to wait until the NIC was 100% up and running. I ended up installing a different model NIC and it started working. I can't remember what model the troublesome one was, unfortunately.
 
Jason
 
 
On Wed, Jun 28, 2017 at 8:54 AM, Rick Jarvis <rick@magicmail.mooo.com> wrote:
Debian Jessie, FreeSWITCH Version 1.4.26-37~64bit (-37 64bit)
 
It starts fine manually, and works if I restart it with systemctl restart, which is why I’m confused, but leaning towards it being a dependency not having started in time when it boots. I can probably fix it by reinstalling and/or upgrading, I’d just like to know why it’s failing ideally...

 

On 28 Jun 2017, at 15:44, Giovanni Maruzzelli <gmaruzz@gmail.com> wrote:
 
What exact platform are you using? Os/distro? FS version? Any virtualization?


Has ever started correctly?

Have you started it from command line (maybe as root user) and then the problems started to appear?
 
Have you tried to reinstall from scratch following strictly the confluence instructions?


Maybe file/directories permission problem?

-giovanni
 
On 28 June 2017 at 16:32, Rick Jarvis <rick@magicmail.mooo.com> wrote:
Just looping with failed registrations:
 
2017-06-28 15:29:42.738155 [NOTICE] sofia_reg.c:448 Registering connection1
2017-06-28 15:29:42.738155 [NOTICE] sofia_reg.c:448 Registering connection2
2017-06-28 15:29:42.738155 [NOTICE] sofia_reg.c:448 Registering xprov
2017-06-28 15:29:42.738155 [ERR] sofia_reg.c:2392 connection2 Failed Registration with status Service Unavailable [503]. failure #101
2017-06-28 15:29:42.738155 [ERR] sofia_reg.c:2392 xprov Failed Registration with status Service Unavailable [503]. failure #101
2017-06-28 15:29:42.838117 [ERR] sofia_reg.c:2392 connection1 Failed Registration with status Service Unavailable [503]. failure #101
2017-06-28 15:29:43.738108 [WARNING] sofia_reg.c:505 connection1 Failed Registration [503], setting retry to 30 seconds.
2017-06-28 15:29:43.738108 [WARNING] sofia_reg.c:505 connection2 Failed Registration [503], setting retry to 30 seconds.
2017-06-28 15:29:43.738108 [WARNING] sofia_reg.c:505 xprov Failed Registration [503], setting retry to 30 seconds.
 
On 28 Jun 2017, at 14:52, Luis Jimenez <ljjimenez@gmail.com> wrote:
 
What about the freeswitch.log file when fs is hung?
 


On Jun 28, 2017, at 09:42, Rick Jarvis <rick@magicmail.mooo.com> wrote:

I’ve tried deleting the db files but no difference unfortunately. Starting manually or even just restarting the service works, so I believe the XML is all as it should be. This is my output from systemctl when it’s in this ‘hung' state:
 
● freeswitch.service - freeswitch
   Loaded: loaded (/etc/systemd/system/freeswitch.service; enabled)
   Active: active (running) since Wed 2017-06-28 14:36:23 BST; 3min 27s ago
  Process: 452 ExecStart=/usr/bin/freeswitch -ncwait -nonat (code=exited, status=0/SUCCESS)
 Main PID: 472 (freeswitch)
   CGroup: /system.slice/freeswitch.service
           └─472 /usr/bin/freeswitch -ncwait -nonat
 
Jun 28 14:36:20 server systemd[1]: Starting freeswitch...
Jun 28 14:36:20 server freeswitch[452]: 472 Backgrounding.
Jun 28 14:36:23 server freeswitch[452]: FreeSWITCH[452] Waiting for background process pid:472 to be ready.....
Jun 28 14:36:23 server freeswitch[452]: FreeSWITCH[452] System Ready pid:472
Jun 28 14:36:23 server systemd[1]: Started freeswitch.

 

On 28 Jun 2017, at 14:18, Mundkowsky, Robert <rmundkowsky@ets.org> wrote:
 
 
1)      The file system database can get messed up.
a.       Stop FS
b.      You can clear then via rm /export/Apps/freeswitch/var/lib/freeswitch/db/*
c.       Restart FS
2)      If there is an error in the configuration files.
a.       Take a look at /export/Apps/freeswitch/var/log/freeswitch/freeswitch.xml.fsxml to see if there are any errors in XML.
 
You can get more details of start problem via:
                journalctl -xn
                systemctl status freeswitch.service
               
                if you do not get enough details, try starting FS directly and you might get more details via:
 
                /…/bin/freeswitch
 
 
Robert Mundkowsky
 
From: FreeSWITCH-users [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Rick Jarvis
Sent: Wednesday, June 28, 2017 7:44 AM
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Subject: [Freeswitch-users] FS service issues (systemd)
 

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]

 

 

 
 
 

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

 
 



-- 

Sincerely,

Giovanni Maruzzelli
OpenTelecom.IT

cell: +39 347 266 56 18
 
 
 
_________________________________________________________________________
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