replication runner syslog

[kever]

Heya,

Installed proxmox 5.0 on top of debian stretch using the steps in the wiki. I noticed that the syslog repeats the following sentences:

Jul 10 14:32:01 pve2 systemd[1]: Started Proxmox VE replication runner.
Jul 10 14:33:00 pve2 systemd[1]: Starting Proxmox VE replication runner...
Jul 10 14:33:01 pve2 systemd[1]: Started Proxmox VE replication runner.
Jul 10 14:34:00 pve2 systemd[1]: Starting Proxmox VE replication runner...
Jul 10 14:34:01 pve2 systemd[1]: Started Proxmox VE replication runner.

It goes on like that. The node has zfsonlinux installed but does not use any kind of configured replication from proxmox

 

[Tomas Waldow]

Hi, i have the same situation, and i have found this on the documentation on the link: https://pve.proxmox.com/pve-docs/qm.1.html

See the image attached.

 

[dietmar]

You can safely ignore that log message.

 

[kever]

It floods the syslog, it's hard to ignore.. really like to keep the root disk writes as minimal as possible

chose the 'dir' type to be sure vms can be accessed and the pool wont be modified with proxmox specifics. So far I can check there is no way to change the type to zfspool without re-adding the storage

 

[kever]

changed /lib/systemd/system/pvesr.timer 'Minutely' to 'Monthly' and 'systemctl daemon-reload' shared for those who dont use the replictation

 

[vooze]

changed /lib/systemd/system/pvesr.timer 'Minutely' to 'Monthly' and 'systemctl daemon-reload' shared for those who dont use the replictation

You should probably use:

systemctl edit -full pvesr.timer

This will move a local file to /etc/ instead of /lib/ which will be overwritten on next update

Thanks for the advice though, this log was driving me crazy.

 

[EvertM]

For total n00bs like me who simply copy/paste vooze's advice:
You need 2 hyphens, so that should be:

systemctl edit --full pvesr.timer

 

[Barret]

Thanks EvertM, that did the trick indeed.

 

[n1nj4888]

I'm seeing the same info output to syslog every minute, even when there is no replication setup...

Mar 26 08:54:00 pve-host1 systemd[1]: Starting Proxmox VE replication runner...
Mar 26 08:54:01 pve-host1 systemd[1]: Started Proxmox VE replication runner.

I see from the above that I can either ignore the output or change the timer to run at a different schedule rather than every minute but is there no way of keeping the replication runner running every minute (in future if I wish to add additional nodes!) but simply surpressing the output to syslog through a config setting somewhere? It would seem to be that the output would only be useful in a debug situation?

 

[wolfgang]

but simply surpressing the output to syslog through a config setting somewhere?

No systemd has no capability to drop this output in the logs. If there will be a way we would set it as default.

 

[fcymk2]

Can I disable pvesr.timer if I not use replication?

```
systemctl stop pvesr.timer
systemctl disable pvesr.timer
```

 

[wolfgang]

Can I disable pvesr.timer if I not use replication?

Yes, you can, but I would use mask to disable it permanently.

 

[healermagnus]

No systemd has no capability to drop this output in the logs. If there will be a way we would set it as default.

An entry in /etc/rsyslog.d/ could filter or redirect this to wherever you want it to go.

Just create something like /etc/rsyslog.d/proxmox.conf

and add something like:

:msg, contains, "replication runner" ~

(don't forget the tilde)

 

[sidereus]

An entry in /etc/rsyslog.d/ could filter or redirect this to wherever you want it to go.

Just create something like /etc/rsyslog.d/proxmox.conf

and add something like:

:msg, contains, "replication runner" ~

(don't forget the tilde)

it help, no these messages any more at the /var/log/syslog, but messages still arrive, if read the syslog via the PVE web.

root@asr2:~# cat /etc/rsyslog.d/proxmox.conf
:msg, contains, "replication runner" stop
:msg, contains, "pvesr.service: Succeeded" stop

 

[swmcdonnell]

As healermagnus noted, if you add the tilde ~ at the end instead of "stop" it eliminates the entries from the log