Services aren't set to start on boot on git7site [#2037347]

The following services are needed to test Git services on http://git7site.devdrupal.org. Can these be set to start at boot so that manual intervention isn't needed after reboot? Or maybe check that they're running in Jenkins and start them if they're not as part of the set up for the automated test runs?

varnish
git ssh daemon
supervisord
beanstalkd

The goal is to prevent automated (and manual) testing from failing because services aren't available so we can focus on problems in the code.

Comments

Comment #1

marvil07 commented 11 July 2013 at 16:25

I have been investigating this, runlevel on gitstaging box is 3, and taking a look to:

 ls /etc/rc3.d/ | grep -i -e supervisor -e varnish -e git -e beanstalk -e ssh
K04supervisord
K10varnish
K10varnishlog
K10varnishncsa
K47beanstalkd
S55sshd

it seems like the only missing server at boot is git ssh daemon, but I could be wrong.

I remember drumm mentioning that the problem behind services not running, which has happened several times, has mainly to do with jenkins jobs (which (re)start/stop services) not ending correctly, so that could explain it.

In any case, git ssh daemon should be running at start. Any specific way to do that on CentOS, or should I just symlink to /etc/rc3.d/ directory.