@NobbZ thank you for taking time to look at this.
Somebody pointed to me that in the systemd config file it shouldn’t be Type=forked but Type=forking.
I changed that and used absolute path. Now I get the following error
ubject: Unit union.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit union.service has finished starting up.
--
-- The start-up result is done.
Jun 08 14:58:45 union-staging run_erl[31042]: Erlang closed the connection.
Jun 08 14:58:46 union-staging union[31472]: ==> Generated sys.config in /test/union/var
Jun 08 14:58:46 union-staging systemd[1]: union.service: control process exited, code=exited status=1
Jun 08 14:58:46 union-staging union[31472]: Node union@127.0.0.1 is not running!
Jun 08 14:58:46 union-staging systemd[1]: Unit union.service entered failed state.
Jun 08 14:58:46 union-staging systemd[1]: union.service failed.
Jun 08 14:58:51 union-staging systemd[1]: union.service holdoff time over, scheduling restart.
Jun 08 14:58:51 union-staging systemd[1]: Starting Union Servers...
-- Subject: Unit union.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit union.service has begun starting up.
Jun 08 14:58:53 union-staging union[31766]: ==> Generated sys.config in /test/union/var
Jun 08 14:58:53 union-staging systemd[1]: PID file /test/union/union.prod.pid not readable (yet?) after start.
Did anybody ever encounter that not readable yet pid file ?
for the pid_file application I use
config :pid_file, file: System.get_env("PIDFILE")
and use conform for environment variables with PIDFILE="/test/union/union.prod.pid"
I forgot to mention that if I use the bin script directly, then it works like a charm
/test/union/bin/union start
