It will print "Starting Jetty servlet engine" and then return very fast to shell prompt.
Why it happens:
This is a problem with "rotatelogs" utility in /etc/init.d/jetty.
Version Jetty 6.1.22-1ubuntu1 has not this problem.
Version Jetty 6.1.24-5 in Debian has this problem. Previous version in Debian has not this problem.
How to work around:
There are two ways to work aroud.
a) To delete /var/log/out.log and to start jetty with "sudo /etc/init.d/jetty start" (the problem will appear again next time you will have to restart jetty).
b) To revert the lines of jetty that use rotatelogs as in previous version:
- $ROTATELOGS "$LOGDIR/out.log" 86400 \
- < "$LOGDIR/out.log"
>>>>>>>>
+ sudo -b -u $JETTY_USER $ROTATELOGS "$LOGDIR/out.log" 86400 \
+ < "$LOGDIR/out.log"
Binary package hint: jetty
How to reproduce this bug:
- Install Jetty 6.1.24-5
- change NO_START variable in /etc/default/jetty
- sudo /etc/init.d/jetty stop
- sudo /etc/init.d/jetty start
It will print "Starting Jetty servlet engine" and then return very fast to shell prompt.
Why it happens:
This is a problem with "rotatelogs" utility in /etc/init.d/jetty.
Version Jetty 6.1.22-1ubuntu1 has not this problem.
Version Jetty 6.1.24-5 in Debian has this problem. Previous version in Debian has not this problem.
How to work around:
There are two ways to work aroud.
a) To delete /var/log/out.log and to start jetty with "sudo /etc/init.d/jetty start" (the problem will appear again next time you will have to restart jetty).
b) To revert the lines of jetty that use rotatelogs as in previous version:
- $ROTATELOGS "$LOGDIR/out.log" 86400 \
- < "$LOGDIR/out.log"
>>>>>>>>
+ sudo -b -u $JETTY_USER $ROTATELOGS "$LOGDIR/out.log" 86400 \
+ < "$LOGDIR/out.log"
This bug have to be reported to Debian too.