Neuer ioBroker-Blog online: Monatsrückblick März/April 2026

[stefu87_CH]

Hallo zusammen

Ich habe bei mir Zuhause das ganze Netzwerk umgestellt. Und nun habe ich auf dem Proxmox Server gemerkt, das es mir diesen Fehler im Log schreibt:

Dec 11 19:47:05 Proxmox nut-monitor[2026949]: Network UPS Tools upsmon 2.8.0
Dec 11 19:47:13 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 19:47:21 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 19:47:29 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 19:47:37 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 19:47:45 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 19:47:53 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 19:48:02 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 19:48:10 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 19:48:18 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 19:48:26 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 19:48:34 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host

Wie kann ich den Dienst vorläufig stoppen bzw. löschen??

Mit dem Befehl

sudo systemctl mask nut-monitor.service

funktioniert das nicht.

[peterfido]

@stefu87_ch
Auf dem Proxmox Host gibt es normal nur root. Also kein sudo notwendig.

systemctl disable nut-server.service nut-client.service

geht nicht?

[stefu87_CH]

@peterfido Nein das klappt auch nicht.

Dec 11 20:25:58 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 20:26:02 Proxmox systemd[1]: Stopping user@0.service - User Manager for UID 0...
Dec 11 20:26:02 Proxmox systemd[2045588]: Activating special unit exit.target...
Dec 11 20:26:02 Proxmox systemd[2045588]: Stopped target default.target - Main User Target.
Dec 11 20:26:02 Proxmox systemd[2045588]: Stopped target basic.target - Basic System.
Dec 11 20:26:02 Proxmox systemd[2045588]: Stopped target paths.target - Paths.
Dec 11 20:26:02 Proxmox systemd[2045588]: Stopped target sockets.target - Sockets.
Dec 11 20:26:02 Proxmox systemd[2045588]: Stopped target timers.target - Timers.
Dec 11 20:26:02 Proxmox systemd[2045588]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Dec 11 20:26:02 Proxmox systemd[2045588]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dec 11 20:26:02 Proxmox systemd[2045588]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Dec 11 20:26:02 Proxmox systemd[2045588]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Dec 11 20:26:02 Proxmox systemd[2045588]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Dec 11 20:26:02 Proxmox systemd[2045588]: Removed slice app.slice - User Application Slice.
Dec 11 20:26:02 Proxmox systemd[2045588]: Reached target shutdown.target - Shutdown.
Dec 11 20:26:02 Proxmox systemd[2045588]: Finished systemd-exit.service - Exit the Session.
Dec 11 20:26:02 Proxmox systemd[2045588]: Reached target exit.target - Exit the Session.
Dec 11 20:26:02 Proxmox systemd[1]: user@0.service: Deactivated successfully.
Dec 11 20:26:02 Proxmox systemd[1]: Stopped user@0.service - User Manager for UID 0.
Dec 11 20:26:02 Proxmox systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Dec 11 20:26:02 Proxmox systemd[1]: run-user-0.mount: Deactivated successfully.
Dec 11 20:26:02 Proxmox systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Dec 11 20:26:02 Proxmox systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Dec 11 20:26:02 Proxmox systemd[1]: Removed slice user-0.slice - User Slice of UID 0.
Dec 11 20:26:06 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 20:26:15 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 20:26:23 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 20:26:31 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 20:26:39 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 20:26:47 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 20:26:55 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host
Dec 11 20:27:04 Proxmox nut-monitor[859]: UPS [ups@192.168.0.188]: connect failed: Connection failure: No route to host

[MCU]

@stefu87_ch chatgpt ->

systemctl stop nut-server
systemctl stop nut-monitor
systemctl disable nut-server
systemctl disable nut-monitor
systemctl status nut-server

[stefu87_CH]

@mcu sagte in NUT-Monitor entfernen?:

@stefu87_ch chatgpt ->

sudo systemctl stop nut-server
sudo systemctl stop nut-monitor
sudo systemctl disable nut-server
sudo systemctl disable nut-monitor
sudo systemctl status nut-server

Hat funktioniert einfach wie schon peterfido geschrieben hat ohne sudo ausführen.