Post-Job Script TIMEOUT Warning

[adrianofante]

What happened?

Hi, We install the latest DEV version. But when the script is run simultaneously with another Backup JOB we always get the TIMEOUT Warning. Are there any restrictions on the simultaneous execution of the Post-Job Script?

Steps To Reproduce

No response

VeeamNotify version

1.0-beta1

PowerShell version

5.1

Veeam Backup & Replication build number

No response

Relevant log output

No response

[Philenst]

Hi @adrianofante

This is really strange.. I've just tested it from my side with a few jobs and I didn't get any timeouts on any of those. Would it be possible to get your latest log for the specific job that is timing out? (By default, it's located in C:\VeeamScripts\VeeamNotify\log, unless disabled), make sure to remove your webhook information as it'll be printed out in the log.

[tigattack]

@adrianofante are you still experiencing this issue?

[Philenst]

Hi @adrianofante, I will close this issue due to inactivity. If you'd like to diagnose this further, feel free to re-open the issue in the future.

[adrianofante]

Hi @tigattack @Philenst

I still have this same problem. It usually occurs when more than 1 backup job runs and completes at the same time.

I tried to do as suggested in the Veeam forum and "call" the script via BAT, but when I call the script via BAT it doesn't run.

https://forums.veeam.com/veeam-backup-replication-f2/v8-post-job-script-timed-out-hp-data-protector-t24354.html

[adrianofante]

.

[tigattack]

Thanks @adrianofante. FYI you did not scrub your webhooks and user details from the logs as suggested by Phil. You may wish to delete or edit them.

Are you receiving your notifications? I don't see any issues in the logs.

Could you please clarify which of the following is the problem here?

• A breaking issue with VeeamNotify
• ONLY related to the timeout warning in VBR (i.e. cosmetic only)

[adrianofante]

I get notifications normally. It happens that due to the Timeout of the script all my Jobs are with the STATUS OF WARNING and this is not good. I couldn't find any errors in the log either.

But the fact is that if I run a backup job without any other concurrent jobs, the script runs normally in a few seconds.

When there are concurrent tasks, the script reaches the timeout and the Job is in Warning status because of the timeout.

I did another test increasing the PostScripts Timeout in the Windows Registry, when I did that the script took more than 1 hour to finish, but it ended without error.

INCREASING POST SCRIPT TIME

JOB EXECUTED WITHOUT OTHER COMPETING JOBS

JOB RUN WITH COMPETITIVE JOBS (TIMEOUT AND WARNING)