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

Syslog (harbor-log) seems not correctly configured, error is reported when starting #7566

Closed
steven-zou opened this issue Apr 26, 2019 · 8 comments
Assignees

Comments

@steven-zou
Copy link
Contributor

steven-zou commented Apr 26, 2019

Installed from master code. (make install CHARTFLAG=true CLAIRFLAG=true NOTARYFLAG=true)

error:

harbor-log | rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 60: error accessing config file or directory '/etc/rsyslog.d/rsyslog_docker.conf' [cwd: /]: Permission denied [v8.26.0 try http://www.rsyslog.com/e/2207 ]
harbor-log | rsyslogd: CONFIG ERROR: there are no active actions configured. Inputs will run, but no output whatsoever is created. [v8.26.0 try http://www.rsyslog.com/e/2103 ]

@reasonerjt
Copy link
Contributor

reasonerjt commented May 8, 2019

This is highly un-reproducible, and looks like an issue in environment, closing it until we reproduce.

@lxcjie
Copy link

lxcjie commented Nov 14, 2019

I have the same issue:
My os version: ubuntu16.04 (3.13.0-115-generic)
My docker verison: 18.03.0-ce

The following is the error:

rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 63: error accessing config file or directory '/etc/rsyslog.d/rsyslog_docker.conf' [cwd: /]: Permission denied [v8.1910.0 try https://www.rsyslog.com/e/2207 ]
rsyslogd: there are no active actions configured. Inputs would run, but no output whatsoever were created. [v8.1910.0 try https://www.rsyslog.com/e/2103 ]
rsyslogd: run failed with error -2103 (see rsyslog.h or try https://www.rsyslog.com/e/2103 to learn what that number means)
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 63: error accessing config file or directory '/etc/rsyslog.d/rsyslog_docker.conf' [cwd: /]: Permission denied [v8.1910.0 try https://www.rsyslog.com/e/2207 ]
rsyslogd: there are no active actions configured. Inputs would run, but no output whatsoever were created. [v8.1910.0 try https://www.rsyslog.com/e/2103 ]
rsyslogd: run failed with error -2103 (see rsyslog.h or try https://www.rsyslog.com/e/2103 to learn what that number means)
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 63: error accessing config file or directory '/etc/rsyslog.d/rsyslog_docker.conf' [cwd: /]: Permission denied [v8.1910.0 try https://www.rsyslog.com/e/2207 ]
rsyslogd: there are no active actions configured. Inputs would run, but no output whatsoever were created. [v8.1910.0 try https://www.rsyslog.com/e/2103 ]
rsyslogd: run failed with error -2103 (see rsyslog.h or try https://www.rsyslog.com/e/2103 to learn what that number means)
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 63: error accessing config file or directory '/etc/rsyslog.d/rsyslog_docker.conf' [cwd: /]: Permission denied [v8.1910.0 try https://www.rsyslog.com/e/2207 ]
rsyslogd: there are no active actions configured. Inputs would run, but no output whatsoever were created. [v8.1910.0 try https://www.rsyslog.com/e/2103 ]
rsyslogd: run failed with error -2103 (see rsyslog.h or try https://www.rsyslog.com/e/2103 to learn what that number means)
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 63: error accessing config file or directory '/etc/rsyslog.d/rsyslog_docker.conf' [cwd: /]: Permission denied [v8.1910.0 try https://www.rsyslog.com/e/2207 ]
rsyslogd: there are no active actions configured. Inputs would run, but no output whatsoever were created. [v8.1910.0 try https://www.rsyslog.com/e/2103 ]
rsyslogd: run failed with error -2103 (see rsyslog.h or try https://www.rsyslog.com/e/2103 to learn what that number means)
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 63: error accessing config file or directory '/etc/rsyslog.d/rsyslog_docker.conf' [cwd: /]: Permission denied [v8.1910.0 try https://www.rsyslog.com/e/2207 ]
rsyslogd: there are no active actions configured. Inputs would run, but no output whatsoever were created. [v8.1910.0 try https://www.rsyslog.com/e/2103 ]
rsyslogd: run failed with error -2103 (see rsyslog.h or try https://www.rsyslog.com/e/2103 to learn what that number means)
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 63: error accessing config file or directory '/etc/rsyslog.d/rsyslog_docker.conf' [cwd: /]: Permission denied [v8.1910.0 try https://www.rsyslog.com/e/2207 ]
rsyslogd: there are no active actions configured. Inputs would run, but no output whatsoever were created. [v8.1910.0 try https://www.rsyslog.com/e/2103 ]
rsyslogd: run failed with error -2103 (see rsyslog.h or try https://www.rsyslog.com/e/2103 to learn what that number means)

@dashcory
Copy link

any update?

@p15r
Copy link

p15r commented Feb 28, 2020

I had the same issue. The harbor-log container mounts /PATHTOHARBOR/harbor-v1.10.1/common/config/log/rsyslog_docker.conf from the host to /etc/rsyslog.d/rsyslog_docker.conf in the container. This failed due to incorrectly configured file system permissions on the Docker host. Once fixed, everything worked as expected.

@identifysun
Copy link

identifysun commented Dec 13, 2021

  1. change to harbor directory
cd path/to/harbor
  1. Fix file system permissions
$ find common/ -type f -exec chmod 0755 \{\} \;

@liuyanzhen34
Copy link

Thank you for helping me solve this problem

@phfnjcqscott
Copy link

@identifysun @p15r

Thank your tips. it help me to resolve my problem.

After I move the harbor installer files to other storage, it can not run agagin.
I got following error message:
ERROR: for chartmuseum Cannot start service chartmuseum: failed to initialize logging driver: dial tcp [::1]:1514: connect: connection refused
Starting registry ... error
ERROR: for harbor-portal Cannot start service portal: failed to initialize logging driver: dial tcp [::1]:1514: connect: connection refused

Starting registryctl ... error

ERROR: for registry Cannot start service registry: failed to initialize logging driver: dial tcp [::1]:1514: connect: connection refused

Starting redis ... error

ERROR: for redis Cannot start service redis: failed to initialize logging driver: dial tcp [::1]:1514: connect: connection refused

thank you so much.

@bingheGT
Copy link

@identifysun 感谢,靠您这个方法解决了问题,6的

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants