Long running jobs time out after 30 seconds
Reported by Ed | 2011-02-15 18:52:21 UTC | 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 2011-03-21 08:06:12 UTC
- Milestone set to “Rundeck 1.3”
- Assigned user set to “Alex-SF”
- Milestone order changed from “12” to “0”
-
Alex-SF 2011-06-03 18:16:18 UTC
- Tag set to “documentation”
-
Alex-SF 2011-06-08 11:21:13 UTC
- Tag changed from “documentation” to “defaults, documentation”
-
Deleted User 2011-06-30 11:00:30 UTC
- 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 2011-07-08 08:57:48 UTC
- 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 2011-07-14 16:45:00 UTC
I've confirmed that the 0 timeout value allows long running jobs to run until completion (>2 minutes anyway)
-
Greg Schueler 2011-07-15 11:10:08 UTC
- 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 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
Ed
Greg Schueler