pvesr Trying to acquire cfs lock 'file-replication_cfg'

[grobs]

Hi,

I see those messages all the time in /var/log/syslog:

Feb 19 04:57:00 proxmox5-02 pvesr[4360]: trying to acquire cfs lock 'file-replication_cfg' ...
Feb 19 05:07:00 proxmox5-02 pvesr[30058]: trying to acquire cfs lock 'file-replication_cfg' ...
Feb 19 05:13:00 proxmox5-02 pvesr[21507]: trying to acquire cfs lock 'file-replication_cfg' ...
Feb 19 05:18:00 proxmox5-02 pvesr[11547]: trying to acquire cfs lock 'file-replication_cfg' ...
Feb 19 05:19:00 proxmox5-02 pvesr[16279]: trying to acquire cfs lock 'file-replication_cfg' ...
Feb 19 05:23:00 proxmox5-02 pvesr[32082]: trying to acquire cfs lock 'file-replication_cfg' ...
Feb 19 05:29:00 proxmox5-02 pvesr[26538]: trying to acquire cfs lock 'file-replication_cfg' ...
Feb 19 05:36:00 proxmox5-02 pvesr[22802]: trying to acquire cfs lock 'file-replication_cfg' ...
Feb 19 05:39:00 proxmox5-02 pvesr[6262]: trying to acquire cfs lock 'file-replication_cfg' ...

Are they harmfull or could I just ignore them?

I saw several topics on this but I don't have neither replication nor pvesr or GUI hanging issues :
https://forum.proxmox.com/threads/replication-runner-on-all-hosts-and-vms-broken-since-update.48310/

# pvesr status
JobID      Enabled    Target                           LastSync             NextSync   Duration  FailCount State

Every node of my 11-nodes cluster has this kind of messages in its logs.

Spoiler: # pveversion -V

proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve)
pve-manager: 5.3-9 (running version: 5.3-9/ba817b29)
pve-kernel-4.15: 5.3-2
pve-kernel-4.15.18-11-pve: 4.15.18-33
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-8-pve: 4.15.18-28
pve-kernel-4.15.18-7-pve: 4.15.18-27
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-3-pve: 4.15.18-22
pve-kernel-4.15.18-2-pve: 4.15.18-21
pve-kernel-4.15.18-1-pve: 4.15.18-19
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-46
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-38
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-33
pve-container: 2.0-34
pve-docs: 5.3-2
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-17
pve-firmware: 2.0-6
pve-ha-manager: 2.0-6
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 3.10.1-1
qemu-server: 5.0-46
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1

Best regards

 

[Stoiko Ivanov]

The entries can be ignored in general - the pve-storage-replication systemd-timer just gets installed and activated by default, so that the configuration can happen easily.

If they bother you, and you don't plan to use storage-replication you can disable it.

Hope this helps!