Actions
Issue #8782
closed
Intermittent psycopg2.errors.AdminShutdown errors in galaxy_ng dev env and pulp-all-in-one
Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Dev Environment, GalaxyNG
Sprint:
Quarter:
Description
Ticket moved to GitHub: "pulp/pulpcore/1996":https://github.com/pulp/pulpcore/issues/1996
A few folks have ran into an issue where when starting up the services including galaxy_ng, that all of the pulp services will start throwing errors like:
worker_1 | pulp [None]: rq.worker:ERROR: Worker rq:worker:1@440b6c94ceca: found an unhandled exception, quitting...
worker_1 | Traceback (most recent call last):
worker_1 | File "/venv/lib64/python3.6/site-packages/django/db/backends/utils.py", line 84, in _execute
worker_1 | return self.cursor.execute(sql, params)
worker_1 | psycopg2.errors.AdminShutdown: terminating connection due to administrator command
worker_1 | server closed the connection unexpectedly
worker_1 | This probably means the server terminated abnormally
worker_1 | before or while processing the request.
I've seen it with ~master ish galaxy_ng with the galaxy_ng dev containers. In that scenario it seems to get triggered by starting up the ./compose up ui ui component.
bmbouter saw it at least once with the pulp-all-in-one container, but it is hard to reproduce.
But filing here for reference.
Files
Actions
.