Jobs with postscripts hang in "Running: Job Completed" (4046765)

Date: Dec 07
Product & Version: All
Module & Version: N/A
OS Version: All
Application version: N/A

Symptoms:
Some jobs that have a postscript configured occasionally hang in a state of "Running: Job completed" and don't execute their script.

Trace will show that the script execution is actually invoked, but the script plugin fails to connect back to the job manager. This indicates a problem in network connectivity - even though the first part of the backup has worked fine. It is the subsequent connection attempt that is rejected on the network, and this is usually caused by a firewall configuration that considers this second connection attempt within a short period of time as some sort of DoS.

If you have this problem, check whether there is any firewall (even with open ports) between the machines. You might want to reconfigure your intrusion detection systems or changing from stateful to stateless inspection.

=======================================
Version française disponible ID 00003335
Deutsche Version verfügbar ID