- Notifications
You must be signed in to change notification settings - Fork120
-
Our current firewall only supports syslog over UDP with port 514. I attempted to follow theSyslog Forwarding guidance in the documentation, exchanging TCP for UDP and specifying port 514/udp in the PublishPort line, but it doesn't seem to be working.
Am I missing something? I'm not super familiar with rsyslog, podman, or elastic. |
BetaWas this translation helpful?Give feedback.
All reactions
Did you restart Fleet after updating PublishPort to 1514? The container won’t bind to the new port until it’s restarted so that may be the issue. You can restart the service with the following commands:
sudo systemctl daemon-reexecsudo systemctl daemon-reloadsudo systemctl restart podman-lme-fleet-server.serviceIf that’s already been done and/or logs still aren’t showing up after restarting, run this to check if the agent inside the container is starting the UDP input or hitting errors:podman logs lme-fleet-server | grep -i input
Replies: 2 comments 6 replies
-
Based on what you shared, your setup looks correct for enabling syslog forwarding over UDP. There are a few things to confirm to make sure the updates you made take effect.
Let us know what you see and if you run into anymore issues. |
BetaWas this translation helpful?Give feedback.
All reactions
-
BetaWas this translation helpful?Give feedback.
All reactions
-
The tcpdump you ran was still checking port 514 and not 1514. Can you try |
BetaWas this translation helpful?Give feedback.
All reactions
-
BetaWas this translation helpful?Give feedback.
All reactions
-
Do you see the logs in the Discover UI? |
BetaWas this translation helpful?Give feedback.
All reactions
-
No, I still see nothing coming to port 1514. ![]() |
BetaWas this translation helpful?Give feedback.
All reactions
-
Did you restart Fleet after updating PublishPort to 1514? The container won’t bind to the new port until it’s restarted so that may be the issue. You can restart the service with the following commands: If that’s already been done and/or logs still aren’t showing up after restarting, run this to check if the agent inside the container is starting the UDP input or hitting errors: |
BetaWas this translation helpful?Give feedback.
All reactions
-
That worked. Thanks again for your help! |
BetaWas this translation helpful?Give feedback.
All reactions
🎉 1



