• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved Log Browser - Error (code: 1)

Sanderv

New Pleskian
Username:

TITLE

Log Browser - Error (code: 1)

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Log Browser v1.3.0-124 - Plesk Obsidian
Versie 18.0.45 Update #2 - Ubuntu 20.04.4 LTS

PROBLEM DESCRIPTION

When I open the Log Browser extension I get the error:
Code:
Error (Code: 1)
STDOUT: ERROR: TypeError: Argument 4 passed to PleskExt\LogBrowser\Helper\Filter::match() must be of the type string, null given, called in /opt/psa/admin/plib/modules/log-browser/library/Parser/JournalParser.php on line 67 (Filter.php:60) . STDERR: PHP Warning: rtrim() expects parameter 1 to be string, array given; File: /opt/psa/admin/plib/modules/log-browser/library/Parser/JournalParser.php, Line: 37 PHP Warning: rtrim() expects parameter 1 to be string, array given in /opt/psa/admin/plib/modules/log-browser/library/Parser/JournalParser.php on line 37 [2022-07-31 22:43:55.761] 2259113:62e6e98b9b9b7 ERR [panel] Argument 4 passed to PleskExt\LogBrowser\Helper\Filter::match() must be of the type string, null given, called in /opt/psa/admin/plib/modules/log-browser/library/Parser/JournalParser.php on line 67: 0: /opt/psa/admin/plib/modules/log-browser/library/Helper/Filter.php:60 PleskExt\LogBrowser\Helper\Filter->match(array, string 'plesk_saslauthd', string '3336931', NULL null) 1: /opt/psa/admin/plib/modules/log-browser/library/Parser/JournalParser.php:67 PleskExt\LogBrowser\Parser\JournalParser->readByLine(string '{"__REALTIME_TIMESTAMP":"1659269150923913","_SYSTEMD_CGROUP":"/system.slice/system-postfix.slice/pos...') 2: /opt/psa/admin/plib/modules/log-browser/library/Parser/JournalParser.php:44 PleskExt\LogBrowser\Parser\JournalParser->read() 3: /opt/psa/admin/plib/modules/log-browser/library/Reader/ReaderList.php:33 PleskExt\LogBrowser\Reader\ReaderList->readLog(integer '999999999', integer '1000') 4: /opt/psa/admin/plib/modules/log-browser/library/Reader/ReaderList.php:24 PleskExt\LogBrowser\Reader\ReaderList->getResult(integer '999999999', integer '1000') 5: /opt/psa/admin/plib/modules/log-browser/library/LogReaderCliWrapper.php:36 PleskExt\LogBrowser\LogReaderCliWrapper->getResults() 6: /opt/psa/admin/sbin/modules/log-browser/log-reader:11

Also when I delete all filters the error stays.
.

STEPS TO REPRODUCE

Open Log Browser

ACTUAL RESULT

Error (code:1)
And can't use the Log Browser extension

EXPECTED RESULT

No error and the Log Browser gui

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out
 
Fixed.

1.3.1 (01 August 2022)​

  • [-] The extension no longer behaves incorrectly if any systemd/journalctl log files contain one or more non UTF-8 characters, non-printable characters, or very long messages. (EXTPLESK-3808)
 
Back
Top