<p dir="ltr">David,</p>
<p dir="ltr">What happens if you either don't start FS via systemd or stop it once the system's done booting, then start it like, say,</p>
<p dir="ltr">su<br>
PATH=/usr/local/freeswitch/bin:$PATH<br>
freeswitch -nc</p>
<p dir="ltr">Note that you'll likely want to keep a record of what the permissions on your FS files and directories are BEFORE doing this.</p>
<p dir="ltr">Does it work then? Can you see from the console where the problem is?</p>
<p dir="ltr">I'm nearly positive that I've chased this same error myself before. Unfortunately, I can't recall what the root cause or the fix was.</p>
<p dir="ltr">Good luck!</p>
<p dir="ltr">- Larry<br>
</p>
<div class="gmail_quote">On Feb 25, 2016 16:30, <<a href="mailto:freeswitch.opencode@spamgourmet.com">freeswitch.opencode@spamgourmet.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, 2016-02-25 at 21:26:09 +0300, Bote wrote:<br>
> A 503 error, huh? Weird. Check for permissions problems.<br>
<br>
> My guess is that you are building as "root" so when you first ran it<br>
> manually all the databases and log files were created with root as owner.<br>
> But when it boots systemd is starting it as root and then dropping<br>
> privileges to the freeswitch user as it should. After dropping privileges it<br>
> can't access its config files or open ports necessary to function.<br>
<br>
Thanks for the suggestion. I compiled as a normal user using Arch Linux's makepkg tool and installed using its pacman tool, so I don't think that's the problem. I'm also letting system start freeswitch.service with its default user setting (as root).<br>
<br>
The weirdest thing is that it does start and connect fine using systemd when make a request after boot to have systemd start it (systemctl start freeswitch or systemctl restart freeswitch). In both cases, systemd is controlling process identity, so I don't think it's a permissions issue. My best guess is there's some kind of race condition at boot and if FreeSWITCH starts too early, it gets a cached but invalid handle of some sort that doesn't allow communicating in or out. This is just a guess though.<br>
<br>
Thanks,<br>
<br>
David<br>
<br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" rel="noreferrer" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://confluence.freeswitch.org" rel="noreferrer" target="_blank">http://confluence.freeswitch.org</a><br>
<a href="http://www.cluecon.com" rel="noreferrer" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div>