Project

General

Profile

Actions
Copy link

Bug #21053

closed

Rudder-jetty doesn't start in 7.0

Added by Nicolas CHARLES almost 2 years ago. Updated 8 months ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
System integration
Target version:
7.2.11
Pull Request:
Severity:
UX impact:
It bothers me each time
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

I don't really know how it happened, but I got to a state where rudder-jetty wouldn't start
Nothing happens when running 

service rudder-jetty start
Job for rudder-jetty.service failed because the control process exited with error code.
See "systemctl status rudder-jetty.service" and "journalctl -xe" for details.

No logs in /var/log/rudder nor systemctl

running 

bash /opt/rudder/bin/rudder-jetty.sh start
/opt/rudder/etc/rudder-jetty.conf: line 72: warning: setlocale: LC_NUMERIC: cannot change locale ()
/opt/rudder/etc/rudder-jetty.conf: line 72: warning: setlocale: LC_NUMERIC: cannot change locale ()
/opt/rudder/etc/rudder-jetty.conf: line 73: warning: setlocale: LC_TIME: cannot change locale ()
/opt/rudder/etc/rudder-jetty.conf: line 73: warning: setlocale: LC_TIME: cannot change locale ()
Setting umask to 0007
Starting Jetty: process already running.

shows that it thinks it is running, but it is not

command

start-stop-daemon -k 0007 -S -p/var/rudder/run/rudder-jetty.pid -d/opt/rudder/etc/rudder-jetty-base -b -m -a /bin/java -- -server -Xms1024m -Xmx1024m -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -Dfile.encoding=UTF-8 -Drudder.configFile=/opt/rudder/etc/rudder-web.properties -Drudder.authFile=/opt/rudder/etc/rudder-users.xml -Dlogback.configurationFile=/opt/rudder/etc/logback.xml -Drun.mode=production -XX:+CrashOnOutOfMemoryError -Djetty.home=/opt/rudder/jetty -Djetty.base=/opt/rudder/etc/rudder-jetty-base -Djava.io.tmpdir=/var/rudder/tmp/jetty -jar /opt/rudder/jetty/start.jar OPTIONS=Server jetty.state=/opt/rudder/etc/rudder-jetty-base/rudder-jetty.state jetty-started.xml start-log-file=/var/log/rudder/webapp/java.log
process already running.

so that's the culprit

file /var/rudder/run/rudder-jetty.pid does exist, with PID 877
but no process with that ID

moving the pid file and running does

 service rudder-jetty start
Job for rudder-jetty.service failed because the control process exited with error code.
See "systemctl status rudder-jetty.service" and "journalctl -xe" for details.

but service is started ...

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #21240: Rudder-jetty service can not be startedRejectedActions
Actions
Copy link

Also available in: Atom PDF