SSH Task Exit Code Lost - VisualCron - Forum

Community forum

weyandt
2016-06-01T06:05:22Z
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
Support
2016-06-01T17:53:42Z
Can you please test 8.1.2 beta from forum and also answer the questions in our email?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
weyandt
2016-06-02T06:15:45Z
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
Support
2016-06-10T13:52:34Z
Please re-download beta 8.1.2 and install again. We have made some alterations.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
weyandt
2016-06-13T10:04:07Z
Unfortunately the problem persists.
Support
2016-06-13T14:13:07Z
Originally Posted by: weyandt 

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
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
weyandt
2016-06-13T14:29:20Z
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.
Support
2016-06-13T16:26:50Z
Originally Posted by: weyandt 

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?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
weyandt
2016-06-14T05:38:27Z
Unfortunately no. It's a company internal Server.
Support
2016-06-14T07:57:20Z
I think we have pinpointed the issue now. Please test this version:

http://www.visualcron.co....aspx?g=posts&t=6721 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2016-06-17T09:39:41Z
Can you confirm that latest beta works now for you?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
weyandt
2016-08-08T14:09:40Z
Hi,

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

Regards,
Florian
Scroll to Top