proxmox node flood messages after adding proxmox backup server as a storage

[ieronymous]

Hello

I notified these messages accidentally while I was watching syslog of the node (and not the backup server). It hag and kept generating multiple messages
Apr 06 02:08:43 node_name pvedaemon[22537]: Can't connect to ip_of_prox_backup: error fetching datastores - 500 Can't connect to ip_of_prox_backup:8007 (No route to host)

Of course when I turn on the prox_backup, the messages disappear . Is there a way to get rid of these messages by turning off a service or something? After all if you dont have the system on a production environment you maybe have schedule the backup-server to open at a specific time to get these backups and close again. Why you have to tolerate all these messages until the next time the backup will be online again? I believe all having these messages and they just didnt notice it.

Thank you

 

[dcsapak]

you can disable the relevant storage if it is not up (datacenter -> storage -> edit)

 

[ieronymous]

you can disable the relevant storage if it is not up (datacenter -> storage -> edit)

Thank you for the answer. Well yeah that did the trick with the extra step to untick the enable option and apply, but this way backup storage completely removed from gui (not even greyd out) I know that re enabling it will make it appear again but isnt there a service I could stop and start like the one mentioned in the syslog ->pvestad (Status Daemon. Is this mandatory for other services as well? or due to pvestatd it can display log messages)

 

[dcsapak]

disabling pvestatd would probably reduce the amounts of connectios to it, but this daemon is also responsible for gathering rrd/other stats. stopping it would mean you limit the infos you get across the cluster

also other daemon may connect to a storage if its necessary (e.g. when listing the content, etc.)

the only 'safe' way to omit connections to a storage is to disable it

 

[ieronymous]

disabling pvestatd would probably reduce the amounts of connectios to it, but this daemon is also responsible for gathering rrd/other stats. stopping it would mean you limit the infos you get across the cluster

also other daemon may connect to a storage if its necessary (e.g. when listing the content, etc.)

the only 'safe' way to omit connections to a storage is to disable it

You said rrd and remembered anoter flood message probably from time-difference or something, I think it was
rrdcached update error and you had to:
Navigate to cd /var/lib/
systemctl stop rrdcached
mv rrdcached rrdcached.bck
systemctl start rrdcached
systemctl restart pve-cluster

And another one came in my mind right now its (and happens probably they way it works but is going to send ssd devices to grave sooner) is
pve systemd[1]: Starting Proxmox VE replication runner...
pve systemd[1]: Started Proxmox VE replication runner.
pve systemd[1]: Starting Proxmox VE replication runner...
pve systemd[1]: Started Proxmox VE replication runner.
each minute 4 logs anf again and again
You have to
systemctl stop pvesr.timer
systemctl disable pvesr.timer
and the outcome Removed /etc/systemd/system/timers.target.wants/pvesr.timer. will appear

In other words not very friendly for home environment where the user dont have setups of HA and replication and backup services. These have to be turned off and on and you dont know whta there are doing in order to correlate them with a future problem and turn them on again.....