|bote_radio at botecomm...
|Posted: Thu Feb 25, 2016 1:27 pm Post subject: [Freeswitch-users] Getting 503 when starting automatically v
|A 503 error, huh? Weird. Check for permissions problems.
My guess is that you are building as "root" so when you first ran it
manually all the databases and log files were created with root as owner.
But when it boots systemd is starting it as root and then dropping
privileges to the freeswitch user as it should. After dropping privileges it
can't access its config files or open ports necessary to function.
Again, this is just my S.W.A.G. but it has happened enough times in the past
that it's a pretty good guess. If it bears out you might want to check the
instructions on this deprecated page:
Also, once you achieve success there are MANY other RPi users out there who
would love to see your recipe for success.
Hope this helps.
Sent: Thursday, 25 February, 2016 02:36
Subject: [Freeswitch-users] Getting 503 when starting automatically via
I'm using Arch Linux (specifically Arch Linux ARM on a Raspberry Pi Zero).
|successfully done a make and install for freeswitch 1.6.6 and when I run
|manually (freeswitch -nonat), it works fine. Also, when I start it
|systemd (systemctl start freeswitch), it still works fine.
However, when I enable freeswitch.service to start automatically and
reboot, the freeswitch log shows 503 errors trying to register out to my
gateway, and my internal client (an Obi200) gets a 503 when trying to
|in to FreeSWITCH as well; this keeps happening repeatedly (waiting 30
seconds and then failing again). However, if I restart the service
|restart freeswitch), connectivity then starts working.
Would the 503 be what's reported up if there's no network connectivity
I'm using the Debian systemd *freeswitch.service file (with very minor
tweaks for my configuration on Arch Linux). Has anyone encountered this
problem before (on Debian, Arch Linux, or elsewhere)? The overall .service
file is very similar to sshd.service, which doesn't have connection
|so my guess is there's something specific to FreeSWITCH going on. If this
|Arch Linux-specific and I ask in their forums, is there anything different
|how FreeSWITCH handles connectivity (perhaps caching some kind of
handle) that would help point things in the right direction?
Professional FreeSWITCH Consulting Services:
Official FreeSWITCH Sites
FreeSWITCH-users mailing list