cron job not executed

G

gralf

New Member
Nov 2, 2024
23
1
3
Hi there, I have a proxmox setup with 3 VMs (Home Assistant, PBS and OMV), and a LXC (pihole)

PBS was rececently installed for backups, obviously.

I just configured cron to start the PBS VM (105) minutes before the backup jobs start, and to shutdown after the jobs are done, well, for that I took 1 hour and then make the machine shutdown, the point is , the first run ocurred on february first as it was schedulled, and almost everything worked fine, but the shutdown.

Now I am looking what happened, but don´t know where to look.

this is my crontab job

Code: 
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/crontab.QfL8Up/crontab installed on Sat Feb  1 14:35:48 2025)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
@reboot (sleep 60 && echo "powersave" | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor)
#05 10 * * * /usr/sbin/qm start 102
#25 10 * * * /usr/sbin/qm stop 102
55 02 1,7,15,22 * * /usr/sbin/qm start 105
55 03 1,7,15,22 * * /usr/sbin/qm shutdowm 105
Click to expand...

I have tried from the console the qm shutdown 105 and works fine

this is the node system log

Feb 01 02:55:01 prx3desiempre CRON[392295]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 01 02:55:01 prx3desiempre CRON[392296]: (root) CMD (/usr/sbin/qm start 105)
Feb 01 02:55:01 prx3desiempre pvestatd[991]: PBScopias: error fetching datastores - 500 Can't connect to 192.168.0.231:8007 (No route to host)
Feb 01 02:55:01 prx3desiempre qm[392297]: <root@pam> starting task UPID:prx3desiempre:0005FC74:00A3F429:697EB275:qmstart:105:root@pam:
Feb 01 02:55:01 prx3desiempre qm[392308]: start VM 105: UPID:prx3desiempre:0005FC74:00A3F429:697EB275:qmstart:105:root@pam:
Feb 01 02:55:01 prx3desiempre systemd[1]: Started 105.scope.
Feb 01 02:55:02 prx3desiempre kernel: tap105i0: entered promiscuous mode
Feb 01 02:55:02 prx3desiempre kernel: vmbr0: port 5(fwpr105p0) entered blocking state
Feb 01 02:55:02 prx3desiempre kernel: vmbr0: port 5(fwpr105p0) entered disabled state
Feb 01 02:55:02 prx3desiempre kernel: fwpr105p0: entered allmulticast mode
Feb 01 02:55:02 prx3desiempre kernel: fwpr105p0: entered promiscuous mode
Feb 01 02:55:02 prx3desiempre kernel: vmbr0: port 5(fwpr105p0) entered blocking state
Feb 01 02:55:02 prx3desiempre kernel: vmbr0: port 5(fwpr105p0) entered forwarding state
Feb 01 02:55:02 prx3desiempre kernel: fwbr105i0: port 1(fwln105i0) entered blocking state
Feb 01 02:55:02 prx3desiempre kernel: fwbr105i0: port 1(fwln105i0) entered disabled state
Feb 01 02:55:02 prx3desiempre kernel: fwln105i0: entered allmulticast mode
Feb 01 02:55:02 prx3desiempre kernel: fwln105i0: entered promiscuous mode
Feb 01 02:55:02 prx3desiempre kernel: fwbr105i0: port 1(fwln105i0) entered blocking state
Feb 01 02:55:02 prx3desiempre kernel: fwbr105i0: port 1(fwln105i0) entered forwarding state
Feb 01 02:55:02 prx3desiempre kernel: fwbr105i0: port 2(tap105i0) entered blocking state
Feb 01 02:55:02 prx3desiempre kernel: fwbr105i0: port 2(tap105i0) entered disabled state
Feb 01 02:55:02 prx3desiempre kernel: tap105i0: entered allmulticast mode
Feb 01 02:55:02 prx3desiempre kernel: fwbr105i0: port 2(tap105i0) entered blocking state
Feb 01 02:55:02 prx3desiempre kernel: fwbr105i0: port 2(tap105i0) entered forwarding state
Feb 01 02:55:02 prx3desiempre qm[392308]: VM 105 started with PID 392321.
Feb 01 02:55:02 prx3desiempre qm[392297]: <root@pam> end task UPID:prx3desiempre:0005FC74:00A3F429:697EB275:qmstart:105:root@pam: OK
Feb 01 02:55:02 prx3desiempre CRON[392295]: pam_unix(cron:session): session closed for user root
Feb 01 02:55:11 prx3desiempre pvestatd[991]: PBScopias: error fetching datastores - 500 Can't connect to 192.168.0.231:8007 (No route to host)
Feb 01 03:00:06 prx3desiempre pvescheduler[393665]: <root@pam> starting task UPID:prx3desiempre:000601C2:00A46B57:697EB3A6:vzdump:100:root@pam:
Feb 01 03:00:07 prx3desiempre pvescheduler[393666]: INFO: starting new backup job: vzdump 100 --fleecing 0 --quiet 1 --mode suspend --prune-backups 'keep-daily=1,keep-last=1,keep-monthly=1,keep-weekly=1' --notification-mode notification-system --compress gzip --node prx3desiempre --storage PBScopias --notes-template '{{guestname}}{{node}} Acaba de hacerse una copia de seguridad'
Feb 01 03:00:07 prx3desiempre pvescheduler[393666]: INFO: Starting Backup of VM 100 (qemu)
Feb 01 03:00:07 prx3desiempre qm[393672]: <root@pam> starting task UPID:prx3desiempre:000601C9:00A46BB9:697EB3A7:qmpause:100:root@pam:
Feb 01 03:00:07 prx3desiempre qm[393673]: suspend VM 100: UPID:prx3desiempre:000601C9:00A46BB9:697EB3A7:qmpause:100:root@pam:
Feb 01 03:00:07 prx3desiempre qm[393672]: <root@pam> end task UPID:prx3desiempre:000601C9:00A46BB9:697EB3A7:qmpause:100:root@pam: OK
Feb 01 03:00:10 prx3desiempre pvescheduler[393666]: VM 100 qmp command failed - VM 100 qmp command 'guest-ping' failed - got timeout
Feb 01 03:01:16 prx3desiempre qm[393985]: <root@pam> starting task UPID:prx3desiempre:00060304:00A4869A:697EB3EC:qmresume:100:root@pam:
Feb 01 03:01:16 prx3desiempre qm[393988]: resume VM 100: UPID:prx3desiempre:00060304:00A4869A:697EB3EC:qmresume:100:root@pam:
Feb 01 03:01:16 prx3desiempre qm[393985]: <root@pam> end task UPID:prx3desiempre:00060304:00A4869A:697EB3EC:qmresume:100:root@pam: OK
Feb 01 03:01:16 prx3desiempre pvescheduler[393666]: INFO: Finished Backup of VM 100 (00:01:09)
Feb 01 03:01:16 prx3desiempre pvescheduler[393666]: INFO: Backup job finished successfully
Feb 01 03:01:16 prx3desiempre perl[393666]: skipping disabled target 'mail-to-root'
Feb 01 03:10:01 prx3desiempre CRON[396180]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 01 03:10:01 prx3desiempre CRON[396181]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /sbin/e2scrub_all -A -r)
Feb 01 03:10:01 prx3desiempre CRON[396180]: pam_unix(cron:session): session closed for user root
Feb 01 03:10:15 prx3desiempre systemd[1]: Starting e2scrub_all.service - Online ext4 Metadata Check for All Filesystems...
Feb 01 03:10:15 prx3desiempre systemd[1]: e2scrub_all.service: Deactivated successfully.
Feb 01 03:10:15 prx3desiempre systemd[1]: Finished e2scrub_all.service - Online ext4 Metadata Check for All Filesystems.
Feb 01 03:17:01 prx3desiempre CRON[397879]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 01 03:17:01 prx3desiempre CRON[397880]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Feb 01 03:17:01 prx3desiempre CRON[397879]: pam_unix(cron:session): session closed for user root
Feb 01 03:20:06 prx3desiempre pvescheduler[398640]: <root@pam> starting task UPID:prx3desiempre:00061531:00A63FE9:697EB856:vzdump:101:root@pam:
Feb 01 03:20:06 prx3desiempre pvescheduler[398641]: INFO: starting new backup job: vzdump 101 --node prx3desiempre --storage PBScopias --mailto movildejose@gmail.com --notes-template '{{guestname}} acaba de hacerse una copia de seguridad' --mailnotification always --quiet 1 --fleecing 0 --mode suspend --prune-backups 'keep-daily=1,keep-last=1,keep-monthly=1,keep-weekly=1' --notification-mode legacy-sendmail --compress zstd
Feb 01 03:20:06 prx3desiempre pvescheduler[398641]: INFO: Starting Backup of VM 101 (lxc)
Feb 01 03:20:39 prx3desiempre pvescheduler[398641]: INFO: Finished Backup of VM 101 (00:00:33)
Feb 01 03:20:39 prx3desiempre pvescheduler[398641]: INFO: Backup job finished successfully
Feb 01 03:20:39 prx3desiempre perl[398641]: notified via target `<movildejose@gmail.com>`
Feb 01 03:20:39 prx3desiempre postfix/pickup[394758]: 62EA42C0857: uid=0 from=<root>
Feb 01 03:20:39 prx3desiempre postfix/cleanup[398830]: 62EA42C0857: message-id=<20260201022039.62EA42C0857@prx3desiempre.local>
Feb 01 03:20:39 prx3desiempre postfix/qmgr[969]: 62EA42C0857: from=<root@prx3desiempre.local>, size=9495, nrcpt=1 (queue active)
Feb 01 03:20:40 prx3desiempre postfix/smtp[398832]: 62EA42C0857: to=<movildejose@gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.133.26]:25, delay=1.4, delays=0.04/0.01/0.82/0.49, dsn=5.7.26, status=bounced (host gmail-smtp-in.l.google.com[74.125.133.26] said: 550-5.7.26 Your email has been blocked because the sender is unauthenticated. 550-5.7.26 Gmail requires all senders to authenticate with either SPF or DKIM. 550-5.7.26 550-5.7.26 Authentication results: 550-5.7.26 DKIM = did not pass 550-5.7.26 SPF [prx3desiempre.local] with ip: [62.81.132.20] = did not pass 550-5.7.26 550-5.7.26 For instructions on setting up authentication, go to 550 5.7.26 https://support.google.com/mail/answer/81126#authentication ffacd0b85a97d-435e11172f5si20629199f8f.128 - gsmtp (in reply to end of DATA command))
Feb 01 03:20:40 prx3desiempre postfix/cleanup[398830]: B524E2C08A5: message-id=<20260201022040.B524E2C08A5@prx3desiempre.local>
Feb 01 03:20:40 prx3desiempre postfix/bounce[398833]: 62EA42C0857: sender non-delivery notification: B524E2C08A5
Feb 01 03:20:40 prx3desiempre postfix/qmgr[969]: B524E2C08A5: from=<>, size=12608, nrcpt=1 (queue active)
Feb 01 03:20:40 prx3desiempre postfix/qmgr[969]: 62EA42C0857: removed
Feb 01 03:20:40 prx3desiempre proxmox-mail-forward[398835]: skipping disabled target 'mail-to-root'
Feb 01 03:20:40 prx3desiempre postfix/local[398834]: B524E2C08A5: to=<root@prx3desiempre.local>, relay=local, delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (delivered to command: /usr/bin/proxmox-mail-forward)
Feb 01 03:20:40 prx3desiempre postfix/qmgr[969]: B524E2C08A5: removed
Feb 01 03:30:01 prx3desiempre CRON[401103]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 01 03:30:01 prx3desiempre CRON[401104]: (root) CMD (test -e /run/systemd/system || SERVICE_MODE=1 /usr/lib/x86_64-linux-gnu/e2fsprogs/e2scrub_all_cron)
Feb 01 03:30:01 prx3desiempre CRON[401103]: pam_unix(cron:session): session closed for user root
Feb 01 03:55:01 prx3desiempre CRON[407236]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 01 03:55:01 prx3desiempre CRON[407237]: (root) CMD (/usr/sbin/qm shutdowm 105)
Feb 01 03:55:02 prx3desiempre CRON[407236]: pam_unix(cron:session): session closed for user root
Feb 01 03:55:02 prx3desiempre postfix/pickup[394758]: 997D02C0857: uid=0 from=<root>
Feb 01 03:55:02 prx3desiempre postfix/cleanup[407245]: 997D02C0857: message-id=<20260201025502.997D02C0857@prx3desiempre.local>
Feb 01 03:55:02 prx3desiempre postfix/qmgr[969]: 997D02C0857: from=<root@prx3desiempre.local>, size=2615, nrcpt=1 (queue active)
Feb 01 03:55:02 prx3desiempre proxmox-mail-forward[407248]: skipping disabled target 'mail-to-root'
Feb 01 03:55:02 prx3desiempre postfix/local[407247]: 997D02C0857: to=<root@prx3desiempre.local>, orig_to=<root>, relay=local, delay=0.02, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (delivered to command: /usr/bin/proxmox-mail-forward)
Feb 01 03:55:02 prx3desiempre postfix/qmgr[969]: 997D02C0857: removed
Feb 01 04:03:27 prx3desiempre pvestatd[991]: status update time (8.291 seconds)
Click to expand...

at 02:55
Feb 01 02:55:01 prx3desiempre CRON[392296]: (root) CMD (/usr/sbin/qm start 105)

at 02:55:02

Feb 01 02:55:02 prx3desiempre qm[392308]: VM 105 started with PID 392321.

VM up

and at 03:55:01

Feb 01 03:55:01 prx3desiempre CRON[407237]: (root) CMD (/usr/sbin/qm shutdowm 105)

but the VM is still up today February, 2nd

how can I dig up for what failed?
 
Hi, thx for your reply.

But if qemu were not installed, would have the VM started ?

And aa for the shutdown. I thought that stoping a VM would end in data los or corruption, isn't shutdown a better way to put down a VM?
 
Last edited:
You can log your cronjobs outputs similar to this
Bash: 
/usr/sbin/qm shutdown 105 2>&1 | /usr/bin/tee -a /root/cronlog.txt
If mail was set up you should've also gotten a notification like this
Bash: 
ERROR: unknown command 'qm shutdom'
Next time please don't use quotes for logs.
 
Last edited:
  • Like
Reactions: gralf
Impact said:
You can log your cronjobs outputs similar to this
Bash: 
/usr/sbin/qm shutdown 105 2>&1 | tee -a /root/cronlog.txt
If mail was set up you should've also gotten a notification like this
Bash: 
ERROR: unknown command 'qm shutdom'
Next time please don't use quotes for logs.
Click to expand...
Thank you, I´ll try that.

And for the notifications issue, let me tell that I just configured the telegram webhook working fine, so emil notifications error will dissapear on the next run.

thank you
 
You must log in or register to reply here.
Top Bottom
Back