-
Notifications
You must be signed in to change notification settings - Fork 202
Open
Description
I get several errors which seem to be related to DNS problems:
Registering database: type-PostgreSQL host-postgresql port-5432 database-registry sslmode-"disable"
Nov 22 13:30:20 172.18.0.1 core[1870]: 2024-11-22T13:30:20Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://postgresql:5432, retry after 2 seconds :dial tcp 172.18.0.4:5432: connect: connection refused
Nov 22 13:30:22 172.18.0.1 core[1870]: 2024-11-22T13:30:22Z [INFO] [/common/dao/base.go:72]: Register database completed
Then i get an error when i try to push a container:
podman push podman-registry.sas2025.lan/ses20/routing_manager
At the host where i do the push i get:
Getting image source signatures
Error: trying to reuse blob sha256:24b5ce0f1e07d37a35460f50d058afcf738619e431013d2e1727609bdff2d7fc at destination: pinging container registry podman-registry.sas2025.lan: Get "https://podman-registry.sas2025.lan/v2/": dial tcp: lookup podman-registry.sas2025.lan on 172.21.80.1:53: server misbehaving
The strange thing in the line above is that the VM does not have a net with 172.21.80.53
In the core.log i find several errors:
failed to list registries: failed to connect to `host=postgresql user=postgres database=registry`: hostname resolving error (l
ookup postgresql on 127.0.0.11:53: no such host)
Nov 22 14:18:30 172.18.0.1 core[1870]: 2024-11-22T14:18:30Z [ERROR] [/lib/http/error.go:57]: {"errors":[{"code":"UNKNOWN","message":"unknown: Get \"https://podman-registry.sas2025.lan/api/version\": tls: failed to verify certificate: x
509: certificate signed by unknown authority"}]}
Nov 22 14:38:36 172.18.0.1 core[1870]: 2024-11-22T14:38:36Z [ERROR] [/lib/http/error.go:57]: {"errors":[{"code":"UNKNOWN","message":"unknown: Get \"https://podman-registry.sas2025.lan/api/version\": tls: failed to verify certificate: x
509: certificate signed by unknown authority"}]}
Nov 22 14:39:00 172.18.0.1 core[1870]: 2024-11-22T14:39:00Z [ERROR] [/lib/http/error.go:57]: {"errors":[{"code":"UNKNOWN","message":"unknown: Get \"https://192.168.11.140:443/api/version\": tls: failed to verify certificate: x509: cert
ificate signed by unknown authority"}]}
Nov 22 14:41:08 172.18.0.1 core[1870]: 2024-11-22T14:41:08Z [ERROR] [/lib/http/error.go:57]: {"errors":[{"code":"UNKNOWN","message":"unknown: Get \"http://podman-registery.sas2025.lan/api/version\": dial tcp: lookup podman-registery.sa
s2025.lan on 127.0.0.11:53: no such host"}]}
Nov 22 14:43:29 172.18.0.1 core[1870]: 2024-11-22T14:43:29Z [ERROR] [/lib/http/error.go:57]: {"errors":[{"code":"UNKNOWN","message":"unknown: Get \"http://podman-registery.sas2025.lan/api/version\": dial tcp: lookup podman-registery.sa
s2025.lan on 127.0.0.11:53: no such host"}]}
failed to ping redis://redis:6379?idle_timeout_seconds=30, retry after 10s : dial tcp: lookup redis on 127.0.0.11:53: no such host
And alst but not least, during boot (docker compose up) i get errors on the console:
harbor-jobservice | 2024-11-22T15:31:41Z [INFO] [/pkg/config/rest/rest.go:47]: get configuration from url: http://core:8080/api/v2.0/internalconfig
harbor-jobservice | 2024-11-22T15:31:41Z [ERROR] [/pkg/config/rest/rest.go:50]: Failed on load rest config err:Get "http://core:8080/api/v2.0/internalconfig": dial tcp 172.18.0.8:8080: connect: connection refused, url:http://core:8080/api/v2.0/internalconfig
harbor-jobservice | panic: failed to load configuration, error: failed to load rest config
harbor-jobservice |
harbor-jobservice | goroutine 1 [running]:
harbor-jobservice | main.main()
harbor-jobservice | /harbor/src/jobservice/main.go:46 +0x3ae
harbor-core | 2024-11-22T15:31:41Z [INFO] [/core/main.go:261]: Version: v2.11.2, Git commit: 201d421d
harbor-core | 2024-11-22T15:31:41Z [INFO] [/core/main.go:263]: Fix empty subiss for meta info data.
harbor-core | 2024-11-22T15:31:41Z [INFO] [/pkg/oidc/fix.go:37]: Not found any records with empty subiss, good to go.
harbor-core | 2024/11/22 15:31:41.826 [I] [server.go:280] http server Running on http://:8080
harbor-jobservice exited with code 0
h
I am runnng this on:
[root@podman-registry harbor]# cat /etc/os-release
NAME="CentOS Stream"
VERSION="9"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="9"
PLATFORM_ID="platform:el9"
PRETTY_NAME="CentOS Stream 9"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:centos:centos:9"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://issues.redhat.com/"
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"
Metadata
Metadata
Assignees
Labels
No labels