Timeline for shibd daemon 'timeout' on systemctl start
Current License: CC BY-SA 4.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 26, 2019 at 12:50 | answer | added | fred2 | timeline score: 1 | |
| Jul 26, 2019 at 1:11 | history | edited | fred2 | CC BY-SA 4.0 |
deleted 2 characters in body
|
| Jul 26, 2019 at 1:11 | comment | added | fred2 | FYI - the current timeout appears to be 5 minutes, not 1.5 minutes as I said. However it is still too short for the metadata to be validated and import. | |
| Jul 26, 2019 at 0:58 | comment | added | fred2 |
Hi @MarkWagner. Running those commands returned nothing at all, so I output all variable, and I got the following:` TimeoutStartUSec=5min` TimeoutStopUSec=5min Result=timeout JobTimeoutUSec=infinity JobTimeoutAction=none
|
|
| Jul 25, 2019 at 17:40 | comment | added | Mark Wagner |
Are the values reported by systemctl show shibd.service -p TimeoutStartSec systemctl show shibd.service -p TimeoutStopSec systemctl show shibd.service -p TimeoutSec correct?
|
|
| Jul 25, 2019 at 16:54 | history | asked | fred2 | CC BY-SA 4.0 |