Hello Support,

since this might also be interesting for other parties, I raise the question here, as well as per mail.
I'm seeing the following behaviour after an upgrade from 7.7.3 to 8.1.1:
SSH Tasks are no longer returning the exit codes of the last command run on the server, but always 0, meaning success. In other words, I cannot make a SSH Task fail any more.
Are there any configuration options, that I have overlooked?

Kind regards,
Florian

Can you please test 8.1.2 beta from forum and also answer the questions in our email?

---

Hi Henrik,

the Problem persists in version 8.1.2 Beta.

Here the more detailed description:
Until now the SSH Task returned the error code from the last command run. Usually that was error 0, meaning command finished successfully. If the command failed it would throw an error code 1 to 100000 and the ssh task would display that error code in the output (error) column and correspondingly fail as well.
After the update the SSH Task does not fail any more. If the last command run fails, the output (error) column displays error code 0 and carries on with the following tasks.

Steps to reproduce:
Create a new job
Add a SSH Task to a linux server of your choice (Ubuntu / SLES 11 tested)
Add a command "cat /bla/blubb/foo/bar" which should fail and return error code 1

With Version 7.7.3 that job would fail. With Version 8.1.1 that Job will succeed.

Regards,
Florian

Please re-download beta 8.1.2 and install again. We have made some alterations.

---

Unfortunately the problem persists.

Hi Henrik,

the Problem persists in version 8.1.2 Beta.

Here the more detailed description:
Until now the SSH Task returned the error code from the last command run. Usually that was error 0, meaning command finished successfully. If the command failed it would throw an error code 1 to 100000 and the ssh task would display that error code in the output (error) column and correspondingly fail as well.
After the update the SSH Task does not fail any more. If the last command run fails, the output (error) column displays error code 0 and carries on with the following tasks.

Steps to reproduce:
Create a new job
Add a SSH Task to a linux server of your choice (Ubuntu / SLES 11 tested)
Add a command "cat /bla/blubb/foo/bar" which should fail and return error code 1

With Version 7.7.3 that job would fail. With Version 8.1.1 that Job will succeed.

Regards,
Florian

Is it possible that you could send us some test connection details as we cannot reproduce this in our environment? support@visualcron.com

---

What kinds of details do you need?

I have a standard SSH Connection to a Linux-Server (Ubuntu 14.04 or SLES 11), timeout 999999, codepage Windows-1252, otherwise standard settings.

What kinds of details do you need?

I have a standard SSH Connection to a Linux-Server (Ubuntu 14.04 or SLES 11), timeout 999999, codepage Windows-1252, otherwise standard settings.

Is it possible to connect to your specific instance from here?

---

Unfortunately no. It's a company internal Server.

I think we have pinpointed the issue now. Please test this version:

http://www.visualcron.co....aspx?g=posts&t=6721 

---

Can you confirm that latest beta works now for you?

---

Hi,

Version 8.1.2 fixed the problem for me. Thank you very much.

Regards,
Florian