Replies: 18 comments 2 replies
-
tail logstash.log |
Beta Was this translation helpful? Give feedback.
-
Do you have any forward nodes? this issue usually happens when your manager can't send events to a search node. So it's odd that you are having this issue with two of them connected but I am not understanding how you have your Network traffic being monitored. are you attempting to monitor using the search nodes? Could you send a Screenshot of your grid (without IP address or hostnames)? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Hi 2nutz4u, |
Beta Was this translation helpful? Give feedback.
-
Sure. I am running distributed model. One manager and two search node. |
Beta Was this translation helpful? Give feedback.
-
Hi, please check the firewall rule and make sure that the traffic is coming to the manager with tcpdump port 5055 for logstash data and 8220 for the fleet manager server, if all of this is correct you should start troubleshooting further. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Please now check the log of Logstash at /opt/Logstash log, to check if there is any related error. |
Beta Was this translation helpful? Give feedback.
-
[root@svr-securityonion logstash]# tail logstash.log |
Beta Was this translation helpful? Give feedback.
-
Hi , please check the configuration make sure that the entry is created |
Beta Was this translation helpful? Give feedback.
-
Yep, looks correct to me. Also, the agents are sowing up as healthy. |
Beta Was this translation helpful? Give feedback.
-
when you go to Administration/Configuration/Firewall/hostgroups/searchnode: do you have the Ip address of your search nodes put in there? If not add them and look at your Redis queue size on your manager in the grid page, it should be going down slowly, and you should start to see things show up in the dashboard. |
Beta Was this translation helpful? Give feedback.
-
Yes, I do . I could be wrong but they were required when joining the search
nodes.
Best Regards,
Rakesh Patel
[image: Bhollo Corp] <https://www.facebook.com/bhollocorp> [image: Bhollo
Corp] <https://twitter.com/bhollocorp>[image:
https://plus.google.com/+Bhollocorp] <https://plus.google.com/+Bhollocorp>
…On Thu, Aug 29, 2024 at 5:37 PM bushcraftbuddy ***@***.***> wrote:
when you go to
Administration/Configuration/Firewall/hostgroups/searchnode: do you have
the Ip address of your search nodes put in there?
If not add them and look at your Redis queue size on your manager in the
grid page, it should be going down slowly, and you should start to see
things show up in the dashboard.
—
Reply to this email directly, view it on GitHub
<#13567 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHIJ23EO4SWJPUPGO2AAWG3ZT6PCHAVCNFSM6AAAAABNIWJDISVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANBZGIZTENI>
.
You are receiving this because you authored the thread.Message ID:
<Security-Onion-Solutions/securityonion/repo-discussions/13567/comments/10492325
@github.com>
|
Beta Was this translation helpful? Give feedback.
-
Providing pictures just in case. |
Beta Was this translation helpful? Give feedback.
-
Performed new install with the latest build. All working as advertised. Thanks everyone for their assistance. |
Beta Was this translation helpful? Give feedback.
-
Hi there, now I am having the same issue than you after fixing previous issue. |
Beta Was this translation helpful? Give feedback.
-
I don't follow. Can you elaborate? |
Beta Was this translation helpful? Give feedback.
-
I was never able to figure out why. I gave up on the 2.4.90 install and downloaded the latest 2.4.100. I performed a new install instead of the upgrade and everything is working. If I had to guess it is broken logstash pipe is broken. My working version does not show the same error. Sorry could not be more helpful. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Version
2.4.90
Installation Method
Security Onion ISO image
Description
configuration
Installation Type
Distributed
Location
on-prem with Internet access
Hardware Specs
Exceeds minimum requirements
CPU
4
RAM
32
Storage for /
293GB
Storage for /nsm
700G
Network Traffic Collection
tap
Network Traffic Speeds
Less than 1Gbps
Status
Yes, all services on all nodes are running OK
Salt Status
No, there are no failures
Logs
Yes, there are additional clues in /opt/so/log/ (please provide detail below)
Detail
I have experience in stalling SO as I already have one in production but want to perform a new setup as lots of changes have been made with version 2.4. I have a distributed install 1 master and 2 search nodes. So-status shows everything running and healthy.
Security Onion Status
Container │ Status │ Details
───────────────────────────────────┼─────────┼────────────────────────────
so-dockerregistry │ running │ Up About an hour
so-elastalert │ running │ Up 14 minutes
so-elastic-fleet │ running │ Up About an hour
so-elastic-fleet-package-registry │ running │ Up About an hour (healthy)
so-elasticsearch │ running │ Up 17 minutes
so-idstools │ running │ Up About an hour
so-influxdb │ running │ Up About an hour (healthy)
so-kibana │ running │ Up 16 minutes
so-kratos │ running │ Up About an hour
so-logstash │ running │ Up 15 minutes
so-nginx │ running │ Up About an hour (healthy)
so-redis │ running │ Up About an hour
so-sensoroni │ running │ Up About an hour
so-soc │ running │ Up About an hour
so-telegraf │ running │ Up About an hour
I have nothing in the dashboard. I have installed couple of Elastic agents (yes installed from the downloads section with no errors) but no logs are being collected. Nothing in discovery all empty.
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions