Project

General

Profile

Actions

Bug #14483

closed

Foreman not starting after update to 1.11 on Debian 8.4

Added by Matthias Wohlgemuth about 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Debian/Ubuntu
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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.


Related issues 1 (0 open1 closed)

Related to Foreman - Refactor #12892: move rails binaries to /bin directoryClosedOhad Levy12/21/2015Actions
Actions

Also available in: Atom PDF