Project

General

Profile

Bug #668

[dbscripts] use set -ex and cronic in all cron jobs

mtjm - about 9 years ago - . Updated over 5 years ago.

Status:
fixed
Priority:
critical
Assignee:
lukeshu
% Done:

100%

Description

They fail and we ignore their failures. We should use set -ex in all cron jobs so maintenance mails about their failures show what exactly fails, and use cronic to get these mails only if a script fail.

History

#1

Updated by lukeshu about 8 years ago

  • Category set to dbscripts cleanup
#2

Updated by lukeshu over 7 years ago

  • Category deleted (dbscripts cleanup)
  • Project changed from libretools to dbscripts
#3

Updated by lukeshu over 5 years ago

  • % Done changed from 0 to 90

For some time we were using cronic for everything, but we have since moved to systemd timers. Now everything is logged to the systemd journal.

Timers:
  • db-cleanup.timer : I'd say it does enough logging
  • db-import@.timer : has adequate logging
  • make_repo_torrents.timer : needs review
  • update-lastsync.timer : has adequate logging (is trivial)
#4

Updated by lukeshu over 5 years ago

make_repo_torrents wasn't even exiting non-zero if there was an error. Should be fixed in git now.

#5

Updated by lukeshu over 5 years ago

  • Assignee set to lukeshu
#6

Updated by lukeshu over 5 years ago

Fixed in v20180925

#7

Updated by lukeshu over 5 years ago

  • % Done changed from 90 to 100
  • Status changed from open to fixed

Also available in: Atom PDF