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
Describe the bug
When shutting down a controller an error is returned "Unable to release shared lock to the database: schema.(Manager).SharedUnlock: postgres.(Postgres).UnlockShared: unknown, unknown: error #0: driver: bad connection"
To Reproduce
Steps to reproduce the behavior, In boundary version 0.1.5:
Make sure that config.hcl has a controller section with a database url specified.
Run boundary database init -config config.hcl
Run boundary server -config config.hcl
Wait for controller to finish starting and hit ctrl-C
See error "Unable to release shared lock to the database: schema.(Manager).SharedUnlock: postgres.(Postgres).UnlockShared: unknown, unknown: error #0: driver: bad connection"
Expected behavior
No error returned
Additional context
The error indicates that the connection to the database was not in a state that allowed releasing the lock. Since this is a postgres advisory lock it should be getting released when the connection to the database is closed. If this happens while the controller is still running it could make it possible for database migrate to happen while the controller is still running.
The text was updated successfully, but these errors were encountered:
Describe the bug
When shutting down a controller an error is returned "Unable to release shared lock to the database: schema.(Manager).SharedUnlock: postgres.(Postgres).UnlockShared: unknown, unknown: error #0: driver: bad connection"
To Reproduce
Steps to reproduce the behavior, In boundary version 0.1.5:
controller
section with a database url specified.boundary database init -config config.hcl
boundary server -config config.hcl
Expected behavior
No error returned
Additional context
The error indicates that the connection to the database was not in a state that allowed releasing the lock. Since this is a postgres advisory lock it should be getting released when the connection to the database is closed. If this happens while the controller is still running it could make it possible for
database migrate
to happen while the controller is still running.The text was updated successfully, but these errors were encountered: