Great that you added those Performance counters.

There is a difference between normal output and error output. It seems that you write your debug to the standard error output?

How do you pass your debug information in the scripts?

---

The scripts we call are regular linux bash scripts that call a java class.

Within the java class we use jlogger which controlls the output.
It is possible that this output is comeing through the std err stream
We would expect that this should not affect usability of the visualcron.

We really would like to stay with visualcron and plan to buy more licences once the problem is solved.

Therfore we are setting up a server in DMZ which can be reached by you and which will have such a bash script with java in the backend available.

Hope this will finally bring us a solution.

What would be the mailadress to send you details regarding the ssh test account?

No, that should not affect usability.

We really appreciate the DMZ setup. Please send all details to support@visualcron.com

Also, please give us any details of limitations and setup of that Task (and suggested setup) - how often we should execute and so on.

Thanks.

---

As a final feedback to this issue I would like to thank for the very good support we got for this problem with SSH tasks.

The problem was solved some weeks ago and we did not examine any more major problems with SSH tasks since we installed server 5.5.3

We are heading for at least one more license now.