Bug #10141
closed
Hitting the resume button on a repo sync job stalled at 53% gives this error
Description
Oops, we're sorry but something went wrong
Warning!
Cannot do Dynflow::Executors::Abstract::Execution[execution_plan_id: 323730a3-e2b7-486d-a538-16daa30f9910, finished: #<Dynflow::Future:0x0000000b2855e0>], no connection to a Listener
If you feel this is an error with Foreman itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trace and relevant log entries.
Dynflow::Error
Cannot do Dynflow::Executors::Abstract::Execution[execution_plan_id: 323730a3-e2b7-486d-a538-16daa30f9910, finished: #<Dynflow::Future:0x0000000b2855e0>], no connection to a Listener
app/models/concerns/foreman/thread_session.rb:33:in `clear_thread'
lib/middleware/catch_json_parse_errors.rb:9:in `call'
Back
Updated by Anonymous almost 10 years ago
- Project changed from Foreman to Katello
- Triaged set to No
Updated by Eric Helms almost 10 years ago
- Status changed from New to Need more information
- Translation missing: en.field_release set to 23
- Triaged changed from No to Yes
Could you see what stage it stalled at previously? Were there any errors in /var/log/messages with respect to the sync itself?
Updated by Nathan Peters over 9 years ago
It got to 50% or just finished downloading the files. This was actually with a katello 2.1 installation. I replaced it with the 2.2RC so I don't have access to those logs anymore.
I think the similar problem still exists in 2.2 because on a single Katello server install after syncing a repo, half the time it will download all the files and then go into suspend status before it can process the metadata or update the repo info with the downloaded packages. I can upload all those relevant log entries from the forum post I made about it this morning if needed.
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release changed from 23 to 51
Updated by Eric Helms over 9 years ago
Honestly, I am not sure how to reproduce this exactly as it could be a resource issue on the box or it could be related to how we were handling Capsule syncs. In the 2.2 official release we included some changes to how syncing occurs to the Capsules and is calculated. There is still the possibility that it could hit a timeout and not ever finish if the Capsule is unreachable for example. But you shouldn't see issues when jsut syncing a repository regularly anymore.
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release changed from 51 to 55
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release changed from 55 to 61
Updated by Eric Helms over 9 years ago
- Translation missing: en.field_release changed from 61 to 31
Updated by Eric Helms over 9 years ago
- Status changed from Need more information to Resolved
Since it has been many months and many changes have gone in to alleviate this issue I am setting to resolved. If you still see the issue, please re-open!