• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Log browser error (after update)

O

OverWolf

Regular Pleskian
Server operating system version
Almalinux 9.4
Plesk version and microupdate number
18.0.62 Update #1
Hi,
after update to version Version 1.8.2-1118, I have many PHP Warning (Uninitialized string offset 0; File: /usr/local/psa/admin/plib/modules/log-browser/library/Database/Mail/Table.php, Line: 287). Why ? Is there a way to fix them ?

Thank you
 

Attachments

  • PleskLogBrowser.jpg
    PleskLogBrowser.jpg
    89.8 KB · Views: 7
As I can see, the bug was fixed in the version 1.8.2,

1.8.2 (04 July 2024)​

  • [...]
  • [-] Fixed the issue where certain mail log entries could stop further processing of the log file, resulting in the "Exception: PHP Warning: Uninitialized string offset 0" error. (EXTPLESK-5642)
  • [...]
Click to expand...

Could you confirm that these errors continue appearing after the upgrade? Could it be you see errors that happened before the upgrade?
 
Hi,
yes, the error persist. As I wrote, I have installed 1.8.2, but nearly every day I have these records in logs
 
Thank you @OverWolf, we were able to reproduce the issue and can confirm the bug.
Currently, the plan is to fix the bug together with the next release.
 
JFYI. A new version of the Log Browser extension has been released, it also contains a fix for this bug (the bug was registered with id EXTPLESK-5700).
 
You must log in or register to reply here.

Similar threads

Dmytro
Issue Log Browser - update data error
Replies
0
Views
507
Dmytro
Dmytro
xx1Andy1xxx
Resolved Log Browser
Replies
5
Views
1K
AYamshanov
AYamshanov
J
Issue Logs Browser Plesk error
Replies
7
Views
1K
JuanCar
J
J
Issue Array to string conversion; File: /usr/local/psa/admin/plib/pm/Locale.php, Line: 234
Replies
0
Views
10K
JuanCar
J
V
Resolved high CPU usage by 'sw-engine' with task 'ext-log-browser-parse-maillog'
Replies
16
Views
2K
wapin55
W
Back
Top