harbor-core connect postgresql refused #10206
Comments
|
You may need to check the dns server of 127.0.0.11:53, it failed to lookup the hostname of |
|
@heww i guess the dns server 127.0.0.11:53 is docker virtual server, how to check? |
|
Are you using http_proxy and https_proxy? if yes, please check the postgres is in the no_proxy list, a complete no_proxy list should be: |
|
@stonezdj |
|
Maybe there are issues for the embedded dns of docker, there is an issue moby/moby#40294 opened for this problem and its version is 18.06 too. |
|
I have also encountered this problem. My MySQL data directory is set in /data/database. After modifying the MySQL data directory and deleting /data/database.Finally, reinstall harbor |
|
the postgresql.conf file has and the pg_hba.conf file has: and |
|
Same here on a setup from scratch using a CentOs 8 fresh install. |
|
After a few hours trying everything under CentOs 8 (including os setup again from scratch), i reinstalled using ubuntu server 19: no problem, working as expected... |
|
Got the same issue recently on CentOS 8, I fixed it like this, you can certainly find more details here https://wiki.libvirt.org/page/Net.bridge.bridge-nf-call_and_sysctl.conf and here https://stackoverflow.com/questions/40214617/docker-no-route-to-host : |
xaleeks
added
doc-impact
|
@josuemotte on CentOS 8 i had the same issue, after running your command Harbor wasn't working. sudo firewall-cmd --zone=public --add-masquerade --permanent
sudo firewall-cmd --permanent --zone=public --change-interface=docker0
sudo firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT 4 -i docker0 -j ACCEPT
sudo firewall-cmd --permanent --zone=public --add-port=5432/tcp
sudo firewall-cmd --reload
sudo systemctl restart dockeras far as I understood this has nothing to do with Harbor, but is docker/firewall configuration... |
On Centos8.1 is working |
|
To me seems that the issue is only related to firewalld configuration. i'm installing harbor 2.0 into this Host [antonio@192 ~]$ cat /etc/centos-release
CentOS Linux release 8.1.1911 (Core)
[antonio@192 ~]$ sudo firewall-cmd --version
0.7.0
[antonio@192 ~]$ sudo docker --version
Docker version 19.03.11, build 42e35e61f3
[antonio@192 ~]$ sudo docker-compose --version
docker-compose version 1.26.0, build d4451659Harbor is installed with ./install.sh --with-clair --with-chartmuseum. after installation we will have 4 network interface. with ifconfig i'm picking up the network interface ids and then: sudo firewall-cmd --permanent --zone=trusted --change-interface=docker0
sudo firewall-cmd --permanent --zone=trusted --change-interface=br-d92d56047624
sudo firewall-cmd --permanent --zone=trusted --change-interface=br-f00c9ed64e80
sudo firewall-cmd --permanent --zone=trusted --change-interface=br-f208abd8081b
sudo firewall-cmd --complete-reload
sudo systemctl restart dockermake sure to fire a the problem is that if we do a after that all problem with nslookup and ping are no more present inside containers. |
|
It seems to be related to the usage of nftables in CentOS 8 : |
It seems more like the firewall setting of CentOS 8. I try by this steps:
|
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I have a gke cluster with Ubuntu as base image for nodes. And I installed harbor with helm chart ... I am facing the same issue .. |
save my day bro |
|
I have a k8s cluster with centos 7.9 and ovn4nfv cni plugin. And I install harbor with helm chart. I am facting the same issue |
|
In my case, there weren't any privileges for registry database like in @damozhiying case. |
If you are reporting a problem, please make sure the following information are provided:
Expected behavior and actual behavior:
A clear and concise description of what you expected to happen and what's the actual behavior. If applicable, add screenshots to help explain your problem.
Steps to reproduce the problem:
Versions:
v1.9.2
Additional context:
harbor.ymland files in the same directory, including subdirectory./var/log/harbor/.The text was updated successfully, but these errors were encountered: