업그레이드 후 NetworkManager를 시작할 수 없습니다.

업그레이드 후 NetworkManager를 시작할 수 없습니다.

업그레이드 후 NetworkManager를 시작할 수 없습니다.

sudo service network-manager restart처음에 다시 시작하는지 확인하기 위해 running: 을 시도했지만 다음 오류가 발생했습니다.

Job for NetworkManager.service failed because the control process exited with error code.
See "systemctl status NetworkManager.service" and "journalctl -xe" for details.

그래서 확인해보니 systemctljounalctl. systemctl은 다음을 반환합니다.

 NetworkManager.service - Network Manager
     Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2022-06-05 12:25:53 CDT; 1min 7s ago
       Docs: man:NetworkManager(8)
    Process: 4097 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=exited, status=1/FAILURE)
   Main PID: 4097 (code=exited, status=1/FAILURE)

Jun 05 12:25:53 joule systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 5.
Jun 05 12:25:53 joule systemd[1]: Stopped Network Manager.
Jun 05 12:25:53 joule systemd[1]: NetworkManager.service: Start request repeated too quickly.
Jun 05 12:25:53 joule systemd[1]: NetworkManager.service: Failed with result 'exit-code'.
Jun 05 12:25:53 joule systemd[1]: Failed to start Network Manager.

Journalctl은 다음을 제공합니다.

Jun 05 12:25:53 joule systemd[1]: Failed to start Network Manager.
-- Subject: A start job for unit NetworkManager.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit NetworkManager.service has finished with a failure.
-- 
-- The job identifier is 3727 and the job result is failed.
Jun 05 12:25:53 joule systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Automatic restarting of the unit NetworkManager.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Jun 05 12:25:53 joule systemd[1]: Stopped Network Manager.
-- Subject: A stop job for unit NetworkManager.service has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A stop job for unit NetworkManager.service has finished.
-- 
-- The job identifier is 3808 and the job result is done.
Jun 05 12:25:53 joule systemd[1]: NetworkManager.service: Start request repeated too quickly.
Jun 05 12:25:53 joule systemd[1]: NetworkManager.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit NetworkManager.service has entered the 'failed' state with result 'exit-code'.
Jun 05 12:25:53 joule systemd[1]: Failed to start Network Manager.
-- Subject: A start job for unit NetworkManager.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit NetworkManager.service has finished with a failure.
-- 
-- The job identifier is 3808 and the job result is failed.
Jun 05 12:25:55 joule /usr/lib/gdm3/gdm-x-session[2021]: (EE) client bug: timer event6 debounce: scheduled expiry is in the past (-10ms), your system is too slow
Jun 05 12:25:55 joule /usr/lib/gdm3/gdm-x-session[2021]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-24ms), your system is too slow
Jun 05 12:26:19 joule /usr/lib/gdm3/gdm-x-session[2021]: (EE) client bug: timer event6 debounce: scheduled expiry is in the past (-1ms), your system is too slow
Jun 05 12:26:19 joule /usr/lib/gdm3/gdm-x-session[2021]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-14ms), your system is too slow
Jun 05 12:27:00 joule /usr/lib/gdm3/gdm-x-session[2021]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-2ms), your system is too slow
Jun 05 12:27:05 joule /usr/lib/gdm3/gdm-x-session[2021]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-10ms), your system is too slow
Jun 05 12:27:15 joule systemd[1]: Starting Message of the Day...
-- Subject: A start job for unit motd-news.service has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit motd-news.service has begun execution.
-- 
-- The job identifier is 3889.
Jun 05 12:27:15 joule systemd[1]: motd-news.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit motd-news.service has successfully entered the 'dead' state.
Jun 05 12:27:15 joule systemd[1]: Finished Message of the Day.
-- Subject: A start job for unit motd-news.service has finished successfully
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit motd-news.service has finished successfully.
-- 
-- The job identifier is 3889.
Jun 05 12:28:20 joule /usr/lib/gdm3/gdm-x-session[2021]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-10ms), your system is too slow

내가 가진 한 가지 단서는 내 이더넷 인터페이스에 이름이 지정되어 enp0s31f6실행하면 sudo dhclient enp0s31f6인터넷에 다시 연결할 수 있다는 것이었습니다. 하지만 이 기계를 서버로 사용하고 싶기 때문에 지속 가능한 옵션은 아닙니다.

다음을 편집하고 추가해 보았지만 /etc/network/interfaces도움이 되지 않는 것 같습니다.

auto enp0s31f6
iface enp0s31f6 inet dhcp

혼란스럽고 사람들이 다음에 무엇을 시도할지 궁금합니다.

메타데이터:

> dhclient --version 
isc-dhclient-4.4.1
> hostnamectl
...
           Boot ID: 0789175e8bad4cb58f441217f4d1135d
  Operating System: Ubuntu 20.04.4 LTS
            Kernel: Linux 5.4.0-113-generic
      Architecture: x86-64

관련 정보