Cron job triggering backup at seemingly random times

[sebastianhaberey]

Hi, I have a question. My backup is configured for 22:00 each day. The configuration options are as follows:

      DB_DUMP_TARGET: /db
      DB_USER: root
      DB_PASS: example
      DB_DUMP_CRON: "0 22 * * *"
      DB_SERVER: common-db

but somehow the backups are created at rather random times:

-rw-r--r--@ 1 user  staff  1020816 Jan  9 23:00 db_backup_2021-01-09T22:00:25Z.tgz
-rw-r--r--@ 1 user  staff  1020985 Jan 11 08:35 db_backup_2021-01-11T07:35:26Z.tgz
-rw-r--r--@ 1 user  staff  1021187 Jan 12 07:09 db_backup_2021-01-12T06:09:05Z.tgz
-rw-r--r--@ 1 user  staff  1021164 Jan 13 11:36 db_backup_2021-01-13T10:36:45Z.tgz
-rw-r--r--@ 1 user  staff  1021159 Jan 14 14:00 db_backup_2021-01-14T13:00:12Z.tgz
-rw-r--r--@ 1 user  staff  1021374 Jan 14 23:58 db_backup_2021-01-14T22:58:50Z.tgz
-rw-r--r--@ 1 user  staff  1020558 Jan 15 23:00 db_backup_2021-01-15T22:00:10Z.tgz
-rw-r--r--@ 1 user  staff  1020556 Jan 17 16:25 db_backup_2021-01-17T15:25:06Z.tgz
-rw-r--r--@ 1 user  staff  1021349 Jan 18 07:27 db_backup_2021-01-18T06:27:05Z.tgz
-rw-r--r--@ 1 user  staff  1020702 Jan 19 16:41 db_backup_2021-01-19T15:41:06Z.tgz
-rw-r--r--@ 1 user  staff  1020703 Jan 19 23:00 db_backup_2021-01-19T22:00:19Z.tgz
-rw-r--r--@ 1 user  staff  1026454 Jan 23 14:51 db_backup_2021-01-23T13:51:29Z.tgz

The PC is sometimes switched off, so I was expecting the backups missing for some days. But the timing seems random. What am I overseeing?

[deitch]

My first reaction was how interesting it is that these dumps are taking almost always exactly one hour. Then I realized that the timestamps in your ls -l probably are local time, which is one hour ahead of UTC, which is what the filenames use. 😄

Addressing the real question, I am not sure. Can you run it in debug mode and see what it says? From the README:

DB_DUMP_DEBUG: If set to true, print copious shell script messages to the container log. Otherwise only basic messages are printed.

If you see anything obvious, say it here; if not, post some logs here and we can see. Be sure to filter for any sensitive information first.

[github-actions]

This issue has been automatically marked as stale due to inactivity.

[github-actions]

Closing this issue due to prolonged inactivity.