You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The backup runs every night, and I have an empty notification every night (the arguments are empty), even though there is no error when checking the logs.
Steps to reproduce
Set the environment variable: NOTIFICATION_CUSTOM_SCRIPT=/assets/custom-scripts/backup-error-notifier.sh
and create this backup-error-notifier.sh file:
As stated in the documentation: This image has capabilities on sending notifications via a handful of services when a backup job fails. This is a global option that cannot be individually set per backup job.
So I expect my script to be executed only if there's an error
Environment
Image version / tag: 4.1.4
Host OS: Linux
Possible fixes
I think it may be related to this log:
Found Custom Post Scripts in /assets/custom-scripts/ - Automatically moving them to '/assets/scripts/post/'
Executing post backup custom script : '/assets/scripts/post/backup-error-notifier.sh'
But i don't understand why it moves it to /assets/scripts/post
The text was updated successfully, but these errors were encountered:
Summary
The backup runs every night, and I have an empty notification every night (the arguments are empty), even though there is no error when checking the logs.
Steps to reproduce
Set the environment variable:
NOTIFICATION_CUSTOM_SCRIPT=/assets/custom-scripts/backup-error-notifier.sh
and create this
backup-error-notifier.sh
file:What is the expected correct behavior?
As stated in the documentation:
This image has capabilities on sending notifications via a handful of services when a backup job fails. This is a global option that cannot be individually set per backup job.
So I expect my script to be executed only if there's an error
Environment
Possible fixes
I think it may be related to this log:
But i don't understand why it moves it to
/assets/scripts/post
The text was updated successfully, but these errors were encountered: