-
-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent PQsocket error #1381
Comments
Nuts, sorry this fell through the cracks on me replying. That's weird! It definitely looks like there is some lifecycle problem happening in the Notifier in regards to the Process record. If you still have them, would you be able to share the stacktraces of the |
No worries at all. Congratulations on launching 4.0! As far as I can tell it hasn't happened since. Here are the stack traces.
|
Hello! Thank you for your work on this gem — it’s a lifesaver for those who want to avoid the complexity of other background job services. However, I’m encountering a small issue that I’m unsure how to diagnose further.
I have a website with fairly low traffic, using a couple of cron jobs to monitor its health and a single queue, which is also not particularly busy.
We’ve been using GoodJob for a couple of months without any issues, but twice in the past week, the jobs have stopped running for about 15 minutes. After this stoppage, the Notifier unsubscribes due to a PQsocket() error, and about 40 AdvisoryLock errors are thrown while the Notifier attempts to resubscribe. Less than a minute later, the Notifier successfully resubscribes, and the scheduled jobs/cron jobs start performing without any user intervention. This has happened once in the middle of the night when there was no activity and once during the day.
Here’s a screenshot of the logs and errors at the time:
Is it a simple thread/pool issue or could it be something else? I'm not sure where to go from here.
The text was updated successfully, but these errors were encountered: