tree 44fc4f362a368d8a4989a1632a988bf68b6b9a03
parent 7460ce02495d7792f2c3bf768e1368543e6a8d87
author Matt Spinler <spinler@us.ibm.com> 1646242962 -0600
committer Matt Spinler <spinler@us.ibm.com> 1646665496 +0000

PEL: Shorten D-Bus timeout value

There are several D-Bus method calls made when creating a PEL to collect
data, and if one of the daemons called into is hung, then
phosphor-log-manager can also hang up to the default timeout value of
25s and an error will be returned to the PEL creator even though the PEL
will eventually be created successfully.

This can cause all sorts of issues for the callers, such as preventing
the PEL from begin reported to the hardware management console to
causing a boot fail because hostboot gets a failure trying to log an
error and shuts down.

To help prevent this, change the timeout value of all D-Bus calls to 10
seconds down from the 25.  This would allow two timeouts to occur during
the creation of a PEL without hitting the 25s timeout that callers use.
When timeouts are hit creating a PEL, that field just won't be filled in
and the PEL can otherwise be created with no issues.

Ten seconds was chosen to allow two failures to occur while still
allowing plenty of time for completion from a healthy daemon.  Also it
seems like if an operation doesn't complete within 10s it wouldn't
complete within 25 either.

Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ib9f2150c235e19109468d562dad697c4949c09a9