Since the latest update (it seems) I am unable to open/view: Firewall logs fw-loggraphs (*) ip address blocklist logs system logs in the WUI. When I select one of these the browser is just waiting for data is seems (waiting for ), but nothing happens. After a while it gives a Gateway Timeout on e.g. “https:///cgi-bin/logs.cgi/log.dat” Not sure if it’s related: It seems also that something is filling up my disk again (/dev/sda4 14G 9.9G 2.8G 78% /) and it is not the suricata cache this time.

For me opening logs is still possible, but really, really slow since update 199.

This looks like the /var/log/messages file is too large. Worth checking; this might be a clue: [image] Core 199 - Hostapd write exessives logs Add-Ons Loglevel was removed from wlanap.cgi in CU188 at the same time as Debuglevel. If that entry was used previously then you could have an entry in settings of DEBUG=0 down to DEBUG=4 with 0 being verbose and 4 being warnings with the default being 4 so at the minimum anybody using wlanap prior to CU188 would likely have some DEBUG entry in settings. Anybody starting with wlanap from CU188 onwards would not have a DEBUG entry in settings. Anybody running with wlanap with CU187 or earlier would ha…

Thanks for the pointer. I removed the DEBUG line from /var/ipfire/wlanap/settings . Noticed my old HTCAPS entry was still present, so I cleaned this one up, too, since some messages seemed related.

The HTCAPS entry shouldn’t matter. This entry to /etc/hostapd.conf is generated by /etc/init.d/hostapd start. BTW: You can see the generated hostapd.conf by /etc/init.d/hostapd show-config from the CLI.

Thanks - you’re right, it shouldn’t matter. Since it looks like HTCAPS and VHTCAPS have been replaced by MODE it seemed prudent to clean up.

Thanks for the replies! I removed the '“DEBUG=4” line from /var/ipfire/wlanapp/settings. Now wait and see how this develops here. EDIT: It was indeed /var/log/messages that was filling up my disk. Ran out of disk-space completely. I deleted messages and the latest “.gz” file of it. Now see how it goes. Regards, Edwin.

“messages” was 6GB in size. I deleted it and created an empty messages file. Not sure if that’s the way to go. After I deleted “messages” I don’t see a lot of free space. The partition is 13GB in size. Any thoughts? Regards, Edwin.

du -h / 2>/dev/null | sort -hr | head -n 20 To search for the 20 largest directories find / -type f -exec du -h {} + 2>/dev/null | sort -hr | head -n 20 To search for the 20 largest files in this directory

Maybe you are affected by this: 13926 – Suricata Hyperscan cache grows indefinitely with no automatic pruning it might be worth checking

Opening log for WUI not possible

Installing & Running IPFire

pscar13 (pscar13) 14 January 2026 10:44 3

This looks like the /var/log/messages file is too large.
Worth checking; this might be a clue: