Long running jobs time out after 30 seconds
Reported by Ed | February 15th, 2011 @ 06:52 PM | in Rundeck 1.3 (closed)
Any long running jobs over 30 seconds timeout with the following
Some steps in the workflow failed: [Step 1 failed: Timeout
period
exceeded, connection dropped.]
At the suggestion of Alex I changed the following in framework.properities
framework.ssh.timeout = 0
This change resolved the issue at least with the testing we have done so far.
Ed
Comments and changes to this ticket
-
Alex-SF March 21st, 2011 @ 08:06 AM
- Milestone set to Rundeck 1.3
- Assigned user set to Alex-SF
- Milestone order changed from 12 to 0
-
Alex-SF June 3rd, 2011 @ 06:16 PM
- Tag set to documentation
-
Alex-SF June 8th, 2011 @ 11:21 AM
- Tag changed from documentation to defaults, documentation
-
Deleted User June 30th, 2011 @ 11:00 AM
- State changed from new to needs_verification
(from [fb0bcf3dacb2124a19afb9382f36828624fde22e]) Set default ssh timeout to 0 (no timeout) [#202 state:needs_verification] https://github.com/dtolabs/rundeck/commit/fb0bcf3dacb2124a19afb9382...
-
Moses Lei July 8th, 2011 @ 08:57 AM
- Assigned user changed from Alex-SF to Deleted User
- State changed from needs_verification to verified
Confirmed default changed to 0 in latest build release-1.3-rc build 72
-
Greg Schueler July 14th, 2011 @ 04:45 PM
I've confirmed that the 0 timeout value allows long running jobs to run until completion (>2 minutes anyway)
-
Greg Schueler July 15th, 2011 @ 11:10 AM
- State changed from verified to resolved
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 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