Certain Syslogs Not Arriving #11845
Replies: 1 comment 1 reply
-
Do you see any issues in |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Version: 2.3.260
On-Prem
Ubuntu 20.04
Seeing an issue where syslogs from specific devices only are not populating into elastic indices. Issue started around the same time another issue occurred which knocked log aggregation offline for a little while, resolved by various reboots and increasing logstash memory allocations. Several devices are still logging successfully, but others are not.
As far as I can tell no other changes were made. I see packets arriving on port 514 and I can read the contained syslog messages, but they do not appear to be getting as far as filebeat in order for ingestion to occur. I am wondering if the syslog module or other component of filebeat was damaged during prior issues.
Is there anywhere I can look for more information? Filebeat logs don't tell me much about incoming syslog or other errors. I do see errors about failing to get tcp and udp stats, but those seem to pre-date this issue.
Is there any way to pull a fresh container image in case corruption has occurred?
Beta Was this translation helpful? Give feedback.
All reactions