-
-
Notifications
You must be signed in to change notification settings - Fork 433
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
Stuck at Wait for port 8008 to become open on the host #738
Comments
Hello @snoby
Would you describe why? In cloud environments, there are usually difficulties to organize a VIP (e.q., keepalived, vip-manager), so I added support for a load balancer from a cloud provider.
which version of the distribution and kernel are you using?
I am confused by the presence of "waiting for leader to bootstrap" Could you attach the Patroni log? Are you using a dedicated etcd cluster? Wasn't there already a cluster with that name? |
This is all that is reported after restarting the patroni service ( at least all that is in journalctl)
the first attempt at an install failed on my kernel not having
on the next run the pgbouncer/config failed
Then after another delete and create cluster here we are. |
Please attach vars directory |
I see that you manually specified "vm.nr_hugepages" for about 8GB (although it is automated) while you left the automatic setting for shared_buffers. Please tell me what is the size of RAM on the server? Since the setting for 25% of the available memory is enabled here, there is a risk that you have specified an insufficient number of "vm.nr_hugepages". |
It's weird, there should be log files in there. Their absence makes diagnosis difficult. Try to manually start Postgres. |
I commented out of vars/system.yml the shared memory value ( which was 8GB). The system in total has 32 GB of ram.
It makes sense that would not be there, i just commented out that install line from the playbook. But i'm still at the last where the playbook is waiting on 8008
hacking around with some commands
strange that it thinks it's a replica. |
here, without logs, it is impossible to understand why the database does not start. Try to deploy the cluster according to this instruction (without manual changes): https://postgresql-cluster.org/deployment/aws |
Is the problem still relevant? Was it possible to deploy the cluster? |
A similar (solved) issue: #747 |
This is an amazing ansible project that you've put together here, very impressive.
I've set the project up to enable haproxy, cluster_vip and etcd, changed running on premise ( will run in aws but i don't want to use their load balancers or anything like that). I'm running it in a lab right now.
I worked through a couple of issues that i had with the install, specifically I had to disable the following items as my minimal kernel does not support them:
I've checked the systemctl status of patroni.service
This seems like an odd line since this SHOULD be the master. I've checked with
lsof
and the port is openThere is nothing in any of the files in the /var/log/postgresql logs directory. I've checked with
ps aux
and postgres is not running but patroni isAny suggestions on what else to look at? ( last part of the ansible run below)
The text was updated successfully, but these errors were encountered: