You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last night when my provider was doing maintenance, the database connection to two of my delayed_job runners was lost, causing them to lock up and throw "Agent#4254: Error when fetching url: Mysql2::Error::TimeoutError: Lock wait timeout exceeded; try restarting transaction" exceptions. The thing is, I don't know exactly when that happened (and I suspect other folks might run into this as well). Would it be possible to print the system's time and date right before the exceptions get dumped?
The text was updated successfully, but these errors were encountered:
Hmm not sure, I am pretty sure the background processors just log to STDOUT, when using docker the timestamp would be added by docker itself. On "manual installations" there might be an option to add the timestamp in runit.
Last night when my provider was doing maintenance, the database connection to two of my delayed_job runners was lost, causing them to lock up and throw "Agent#4254: Error when fetching url: Mysql2::Error::TimeoutError: Lock wait timeout exceeded; try restarting transaction" exceptions. The thing is, I don't know exactly when that happened (and I suspect other folks might run into this as well). Would it be possible to print the system's time and date right before the exceptions get dumped?
The text was updated successfully, but these errors were encountered: