Hi Andrei,
That worked, thank you so much!
Here is the final of the hello-phoenix.service:
[Unit]
Description=hello-phoenix service
[Service]
WorkingDirectory=/home/hello-phoenix/app/bin
ExecStart=/home/hello-phoenix/app/bin/hello_phoenix foreground
Environment=MIX_ENV=prod PORT=
Hi Michael,
How did you get this /home/hello-phoenix/app/bin/hello_phoenix script
anyway? If it is generated by exrm, I'd suggest to try "hello_phoenix
foreground" in ExecStart directive — it'd prevent forking and detaching
from console (it is unnecessary if being supervised by systemd).
On Thu, Jul 07, 2016 at 07:29:20AM -0700, Michael Chavez wrote:
> Hello,
>
> I am a newbie trying to get systemd to load my phoenix/elixir app.
>
> I have tried many variations of my hello-phoenix service file, the version
> that I feel is closest to being correct looks like this:
>
> [Service]
Thanks for the reply. I added "Type=forking" and still get same results:
● hello-phoenix.service - hello-phoenix service
Loaded: loaded (/etc/systemd/system/hello-phoenix.service; enabled)
Active: failed (Result: start-limit) since Thu 2016-07-07 10:59:25 EDT;
23s ago
Process: 7139
> Process: 4281 ExecStart=/home/hello-phoenix/app/bin/hello_phoenix start
(code=exited, status=0/SUCCESS)
If it's a 'daemon', use Type=forking.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
Hello,
I am a newbie trying to get systemd to load my phoenix/elixir app.
I have tried many variations of my hello-phoenix service file, the version
that I feel is closest to being correct looks like this:
[Unit]
Description=hello-phoenix service
[Service]
