Done
Details
Security Level Help
NoneAssignee
Peter SirotnakPeter SirotnakReporter
Konstantin TrushinKonstantin TrushinPriority
MediumComponents
Labels
Details
Details
Security Level Help
None
Assignee
Peter Sirotnak
Peter SirotnakReporter
Konstantin Trushin
Konstantin TrushinPriority
Components
Labels
Smart Checklist
Smart Checklist
Smart Checklist
Created October 23, 2024 at 2:59 PM
Updated 2 days ago
Resolved November 13, 2024 at 10:18 AM
Platform: Ubuntu 24.04 inside a Docker container.
I was removing Percona Server for MongoDB with
sudo apt-get purge percona-server-mongodb-server percona-telemetry-agent
and got some errors related to the telemetry agent, the server has been removed successfully though. Removing the agent individually produced the following:
$ sudo apt-get remove percona-telemetry-agent Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: percona-telemetry-agent 0 upgraded, 0 newly installed, 1 to remove and 111 not upgraded. 1 not fully installed or removed. After this operation, 20.1 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 72567 files and directories currently installed.) Removing percona-telemetry-agent (1.0.1-1.noble) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 79.) debconf: falling back to frontend: Readline System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down dpkg: error processing package percona-telemetry-agent (--remove): installed percona-telemetry-agent package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: percona-telemetry-agent Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1)
I guess the issue is that the OS works in a Docker container and thus no
systemd
is available, while the post-removal script assumes it is present.