ZenArmor eastpect filesystem full error

[dinguz]

I am seeing these error messages in my logs:

pid 22 (eastpect), uid 0 inumber 8 on /usr/local/sensei/output/active/temp: filesystem full
pid 22 (eastpect), uid 0 inumber 8 on /usr/local/sensei/output/active/temp: filesystem full
pid 22 (eastpect), uid 0 inumber 11 on /usr/local/sensei/output/active/temp: filesystem full
pid 22 (eastpect), uid 0 inumber 11 on /usr/local/sensei/output/active/temp: filesystem full
pid 22 (eastpect), uid 0 inumber 18 on /usr/local/sensei/output/active/temp: filesystem full
pid 22 (eastpect), uid 0 inumber 18 on /usr/local/sensei/output/active/temp: filesystem full
pid 22 (eastpect), uid 0 inumber 23 on /usr/local/sensei/output/active/temp: filesystem full
pid 22 (eastpect), uid 0 inumber 23 on /usr/local/sensei/output/active/temp: filesystem full
pid 22 (eastpect), uid 0 inumber 28 on /usr/local/sensei/output/active/temp: filesystem full
pid 22 (eastpect), uid 0 inumber 28 on /usr/local/sensei/output/active/temp: filesystem full
pid 22 (eastpect), uid 0 inumber 30 on /usr/local/sensei/output/active/temp: filesystem full

Is this something to be concerned about? Anything I should change in the settings?
I have never seen these before, so this seems to coincide with the 1.12 release of ZenArmor, or the 22.7.7 release of OPNsense.

[beki]

Hi dinguz,
You may try to increase temp size by following the steps in the guide:

https://www.zenarmor.com/docs/opnsense/configuring/reporting-data#size-of-the-fast-temporary-memory-disk-in-megabytes--capacity

[dinguz]

I have never seen this error before, so I would like to know what has changed, that caused this to start happening now. And how do I find out what the necessary size is, without resorting to trial and error?