解析-拉-解.路径错误

Question

GoodDay all

新的一天，新的linux冒险在我的家庭服务器上：

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

背景资料：

最近，在apt更新& apt升级的例行执行之后，我将服务器更新/升级为最新更新，并开始工作。

后来，我试图在我的静态IP地址上对服务器进行ssh，但是没有连接。我认为我需要重新启动服务器，我应该可以再次运行并再次运行。稍后我再次向服务器ssh，仍然没有找到与主机的连接。那时我开始担心了。

在启动系统时，当我看到屏幕时，我注意到第一个失败是解析的-拉-解析式的，后来又不能带op网络(第二个失败)。

尝试了一些像这个页面一样的东西，但是没有帮助。

尝试了-xe的日志，得到了很多红色的东西。但我似乎并没有弄清楚为什么会发生这种情况。

所以现在我想知道是否有两个问题，或者是一个问题导致了另一个问题。正如我对Linux的一些基本了解一样，这远远超出了我的知识。

任何指点都是非常感谢的，我想事先对你的帮助表示感谢。

我已经有一个新的现场USB棒挂在重新安装服务器，但话说回来，有什么有趣的地方。

PS:我的服务器上的其他信息可以找到这里。

在这里，我有一个更新，持有libtevent >希望没有版本冲突

所以再一次，有人能解释一下这件事吗？

编辑：

systemctl状态解析

● 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状态解析-服务

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

systemctl状态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

Answer 1

因此，在做了更多的服务器研究之后，我的网络设备也出现了错误。因为上面的事情不那么容易，我想给另一个失败看一眼：

systemctl状态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网络list列表

给我

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

2 links listed.

由于我不是一个IT人员，我花了一段时间才意识到我的网络只是没有打开。

cat /etc/网络/接口

# 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

所以事情变得复杂起来，因为我不知道这意味着什么。因为某种原因，也许是因为我在某个地方遵循了指示

网络状态

然后给了我：

● 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-更新&apt-升级，进行得很好，重新启动了>没有互联网。

像我这样的白痴

也有相同的结果：

● 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状态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返回的代码相同。

因此，解决问题的原因显然是由于eth0没有启动。

这个故事可能会短得多，但是管理员可能会缩短它:)或者纠正我的语法。