linuxserver / docker-syslog-ng Goto Github PK

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I download container and run it. Container create folders config and log and starts/

But it cant log nothing. In main log I get this:
"Error opening file for writing; filename='/var/log/messages', error='No such file or directory (2)'"

Restarting container not helped to me.

Expected Behavior

No response

Steps To Reproduce

Ubuntu 20.22

Environment

- OS: Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-100-generic x86_64)
- How docker service was installed: Standard docker through apt install. Docker version 26.0.0, build 2ae903e

CPU architecture

x86-64

Docker creation

docker run -d \
   --name syslog-ng \
   --restart=unless-stopped \
   -p 514:5514/udp \
   -p 601:6601/tcp \
   -p 6514:6514/tcp \
   -e TZ=Europe/Moscow \
   -v /srv/syslog-ng/config:/config \
   -v /srv/syslog-ng/log:/var/log \
   lscr.io/linuxserver/syslog-ng

Container logs

[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[ls.io-init] done.

Is this a new feature request?

• I have searched the existing issues

Wanted change

I have currently deployed the following container in a root-access disabled k8s cluster and encountered the following error log during deployment:

s6-overlay-suexec: warning: unable to gain root privileges (is the suid bit set?)
s6-mkdir: warning: unable to mkdir /run/s6: Permission denied
s6-mkdir: warning: unable to mkdir /run/service: Permission denied
s6-overlay-suexec: fatal: child failed with exit code 111

This is currently preventing me from deploying it and was wondering if a rootless mode would be something that can be introduced to allow its deployment.

Reason for change

Allow rootless mode for the container to be deployed and run in an rootless container orchestration platform

Proposed code change

No response

Expected Behavior

there should be the collected logs in ./log

Current Behavior

there is nothing

Steps to Reproduce

1. docker compose

version: "2.1"
services:
  syslog-ng:
    image: lscr.io/linuxserver/syslog-ng:latest
    container_name: syslog-ng
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - ./syslog-ng:/config
      - ./log:/var/log
    ports:
      - 5514:5514/udp
    restart: unless-stopped

2. generate syslog message to this server

logger -n 192.168.1.1 -P 5514 asdf

3. check the directory and find there is no file in ./log

Environment

OS: Arch Linux, Raspberry Pi
CPU architecture: x86_64/arm32/arm64
How docker service was installed:

Arch Linux: official repo
Raspberry Pi: get-docker.sh

Command used to create docker container (run/create/compose/screenshot)

docker compose attached above

Docker logs

[+] Running 2/2
 ⠿ Network syslog-ng_default  Created                                                                    0.2s
 ⠿ Container syslog-ng        Created                                                                    1.1s
Attaching to syslog-ng
syslog-ng  | [custom-init] No custom services found, skipping...
syslog-ng  | s6-rc: info: service s6rc-oneshot-runner: starting
syslog-ng  | s6-rc: info: service s6rc-oneshot-runner successfully started
syslog-ng  | s6-rc: info: service fix-attrs: starting
syslog-ng  | s6-rc: info: service 00-legacy: starting
syslog-ng  | s6-rc: info: service 00-legacy successfully started
syslog-ng  | s6-rc: info: service fix-attrs successfully started
syslog-ng  | s6-rc: info: service legacy-cont-init: starting
syslog-ng  | cont-init: info: running /etc/cont-init.d/01-envfile
syslog-ng  | cont-init: info: /etc/cont-init.d/01-envfile exited 0
syslog-ng  | cont-init: info: running /etc/cont-init.d/01-migrations
syslog-ng  | [migrations] started
syslog-ng  | [migrations] no migrations found
syslog-ng  | cont-init: info: /etc/cont-init.d/01-migrations exited 0
syslog-ng  | cont-init: info: running /etc/cont-init.d/10-adduser
syslog-ng  | 
syslog-ng  | -------------------------------------
syslog-ng  |           _         ()
syslog-ng  |          | |  ___   _    __
syslog-ng  |          | | / __| | |  /  \
syslog-ng  |          | | \__ \ | | | () |
syslog-ng  |          |_| |___/ |_|  \__/
syslog-ng  | 
syslog-ng  | 
syslog-ng  | Brought to you by linuxserver.io
syslog-ng  | -------------------------------------
syslog-ng  | 
syslog-ng  | To support LSIO projects visit:
syslog-ng  | https://www.linuxserver.io/donate/
syslog-ng  | -------------------------------------
syslog-ng  | GID/UID
syslog-ng  | -------------------------------------
syslog-ng  | 
syslog-ng  | User uid:    1000
syslog-ng  | User gid:    1000
syslog-ng  | -------------------------------------
syslog-ng  | 
syslog-ng  | cont-init: info: /etc/cont-init.d/10-adduser exited 0
syslog-ng  | cont-init: info: running /etc/cont-init.d/50-config
syslog-ng  | cont-init: info: /etc/cont-init.d/50-config exited 0
syslog-ng  | cont-init: info: running /etc/cont-init.d/99-custom-files
syslog-ng  | [custom-init] No custom files found, skipping...
syslog-ng  | cont-init: info: /etc/cont-init.d/99-custom-files exited 0
syslog-ng  | s6-rc: info: service legacy-cont-init successfully started
syslog-ng  | s6-rc: info: service init-mods: starting
syslog-ng  | s6-rc: info: service init-mods successfully started
syslog-ng  | s6-rc: info: service init-mods-package-install: starting
syslog-ng  | s6-rc: info: service init-mods-package-install successfully started
syslog-ng  | s6-rc: info: service init-mods-end: starting
syslog-ng  | s6-rc: info: service init-mods-end successfully started
syslog-ng  | s6-rc: info: service init-services: starting
syslog-ng  | s6-rc: info: service init-services successfully started
syslog-ng  | s6-rc: info: service legacy-services: starting
syslog-ng  | services-up: info: copying legacy longrun syslog-ng (no readiness notification)
syslog-ng  | s6-rc: info: service legacy-services successfully started
syslog-ng  | s6-rc: info: service 99-ci-service-check: starting
syslog-ng  | [ls.io-init] done.
syslog-ng  | s6-rc: info: service 99-ci-service-check successfully started
^CGracefully stopping... (press Ctrl+C again to force)
[+] Running 1/1
 ⠿ Container syslog-ng  Stopped                                                                          5.9s
canceled

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hi leaving credentials in ci/cd is not good practice.
I don't known if you do this deliberatly or how far this goes as security risk right now
.
Please look at:
GITHUB_TOKEN=credentials(
GITLAB_TOKEN=credentials(

in your Jenkinsfile.....

Expected Behavior

Credentials and tokens do not belong in SCM.

Steps To Reproduce

Look at:
https://github.com/linuxserver/docker-syslog-ng/blob/main/Jenkinsfile

Environment

btw
Thanks for your docker-image it works out of the box!

CPU architecture

x86-64

Docker creation

I used default example.

Container logs

...

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

On unRAID:
docker run
-d
--name='syslog-ng'
--net='bridge'
-e TZ="Europe/London"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="ExternalServer"
-e HOST_CONTAINERNAME="syslog-ng"
-e 'PUID'='99'
-e 'PGID'='100'
-e 'UMASK'='022'
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/syslog-ng-logo.png'
-p '514:5514/udp'
-p '601:6601/tcp'
-p '6514:6514/tcp'
-v '':'/var/log':'rw'
-v '/mnt/user/appdata/syslog-ng':'/config':'rw' 'lscr.io/linuxserver/syslog-ng'
Unable to find image 'lscr.io/linuxserver/syslog-ng:latest' locally
docker: Error response from daemon: Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.

The command failed.

Expected Behavior

I expected an install to complete

Steps To Reproduce

Unraid 6.11.5, very limited configuration, with FreePBX installed but not running.

Environment

Unraid 6.11.5
Syslog package in Community Applications Plugin

CPU architecture

x86-64

Docker creation

docker run
  -d
  --name='syslog-ng'
  --net='bridge'
  -e TZ="Europe/London"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="ExternalServer"
  -e HOST_CONTAINERNAME="syslog-ng"
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/syslog-ng-logo.png'
  -p '514:5514/udp'
  -p '601:6601/tcp'
  -p '6514:6514/tcp'
  -v '':'/var/log':'rw'
  -v '/mnt/user/appdata/syslog-ng':'/config':'rw' 'lscr.io/linuxserver/syslog-ng'
Unable to find image 'lscr.io/linuxserver/syslog-ng:latest' locally
docker: Error response from daemon: Get "https://ghcr.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.

The command failed.

Container logs

Sorry, that is all I can find.

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

After create a docker-compose file and run it, I get log:

2023-07-24 14:20:03.983945015  [2023-07-24T14:20:03.983913] Error opening file for writing; filename='/var/log/messages', error='No such file or directory (2)'
2023-07-24 14:20:03.984001063  [2023-07-24T14:20:03.983989] Error opening file for writing; filename='/var/log/messages-kv.log', error='No such file or directory (2)'
2023-07-24 14:21:04.040980883  [2023-07-24T14:21:04.040943] Error opening file for writing; filename='/var/log/messages', error='No such file or directory (2)'
2023-07-24 14:21:04.041039840  [2023-07-24T14:21:04.041022] Error opening file for writing; filename='/var/log/messages-kv.log', error='No such file or directory (2)'
2023-07-24 14:22:04.082063882  [2023-07-24T14:22:04.082028] Error opening file for writing; filename='/var/log/messages', error='No such file or directory (2)'
2023-07-24 14:22:04.082123633  [2023-07-24T14:22:04.082107] Error opening file for writing; filename='/var/log/messages-kv.log', error='No such file or directory (2)'

Expected Behavior

Work properly.
I need to go inside a container and add rights 777 to files /var/log/messages and /var/log/messages-kv.log. After this it's work properly.

Steps To Reproduce

1. Create docker-compose file.
2. Run docker-compose file in detached mode.

Environment

- OS:Ubuntu 20.04.6 LTS (Focal Fossa)
- How docker service was installed: in terminal by official guied. (Docker version 24.0.4, build 3713ee1) (docker-compose version 1.25.0, build unknown) 

CPU architecture

x86-64

Docker creation

version: '2.1'
services:
  syslog-ng:
    image: lscr.io/linuxserver/syslog-ng:latest
    container_name: syslog-ng
    environment:
      - PUID="1000"
      - PGID="1000"
      - TZ=Etc/UTC
    volumes:
      - ~/syslog-ng/config:/config
      - ~/syslog-ng/logs:/var/log
    ports:
      - 514:5514/udp
    restart: unless-stopped

Container logs

[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[ls.io-init] done.
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[ls.io-init] done.

Expected Behavior

With syslog-ng-ctl reload i should be able to reload the config file.

Current Behavior

Instead of reloading the config the container prints out this:
Error connecting control socket, socket='/run/syslog-ng.ctl', error='No such file or directory'

Steps to Reproduce

1. Pull Image
2. Start Container
3. Do something or nothing to the config, doesn't matter
4. docker exec syslog-ng syslog-ng-ctl reload or do docker exec -it syslog-ng bash and run the command inside.

Environment

OS: Ubuntu 20.04.4 LTS
CPU architecture: x86_64
How docker service was installed: From the docker hub. Version 3.36.1

Command used to create docker container (run/create/compose/screenshot)

version: "3"
services:
  syslog-ng:
    image: linuxserver/syslog-ng:3.36.1
    container_name: syslog-ng
    environment:
      - PUID=0
      - PGID=0
      - TZ=[REDACTED]
    volumes:
      - /srv/syslog/config:/config
      - /srv/syslog/logs:/var/log
    ports:
      - 514:5514/udp
      - 601:6601/tcp
      - 6514:6514/tcp
    restart: unless-stopped
    networks:
      - syslog
    deploy:
      mode: replicated
      replicas: 1
      placement:
        constraints:
        - node.hostname == [REDACTED]
    logging:
      driver: "json-file"
networks:
  syslog:
    external: true

Docker logs

Nothing gets printed in the logs, so not relatable.

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When using syslog-ng -s -f <filename> to check the syntax of files the following error is being generated

Error opening plugin module; module='cloud_auth', error='Error relocating /usr/lib/syslog-ng/libcloud_auth.so: _ZTVN10__cxxabiv117__class_type_infoE: symbol not found'

Expected Behavior

Syntax checking to occur without error

Steps To Reproduce

1. curl -LO https://github.com/splunk/splunk-connect-for-syslog/archive/refs/tags/v3.19.1.tar.gz
2. gunzip v3.19.1.tar.gz
3. tar -xf v3.19.1.tar
4. cd splunk-connect-for-syslog-3.19.1/
5. syslog-ng -s -f ./package/etc/conf.d/conflib/syslog/app-syslog-vmware_vsphere.conf

Environment

- OS: centos7
- How docker service was installed: yum

CPU architecture

x86-64

Docker creation

docker container run -itd --rm --name sc4s linuxserver/syslog-ng:latest

docker exec -it sc4s bash

Container logs

[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────

[custom-init] No custom files found, skipping...
crond[168]: crond (busybox 1.36.1) started, log level 5
[ls.io-init] done.

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The ports provided in the docker compose are not mentioned in the default config/syslog-ng.conf. I dont think without it being configured, it will work.

Expected Behavior

This port should be configured as source with the correct protocol, similar to how TCP and UDP are configured in there.

I've not got much of an idea of syslog-ng, so perhaps I'm wrong. I can't test this, because I can't get through messages even with basic unsecure TCP. Only UDP works for me.

Steps To Reproduce

look at the reference files. This of also CPU overarching.

Environment

--------

CPU architecture

x86-64

Docker creation

---------

Container logs

----------

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

syslog-ng refuse to start or reload config when configuring a SQL destination

Expected Behavior

syslog-ng accepts SQL destination

Steps To Reproduce

• configure any sql destination in syslog-ng
• reload config
• see in syslog-ng logs : "Unable to initialize database access (DBI); rc='-1', error='No such file or directory (2)'"
• strace shows syslog-ng try to access /usr/lib/dbd which does not exist
• reload fails
• install libbdi-drivers : apk add libdbi-drivers
• syslog-ng now accept configuration

Environment

- OS: latest (as of 30/12/2022) image on rocky linux 9 (podman)
- How docker service was installed: packaged

CPU architecture

x86-64

Docker creation

not pertinent

Container logs

not pertinent