scirius icon indicating copy to clipboard operation
scirius copied to clipboard

Fails on sources updating

Open woundride opened this issue 2 years ago • 3 comments

I've updated Scirius container on 2023/07/24

From update, only first source is automatically updated.

Sometimes, when I try to update mannually, I receive error message : database is locked.

fail_update_sources_selks

woundride avatar Jul 27 '23 21:07 woundride

Thanks for posting the report.
I can not reproduce the problem locally.
What version of Scirius are you using ?

In my case i just clicked on fetch and update all sources from the Suricata tab (Ruleset acions - and select all actions: update, build,push)
Screenshot from 2023-07-28 11-00-02 Screenshot from 2023-07-28 10-59-01

pevma avatar Jul 28 '23 10:07 pevma

Thanks for your reply @pevma !

I've the last version of Scirius, alwalys tagged 3.8.0, but it's updated (new date in © section) :

scirius_version

Another issue observed when I try to update mannually all sources from Suricata > Ruleset actions :

update_all_sources

I receive Server error 500 :

error_500

woundride avatar Jul 28 '23 10:07 woundride

I think you should pull/update git to the latets selks code then build.
I tested and locally forks as expected. Example: Hi, I just tested the sequence - it works fine/as expected. What you should do first is git pull the SELKS master then build, so you don't end up with the development version. Basically just an example setup run command below in terms of memory (16GB), interface (dummy0) and ELK version (7.17.11) setting up if you want to switch to different ELK version:

 cd SELKS
 git pull
 docker compose stop
./easy-setup.sh -n --iA --es-memory 16G -i dummy0  --elk-version 7.17.11  ;
 sudo -E docker compose up -d


https://github.com/StamusNetworks/SELKS/wiki/Docker#upgrade-all-containers

Of course , as always , following a good practice - please test in QA/Dev setup before doing in prod :)

pevma avatar Jul 30 '23 08:07 pevma