Sensei stuck on initializing

[lignumaqua]

New install of Sensei on OPNSense 21.7.3_3 using external ElasticSearch database. Install looked to go OK, worked successfully through the wizard, but now the Sensei GUI page is stuck on 'Initializing...' It's been like that for over an hour. Tried rebooting OPNSense but Sensei still says initializing.

Is it normal to take so long to initialize? How do I find out what the problem is?

(It has also killed the responsiveness of the OPNSense GUI. Now taking many 10's of seconds to open a page)

[mb]

@lignumaqua, this is not expected. Shoot a Bug Report and the team will have a look.

[lignumaqua]

Unfortunately I don't know how to submit a Sensei bug report as the Sensei GUI in OPNSense is inaccessible. All you get on any of the Sensei tabs is the 'Initializing...' bar. No access to configuration page. It pretty much locks up the rest of OPNSense as well with pages taking nearly a minute to load.

I tried removing the Sensei plug in through Firmware/Plugins (no access to uninstaller). Deleted the /usr/local/sensei folder and tried again. Same result unfortunately, OPNSense grinds to a crawl and the Sensei GUI is not accessible. For now I've deleted it all again so OPNSense can run. Deleting the plug-in restores OPNsense and the GUi to normal operation.

System is Qotom 4 Q355G4 Intel i5 running at 2.2GHz so should have the power to run Sensei.

How would you like me to submit the bug report?

   

[sy]

Hi,

Try to access GUI by stopping the packet engine service. Log in to the console as root then run the command
service eastpect stop

The bug report is the upper right corner of Sensei GUI.

[lignumaqua]

Thanks, I'll try that when I pluck up the courage to try again. However 'top' showed that eastpect was only using max 6.5% of CPU. The entire system was running at only 2.9% CPU so I don't think it was anything being processor bound that was causing the problem with the GUI.

I could see packets being filtered in the logs, and the Elasticsearch database was being updated, it was just the OPNSense GUI that was completely borked.

[lignumaqua]

@sy, I take it all back, you were correct! I stopped eastpect through ssh and the GUI returned. I could then access the bug report. Thank you!

[lignumaqua]

Thanks to help from the support staff I was able to track this problem down. Had to check the 'Disable hardware TCP segmentation offload' box in the interface settings. Everything running fine now.  :)