Project

General

Profile

Actions

action #170494

closed

nginx.service on monitor failed because of: "No such file or directory:calling fopen(/etc/dehydrated/certs/loki.qa.suse.de/fullchain.pem"

Added by nicksinger 6 days ago. Updated 5 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Observation

https://monitor.qa.suse.de/ reports "Unable to connect". Ping and ssh to monitor work but systemctl --failed on monitor shows that nginx failed to (re)start:

× nginx.service - The nginx HTTP and reverse proxy server
     Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2024-11-28 21:09:45 CET; 40min ago
   Duration: 6d 7h 32min 15.631s
    Process: 6795 ExecStartPre=/usr/sbin/nginx -t (code=exited, status=1/FAILURE)
        CPU: 61ms

Nov 28 21:09:45 monitor systemd[1]: Starting The nginx HTTP and reverse proxy server...
Nov 28 21:09:45 monitor nginx[6795]: nginx: [emerg] cannot load certificate "/etc/dehydrated/certs/loki.qa.suse.de/>
Nov 28 21:09:45 monitor nginx[6795]: nginx: configuration file /etc/nginx/nginx.conf test failed
Nov 28 21:09:45 monitor systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
Nov 28 21:09:45 monitor systemd[1]: nginx.service: Failed with result 'exit-code'.
Nov 28 21:09:45 monitor systemd[1]: Failed to start The nginx HTTP and reverse proxy server.

Related issues 1 (1 open0 closed)

Copied from openQA Infrastructure (public) - action #170338: No monitoring data from OSD since 2024-11-25 1449Z size:MIn Progressnicksinger2024-11-272024-12-12

Actions
Actions

Also available in: Atom PDF