Actions
Bug #14483
closedForeman not starting after update to 1.11 on Debian 8.4
Difficulty:
Triaged:
Description
After the update Foreman from 1.10 to 1.11, the stand-alone server was not starting anymore.
Manually starting foreman gives:
foreman@hostname:~$ bundle exec rails server Usage: rails new APP_PATH [options] Options: -r, [--ruby=PATH] # Path to the Ruby binary of your choice # Default: /usr/bin/ruby ...
After running
foreman@hostname:~$ bundle exec rake rails:update:bin
and changing the init script accordingly to:
@@ -23,7 +23,7 @@ FOREMAN_PID=${FOREMAN_PID:-"${FOREMAN_HOME}/tmp/pids/server.pid"} DAEMON="/usr/bin/bundle" -DAEMON_OPTS="exec rails server -b ${FOREMAN_IFACE} -p ${FOREMAN_PORT} -e ${FOREMAN_ENV} -d" +DAEMON_OPTS="exec bin/rails server -b ${FOREMAN_IFACE} -p ${FOREMAN_PORT} -e ${FOREMAN_ENV} -d" . /lib/init/vars.sh . /lib/lsb/init-functions
the server starts again.
I sugguest this to be patched in future versions.
Updated by Dominic Cleal over 8 years ago
- Project changed from Foreman to Packaging
- Category set to Debian/Ubuntu
- Translation missing: en.field_release set to 141
The bin/ dir is shipped in the Foreman tarball, so it can just be copied to /usr/share/foreman to save running the rake task.
Updated by Dominic Cleal over 8 years ago
- Related to Refactor #12892: move rails binaries to /bin directory added
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Assignee set to Dominic Cleal
- Pull request https://github.com/theforeman/foreman-packaging/pull/1079 added
Updated by Dominic Cleal over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 0839c4d620ba39ad0205f45fcc1f15a3f172e30e.
Actions