Closed exente closed 5 years ago
Tested everything and works on CentOS 7.6.1810 (Core)
@exente Thanks again for the suggestions! If you want, I created a team on Keybase called osweep for collaboration. Creating issues on GitHub works as well since it makes the information readily available.
I'll spin up a CentOS VM today to test the prerequisites you mentioned and then place it in the wiki.
For now, the path should be needed since the code is referencing the absolute path to the lookup tables. I'll reopen this issue to test using the relative path instead. That "should" work.
I'll add the other considerations to the wiki under Troubleshooting.
Considerations 2 and 3 added.
Recommended prerequisites have been tested for CentOS 7+ and added to the wiki. I had to install gcc
to get the Pip packages to build.
The command on the Setup page in the wiki has been updated:
A recommended hardware section will be built later but this is the minimum hardware I needed for CentOS:
Release v1.5.3 (commit 8d183485dc90161a2b6c0ba579ed0257c5d2743a
) has been pushed to solve any non-default installation path issues. The setup commands found in the wiki should solve any absolute path issues.
Although is not an issue itself, I apologize but I don't know other place to share this info for the people after do an intallation in a different Linux Platform.
Prerequites: Also is required Python-devel package If you are newbie on CentOS, keep in mind you need also to install "epel-release" and python-pip packages too
Considerations: When you clone using git, is not required to move the folder from owseep-master to osweep as it is beign downloaded as osweep After each update, installation or any change review and change the owner of all files on the splunk intallation (solves initial issues) Most of the issues will come from the Splunk configuration rather from an app configuration or deployment, so it's useful to check the splunk log file on [splunk_installation_folder]/var/log/splunk/ (mainly splunkd.log)