K
K
Ka4a2016-02-12 16:33:58
linux
Ka4a, 2016-02-12 16:33:58

Why does GOD start badly?

Welcome all. Please advise with this problem. There are Gentoo, Ubuntu, Debian servers. GOD does not start automatically at OS startup. If I do service god statusnot receive a response from the team, or I receive

/lib64/rc/sh/runscript.sh: line 103: service_stopping: command not found
/lib64/rc/sh/runscript.sh: line 106: service_starting: command not found
/lib64/rc/sh/runscript.sh: line 109: service_inactive: command not found
/lib64/rc/sh/runscript.sh: line 112: service_started: command not found
/lib64/rc/sh/runscript.sh: line 120: einfo: command not found

If I do god status then I get the correct answer. For example, on Gentoo, if I do rc-status, then god has the stopped status there. If I do it on Debian or Ubuntu, I service --status-allsee opposite god - (not running), although again, if I do god status, I get the correct answer. God installed via gem install god. Init script for auto start installed.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
K
Ka4a, 2016-03-02
@ka4a

The answer, as always, was simple.

rvm wrapper 2.2.2 bootup god
$ ls -l /usr/local/rvm/bin/bootup_god 
lrwxrwxrwx 1 root rvm 43 Jan 25 13:38 /usr/local/rvm/bin/bootup_god -> /usr/local/rvm/wrappers/ruby-2.2.2/god*

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question