-
-
Notifications
You must be signed in to change notification settings - Fork 566
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
Some confusing issues with pid_one_command: /bin/systemd and postgresql service #680
Comments
@Pursu1tOfHapp1ness does |
Hey, Sorry for such a long waiting.. journalctl -u postgresql
-- Logs begin at Fri 2021-05-21 11:20:14 UTC, end at Fri 2021-05-21 11:35:01 UTC. --
-- No entries -- Logs of systemctl status postgresql
● postgresql.service - PostgreSQL RDBMS
Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
Active: inactive (dead) And maybe logs from 2021-05-21 11:23:09.316 UTC [5852] LOG: starting PostgreSQL 12.7 (Debian 12.7-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2021-05-21 11:23:09.316 UTC [5852] LOG: listening on IPv4 address "127.0.0.1", port 5432
2021-05-21 11:23:09.317 UTC [5852] LOG: could not bind IPv6 address "::1": Cannot assign requested address
2021-05-21 11:23:09.317 UTC [5852] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2021-05-21 11:23:09.318 UTC [5852] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2021-05-21 11:23:09.336 UTC [5853] LOG: database system was shut down at 2021-05-21 11:23:07 UTC
2021-05-21 11:23:09.341 UTC [5852] LOG: database system is ready to accept connections |
It looks like there's another PG instance running on the server. Does that seem correct? |
🗣️ Foreword
Hello!
In my case, I'd like to install sonarqube+postgresql as services with Chef instruments (chef-client and cookbooks). I started to develop such decision and faced obstacles with restarting/starting postgresql service. So, try to answer this question to you.
👻 Brief Description
So, after reading and understanding what kind of resources I need, start to create custom recipe, that it is:
Variables:
.kitchen.yml:
So, after kitchen is creating and start to converge, in logs I see:
🥞 Cookbook version
Latest cookbook version of postgresql:
postgresql (8.2.1)
apt (>= 0.0.0)
yum-epel (>= 0.0.0)
👩🍳 Chef-Infra Version
Version of chef-client in my environment:
chef-client version: 14.15.6
delivery version: master (4b21ec7e07fdfa82e86aa80e4f2372dde8e368bb)
berks version: 7.0.8
kitchen version: 1.25.0
inspec version: 3.9.3
🎩 Platform details
CentOS Linux release 7.9.2009 (Core)
Steps To Reproduce
Steps to reproduce the behavior:
🚓 Expected behavior
Expect to restart/reload postgresql service as normal service, without timeout issues.
➕ Additional context
Vice verse, if I use in .kitchen.yml next code:
.kitchen.yml:
Everything will be good. Thanks for answering!
The text was updated successfully, but these errors were encountered: