# Opening log for WUI not possible

**URL:** <https://community.ipfire.org/t/opening-log-for-wui-not-possible/15401>\
**Category:** Installing & Running IPFire\
**Created:** [10 January 2026 12:04 UTC](https://community.ipfire.org/t/opening-log-for-wui-not-possible/15401 "2026-01-10T12:04:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pscar13](https://community.ipfire.org/user_avatar/community.ipfire.org/pscar13/32/16558_2.png) [@pscar13](https://community.ipfire.org/u/pscar13)\
**Post date:** [14 January 2026 10:44 UTC](https://community.ipfire.org/t/opening-log-for-wui-not-possible/15401/3 "2026-01-14T10:44:50Z")

</div>

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

> [@Core 199 - Hostapd write exessives logs](https://community.ipfire.org/t/core-199-hostapd-write-exessives-logs/15403/8):
>
> 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…

---

_[View the full topic](https://community.ipfire.org/t/opening-log-for-wui-not-possible/15401)._