그래서 오늘은 사용하는 동안 많은 오류가 발생했습니다.스도나에게 명령하다크롬북그리고리눅스설치하다. 예를 들어, 내 계정을 삭제하려고 하면구글 크롬 베타응용 프로그램에서 나는 이것을 시도했습니다.
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
어떤 제안이 있으십니까?
추신: 나는 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또한 와 같은 명령을 실행할 때마다 예상대로 수행되지만 389-admin을 설정하려고 시도한다는 것도 알아 remove냈습니다 upgrade.
답변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).
내 답변에서 말했듯이, 수신되는 오류 메시지를 살펴보세요. 오류 메시지는 정확히 무엇이 잘못되었고 무엇을 해야 하는지 알려줍니다.