Manual triggers extremely delayed

[Evan Amstutz]

Hello, 

We had to restart our gocd 25.1.0 (20070-8f4b43b7bab6e0666bc9282ef4e25fa80d5b0529).  restart on a new ec2 instance due to a catostrophic error. We have recovered the majority of the previous server but we now see extreme delays when manually kicking off a pipeline. Triggered by changes works as expected as does rerunning failed slices but manual triggers take well over 5 minutes to register. Any ideas on what could be causing that?

Thank you,

Evan Amstutz

[Chad Wilson]

Not sure. Whats in the server logs in the time period? Are there git child processes stuck or doing a lot of work? (Assuming you're using git)

If nothing obvious, you could use jstack or "kill -3 pid" to dump stack traces to logs and see if there is an obvious place something is stuck during the manual trigger.

Otherwise would probably need more details about your deployment and how you did your recovery (perhaps what originally failed) to make any guesses.

-Chad

--
You received this message because you are subscribed to the Google Groups "GoCD Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/go-cd/47c215a3-a8b4-46db-b094-db329c019d4cn%40googlegroups.com.