[SOLVED] PVE Proxy geht nicht mehr und APT Update auch nicht

TZockt · Oct 12, 2021

Hi zusammen,

hab gerade folgendes Problem das seit gestern mein PVEProxy nicht mehr starten möchte und ich ebenfalls keine Updates mehr machen kann.
Hat jemand eventuell eine Idee?

APT Problem:

Bash:

root@pve ~ # apt-get update
Err:1 http://ftp.de.debian.org/debian bullseye InRelease
  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
Err:2 http://security.debian.org bullseye-security InRelease
  System error resolving 'security.debian.org:80' - getaddrinfo (16: Device or resource busy)
Err:3 http://download.proxmox.com/debian/pve bullseye InRelease
  System error resolving 'download.proxmox.com:80' - getaddrinfo (16: Device or resource busy)
Err:4 http://hwraid.le-vert.net/debian bullseye InRelease
  System error resolving 'hwraid.le-vert.net:80' - getaddrinfo (16: Device or resource busy)
Err:5 http://ftp.de.debian.org/debian bullseye-updates InRelease
  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
Reading package lists... Done
W: Failed to fetch http://ftp.de.debian.org/debian/dists/bullseye/InRelease  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://ftp.de.debian.org/debian/dists/bullseye-updates/InRelease  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://security.debian.org/dists/bullseye-security/InRelease  System error resolving 'security.debian.org:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bullseye/InRelease  System error resolving 'download.proxmox.com:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://hwraid.le-vert.net/debian/dists/bullseye/InRelease  System error resolving 'hwraid.le-vert.net:80' - getaddrinfo (16: Device or resource busy)
W: Some index files failed to download. They have been ignored, or old ones used instead.

PVEProxy Problem:

Code:

root@pve ~ # systemctl start pveproxy
Job for pveproxy.service failed because the control process exited with error code.
See "systemctl status pveproxy.service" and "journalctl -xe" for details.
root@pve ~ # systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
     Active: activating (start) since Tue 2021-10-12 16:09:20 CEST; 1s ago
    Process: 4529 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Cntrl PID: 4531 (pveproxy)
      Tasks: 1 (limit: 115808)
     Memory: 93.9M
        CPU: 1.690s
     CGroup: /system.slice/pveproxy.service
             └─4531 /usr/bin/perl -T /usr/bin/pveproxy start

Oct 12 16:09:20 pve.tzockt.de systemd[1]: Starting PVE API Proxy Server...
Oct 12 16:09:22 pve.tzockt.de pveproxy[4531]: start failed - Unrecognised protocol tcp at /usr/share/perl5/PVE/Daemon.pm line 835.
Oct 12 16:09:22 pve.tzockt.de pveproxy[4531]: start failed - Unrecognised protocol tcp at /usr/share/perl5/PVE/Daemon.pm line 835.
Oct 12 16:09:22 pve.tzockt.de systemd[1]: pveproxy.service: Control process exited, code=exited, status=255/EXCEPTION
Oct 12 16:09:22 pve.tzockt.de systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Oct 12 16:09:22 pve.tzockt.de systemd[1]: Failed to start PVE API Proxy Server.
Oct 12 16:09:22 pve.tzockt.de systemd[1]: pveproxy.service: Consumed 2.031s CPU time.
Oct 12 16:09:22 pve.tzockt.de systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 250.
Oct 12 16:09:22 pve.tzockt.de systemd[1]: Stopped PVE API Proxy Server.
Oct 12 16:09:22 pve.tzockt.de systemd[1]: pveproxy.service: Consumed 2.031s CPU time.

mira · Oct 12, 2021

Das sieht nicht gut aus.
Tritt das Problem auch nach einem Reboot auf?

TZockt · Oct 12, 2021

showiproute · Oct 12, 2021

Kannst du mal deinen DNS checken?
Der Fehler System error resolving 'ftp.de.debian.org:80 deutet darauf hin, dass es hier irgendwelche DNS Probleme gibt.

TZockt · Oct 12, 2021

DNS funktioniert ohne Probleme

Code:

root@pve ~ # nslookup ftp.de.debian.org
Server:         192.168.178.1
Address:        192.168.178.1#53

Non-authoritative answer:
Name:   ftp.de.debian.org
Address: 141.76.2.4

showiproute · Oct 12, 2021

hmm eine Idee käme mir noch: statt apt-get probier' nur mal apt update

TZockt · Oct 12, 2021

Joa kommt genau das gleiche.

Code:

root@pve ~ # apt update
Err:1 http://ftp.de.debian.org/debian bullseye InRelease
  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
Err:2 http://security.debian.org bullseye-security InRelease
  System error resolving 'security.debian.org:80' - getaddrinfo (16: Device or resource busy)
Err:3 http://download.proxmox.com/debian/pve bullseye InRelease
  System error resolving 'download.proxmox.com:80' - getaddrinfo (16: Device or resource busy)
Err:4 http://hwraid.le-vert.net/debian bullseye InRelease
  System error resolving 'hwraid.le-vert.net:80' - getaddrinfo (16: Device or resource busy)
Err:5 http://ftp.de.debian.org/debian bullseye-updates InRelease
  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://ftp.de.debian.org/debian/dists/bullseye/InRelease  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://ftp.de.debian.org/debian/dists/bullseye-updates/InRelease  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://security.debian.org/dists/bullseye-security/InRelease  System error resolving 'security.debian.org:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bullseye/InRelease  System error resolving 'download.proxmox.com:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://hwraid.le-vert.net/debian/dists/bullseye/InRelease  System error resolving 'hwraid.le-vert.net:80' - getaddrinfo (16: Device or resource busy)
W: Some index files failed to download. They have been ignored, or old ones used instead.

showiproute · Oct 12, 2021

Meiner Meinung nach deutet irgendetwas darauf hin, dass hier kein korrekter forward lookup durchgeführt wird.
Ich gehe mal aus via dig bekommst du auch einen Treffer?

Wenn dem so ist, kannst du mal versuchen, dass du die Adressen, die aptnicht auflösen kann in /etc/hosts einträgst und dann nochmals checken, ob du Updates findest.

TZockt · Oct 12, 2021

nope hat auch nicht geklappt

noPa$$word · Oct 13, 2021

Ich gehe davon aus, dass der Nameserver vom Router verwendet wird. Kannst du einmal den Google Nameserver (8.8.8.8) testen?

TZockt · Oct 13, 2021

klappt auch nicht

Am Netzwerk liegt es glaub weniger eher an diesem Fehler "getaddrinfo (16: Device or resource busy)"

fabian · Oct 13, 2021

funktioniert curl 1.1.1.1? sollte ein kurzes HTML dokument ausgeben..

TZockt · Oct 13, 2021

Jup funktioniert

Code:

root@pve ~ # curl 1.1.1.1
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>cloudflare</center>
</body>
</html>

fabian · Oct 13, 2021

okay, also zusammengefasst:
- DNS funktioniert
- HTTP (TCP) auf IP geht
- apt geht nicht weil glibc DNS fehlschlaegt
- pveproxy geht nicht weil binding fehlschlaegt

fuer die APT fehlermeldung liefert google den hinweis, dass eventuell permissions fuer pfade die glibc nachlaedt falsch sein koennten. vielleicht kannst du mal mit strace -ff -o strace_apt apt update schauen, welcher call 'EBUSY' zurueckliefert? von dem befehl werden einige files mit strace_apt prefix angelegt..

edit: vielleicht auch interessant - funktionieren die tests (DNS, curl) auch als nicht-root?

sowohl apt als auch pveproxy laufen (teilweise) als unprivilegierte user..

TZockt · Oct 13, 2021

User wechsel von Root aus geht schon mal nicht

Code:

root@pve ~ # su tzockt
su: failed to execute /bin/bash: Permission denied

und einloggen als User per SSH klappt auch nicht

Code:

root@homeserver ~ # ssh pve -l tzockt
tzockt@pve's password:
Linux pve.tzockt.de 5.11.22-5-pve #1 SMP PVE 5.11.22-10 (Tue, 28 Sep 2021 08:15:41 +0200) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
/bin/bash: Permission denied
Connection to pve closed.

Strace Ausgabe:

Code:

root@pve ~ # strace -ff -o strace_apt apt update
Err:1 http://ftp.de.debian.org/debian bullseye InRelease
  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
Err:2 http://security.debian.org bullseye-security InRelease
  System error resolving 'security.debian.org:80' - getaddrinfo (16: Device or resource busy)
Err:3 http://ftp.de.debian.org/debian bullseye-updates InRelease
  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
Err:4 http://download.proxmox.com/debian/pve bullseye InRelease
  System error resolving 'download.proxmox.com:80' - getaddrinfo (16: Device or resource busy)
Err:5 http://hwraid.le-vert.net/debian bullseye InRelease
  System error resolving 'hwraid.le-vert.net:80' - getaddrinfo (16: Device or resource busy)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://ftp.de.debian.org/debian/dists/bullseye/InRelease  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://ftp.de.debian.org/debian/dists/bullseye-updates/InRelease  System error resolving 'ftp.de.debian.org:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://security.debian.org/dists/bullseye-security/InRelease  System error resolving 'security.debian.org:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bullseye/InRelease  System error resolving 'download.proxmox.com:80' - getaddrinfo (16: Device or resource busy)
W: Failed to fetch http://hwraid.le-vert.net/debian/dists/bullseye/InRelease  System error resolving 'hwraid.le-vert.net:80' - getaddrinfo (16: Device or resource busy)
W: Some index files failed to download. They have been ignored, or old ones used instead.

fabian · Oct 13, 2021

das klingt als waeren irgendwo permissions grob falsch gesetzt - was sagt denn

Code:

stat /
stat /bin
stat /bin/bash

vom strace braeuchten wir nicht die ausgabe, sondern die generierten traces (files strace_apt*)

TZockt · Oct 13, 2021

Bash:

root@pve ~ # stat /
  File: /
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: fd01h/64769d    Inode: 2           Links: 18
Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-10-13 09:40:43.185530330 +0200
Modify: 2021-10-08 21:32:40.346725968 +0200
Change: 2021-10-08 21:32:40.346725968 +0200
 Birth: 2020-12-03 19:57:53.000000000 +0100
root@pve ~ # stat /bin/bash
  File: /bin/bash
  Size: 1234376         Blocks: 2416       IO Block: 4096   regular file
Device: fd01h/64769d    Inode: 1334008     Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-10-12 22:18:07.386177644 +0200
Modify: 2021-08-04 22:25:59.000000000 +0200
Change: 2021-08-06 12:48:31.452098987 +0200
 Birth: 2021-08-06 12:48:31.260122784 +0200
root@pve ~ # stat /bin
  File: /bin -> usr/bin
  Size: 7               Blocks: 0          IO Block: 4096   symbolic link
Device: fd01h/64769d    Inode: 12          Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-10-12 14:53:01.329498503 +0200
Modify: 2020-11-25 16:23:57.000000000 +0100
Change: 2020-12-03 19:57:53.567992861 +0100
 Birth: 2020-12-03 19:57:53.567992861 +0100

fabian · Oct 13, 2021

und stat /etc und stat /etc/hosts?

TZockt · Oct 13, 2021

Bash:

  File: /etc
  Size: 12288           Blocks: 24         IO Block: 4096   directory
Device: fd01h/64769d    Inode: 655361      Links: 111
Access: (0644/drw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-10-13 09:41:41.673529785 +0200
Modify: 2021-10-13 10:56:54.405487809 +0200
Change: 2021-10-13 10:56:54.405487809 +0200
 Birth: 2020-12-03 19:57:53.567992861 +0100
root@pve ~ # stat /etc/hosts
  File: /etc/hosts
  Size: 422             Blocks: 8          IO Block: 4096   regular file
Device: fd01h/64769d    Inode: 656781      Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2021-10-13 09:58:31.557520392 +0200
Modify: 2021-10-12 21:19:19.419313995 +0200
Change: 2021-10-13 09:58:29.905520407 +0200
 Birth: 2020-12-04 08:41:02.858812753 +0100

fabian · Oct 13, 2021

da haben wirs - /etc ist fuer niemanden ausser root auflistbar (fehlendes 'x' - 0644 statt 0755). hoffentlich nur der eine ordner - wuerde mal in der shell history suchen wem/wann das passiert ist

[SOLVED] PVE Proxy geht nicht mehr und APT Update auch nicht

Member

Proxmox Staff Member

Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Member

Renowned Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Attachments

Proxmox Staff Member

Member

Proxmox Staff Member