[Bug]: After upgrade the webUI page with logs started to decline to be shown

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

After the upgrade from 26.. to 27.. I've found that the webUI log page is often not shown, but the infinite loop with circle. Only forced removing or renaming nextcloud.log helps to solve issue, but I am loosing the journal. The size of the last nextcloud.log, when the UI was frozen is 90MB.

Steps to reproduce

1. Work with nextcloud for a certain time.
2. Go to logging (journal)
3. Observe infinite loop trying to show the content of the web page.
4. SSH to your server, rename or remove nextcloud.log
5. Observe, that the logging page is shown again but without saved journal with earlier data.

Expected behavior

The nextcloud.log file should rotate more frequently or the UI subsystem must be more adjusted to show the content of the log page.

Installation method

Community Web installer on a VPS or web space

Nextcloud Server version

27

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.1

Web server

Apache (supported)

Database engine version

MariaDB

Is this bug present after an update or on a fresh install?

Upgraded to a MAJOR version (ex. 22 to 23)

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

config.php contains:

logtype = file
loglevel = 0
logfile = /mnt/data/nextcloud.log

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

Start by reproducing the logreader web UI failure with a nextcloud.log around 90 MB, then compare the page behavior before and after the log file is renamed. Investigate the log display and rotation behavior described in the issue; done means the journal remains available and the logging page renders reliably without requiring deletion or renaming of the file.