Page MenuHomePhabricator responds with 503
Closed, ResolvedPublic


It seems is non-functional, responding with 503 errors for any request.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 22 2018, 6:34 PM
bd808 edited projects, added Toolforge; removed Cloud-Services.Jun 22 2018, 6:36 PM
bd808 added a subscriber: bd808.

Adding observability to help with classification and maybe to flag this for someone who can help figure out if we have a runbook for debugging Prometheus.

Bstorm added a subscriber: Bstorm.Jun 22 2018, 7:09 PM
$ systemctl status prometheus@tools.service
● prometheus@tools.service - prometheus server (instance tools)
   Loaded: loaded (/lib/systemd/system/prometheus@tools.service; static)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2018-06-22 19:02:37 UTC; 1s ago
  Process: 30784 ExecStart=/usr/bin/prometheus -storage.local.max-chunks-to-persist 524288 -storage.local.memory-chunks 1048576 -storage.local.path /srv/prometheus/tools/metrics -web.listen-address -web.external-url -storage.local.retention 730h0m0s -config.file /srv/prometheus/tools/prometheus.yml -storage.local.chunk-encoding-version 2 (code=exited, status=1/FAILURE)
 Main PID: 30784 (code=exited, status=1/FAILURE)

The issue appears to be that it failed suddenly at some point, and a lockfile at

$ sudo ls -l /srv/prometheus/tools/metrics/DIRTY
-rw-r--r-- 1 14736 wikidev 0 Jan 31 15:49 /srv/prometheus/tools/metrics/DIRTY

Apparently wasn't cleaned up. Now it is stuck in a restart loop trying to lock that file. I wonder if this died during network maintenance recently--or is the problem that old? I'm not 100% sure the safest way to ensure this comes back up in a consistent state. Removing the lock file should allow it to start the service, but...

Apparently, the file's existence shouldn't matter (at least in current Prometheus). It should be able to lock it, but it cannot

Dude! The answer was right in front of me. On a *nix system, prometheus tries to open the file for reading:

Above, the permissions on the file are from the LDAP user that we deleted. Chowning to the local prometheus user.

$ systemctl status prometheus@tools.service
● prometheus@tools.service - prometheus server (instance tools)
   Loaded: loaded (/lib/systemd/system/prometheus@tools.service; static)
   Active: active (running) since Fri 2018-06-22 19:44:36 UTC; 7min ago
 Main PID: 12729 (prometheus)
   CGroup: /system.slice/system-prometheus.slice/prometheus@tools.service
           └─12729 /usr/bin/prometheus -storage.local.max-chunks-to-persist 524288 -storage.local.memory-chunks 1048576 -storage.local.path /srv/prometheus/tools/metrics -web.listen-a.
Bstorm closed this task as Resolved.Jun 22 2018, 7:52 PM
Bstorm claimed this task.
Vvjjkkii renamed this task from responds with 503 to yfaaaaaaaa.Jul 1 2018, 1:02 AM
Vvjjkkii reopened this task as Open.
Vvjjkkii removed Bstorm as the assignee of this task.
Vvjjkkii triaged this task as High priority.
Vvjjkkii updated the task description. (Show Details)
Vvjjkkii removed a subscriber: Aklapper.
Matthewrbowker renamed this task from yfaaaaaaaa to responds with 503.Jul 1 2018, 1:31 AM
Matthewrbowker closed this task as Resolved.
Matthewrbowker assigned this task to Bstorm.
Matthewrbowker raised the priority of this task from High to Needs Triage.
Matthewrbowker updated the task description. (Show Details)
Matthewrbowker added a subscriber: Aklapper.