-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upstart not working on Ubuntu 14.04: cannot create PID file #357
Comments
Just noticed 14.04 is not officially supported. In that case, great that it works with the SysV workaround. |
flowma
added a commit
to flowma/sbt-native-packager
that referenced
this issue
Sep 23, 2014
…bt#357 for Ubuntu 14.04.
flowma
added a commit
to flowma/sbt-native-packager
that referenced
this issue
Sep 23, 2014
flowma
added a commit
to flowma/sbt-native-packager
that referenced
this issue
Sep 24, 2014
…bt#357 for Ubuntu 14.04.
flowma
added a commit
to flowma/sbt-native-packager
that referenced
this issue
Sep 24, 2014
muuki88
added a commit
that referenced
this issue
Sep 28, 2014
changed template for /etc/init/{{app_name}} This seems to fix issue #357...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is probably related to #164 .
debian:packageBin
. Works great.Now, when I restart the the target machine, Ubuntu will re-populate
/var/run
. Then the Play! app tries to create the PID file, but it fails because the directory/var/run/{{app_name}}
does not exist (I have-Dpidfile.path=/var/run/${{app_name}}/play.pid
insrc/templates/etc-default
)./var/log/upstart/$app_name.log
saysUpstart is to be replaced with systemd on Ubuntu, so maybe it's not worth maintaining that code. But 14.04 is going to be around for a while, so it would be nice to have a working default or at least clearly documented workaround.
It work smoothly if I switch to SystemV in
build.sbt
:The text was updated successfully, but these errors were encountered: