Getting error message attemping to upgrade to 3.1.0t #15981
Replies: 2 comments 17 replies
|
Looks like there was an issue querying Elasticsearch for your current version. I see the resources are minimal, check the Elasticsearch log ( |
|
If you run |
|
Yes, on version 3.0.0; removed /tmp/sogh. Tried running soup and got this error: Soup failed with error 160: Incompatible Elasticsearch upgrade |
|
Sounds like |
|
After applying chmod +x to the new so-yaml.py file, when executed I get this new error: |
I had the same problem, and this helped. Thank you. |
|
One other thing I noticed this something seems to be generating fleet servers, I have four that are inactive now. 
|
|
sudo soup still fails even with the new so-yaml.py file which also returns an error message when executed. |
|
What is the error you are seeing? The same |
|
Nevermind... repeated the same commands and now soup is running.. I guess the fifth time's the charm. |
Uh oh!
There was an error while loading. Please reload this page.
Version
3.1.0
Installation Method
Security Onion ISO image
Description
upgrading
Installation Type
Distributed
Location
on-prem with Internet access
Hardware Specs
Meets minimum requirements
CPU
4
RAM
16 GB
Storage for /
162.4 GB
Storage for /nsm
325.7 GB
Network Traffic Collection
span port
Network Traffic Speeds
1Gbps to 10Gbps
Status
Yes, all services on all nodes are running OK
Salt Status
Yes, there are salt failures (please provide detail below)
Logs
No, there are no additional clues
Detail
local:
Data failed to compile:
Soup Log:
Preparing soup at Thu Jun 18 02:39:42 PM UTC 2026
Checking if we can access the salt master and that it is ready at: Jun 18 14:39:42
Successfully accessed and salt master ready at: Jun 18 14:39:47
Checking to see if this is a manager.
This is a manager, so we can proceed.
Enabling highstate.
local:
----------
msg:
Info: highstate state already enabled.
res:
True
Salt Master does not need unlocked.
The manager's pillars can be rendered. We can proceed with SOUP.
Checking to see if this is an airgap install.
Found that Security Onion 3.0.0 is currently installed.
Cloning Security Onion github repo into /tmp/sogh/securityonion.
Removing previous upgrade sources.
Cloning the Security Onion Repo.
Verifying we have the latest soup script.
This version of the soup script is up to date. Proceeding.
Verifying Elasticsearch version compatibility across the grid before upgrading.
Couldn't determine the target Elasticsearch version (post soup version) to ensure compatibility with current Elasticsearch version. Exiting
Enabling highstate.
local:
----------
msg:
Info: highstate state already enabled.
res:
True
Salt Master does not need unlocked.
Soup failed with error 160: Incompatible Elasticsearch upgrade
Guidelines
All reactions