Skip to content
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

Service name is incorrect on recent Debian-based systems #23

Open
natefoo opened this issue Mar 6, 2020 · 3 comments
Open

Service name is incorrect on recent Debian-based systems #23

natefoo opened this issue Mar 6, 2020 · 3 comments
Labels

Comments

@natefoo
Copy link
Member

natefoo commented Mar 6, 2020

Recent Debian systems get a service named postgresql.service but restarting this actually does not restart PostgreSQL, for this you have to restart postgresql@<version>-<cluster> (e.g. postgresql@10-main).

@natefoo natefoo added the bug label Mar 6, 2020
@natefoo natefoo changed the title Use correct service name on Debian-based systems Service name is incorrect on recent Debian-based systems Mar 6, 2020
@hexylena
Copy link
Member

hexylena commented Dec 9, 2021

It has not been addressed in almost 2 years

yes we've been having a global pandemic, our bandwidth is lower than normal. galaxyproject is specifically a bioinformatics project heavily used during covid times, so, you can understand.

is it going to be maintained

we will be continuing to use it in production in a number of sites. It is up to you if you find this role useful or wish to find another one, or fork this one.

This is a major problem that you cannot use systemd to start the cluster installed by this ansible role

The cluster should get started, it is just that a restart handler wouldn't trigger a cluster restart properly.

@MichaelDBA
Copy link

Whoops, I accidentally deleted my issue comments. Thanks for your responses. Regarding the last comment, are you going to fix the restart handler so a restart can be done via ansible?

@hexylena
Copy link
Member

hexylena commented Dec 9, 2021

Yes, it's very likely we will fix this, especially now that ubuntu support will grow as centos is ended. I cannot provide a timeline I'm afraid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants