-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ubuntu packaging test: dpkg status database is locked by another process #33762
Comments
Pinging @elastic/es-core-infra |
Another one: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+packaging-tests/63/console
|
If `dpkg` fails, try and look for who has `/var/lib/dpkg/lock` open. If it exists and is open then return a failure with information about who has file open. This should help us debug elastic#33762. Closes elastic#34309
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+packaging-tests/154/consoleFull got us more debugging information:
I'll do a little more digging. |
I just checked on our ubuntu 1604 image. There is a file in
When I shift Jenkins into the server's local time zone it looks like the failure occurs right after 6am:
That doesn't quite line up! More digging! |
I think I figured it out! Ubuntu 16.04 uses systemd and In systemd Ubuntu 16.04 has a timer at
Which lines up well with the error. The unit file that is tied to the timer kicks off an apt-get update. That script runs |
New vagrant boxes have been pushed that have various upgrade services disabled. Details in: #37181 (comment) Last failure occurred on Thursday, i.e. 1 day before the updated packages were pushed: I am closing this issue now, will monitor build stats for any new occurrences of:
or
and reopen this issue if it happens again. |
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+packaging-tests/5/console failed as follows
Possibly related to #32309 (comment), but I can't see any other occurrences.
Allegedly this works, but not for me:
The text was updated successfully, but these errors were encountered: