-
Notifications
You must be signed in to change notification settings - Fork 34
Troubleshooting Guide
Mark Feit edited this page Feb 7, 2024
·
1 revision
THIS IS A WORK IN PROGRESS
Before doing anything else, make sure pScheduler is fully-functional on the host in question:
$ pscheduler troubleshoot
Performing basic troubleshooting of ps.example.org.
ps.example.org:
Measuring MTU... 65535 (Local)
Looking for pScheduler... OK.
Fetching API level... 5
Checking clock... Unsynchronized (Not considered fatal)
Exercising API... Archivers... Contexts... Tests... Tools... OK.
Fetching service status... OK.
Checking services... Ticker... Scheduler... Runner... Archiver... OK.
Checking limits... OK.
Last run scheduled... 1 hour ago
Last run completed... 1 hour ago
Idle test.... 4 seconds... Finished... Checking archiving... OK.
pScheduler appears to be functioning normally.
If the process ends with anything other than pScheduler appears to be functioning normally
, there is a problem.
Note that to troubleshoot a remote host, you can do this:
$ pscheduler troubleshoot --host ps2.example.org
$ pscheduler schedule -PT1H
...
2024-02-07T19:50:39Z - 2024-02-07T19:50:41Z (Finished)
idle --duration PT2S (Run with tool 'snooze')
https://work/pscheduler/tasks/17db87d0-1d42-47d2-9a5e-2b770756274e/runs/fdd4f33d-d45a-4b3e-8820-3402591223d3
...
The URL at the bottom of each section
$ pscheduler result --full https://work/pscheduler/tasks/17db87d0-1d42-47d2-9a5e-2b770756274e/runs/fdd4f33d-d45a-4b3e-8820-3402591223d3
2024-02-07T19:50:39+00:00 on work with snooze:
...
Archivings:
To Campus Archive using http, Finished
2024-02-07T19:50:42Z Succeeded
To Regional Archive using http, Unfinished
2024-02-07T19:50:41Z Unable to connect to ps-archive.example.net: connection refused
2024-02-07T19:50:52Z Unable to connect to ps-archive.example.net: connection refused
2024-02-07T19:51:02Z Unable to connect to ps-archive.example.net: connection refused; giving up.