Bug #7639
closedTimeout error when searching for updates
0%
Description
Some days, at 16:11 (it was 15:11 before the time change) we get the email from cron with subject:
Cron <root@mentat-hub> if test -x /usr/sbin/apticron; then /usr/sbin/apticron --cron; else true; fi
and body:
Error: Timeout was reached
Updated by Rajmund Hruška about 1 year ago
- Subject changed from timeout error when searching for updates to Timeout error when searching for updates
Updated by Rajmund Hruška about 1 year ago
I tried manually running apt-get commands from /usr/sbin/apticron source code, but I didn't get the error. Also, googling this error message doesn't come up with any satisfying solutions.
Updated by Rajmund Hruška about 1 year ago
- To be discussed changed from No to Yes
Updated by Rajmund Hruška about 1 year ago
On 13 April, Pavel Kácha edited /etc/cron.d/apticron and changed the time when the job is scheduled to be executed. But a few minutes later, the previous (default) value appeared again and the file with updated value was renamed to /etc/cron.d/apticron~.
Since that day, we no longer get the timeout error but we also don't receive email about pending updates. Prior to changing the /etc/cron.d/apticron, we were receiving emails about pending updates for postgresql-common and postgresql-client-common. I tried updating them now and it says that they are on the newest version, the same one which was mentioned in the email. Did someone update those packages?
Updated by Rajmund Hruška about 1 year ago
- Status changed from New to Closed
- Assignee set to Rajmund Hruška
Radko Krkoš updated the packages so we no longer receive the emails.
As Pavel Kácha suggested, if this issue comes back, we should try temporarily removing the repository to see which repository is the cause of this error.