Bamboo is shutting down with takeBuildContext errors

[Alejandro Carretero Trejo]

Good morning, 

We are receiving in the past few days random errors from Bamboo Data Center instance that are shutting down the service but are strange, because we don't have changed anything in the server settings and in the last months we have never received any other error like that.

The first day the atlassian-bamboo.log said that the error was this:

2024-09-17 04:23:19,604 ERROR [20-BAM::Agente 1::Agent:Thread-45] [BuildQueueManagerImpl] Bamboo operation time: takeBuildContext took 481594 ms 2024-09-17 04:26:22,298 ERROR [21-BAM::Agente 2::Agent:Thread-46] [BuildQueueManagerImpl] Bamboo operation time: takeBuildContext took 636597 ms

and after that the log said:

Rejecting OAuth request for url "<url_bamboo>/rest/remote-event-consumer/latest/events/stash-branch-changed-remote-event" due to invalid timestamp ({oauth_problem=timestamp_refused, oauth_acceptable_timestamps=1726539860-1726540460}). This is most likely due to our system clock not being synchronized with the consumer's clock.

The second day, the log said that the error was:

Bamboo operation time: takeBuildContext took xxxx ms

and after some logs like this, it shows:

HikariPool-2: Thread starvation or clock leap detected...

Any possible workaround or reason?

Thanks in advance.