19.7.3 with Sensei - Dashboard Error Message after OPNsense reboot

[ckishappy]

..I get after every reboot the "An error occurred while report is being loaded" message in Sensei.

Error
{
  "error": {
    "root_cause": [
      {
        "type": "index_not_found_exception",
        "reason": "no such index",
        "resource.type": "index_or_alias",
        "resource.id": "conn_all",
        "index_uuid": "_na_",
        "index": "conn_all"
      }
    ],
    "type": "index_not_found_exception",
    "reason": "no such index",
    "resource.type": "index_or_alias",
    "resource.id": "conn_all",
    "index_uuid": "_na_",
    "index": "conn_all"
  },
  "status": 404
}

Also the Live Sessions Explorer does not work then after the reboot. Not sure if Sensei is still operational or not. I can fix this by Reseting the Reporting (under Sensei : Configuration : Reporting & Data) but would expect that this functionality is there out of the box and Sensei survives a system reboot?

Sensei standard install (https://help.sunnyvalley.io/hc/en-us/articles/360024899634-Installing-Sensei-on-OPNsense) on Deciso Rack Xeon box with OPNsense 19.7.3.

Please advise & thanks in advance, Chris

[mb]

Hi @ckishappy,

This shouldn't be happening if the firewall is gracefully rebooted/shut down.

This mostly happens after an abnormal shutdown of the firewall. Since Elasticsearch does buffered writes, an abrupt shutdown leaves the indexes in an unstable state.

If this is not the case, let's investigate this together.

[ckishappy]

hi @mb, hmm thanks! As a first measure, I disabled the use of /tmp RAM disk and /var RAM disk (so that tmp and var are on the hd as opposed to the memory). Since then I rebooted twice and the reporting looks fine. Will let it boot & run for a couple of days to check if this did the trick. Br, Chris

[mb]

Hi Chris, good to hear that you're now able to use Sensei. Many thanks for the update.