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
I'm using ansible to install/configure galaxy using our own SSL private key. In the ssl-internal.yml role the permission on the private key is set to 0400, however in our installation, this needs to be 0440 as the key must be accessible to PostgreSQL (the group is postgres). This causes PostgreSQL to fail to start, galaxy then spins trying to connect to the database, and eventually the filesystem fills up due to all the log messages. I think an easy fix would be to make this permission setting configurable.
The text was updated successfully, but these errors were encountered:
I'm using ansible to install/configure galaxy using our own SSL private key. In the ssl-internal.yml role the permission on the private key is set to 0400, however in our installation, this needs to be 0440 as the key must be accessible to PostgreSQL (the group is postgres). This causes PostgreSQL to fail to start, galaxy then spins trying to connect to the database, and eventually the filesystem fills up due to all the log messages. I think an easy fix would be to make this permission setting configurable.
The text was updated successfully, but these errors were encountered: