Randomly getting 'Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend)' through multiple runs #1120
Comments
miketimofeev
added
Area: Deployment / Release
investigate
|
Hello @GWarrior5595,
before apt installation. It should help to understand which process takes the file. The investigation is ongoing. I hope I will be able to return back with an answer or new ideas. |
|
Hello @GWarrior5595, |
|
@Darleev I am still running into the issue transiently. I tried the command but I don't get a response from that command before the failure happened |
|
Hello @GWarrior5595, I was able to reproduce the issue one time before Friday, but currently, the issue is not reproducing anymore on our side. |
|
Hello @GWarrior5595, |
|
@Darleev I still get the issue when i try to run this nightly. It succeeds every 3-6 days Here are the last few lines for the logs on failure ` ` |
miketimofeev
removed
the
investigate
|
Hi @GWarrior5595! |
|
@GWarrior5595 I'm going to close the issue since we haven't faced this issue any more after the fix but feel free to contact us if you have any concerns. |
|
Have seen that during Ubuntu16 build again, reopening for additional investigation |
|
@miketimofeev I have started running my packer builds again. I have pulled the latest |
|
@GWarrior5595 is it for ubuntu18? No changes being made for the template? |
|
@miketimofeev Yes, for the Ubuntu1804. I am using the templates from "main" branch of this repo |
|
@GWarrior5595 could you please provide as many cases as possible or all of them failed on |
|
@miketimofeev It has failed on that several times but sometimes it gets through that and fails on other parts such as the docker installation |
|
@GWarrior5595 So it's random. My assumption is that it can be some system update service. Would you mind adding Threads with similar issues for reference: |
|
@GWarrior5595 @prashant6475 could you please try the suggested solution? I've built 6 Ubuntu 16.04 images without any issues with this change. If it helps we'll create a PR, if not — will work further on the investigation |
miketimofeev
added
the
investigate
|
We are testing on ubuntu 18.04 image will add that fix and let you know |
|
Additionally, the following warnings are displayed at the end of a build: |
|
@ausfestivus thank you for the information. It's very strange since before branch publishing it was tested that build works as expected. |
|
I managed to get a couple of good builds out of the branch today. No other failures since the logs I posted earlier. Will keep an eye out for the updates. |
|
@ausfestivus thank you for the update, I have prepared another workaround for the issue, and added it to separate branch in the forked repo. We are looking forward to your reply. |
|
@ausfestivus @erphunranjbar I have updated the branch with the latest image scripts. We are looking forward to your reply. |
|
Hey @Darleev. Appreciate the poke. Sorry mate. |
|
Hey @Darleev, some time did turn up. I had one scheduled run which failed in one landscape. I re-ran the job and it finished fine. Here is the output from the job: Hope that helps. |
|
Hello @ausfestivus, |
|
Region: australiaeast |
|
@ausfestivus @erphunranjbar we have disabled all possible concurrent updates on Ubuntu images and added apt retry logic in ubuntu images. |
|
@Darleev sorry for not responding! I just got a chance to rerun our build and I still got an apt-lock issue: I am guessing it is from the |
|
@erphunranjbar is it from the latest main? |
|
@Darleev I switched over to the main branch for a run on the weekend. The pipeline now gets stuck at the following point and never progresses. Suspect this is a different issue in main though. Im running a build with the |
|
Latest output from failed run on |
|
Even i m getting this issue. Please find the logs below. amazon-ebs: output will be in this color. ==> amazon-ebs: Prevalidating any provided VPC information |
|
I'm getting this too with the ubuntu/20201115.1 release. |
|
Hello @erphunranjbar, |
|
Hello, In case of any questions, do not hesitate to contact us. |
Describe the bug
When I attempt to run the Ubuntu 18.04 provisioner, I keep getting the
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?error in random places. The image gets created nightly and i would say 90% of the time, it fails to create because of the lock... I addedsleep 80after the homebrew validation and it sometimes helps. I also added asudo killall apt apt-get || truein the beginning of most scripts to attempt to combat this and it only sometimes helps... Anyone have any suggestions on what I can do or if there is a workaround?Area for Triage:
Deployment/Release
Question, Bug, or Feature?:
Question/Bug
Virtual environments affected
Expected behavior
I would expect the Ubuntu 18.04 image to get created
Actual behavior
A description with steps to reproduce the issue. If your have a public example or repo to share,
please provide the link.
The text was updated successfully, but these errors were encountered: