resolvconf-pull-resolved.path 错误

resolvconf-pull-resolved.path 错误

大家好,

新的一天,我的家庭服务器上新的 Linux 冒险:

Can resolvconf-pull-resolved.path be blocking my servers internet connection ?

背景信息:

我最近按照 apt update && apt upgrade 的例行执行将我的服务器更新/升级到最新更新并开始工作。

后来我尝试使用我拥有的静态 IP 地址 ssh 连接到我的服务器,但没有连接。我想我需要重新启动服务器,然后我就可以再次运行了,然后又跑开了。过了一会儿,我再次 ssh 连接到服务器,仍然没有找到与主机的连接。那时我开始担心了。

启动系统时看着屏幕,我注意到第一个 [FAILED] 被 resolvconf-pull-resolved 并且稍后无法带来 op 网络(第二个 [FAILED])。

尝试了一些已经类似此页面的内容,但没有帮助。

尝试了 journalctl -xe,结果显示很多红色内容。但我似乎没有弄清楚为什么会发生这种情况。

所以现在我想知道是否存在 2 个问题,或者 1 个问题导致另一个问题。由于我对 Linux 了解一些基本知识,这远远超出了我的知识范围。

非常感谢您的任何指点,并想提前感谢您提供的帮助。

我已经有了一个新的实时 USB 记忆棒,用于重新安装服务器,但是话又说回来,这有什么乐趣呢?

PS:其他情报可以在我的服务器上找到这里

我对 libtevent 进行了更新,希望没有版本冲突

那么,有人可以再次解释一下这个问题吗?

编辑:

systemctl status resolvconf-pull-resolved.path

● resolvconf-pull-resolved.path Loaded: loaded (/lib/systemd/system/resolvconf-pull-resolved.path; enabled; vendor preset: enabled) Active: inactive (dead) Jan 22 21:46:48 rabbithole systemd1: resolvconf-pull-resolved.path: Refusing to start, unit to trigger not loaded. Jan 22 21:46:48 rabbithole systemd1: Failed to start resolvconf-pull-resolved.path.

systemctl status resolvconf-pull-resolved.service

● resolvconf-pull-resolved.service Loaded: error (Reason: Invalid argument) Active: inactive (dead)

systemctl status resolvconf.service

● resolvconf.service - Nameserver information manager Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; vendor preset: enabled) Active: active (exited) since Tue 2019-01-22 21:46:47 CET; 4min 10s ago Docs: man:resolvconf(8) Process: 545 ExecStart=/sbin/resolvconf --enable-updates (code=exited, status=0/SUCCESS) Process: 538 ExecStartPre=/bin/touch /run/resolvconf/postponed-update (code=exited, status=0/SUCCESS) Process: 535 ExecStartPre=/bin/mkdir -p /run/resolvconf/interface (code=exited, status=0/SUCCESS) Main PID: 545 (code=exited, status=0/SUCCESS) CGroup: /system.slice/resolvconf.service Jan 22 21:46:47 rabbithole systemd1: Starting Nameserver information manager... Jan 22 21:46:47 rabbithole systemd1: Started Nameserver information manager. Jan 22 21:46:47 rabbithole resolvconf[545]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf

答案1

因此,在对服务器进行更多研究后,我的网络设备也出现了错误。由于上述问题不太简单,所以我想看看另一个故障:

sudo systemctl status networking.service 返回此信息:

 ● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset:      
   enabled)
  Drop-In: /run/systemd/generator/networking.service.d
           └─50-insserv.conf-$network.conf
   Active: failed (Result: exit-code) since Sat 2019-01-26 22:47:08 CET; 15min ago
     Docs: man:interfaces(5)
 Main PID: 707 (code=exited, status=1/FAILURE)

Jan 26 22:47:07 rabbithole systemd[1]: Starting Raise network interfaces...
Jan 26 22:47:07 rabbithole sh[702]: Unknown interface eth0
Jan 26 22:47:08 rabbithole ifup[707]: Unknown interface eth0
Jan 26 22:47:08 rabbithole systemd[1]: networking.service: Main process exited,     
                code=exited, status=1/FAILURE
Jan 26 22:47:08 rabbithole systemd[1]: Failed to start Raise network interfaces.
Jan 26 22:47:08 rabbithole systemd[1]: networking.service: Unit entered failed state.
Jan 26 22:47:08 rabbithole systemd[1]: networking.service: Failed with result'exit-code'.

sudo networkctl 列表

给我

 IDX LINK             TYPE               OPERATIONAL SETUP     
1 lo               loopback           carrier     unmanaged 
2 eth0             ether              off         unmanaged 

2 links listed.

由于我不是 IT 人员,所以我花了一些时间才意识到我的网络没有打开。

猫/等/网络/接口

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo eth0
    iface lo inet loopback

# The primary network interface
auto eth0
    iface dhcp inet dhcp

那时我以为网卡坏了

串行通信

00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port (rev 02)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 02)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801IB (ICH9) 2 port SATA Controller [IDE mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA Controller [IDE mode] (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporation GT215 [GeForce GT 240] (rev a2)
01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)
02:00.0 Ethernet controller: Qualcomm Atheros Attansic L1 Gigabit Ethernet (rev b0)
03:00.0 SATA controller: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)
03:00.1 IDE interface: JMicron Technology Corp. JMB363 SATA/IDE Controller (rev 03)
05:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)

但这表明网卡没有任何问题,所以现在我认为一定是其他地方出了问题。

然后我就这么做了(不知道在哪里找到的)

sudo dhclient

这给了我:

/etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf

所以事情对我来说变得复杂了,因为我不确定这意味着什么。出于某种原因,也许是因为我遵循了某处的指示。

networkctl 状态

然后给了我:

● 2: eth0
   Link File: /lib/systemd/network/99-default.link
Network File: n/a
        Type: ether
       State: routable (unmanaged)
        Path: pci-0000:02:00.0
      Driver: atl1
      Vendor: Qualcomm Atheros
       Model: Attansic L1 Gigabit Ethernet (P5KPL-VM Motherboard)
  HW Address: 00:1b:fc:5a:3c:7e (ASUSTek COMPUTER INC.)
     Address: 192.168.178.37
              fe80::21b:fcff:fe5a:3c7e
     Gateway: 192.168.178.1 (Cisco SPVTG)

其中状态:可路由(未管理)变为绿色。

尝试 ping 8.8.8.8,立即得到答复。然后我以为我已经解决了问题,执行了 apt-update && apt-upgrade,一切顺利,重新启动 > 没有互联网

像我这样白痴

再次执行 sudo dhclient ,结果相同:

● 2: eth0
   Link File: /lib/systemd/network/99-default.link
Network File: n/a
        Type: ether
       State: routable (unmanaged)
        Path: pci-0000:02:00.0
      Driver: atl1
      Vendor: Qualcomm Atheros
       Model: Attansic L1 Gigabit Ethernet (P5KPL-VM Motherboard)
  HW Address: 00:1b:fc:5a:3c:7e (ASUSTek COMPUTER INC.)
     Address: 192.168.178.37
              fe80::21b:fcff:fe5a:3c7e
     Gateway: 192.168.178.1 (Cisco SPVTG)

互联网再次备份

做过

systemctl status resolvconf.service

● resolvconf.service - Nameserver information manager
   Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sat 2019-01-26 23:29:31 CET; 25min ago
         Docs: man:resolvconf(8)
  Process: 547 ExecStart=/sbin/resolvconf --enable-updates (code=exited, status=0/SUCCESS)
  Process: 542 ExecStartPre=/bin/touch /run/resolvconf/postponed-update (code=exited, status=0/SUCCESS)
  Process: 538 ExecStartPre=/bin/mkdir -p /run/resolvconf/interface (code=exited, status=0/SUCCESS)
 Main PID: 547 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/resolvconf.service

Jan 26 23:29:31 rabbithole systemd[1]: Starting Nameserver information manager...
Jan 26 23:29:31 rabbithole systemd[1]: Started Nameserver information manager.
Jan 26 23:29:31 rabbithole resolvconf[547]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf

这个故事中有趣的部分是我刚刚意识到最后一行与 sudo dhclient 返回的代码相同。

因此,resolvconf 的情况显然是由于 eth0 没有启动而导致的。

这个故事可能本来可以短得多,但有些管理员可能会缩短它:)或者纠正我的语法。

相关内容