[SOLVED] when running systemctl status pve-daily-update shows inactive (DEAD) ?

[Spirog]

Hello,
wondering if this is normal activity for pve-daily-update

I am using PVE latest

proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-5.15: 7.2-3
pve-kernel-helper: 7.2-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.4: 6.4-11
pve-kernel-5.15.35-1-pve: 5.15.35-2
pve-kernel-5.15.30-2-pve: 5.15.30-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.157-1-pve: 5.4.157-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 16.2.7
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

I am on single Node only with a few VMs

the acme certificate is installed from GUI using cloudflare.



I am just wondering if this is "Active: inactive (dead) since Fri 2022-05-06 06:04:47 CDT; 11h ago"

because a cron only triggers it daily?

or is this an issue where I have to start this service and enable it via command line some how?

root@proxmox:~# systemctl status pve-daily-update
● pve-daily-update.service - Daily PVE download activities
     Loaded: loaded (/lib/systemd/system/pve-daily-update.service; static)
     Active: inactive (dead) since Fri 2022-05-06 06:04:47 CDT; 11h ago
TriggeredBy: ● pve-daily-update.timer
    Process: 28450 ExecStart=/usr/bin/pveupdate (code=exited, status=0/SUCCESS)
   Main PID: 28450 (code=exited, status=0/SUCCESS)
        CPU: 6.351s

May 06 06:04:40 proxmox systemd[1]: Starting Daily PVE download activities...
May 06 06:04:42 proxmox pveupdate[28450]: <root@pam> starting task UPID:proxmox:755470B2:000ccderC:698770CA:aptupdate::root@pam:
May 06 06:04:44 proxmox pveupdate[28850]: update new package list: /var/lib/pve-manager/pkgupdates
May 06 06:04:47 proxmox pveupdate[28450]: <root@pam> end task UPID:proxmox:755470B2:000ccderC:698770CA:aptupdate::root@pam: OK
May 06 06:04:47 proxmox pveupdate[28450]: Custom certificate does not expire soon, skipping ACME renewal.
May 06 06:04:47 proxmox systemd[1]: pve-daily-update.service: Succeeded.
May 06 06:04:47 proxmox systemd[1]: Finished Daily PVE download activities.
May 06 06:04:47 proxmox systemd[1]: pve-daily-update.service: Consumed 6.351s CPU time.

Thanks so much
Spiro

 

[bbgeek17]

This is normal. Notice this line: TriggeredBy: ● pve-daily-update.timer
Until its triggered - its inactive.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Spirog]

This is normal. Notice this line: TriggeredBy: ● pve-daily-update.timer
Until its triggered - its inactive.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

excellent that's what I was thinking but was not sure ...
again I totally appreciate you for your help!!!

Kind Regards,
Spiro