I can't connect to the GUI after a while but the GUI was working fine before... The containers working fine, only the GUI failed this a ERR_CONNECTION_REFUSED
I try to restart the pveproxy without success
Any idea?
Code:
root@ns3128946:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.13 (stretch)
Release: 9.13
Codename: stretch
Code:
root@ns3128946:~# pveversion
pve-manager/5.4-15/d0ec33c6 (running kernel: 4.15.18-28-pve)
Code:
root@ns3128946:~# service networking status
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2020-10-07 10:26:54 CEST; 36min ago
Docs: man:interfaces(5)
Process: 5295 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Process: 5281 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=0/SUCCESS)
Main PID: 5295 (code=exited, status=1/FAILURE)
CPU: 84ms
oct. 07 10:26:54 ns3128946 systemd[1]: Starting Raise network interfaces...
oct. 07 10:26:54 ns3128946 ifup[5295]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
oct. 07 10:26:54 ns3128946 ifup[5295]: RTNETLINK answers: File exists
oct. 07 10:26:54 ns3128946 ifup[5295]: ifup: failed to bring up vmbr0
oct. 07 10:26:54 ns3128946 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
oct. 07 10:26:54 ns3128946 systemd[1]: Failed to start Raise network interfaces.
oct. 07 10:26:54 ns3128946 systemd[1]: networking.service: Unit entered failed state.
oct. 07 10:26:54 ns3128946 systemd[1]: networking.service: Failed with result 'exit-code'.I try to restart the pveproxy without success
Code:
root@ns3128946:~# service pveproxy restart
Job for pveproxy.service failed because of unavailable resources or another system error.
See "systemctl status pveproxy.service" and "journalctl -xe" for details.
root@ns3128946:~# service pveproxy status
● pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
Active: failed (Result: resources) since Wed 2020-10-07 10:41:07 CEST; 6s ago
Process: 7540 ExecStop=/usr/bin/pveproxy stop (code=exited, status=0/SUCCESS)
Process: 7440 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
Process: 18312 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
Main PID: 3074 (code=exited, status=255)
CPU: 639ms
oct. 07 10:41:06 ns3128946 systemd[1]: Starting PVE API Proxy Server...
oct. 07 10:41:07 ns3128946 pveproxy[18312]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
oct. 07 10:41:07 ns3128946 pveproxy[18312]: start failed - Unable to create new inotify object: Too many open files at /usr/share/perl5/PVE/INotify.pm line 397.
oct. 07 10:41:07 ns3128946 pveproxy[18502]: start failed - Unable to create new inotify object: Too many open files at /usr/share/perl5/PVE/INotify.pm line 397.
oct. 07 10:41:07 ns3128946 systemd[1]: pveproxy.service: PID file /var/run/pveproxy/pveproxy.pid not readable (yet?) after start: No such file or directory
oct. 07 10:41:07 ns3128946 systemd[1]: pveproxy.service: Daemon never wrote its PID file. Failing.
oct. 07 10:41:07 ns3128946 systemd[1]: Failed to start PVE API Proxy Server.
oct. 07 10:41:07 ns3128946 systemd[1]: pveproxy.service: Unit entered failed state.
oct. 07 10:41:07 ns3128946 systemd[1]: pveproxy.service: Failed with result 'resources'.Any idea?
