action #110452
closedhttp://jenkins.qa.suse.de/ throws an error with "Faithfully yours, nginx." so the jenkins instance behind seems to be problematic
0%
Description
Observation¶
http://jenkins.qa.suse.de/ is reachable but shows
An error occurred.
Sorry, the page you are looking for is currently unavailable.
Please try again later.
If you are the system administrator of this resource then you should check the error log for details.
Faithfully yours, nginx.
so the proxy is reachable but not the jenkins instance behind.
Impact¶
Our automatic submissions of os-autoinst+openQA to openSUSE:Factory depend on the instance as well as some other minor products like openSUSE Krypton/Argon.
Updated by okurz almost 2 years ago
- Status changed from New to In Progress
- Assignee set to okurz
I found that the systemd service is actually disabled and was not running. A simple systemctl start jenkins already helped. I also did systemctl enable --now jenkins.
Updated by okurz almost 2 years ago
- Status changed from In Progress to Resolved
I found that the latest time /var/log/jenkins.log was written was 2022-03-08 although openQA-in-openQA tests were still triggered three days ago. I assume that jenkins was still running before the last reboot of the VM hypervisor.
I triggered another reboot and now everything is fine. I rebooted again and still fine. I asked members of the team but we couldn't find a better hypothesis than "something with package upgrades".