Can't reload syslog-ng
Issykul opened this issue · 7 comments
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
- Pull Image
- Start Container
- Do something or nothing to the config, doesn't matter
docker exec syslog-ng syslog-ng-ctl reloador dodocker exec -it syslog-ng bashand 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.
I know i could re-deploy the compose file. But that is not what i am looking for.
Let me do some tests, it's an achievable goal but I'm not sure the cleanest way to do it.
Try syslog-ng-ctl reload -c /config/syslog-ng.ctl
@thespad Could you add this to the Support Info Headline in the README? So if I forget about this in the future, i can find it here 😂
I'll add it to the readme when I get a chance.
