Hello, This can happen if the material updates for the pipeline are stuck for some reason. Can you check if that is the case.
Do you see any Errors & Warnings for material update? Can you check the go-server logs, do you see any messages for the material update being skipped? Thanks, Mahesh On Wednesday, December 16, 2020 at 3:47:49 AM UTC+5:30 [email protected] wrote: > P.S. Go Version: 18.9.0 - and if we stop and restart the server it > seems to "fix" it. > > On 12/15/20, Fenn <[email protected]> wrote: > > Periodically our GoCD server goes belly up and many pipelines get > > these errors on the Web UI: > > > > Failed to trigger pipeline: NameOfMyPipeline { Pipeline already > triggered } > > > > But there is nothing in the server log to tell me it happened. > > > > I looked online but the only thing I see is this: > > > > https://github.com/gocd/gocd/issues/3459 > > > > Which offers no idea of the root cause, or additional troubleshooting > > steps. > > > > I also see this: > > > > https://github.com/gocd/gocd/issues/4647 > > > > but as I read it it does not really tell me what the root cause or how > > to troubleshoot or fix. > > Unless I am missing something. > > > > Any tips? Can this be logged if I change log-level? > > > > Brian Fennell > > > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/1b6b485f-d803-4819-ac2e-16c4461e601cn%40googlegroups.com.
