Question
"dpkg: unrecoverable fatal error" when trying to update monitoring agent
- Posted on October 13, 2019
- UbuntuMonitoringLinux Commands
Asked by Workshed
Hi,
I’m following the guide to upgrade the monitoring agent https://www.digitalocean.com/docs/monitoring/how-to/upgrade-legacy-agent/
However when I run
sudo apt-get purge do-agent
I get
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
I run the command as instructed and then re-run the first command but that results in
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
linux-headers-4.4.0-154
The following packages will be REMOVED:
do-agent* letsencrypt
The following packages will be upgraded:
linux-headers-4.4.0-154
1 upgraded, 0 newly installed, 2 to remove and 213 not upgraded.
3 not fully installed or removed.
Need to get 0 B/10.2 MB of archives.
After this operation, 63.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 870640 files and directories currently installed.)
Removing letsencrypt (0.19.0-1+ubuntu16.04.1+certbot+1) ...
dpkg: unrecoverable fatal error, aborting:
fork failed: Cannot allocate memory
E: Sub-process /usr/bin/dpkg returned an error code (2)
Can anyone help?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
If anyone comes across this thread I managed to resolve the issue with
debconf-i18nby doingapt-get install --reinstall debconf-i18nHi @KDSys,
Sorry for the long delay in getting back to you. Unfortunately we’re still in the same situation after adding those additional sources:
@KDSys unfortunately the dry-run gives us another error: