Server shutdown after the restart, Jenkins boot failure, status=7-CodePudding

Jenkins before is good, because among power outages server shutdown restart once, then start Jenkins reported failure

According to the prompt "systemctl status Jenkins. Service", only show the status=7, no error message

And then input "journalctl - xe" information has nothing to do with the launch, should be I try to use the browser to access blocked

Excuse me how should solve? Or you can also view the log information?

CodePudding user response:

According to the basic orientation to the error code is/etc/init. D/Jenkins scripts do_start function the last line of the error:
$SU - l $JENKINS_USER - shell=/bin/bash - c "$$DAEMON_ARGS DAEMON - $$JAVA_ARGS - JAVA jar $$JENKINS_ARGS JENKINS_WAR" | | return 2
Here to return to the 2

There is no way, only try to uninstall reshipment, but still an error: when heavy

reference

invoke - rc. D: initscript Jenkins, action "start" failed.
Low Jenkins. Service - LSB: Start Jenkins at boot time
The Loaded: the Loaded (/etc/init. D/Jenkins; Generated)
Active: failed (Result: exit - code) since Thu 15:11:35 2020-05-28 CST; 8 ms line
Docs: man: systemd sysv - generator (8)
Process: 16139 ExecStart=/etc/init. D/Jenkins start (code=exited, status=7)

May 28 15:11:35 server Jenkins [16139] : - E - stderr=spec - Send the client 's stderr to syslog or file
May 28 15:11:35 server Jenkins [16139] : - running - Check if daemon is running a named
May 28 15:11:35 server Jenkins [16139] : - restart to restart a daemon client named
May 28 15:11:35 server Jenkins [16139] : - stop - the Terminate a daemon process named
May 28 15:11:35 server su [16193] : pam_unix (su: session) : the session closed for user Jenkins
May 28 15:11:35 server Jenkins [16139] :/etc/init. D/Jenkins: line 220: sleep: command not found
May 28 15:11:35 server Jenkins [16139] : a failed!
May 28 15:11:35 server systemd [1] : Jenkins. Service: Control the process exited, code=exited the status=7
May 28 15:11:35 server systemd [1] : Jenkins. Service: Failed with result 'exit - code.
May 28 15:11:35 server systemd [1] : Failed to start the LSB: start Jenkins at boot time.
DPKG: error processing package Jenkins (- configure) :
Installed Jenkins package post - the installation script subprocess returned error exit status 1
Errors were encountered while processing:
Jenkins

Look from the scarlet letter part or an error when I was in the su command, continue to analyze,,,

CodePudding user response:

Like this kind of power failure or malfunction of the server host is easily to have backup or emergency response mechanism.

CodePudding user response:

Because itself is a test environment, so there is no backup or emergency treatment!

After a few days and tried, under/var/log/syslog found some new error message:

Into the/var/run/directory, and found that there is really no Jenkins directory (I don't know, I also dare not ask)

Then manually mkdir creates a Jenkins directory

Performed again sudo DPKG -i jenkins_2. 222.3 _all. Deb, successful

Then start Jenkins: sudo systemctl restart Jenkins, not an error, but Jenkins did not start successfully, to 404

Via sudo systemctl status Jenkins command to see

Have found an error, but behind again show the done and successful, now suspect Jenkins user permissions, or is still the problem of path, and then analysis...