Goedenavond.
[timestamp : 23.00]
Ik hoop dat ik hier de juiste hulp kan vinden. Al denk ik op dit moment dat ik fysiek bezoek nodig ga hebben om het opgelost te krijgen.
Ik hoop niet dat het erg is, maar ik had deze vraag ook al op askubuntu gesteld, maar behalve commentaar op mijn originele layout was er nog niet veel reactie :
https://askubuntu.com/questions/1112058/resolvconf-pull-resolved-path-errorGoodDay all,
New day, new linux adventures on my home server:
Can resolvconf-pull-resolved.path be blocking my servers internet connection ?
Background info:
I updated/upgraded my server to the latest updates recently, following the routine execution of apt update && apt upgrade and went to work.
Later I was trying to ssh to my server on the static IP address I have for it, but there was no connection. Figured I needed to reboot the server and I should be good to go again and ran off again. Sometime later I ssh again to the server, still found no connection to host. By then I got worried.
Booting the system while looking to the screen I noticed the first [FAILED] to be resolvconf-pull-resolved and a bit later unable to bring op networking (second [FAILED]).
Tried some stuff already like this page, but that did not help.
Tried journalctl -xe and got a lot of stuff in red. But I did not seem to get to the bottom of why this is happening.
So now I am wondering if there are 2 problems, or that it is 1 problem that leads to another. As I know my around Linux a bit to do basic stuff, this is way above my knowledge.
Any pointers are well appreciated and I would like to say thanks in advance for any help.
I already have a new live USB stick hanging around for reinstalling the server, but then again, what is the fun in that.
PS: Other intel information on my server can be found Here.
Where I have an update hold on libtevent > hope that there is no version conflict
So again, can somebody shed light on this?
EDIT:
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
Vanavond ben ik hier nog eens mee bezig geweest, en er is nog iets dat me opvalt :
mijn netwerk (eth0) lijkt ook niet te werken. (tussendoor werd ik ff gek)
Zoals jullie zullen begrijpen is mijn server niet te bereiken via ssh, dus alle output moest gegenereerd worden met een usb stick. Op zich niet erg. was weer erg leerzaam. schijnbaar is ergens tussen woensdag en vrijdag het ownership van mijn home folder ook verandert aangezien ik hier geen output in text bestand mocht genereren. Maar even terug naar waar het om draait >
tijdens starten zag ik ook dat er iets met netwerkinterfaces niet goed ging:
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'.networkctl status
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 ether off unmanaged
2 links listed.cat /etc/network/interfaces
# 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 dhcplspci
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[timestamp 23.30]
Om het verhaal even lekker gecompliceerd te maken:
Terwijl ik al aardig wat websites en linkjes heb gevolgd, en heel wat had geprobeerd, vooral om de oorzaak te vinden en ik met moeite (vanwege ownership issues) die outputs van die commands op mijn usb stick aan het friemelen was zie ik tot mijn hele stomme verbazing dat networkctl-status ineens dit weergeeft :
● 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)Waarbij state :
routable duidelijk opvalt. Dit is het punt waarop ik van mijn stoel glij en me afvraag waar het misgaat. ik ping 8.8.8.8 > krijg wonderbaarlijk nog een antwoord ook.
Ik snel apt-update && apt-updrage uitgevoerd > in de hoop dat er iets veranderd. Na een reboot >
geen internetzucht... en toch ook weer niet. schijnbaar heeft 1 van de commando's die ik uitgevoerd heb iets getriggered waardoor wel mijn interface up gaat.
1 voor 1 alles nagelopen met iedere keer networkctl status tussendoor, blijkt dat er na sudo dhclient de status te veranderen en mijn eth0 up gaat.
dan komt ook ineens (logisch waarschijnlijk) resolvconf.service weer kijken :
diet@rabbithole:~$ sudo 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
blijft dat onderstaande 2 inactive/dead zijn.
diet@rabbithole:~$ sudo systemctl status resolvconf
resolvconf-pull-resolved.path resolvconf-pull-resolved.service resolvconf.service
diet@rabbithole:~$ sudo 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 26 23:29:32 rabbithole systemd[1]: resolvconf-pull-resolved.path: Refusing to start, unit to trigger not loaded.
Jan 26 23:29:32 rabbithole systemd[1]: Failed to start resolvconf-pull-resolved.path.
[timestamp 0.04]
Dus op dit moment denk ik dat het bezoek nog even niet nodig is. Nu alleen nog maar uitvogelen waarom ik sudo dhclient moet doen om eth0 up te krijgen. Dat zal ik vandaag niet meer uitvogelen, maar mocht iemand nog een tip hebben dan hoor ik dat graag.
