[Temporarily SOLVED] Destroyed firewalld ipset after hard reset

Support
1

Continuing the discussion from [SOLVED] 500 internal error after hard reset:

Unfortunately it’s broken again :confused:

After updating to 20.20 the machine hung and I had again to hard reset by unplugging and replugging power.
After that I again experienced the 500 error because of a non-running firewalld.

But now I receive this after trying to restart it (systemctl status excerpt):

Dez 26 10:46:04 odroidxu4 firewalld[10964]: WARNING: ipset not usable, disabling ipset usage in firewall.
Dez 26 10:46:04 odroidxu4 firewalld[10964]: ERROR: INVALID_ZONE

I tried to restore firewalld from a former backup but that didn’t change the unusable ipset.

What now? How can I fix or regain the ipset?

2

Reinstallig firewalld and restarting device again didn’t help.

And I don’t know why, but there’s a lot of:

Dez 26 11:32:44 odroidxu4 rsyslogd[630]: file '8' write error: No space left on device [v8.1901.0 try https://www.rsyslog.com/e/2027 ]

and /var/log/ is shown as full (100% of /dev/zram0).

3

OK, this CAN be a device related i.e. armbian related problem. For I have now raised the possible zram-size from 50 to 150MB now the firewall started again and I seem to receive no more 500 errors on plinth.

Still /var/log takes 92% of the 150MB already (123MB of it are /var/logs/pcp !). There is still this message:
Dez 26 12:42:11 odroidxu4 firewalld[563]: WARNING: ipset not usable, disabling ipset usage in firewall.

For now it seems to work … but I fear the next update …