Replies: 1 comment
-
This is most likely a RAM issue. From https://docs.securityonion.net/en/2.4/hardware.html#standalone-deployments (emphasis added):
If you are able to increase RAM, then that would be the best option. If you are unable to increase RAM, you have a few options:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Version
2.4.111
Installation Method
Security Onion ISO image
Description
configuration
Installation Type
Standalone
Location
on-prem with Internet access
Hardware Specs
Meets minimum requirements
CPU
4
RAM
16
Storage for /
250GB
Storage for /nsm
1TB
Network Traffic Collection
span port
Network Traffic Speeds
Less than 1Gbps
Status
No, one or more services are failed (please provide detail below)
Salt Status
No, there are no failures
Logs
No, there are no additional clues
Detail
Hi,
I use a small security Onion System at Home.
16GB ECC Ram
250GB root single SSD
1TB single SSD for nsm
4 CPU cores intel xeon
6 Elastic agents on small linux systems
Everything works well, but at morning after around 14h the system are not reachable (web, ssh). The drive LED is permanent on (like heavy write or read actions on disc). After restart everythings work well the next 14h.
System are installed bare metall and up to date.
System is only 2 days old out of the box, no customation, no custom rules, no custom integrations.
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions