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

Parsing error on /etc/rsyslog.conf file #50

Open
browser-bug opened this issue Apr 17, 2024 · 0 comments
Open

Parsing error on /etc/rsyslog.conf file #50

browser-bug opened this issue Apr 17, 2024 · 0 comments

Comments

@browser-bug
Copy link

I'm running a maxscale container as stated in the documentation with:

docker run -p 8989:8989 --name mxs mariadb/maxscale:latest

This is the output I'm getting. It looks like it doesn't really bother the startup at the end but there's a 60s delay that's kinda annoying.

❯ docker run -p 8989:8989 --name mxs mariadb/maxscale:latest
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 13: warnings occured in file '/etc/rsyslog.conf' around line 13 [v8.2102.0-15.el8 try https://www.rsyslog.com/e/2207 ]
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 13: invalid character '=' - is there an invalid escapesequence somewhere? [v8.2102.0-15.el8 try https://www.rsyslog.com/e/2207 ]
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 13: invalid character '"' - is there an invalid escapesequence somewhere? [v8.2102.0-15.el8 try https://www.rsyslog.com/e/2207 ]
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 13: warnings occured in file '/etc/rsyslog.conf' around line 13 [v8.2102.0-15.el8 try https://www.rsyslog.com/e/2207 ]
rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 13: invalid character '"' - is there an invalid escapesequence somewhere? [v8.2102.0-15.el8 try https://www.rsyslog.com/e/2207 ]
rsyslog startup failure, child did not respond within startup timeout (60 seconds)
Starting...
MaxScale PID = 17
 New Monit id: 12becc3f08740961eb18c9f15df19ad9
 Stored in '/root/.monit.id'
Starting Monit 5.33.0 daemon with http interface at [localhost]:2812
'9c23de27b04b' Monit 5.33.0 started

I'd like to know if this is reproducible and if this is expected.
Here's my current system informations:

❯ docker info
Client:
 Version:    26.0.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  0.13.1
    Path:     /usr/lib/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  2.26.1
    Path:     /usr/lib/docker/cli-plugins/docker-compose

Server:
 Containers: 26
  Running: 1
  Paused: 0
  Stopped: 25
 Images: 131
 Server Version: 26.0.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: true
  Native Overlay Diff: false
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 926c9586fe4a6236699318391cd44976a98e31f1.m
 runc version:
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.8.5-arch1-1
 Operating System: Arch Linux
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 22.31GiB
 Name: aidia-thinkpad
 ID: b89b35f4-c871-41e6-ba75-ac2e5107f16c
 Docker Root Dir: /home/docker
 Debug Mode: false
 Username: aidiateam
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
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

1 participant