所以今天我在使用时遇到了一堆错误须藤对我的命令Chromebook和Linux安装。例如，当我尝试删除我的谷歌浏览器测试版应用程序，我尝试了这个：
sudo apt-get remove google-chrome-beta
但我得到了这个错误：
(Reading database ... 81090 files and directories currently installed.)
Removing google-chrome-beta (74.0.3729.75-1) ...
Setting up 389-admin (1.1.43-1+b1) ...
Job for dirsrv-admin.service failed because the control process exited with error code.
See "systemctl status dirsrv-admin.service" and "journalctl -xe" for details.
invoke-rc.d: initscript dirsrv-admin, action "start" failed.
● dirsrv-admin.service - 389 Administration Server.
Loaded: loaded (/lib/systemd/system/dirsrv-admin.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-04-11 17:08:08 UTC; 39ms ago
Process: 7507 ExecStart=/usr/sbin/apache2 -k start -f /etc/dirsrv/admin-serv/httpd.conf (code=exited, status=1/FAILURE)
Apr 11 17:08:08 penguin systemd[1]: Starting 389 Administration Server....
Apr 11 17:08:08 penguin apache2[7507]: AH00558: apache2: Could not reliably determine the server's fully qualified doma… message
Apr 11 17:08:08 penguin apache2[7507]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/dirsrv/…rror log
Apr 11 17:08:08 penguin apache2[7507]: AH00014: Configuration check failed
Apr 11 17:08:08 penguin systemd[1]: dirsrv-admin.service: Control process exited, code=exited status=1
Apr 11 17:08:08 penguin systemd[1]: Failed to start 389 Administration Server..
Apr 11 17:08:08 penguin systemd[1]: dirsrv-admin.service: Unit entered failed state.
Apr 11 17:08:08 penguin systemd[1]: dirsrv-admin.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package 389-admin (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
dpkg: dependency problems prevent configuration of 389-ds-console:
389-ds-console depends on 389-admin; however:
Package 389-admin is not configured yet.
dpkg: error processing package 389-ds-console (--configure):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
389-admin
389-ds-console
E: Sub-process /usr/bin/dpkg returned an error code (1)
当我尝试更新我的软件包时，我什至得到了这一点，例如
sudo apt-get update && sudo apt-get upgrade
有什么建议么？
PS：我不想删除 Chrome-beta，这不是我的问题。这是我试图解决的错误，因为我在尝试更新时遇到了它。
另一件事：当我输入时apt-get install -f显示：
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?
所以我输入：sudo apt-get install -f这显示：
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
389-ds-console-doc
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up 389-admin (1.1.43-1+b1) ...
Job for dirsrv-admin.service failed because the control process exited with error code.
See "systemctl status dirsrv-admin.service" and "journalctl -xe" for details.
invoke-rc.d: initscript dirsrv-admin, action "start" failed.
● dirsrv-admin.service - 389 Administration Server.
Loaded: loaded (/lib/systemd/system/dirsrv-admin.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-04-11 19:39:39 UTC; 46ms ago
Process: 17449 ExecStart=/usr/sbin/apache2 -k start -f /etc/dirsrv/admin-serv/httpd.conf (code=exited, status=1/FAILURE)
Apr 11 19:39:38 penguin systemd[1]: Starting 389 Administration Server....
Apr 11 19:39:39 penguin apache2[17449]: AH00558: apache2: Could not reliably determine the server's fully qualified dom… message
Apr 11 19:39:39 penguin apache2[17449]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/dirsrv…rror log
Apr 11 19:39:39 penguin apache2[17449]: AH00014: Configuration check failed
Apr 11 19:39:39 penguin systemd[1]: dirsrv-admin.service: Control process exited, code=exited status=1
Apr 11 19:39:39 penguin systemd[1]: Failed to start 389 Administration Server..
Apr 11 19:39:39 penguin systemd[1]: dirsrv-admin.service: Unit entered failed state.
Apr 11 19:39:39 penguin systemd[1]: dirsrv-admin.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package 389-admin (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
389-admin
E: Sub-process /usr/bin/dpkg returned an error code (1)
然后我尝试了一下sudo dpkg --force-depends --configure 389-admin
，它输出：
Setting up 389-admin (1.1.43-1+b1) ...
Job for dirsrv-admin.service failed because the control process exited with error code.
See "systemctl status dirsrv-admin.service" and "journalctl -xe" for details.
invoke-rc.d: initscript dirsrv-admin, action "start" failed.
● dirsrv-admin.service - 389 Administration Server.
Loaded: loaded (/lib/systemd/system/dirsrv-admin.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-04-11 19:41:11 UTC; 43ms ago
Process: 17507 ExecStart=/usr/sbin/apache2 -k start -f /etc/dirsrv/admin-serv/httpd.conf (code=exited, status=1/FAILURE)
Apr 11 19:41:11 penguin systemd[1]: Starting 389 Administration Server....
Apr 11 19:41:11 penguin apache2[17507]: AH00558: apache2: Could not reliably determine the server's fully qualified dom… message
Apr 11 19:41:11 penguin apache2[17507]: (2)No such file or directory: AH02291: Cannot access directory '/var/log/dirsrv…rror log
Apr 11 19:41:11 penguin apache2[17507]: AH00014: Configuration check failed
Apr 11 19:41:11 penguin systemd[1]: dirsrv-admin.service: Control process exited, code=exited status=1
Apr 11 19:41:11 penguin systemd[1]: Failed to start 389 Administration Server..
Apr 11 19:41:11 penguin systemd[1]: dirsrv-admin.service: Unit entered failed state.
Apr 11 19:41:11 penguin systemd[1]: dirsrv-admin.service: Failed with result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package 389-admin (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
389-admin
我还注意到，每次我运行install,之类的命令时remove，upgrade它都会执行它应该执行的操作，但随后它会尝试设置 389-admin。
答案1
您可以像这样重新配置包安装：
sudo dpkg-reconfigure 389-admin
然后运行回来卸载：
sudo apt-get remove google-chrome-beta
或者，您可以在卸载之前直接将其删除google-chrome-beta：
sudo dpkg -r 389-admin
答案2
sudo工作正常，这只告诉系统apt-get以超级用户帐户运行（它正在这样做）。您的主要问题是损坏的软件包安装（389-admin），它看起来失败了，因为系统上缺少一个文件夹，导致 apache2 无法运行，在该软件包安装完成之前，apt 无法继续。如果您按照 Paradox 提到的说明进行操作，您应该能够解决该问题，但如果问题仍然存在，那么您应该查看哪些其他软件包无法安装。密切注意您收到的错误消息，因为它们准确地描述了问题所在
dpkg: error processing package 389-admin (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
dpkg: dependency problems prevent configuration of 389-ds-console:
389-ds-console depends on 389-admin; however:
Package 389-admin is not configured yet.
dpkg: error processing package 389-ds-console (--configure):
dependency problems - leaving unconfigured
Processing triggers for man-db (2.7.6.1-2) ...
Errors were encountered while processing:
389-admin
389-ds-console
答案3
我还没有足够的点来评论其他答案，但是根据您的评论线程，您需要删除或修复损坏的软件包（简单的路线就是删除，所以运行sudo apt-get remove 389-ds-console）
正如我在回答中所说，查看您收到的错误消息，它们准确地告诉您出了什么问题以及您需要做什么。