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
Not displaying syslogs #223
Comments
Hi, docker-composer is same of examples. syslogng: bash-5.1# pwd ` |
From the sight of the service container all your incoming packets are coming from the ingress network, if you are running in swarm mode. All syslog messages appear from the same ip from the ingress range (like 10.0.0.2). LibreNMS only shows messages for created devices. All other are disacrded. moby/moby#25526 is the right disussion https://github.com/newsnowlabs/docker-ingress-routing-daemon works as workaround for me |
I am having the same issue, the log reaches the server, I can see on tcpdump 16:16:47.519668 IP 172.19.10.3.38514 > librenmsadmin-04.syslog: SYSLOG local7.critical, length: 273 Why its not showing in librenms, how can I check whether it's reaching the container? |
I do believe container has to run as privileged to get access to ports 1-1024, can you try on port above 1024? I had similar issue in graylog docker. |
looking the this it looks like the docker is NATing the incoming traffic (172.19.10.3 is a docker proxy IP), haven't done this in docker (using k3s) but what you need to do is make sure docker is using source based load balancing so that the container inside sees the actual IP of the device and can match it against its database. |
If you have IPv6 on your host but not in the container, docker will set up nat64 automatically, and that might cause this. I can not guarantee that this is the same problem, but I have a similar issue. I have verified that the syslog messages actually reach the container from the right IP.
netstat shows that syslog-ng is listening
But as you can see, the receive-q is growing for each log-message:
So the process is not able to read the messages, for some reason What I see is that there are two syslog-ng-processes in the container:
And the last one is using a lot of cpu cycles After installing strace I can see why...
And it was counting and counting and counting... Until
And then all of a sudden, it started parsing syslog-messages... But something is definitely not playing well here...since it first tries to close millions of un-existing file descriptors... |
I'm also having issue with displaying syslog data in LibreNMS. Problem is that it should work according to instruction from https://github.com/librenms/docker : enable_syslog: true" I tried it in config.php.yaml I tried in syslog.yaml Is it broken or am I putting this "enable_syslog: true" in wrong place? |
Hi, my
I cannot actually comment on the syslog thing as I use Graylog and LibreNMS Graylog integration which when enabled replaces syslog. |
@hugalafutro thank you. Confirmed. If file is named anythinghere.php and have full structure like in your example it's working flawlessly. |
I tried enable syslog according to https://github.com/librenms/docker#syslog-ng-container but without success. |
@kyob read the 2 posts above yours. The instructions for modifying config.php in docker install are different. |
Hi - I'm not seeing syslogs being displayed in the libreNMS UI. I am publishing on a non-standard port (515) and I confirmed the docker host is receiving the syslogs on the expected port.
Thanks in advance.
docker-compose
validate.php
sudo docker ps
packet capture on host
The text was updated successfully, but these errors were encountered: