Failed to start Proxmox VE replication runner while no replication set

Sasha

Sasha

Well-Known Member
Proxmox Subscriber
Oct 18, 2018
111
1
58
Kazahstan
Hi, guys.

Every reboot of host shows Aug 28 08:07:05 hq systemd[1]: Failed to start Proxmox VE replication runner. But I don't use any replications,
So is it possible to disable that tries of starting that service?
 
Hi,
what is the output of pveversion -v and systemctl status pvesr.service pvesr.timer? That service shouldn't even exist anymore since Proxmox VE 7.1, as it got replaced by pvescheduler.service.
 
  • Like
Reactions: Sasha
fiona said:
Hi,
what is the output of pveversion -v and systemctl status pvesr.service pvesr.timer? That service shouldn't even exist anymore since Proxmox VE 7.1, as it got replaced by pvescheduler.service.
Click to expand...
Code: 
pveversion -v
 
proxmox-ve: 7.4-1 (running kernel: 5.15.111-1-pve)
pve-manager: 7.4-16 (running version: 7.4-16/0f39f621)
pve-kernel-5.15: 7.4-5
pve-kernel-5.4: 6.4-20
pve-kernel-5.15.111-1-pve: 5.15.111-1
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.107-1-pve: 5.15.107-1
pve-kernel-5.4.203-1-pve: 5.4.203-1
pve-kernel-4.13.8-3-pve: 4.13.8-30
pve-kernel-4.13.8-2-pve: 4.13.8-28
pve-kernel-4.13.4-1-pve: 4.13.4-26
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve2
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.3-1
proxmox-backup-file-restore: 2.4.3-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-5
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1

Code: 
 systemctl status pvesr.service pvesr.timer
Unit pvesr.service could not be found.
● pvesr.timer - Proxmox VE replication runner
     Loaded: loaded (/etc/systemd/system/pvesr.timer; enabled; vendor preset: enabled)
     Active: inactive (dead)
    Trigger: n/a
   Triggers: ● pvesr.service

Aug 28 08:07:05 hq systemd[1]: pvesr.timer: Refusing to start, unit pvesr.service to trigger not loaded.
Aug 28 08:07:05 hq systemd[1]: Failed to start Proxmox VE replication runner.

Code: 
systemctl status pvescheduler.service
● pvescheduler.service - Proxmox VE scheduler
     Loaded: loaded (/lib/systemd/system/pvescheduler.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2023-08-28 08:08:23 +05; 9h ago
    Process: 3548 ExecStart=/usr/bin/pvescheduler start (code=exited, status=0/SUCCESS)
   Main PID: 3711 (pvescheduler)
      Tasks: 1 (limit: 19001)
     Memory: 99.5M
        CPU: 9.022s
     CGroup: /system.slice/pvescheduler.service
             └─3711 pvescheduler

Aug 28 08:08:22 hq systemd[1]: Starting Proxmox VE scheduler...
Aug 28 08:08:23 hq pvescheduler[3711]: starting server
Aug 28 08:08:23 hq systemd[1]: Started Proxmox VE scheduler.
 
Yes, IIRC you can also use systemctl disable pvesr.timer to do so.
 
  • Like
Reactions: Sasha
You must log in or register to reply here.
Top Bottom