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

confused log in clair container #10222

Closed
heww opened this issue Dec 11, 2019 · 8 comments · Fixed by #12322
Closed

confused log in clair container #10222

heww opened this issue Dec 11, 2019 · 8 comments · Fixed by #12322
Assignees

Comments

@heww
Copy link
Contributor

heww commented Dec 11, 2019

There are some confused logs ls: /harbor_cust_cert: No such file or directory for clair when it started.

Maybe these logs also exist in others containers.

@irLinja
Copy link

irLinja commented Dec 18, 2019

Same here!
and clair is in restarting status

[root@Harbor harbor]# docker-compose ps
      Name                     Command                  State                 Ports          
---------------------------------------------------------------------------------------------
chartmuseum         ./docker-entrypoint.sh           Up (healthy)   9999/tcp                 
clair               ./docker-entrypoint.sh           Restarting                              
clair-adapter       /clair-adapter/clair-adapter     Restarting                              
harbor-core         /harbor/harbor_core              Up (healthy)                            
harbor-db           /docker-entrypoint.sh            Up (healthy)   5432/tcp                 
harbor-jobservice   /harbor/harbor_jobservice  ...   Up (healthy)                            
harbor-log          /bin/sh -c /usr/local/bin/ ...   Up (healthy)   127.0.0.1:1514->10514/tcp
harbor-portal       nginx -g daemon off;             Up (healthy)   8080/tcp                 
nginx               nginx -g daemon off;             Up (healthy)   0.0.0.0:80->8080/tcp     
redis               redis-server /etc/redis.conf     Up (healthy)   6379/tcp                 
registry            /home/harbor/entrypoint.sh       Up (healthy)   5000/tcp                 
registryctl         /home/harbor/start.sh            Up (healthy)                    

Clair logs here:

Dec 18 23:33:10 172.24.0.1 clair[9887]: ls: /harbor_cust_cert: No such file or directory
Dec 18 23:33:10 172.24.0.1 clair[9887]: {"Event":"pgsql: database connection string is not a valid URL","Level":"fatal","Location":"main.go:97","Time":"2019-12-18 20:03:10.987690"}
Dec 18 23:33:37 172.24.0.1 clair[9887]: ls: /harbor_cust_cert: No such file or directory
Dec 18 23:33:37 172.24.0.1 clair[9887]: {"Event":"pgsql: database connection string is not a valid URL","Level":"fatal","Location":"main.go:97","Time":"2019-12-18 20:03:37.067348"}

@joeyjy
Copy link

joeyjy commented Jan 16, 2020

I found this log in registryctl container when starting

registryctl[9501]: ls: /harbor_cust_cert: No such file or directory

@lazzio7
Copy link

lazzio7 commented Feb 12, 2020

hi,

same here:

[root@harbor-test harbor]# grep -w "ls: /harbor_cust_cert:" *
chartmuseum.log:Feb 12 14:59:36 172.18.0.1 chartmuseum[9428]: ls: /harbor_cust_cert: No such file or directory
clair.log:Feb 12 14:59:40 172.18.0.1 clair[9428]: ls: /harbor_cust_cert: No such file or directory
clair.log:Feb 12 14:59:43 172.18.0.1 clair[9428]: ls: /harbor_cust_cert: No such file or directory
clair.log:Feb 12 14:59:45 172.18.0.1 clair[9428]: ls: /harbor_cust_cert: No such file or directory
clair.log:Feb 12 14:59:46 172.18.0.1 clair[9428]: ls: /harbor_cust_cert: No such file or directory
clair.log:Feb 12 14:59:49 172.18.0.1 clair[9428]: ls: /harbor_cust_cert: No such file or directory
clair.log:Feb 12 15:39:08 172.18.0.1 clair[943]: ls: /harbor_cust_cert: No such file or directory
registryctl.log:Feb 12 14:59:34 172.18.0.1 registryctl[9428]: ls: /harbor_cust_cert: No such file or directory
registry.log:Feb 12 14:59:36 172.18.0.1 registry[9428]: ls: /harbor_cust_cert: No such file or directory

i get to this thread becasue i am still not able pull image to harbor ..still get:

$ docker -D push harbor-test.xxxx.xx/test/wiki:test The push refers to repository [harbor-test.xxxx.xx/test/wiki] Get https://harbor-test.xxxx.xx/v2/: Service Unavailable
is it because of potential issu with cert ?
i install harbor with :
./install.sh --with-notary --with-clair --with-chartmuseum

installation went OK, connect to harbor is via https,, but when i create CA and so on, i do not see under systemcl status docker mentioned line with docker/certs.....

also on web portal clair shows "unhealthy" status

thanks for hints...

@lazzio7
Copy link

lazzio7 commented Feb 12, 2020

update:
when i move /etd/docker/key.json to ~ .. then stop-start docker-compose... clair is healthy also container, but key.json was recreated probably, is there

[root@harbor-test docker]# ll /etc/docker/ total 4 drwxr-xr-x 3 root root 35 Feb 12 14:43 certs.d -rw------- 1 root root 244 Feb 12 16:29 key.json

anyway...

logs stil looks not good:

[root@harbor-test harbor]# docker-compose logs
Attaching to harbor-jobservice, nginx, notary-server, clair-adapter, harbor-core, notary-signer, clair, chartmuseum, harbor-portal, redis, harbor-db, registry, registryctl, harbor-log
chartmuseum | WARNING: no logs are available with the 'syslog' log driver
clair | WARNING: no logs are available with the 'syslog' log driver
clair-adapter | WARNING: no logs are available with the 'syslog' log driver
harbor-core | WARNING: no logs are available with the 'syslog' log driver
harbor-db | WARNING: no logs are available with the 'syslog' log driver
harbor-jobservice | WARNING: no logs are available with the 'syslog' log driver
harbor-portal | WARNING: no logs are available with the 'syslog' log driver
nginx | WARNING: no logs are available with the 'syslog' log driver
notary-server | WARNING: no logs are available with the 'syslog' log driver
notary-signer | WARNING: no logs are available with the 'syslog' log driver
redis | WARNING: no logs are available with the 'syslog' log driver
registry | WARNING: no logs are available with the 'syslog' log driver
registryctl | WARNING: no logs are available with the 'syslog' log driver

and push still do not work:

$ docker push harbor-test.xxxx.xx/test/wiki:test
The push refers to repository [harbor-test.xxxx.xx/test/wiki]
Get https://harbor-xxxx.xx/v2/: Service Unavailable

@lazzio7
Copy link

lazzio7 commented Feb 19, 2020

solved,, turn off proxy or no_proxy in systemd conf...

@hicaro
Copy link

hicaro commented Feb 26, 2020

@lazzio7 I am having the same problem. I added my domain to the NO_PROXY key. I followed the process described here: https://docs.docker.com/config/daemon/systemd/#httphttps-proxy.
The issue is still happening. Did you do anything else?

@lazzio7
Copy link

lazzio7 commented Feb 27, 2020

for http harbor:

[root@harbor ~]# cat /etc/docker/daemon.json
{
"insecure-registries" : ["harbor.xxx.xx", "0.0.0.0"]
}

[root@harbor ~]# cat /etc/systemd/system/docker.service.d/http-proxy.conf
[Service]
Environment="HTTP_PROXY=http://xxx.xxx.xxx.xxx:8888/"
Environment="no_proxy=harbor.xxx.xx"

for https harbor.. i had to turn off proxy ...
i have not findout, how to fix yet..

@stale
Copy link

stale bot commented May 29, 2020

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.

@stale stale bot added the Stale label May 29, 2020
@stale stale bot closed this as completed Jun 20, 2020
heww added a commit to heww/harbor that referenced this issue Jun 24, 2020
Closes goharbor#10222

Signed-off-by: He Weiwei <hweiwei@vmware.com>
heww added a commit to heww/harbor that referenced this issue Jun 24, 2020
Closes goharbor#10222

Signed-off-by: He Weiwei <hweiwei@vmware.com>
heww added a commit to heww/harbor that referenced this issue Jun 25, 2020
Closes goharbor#10222

Signed-off-by: He Weiwei <hweiwei@vmware.com>
cafeliker pushed a commit to cafeliker/harbor that referenced this issue Jul 14, 2020
Closes goharbor#10222

Signed-off-by: He Weiwei <hweiwei@vmware.com>
Signed-off-by: Ye Liu <ye.liu@hp.com>
bmfp pushed a commit to bmfp/harbor that referenced this issue Jul 22, 2020
Closes goharbor#10222

Signed-off-by: He Weiwei <hweiwei@vmware.com>
Signed-off-by: molinber <bertrand.molin@credit-agricole.net>
tedgxt pushed a commit to tedgxt/harbor that referenced this issue Aug 11, 2020
Closes goharbor#10222

Signed-off-by: He Weiwei <hweiwei@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants