Issue Recurring problem with log-browser scheduled task

[Janko Falli]

Server operating system version

Ubuntu 24.04 LTS

Plesk version and microupdate number

Obsidian 18.0.76

Hello,

I am experiencing a recurring issue with the Log Browser extension scheduled task. The task runs automatically but always returns an error in the output:
Task "/opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/log-browser/scripts/parse-logs.php'" successfully completed in 0 seconds, output:
[2026-03-06 09:58:44.696] 1538001:69aa9744a9e8f ERR [panel] No such file or directory
[2026-03-06 09:58:44.704] 1538001:69aa9744a9e8f ERR [panel] No such file or directory

The system otherwise works normally, but the scheduled task repeatedly logs these errors. The task itself reports “successfully completed”, but the error appears every time it runs. The problem persists even after reinstalling the log-browser itself and plesk-web-socket package which was previously missing (done by plesk support).

Is this related to missing log paths or an internal extension issue?Is there a recommended way to reset or rebuild the log-browser environment?

Thanks

 

[Aleksei Fedorov]

Hello, the error in the logs appears too generic. Please enable debug logging and run the script manually.
Then please share the detailed logs.

Best regards, Aleksei

 

[Janko Falli]

Hello,

Debug logging was enabled in panel.ini and sw-engine was restarted.
The script was executed manually again:

/opt/psa/admin/bin/php -dauto_prepend_file=sdk.php /opt/psa/admin/plib/modules/log-browser/scripts/parse-logs.php

However, the result is still exactly the same and no additional diagnostic details are written to panel.log. The log still only shows:

ERR [panel] No such file or directory

Please advise.
Thanks

 

[Aleksei Fedorov]

In debug logs you can see the exact command to run journalctl, please share it
P.S. util_exec options should be enabled as well https://support.plesk.com/hc/en-us/articles/12377672365975-How-to-enable-disable-Plesk-debug-mode

 

[Janko Falli]

The issue was caused by the plesk-web-socket service not running.

In panel.log we were seeing errors like:

Http\Client\Socket\Exception\ConnectionException: No such file or directory
unix:///run/plesk-web-socket/ws-inner.sock

In our case the service was installed but disabled and inactive:

systemctl status plesk-web-socket
Active: inactive (dead)
Loaded: ... disabled

After enabling and starting the service:

systemctl enable --now plesk-web-socket

the socket /run/plesk-web-socket/ws-inner.sock was created and the log-browser tasks (e.g. parse-logs.php) started working normally.

The confusion came from the fact that the component was installed from plesk support and appeared functional, but looks like the websocket service was not enabled to start automatically, so after a restart it remained stopped.

Thanks for your help!