Rudder

It looks like the web application take too long to start, and the init script times out waiting for it.

This shouldn't happen of course.

One benefit you will get soon is that Rudder 3.0 removed a rather slow migration script at startup so this probably won't happen in that version.

By any chance could you use a snapshot VM copy to upgrade to current 2.12 nightly version and see if it is still as slow?

Is it not possible to change something in 2.11.3 to test? Also /etc/init.d/jetty still exists and gives no errors.

After kill -9 jetty, the script now works as expected.

On 2.11.4 that is...

The important code bit is:

if [ $(ps aux|grep -E "java .* /opt/rudder/jetty7/start.jar"|grep -v grep|wc -l) -ne 0 ]
then
  if [ -e ${JETTY_STATE} ] && grep -q "STARTING" ${JETTY_STATE} || grep -q "STARTED" ${JETTY_STATE}
  then
    echo "already running." 
    exit 0
  fi
fi

I check if a Jetty process seems running in the process list, and if it looks linked to the jetty status file (STARTING or STARTED), and just leave it alone in this case.

If those conditions are not fulfilled, and only in this case, remove the state file and try to run Jetty just like before.

I also cleanup the state file properly when stopping Jetty gracefully.

This is still true on Rudder 3.0:

# /etc/init.d/rudder-jetty restart
Stopping Jetty: OK
Setting umask to 0007
Starting Jetty: . . . . . . . . . . . . . . FAILED Tue Feb 17 14:06:08 CET 2015

# /etc/init.d/rudder-jetty check | tail -1
Jetty running pid=18190

Applied in changeset rudder-packages|commit:22f38c0a3c3a7fbd44d9c13e5f761dd0a5dec8ea.

This bug has been fixed in Rudder 2.11.10 and 3.0.4 which were released today.

• Announcement 2.11 3.0
• Changelog 2.11 3.0
• Download information: https://www.rudder-project.org/site/get-rudder/downloads/

This was fixed in 2.10.13 and not 2.11.10 as previously stated