jenkins用rpm安装的jenkins-2.299,后来下载最新版2.313的war包升级
来源:4-3 Jenkins安装配置管理

慕后端7294772
2021-09-28
问题描述:
1、jenkins用rpm安装的jenkins-2.299,后来下载最新版2.313的war包升级,升级后用/etc/init.d/jenkins start报超时错误,但是端口打开了,进程启了,控制台也可以打开正常使用。8080端口没被占用,就是用/etc/init.d/jenkins start和systemctl start jenkins会报超时错误,systemctl stop jenkins和/etc/init.d/jenkins stop关不了服务,进程和端口还是在。
2、jenkins.log日志的时间与系统时间相差8小时,在/etc/sysconfig/jenkins中配置了亚洲上海时区,控制台也显示的亚洲上海时区,但是查看日志还是相差8小时。
[root@ansible alternatives]# /etc/init.d/jenkins start
Starting jenkins (via systemctl): Job for jenkins.service failed because a timeout was exceeded. See “systemctl status jenkins.service” and “journalctl -xe” for details.
[FAILED]
[root@ansible ~]# systemctl status jenkins
● jenkins.service - LSB: Jenkins Automation Server
Loaded: loaded (/etc/rc.d/init.d/jenkins; bad; vendor preset: disabled)
Active: activating (start) since Tue 2021-09-28 13:59:35 CST; 4min 27s ago
Docs: man:systemd-sysv-generator(8)
Control: 4037 (jenkins)
CGroup: /system.slice/jenkins.service
├─4037 /bin/sh /etc/rc.d/init.d/jenkins start
├─4042 runuser -s /bin/bash deploy -c ulimit -S -c 0 >/dev/null 2>&1 ; /etc/alternatives/java -Djava.awt.headless=true -Duser.t…
├─4043 bash -c ulimit -S -c 0 >/dev/null 2>&1 ; /etc/alternatives/java -Djava.awt.headless=true -Duser.timezone=Asia/Shanghai …
└─4044 /etc/alternatives/java -Djava.awt.headless=true -Duser.timezone=Asia/Shanghai -DJENKINS_HOME=/var/lib/jenkins -jar /usr/…
Sep 28 13:59:35 ansible systemd[1]: Starting LSB: Jenkins Automation Server…
Sep 28 13:59:35 ansible runuser[4042]: pam_unix(runuser:session): session opened for user deploy by (uid=0)
Sep 28 13:59:41 ansible jenkins[4037]: Starting Jenkins WARNING: An illegal reflective access operation has occurred
Sep 28 13:59:41 ansible jenkins[4037]: WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$2…nDomain)
Sep 28 13:59:41 ansible jenkins[4037]: WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cg…tUtils$2
Sep 28 13:59:41 ansible jenkins[4037]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
Sep 28 13:59:41 ansible jenkins[4037]: WARNING: All illegal access operations will be denied in a future release
Hint: Some lines were ellipsized, use -l to show in full.
[root@ansible ~]# systemctl status jenkins
● jenkins.service - LSB: Jenkins Automation Server
Loaded: loaded (/etc/rc.d/init.d/jenkins; bad; vendor preset: disabled)
Active: failed (Result: timeout) since Tue 2021-09-28 14:04:49 CST; 4min 31s ago
Docs: man:systemd-sysv-generator(8)
Process: 4037 ExecStart=/etc/rc.d/init.d/jenkins start (code=killed, signal=TERM)
CGroup: /system.slice/jenkins.service
├─4042 runuser -s /bin/bash deploy -c ulimit -S -c 0 >/dev/null 2>&1 ; /etc/alternatives/java -Djava.awt.headless=true -Duser.timezone=Asia/Shanghai -DJENKINS_HOME=/…
├─4043 bash -c ulimit -S -c 0 >/dev/null 2>&1 ; /etc/alternatives/java -Djava.awt.headless=true -Duser.timezone=Asia/Shanghai -DJENKINS_HOME=/var/lib/jenkins -jar /u…
└─4044 /etc/alternatives/java -Djava.awt.headless=true -Duser.timezone=Asia/Shanghai -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war --logfile=/var/…
Sep 28 13:59:35 ansible runuser[4042]: pam_unix(runuser:session): session opened for user deploy by (uid=0)
Sep 28 13:59:41 ansible jenkins[4037]: Starting Jenkins WARNING: An illegal reflective access operation has occurred
Sep 28 13:59:41 ansible jenkins[4037]: WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils2(file:/var/cache/jenkins/war/WEB−I...ctionDomain)Sep2813:59:41ansiblejenkins[4037]:WARNING:Pleaseconsiderreportingthistothemaintainersofcom.google.inject.internal.cglib.core.2 (file:/var/cache/jenkins/war/WEB-I...ctionDomain)
Sep 28 13:59:41 ansible jenkins[4037]: WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.2(file:/var/cache/jenkins/war/WEB−I...ctionDomain)Sep2813:59:41ansiblejenkins[4037]:WARNING:Pleaseconsiderreportingthistothemaintainersofcom.google.inject.internal.cglib.core.ReflectUtils$2
Sep 28 13:59:41 ansible jenkins[4037]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
Sep 28 13:59:41 ansible jenkins[4037]: WARNING: All illegal access operations will be denied in a future release
Sep 28 14:04:49 ansible systemd[1]: jenkins.service start operation timed out. Terminating.
Sep 28 14:04:49 ansible systemd[1]: Failed to start LSB: Jenkins Automation Server.
Sep 28 14:04:49 ansible systemd[1]: Unit jenkins.service entered failed state.
Sep 28 14:04:49 ansible systemd[1]: jenkins.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@ansible ~]# tail -f /var/log/jenkins/jenkins.log
2021-09-28 05:59:43.362+0000 [id=35] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins
2021-09-28 05:59:43.411+0000 [id=35] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions
2021-09-28 05:59:44.680+0000 [id=35] INFO jenkins.InitReactorRunner$1#onAttained: System config loaded
2021-09-28 05:59:44.681+0000 [id=35] INFO jenkins.InitReactorRunner$1#onAttained: System config adapted
2021-09-28 05:59:44.696+0000 [id=29] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs
2021-09-28 05:59:44.707+0000 [id=34] INFO jenkins.InitReactorRunnerKaTeX parse error: Expected 'EOF', got '#' at position 2: 1#̲onAttained: Con…doRunKaTeX parse error: Expected 'EOF', got '#' at position 102: …yncPeriodicWork#̲lambdadoRun$0: Finished Download metadata. 27 ms
2021-09-28 05:59:44.800+0000 [id=33] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization
2021-09-28 05:59:44.819+0000 [id=23] INFO hudson.WebAppMain$3#run: Jenkins is fully up and running
2回答
-
1、jenkins用rpm安装的jenkins-2.299,后来下载最新版2.313的war包升级,升级后用/etc/init.d/jenkins start报超时错误,但是端口打开了,进程启了,控制台也可以打开正常使用。8080端口没被占用,就是用/etc/init.d/jenkins start和systemctl start jenkins会报超时错误,systemctl stop jenkins和/etc/init.d/jenkins stop关不了服务,进程和端口还是在。
首先推荐使用yum源的更新方式更新jenkins版本,如果因为其他原因无法使用yum 你这个问题可以尝试kill -9 jenkins进程号 看能不能kill掉jenkins 然后再尝试启动2、jenkins.log日志的时间与系统时间相差8小时,在/etc/sysconfig/jenkins中配置了亚洲上海时区,控制台也显示的亚洲上海时区,但是查看日志还是相差8小时。
更改jenkins时区需要在jenkins admin后台进行修改,具体配置详见
https://www.jenkins.io/doc/book/using/change-time-zone/012021-10-02 -
慕后端7294772
提问者
2021-09-28
rpm安装jenkins-2.299后是可以正常使用systemctl start jenkins的,就是换了war包升级后再用systemctl命令启动会报超时,查了很多资料没找到原因
00
相似问题