When a command fails on a node, there needs to be more explanation as to why it failed
Reported by Deleted User | October 8th, 2010 @ 10:40 AM
While the command may fail, the transport, ssh may fail for various reasons. It should be evident if it's due to connection timeout or something else.
The node that failed should contain information related to:
- base OS errors (memory, ports, files limitations)
- transport errors (connection timeout, connection dropped)
- return codes
- signals caught (SIGHUP, etc.)
Comments and changes to this ticket
-
Alex-SF November 2nd, 2010 @ 03:20 PM
- Milestone changed from “Rundeck 1.0” to “Rundeck 1.1”
- Milestone order changed from “2” to “0”
-
Alex-SF December 17th, 2010 @ 09:55 AM
- Tag changed from “failure, reporting, ssh” to “failure, history, ssh”
-
Alex-SF January 13th, 2011 @ 07:46 AM
- Milestone changed from “Rundeck 1.1” to “Rundeck 1.2”
- Milestone order changed from “1” to “0”
-
Alex-SF February 14th, 2011 @ 01:09 PM
- Milestone cleared.
- Milestone order changed from “2” to “0”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
Alex-SF
Greg Schueler