Issue panel.log use 00 instead of 20 for space

[Azurel]

Server operating system version

AlmaLinux 9.8

Plesk version and microupdate number

18.0.80#1

I have encountered an issue with a file generated by Plesk that contains a NUL byte (0x00) in the middle of a PHP stack trace. The affected line contains the following sequence:



The 0x00 byte occurs immediately after Interface@anonymous and before /usr/local/psa/....

In a hex editor, the byte at this position is confirmed to be 00. This causes problems when opening the text in WinSCP's internal editor and copying the line, the copied text is truncated at the NUL byte. Removing the 0x00 byte makes the entire line copy correctly.

Could you please investigate why Plesk/the affected component is writing a NUL byte into this text file and whether this is expected or a bug?

 

[scsa20]

Sounds like you might have SELinux issue, check to make sure your SELinux is configured correctly, put it into permissive mode temporary to see if the behavior goes away.

 

[Azurel]

# sestatus
SELinux status: disabled

But what does SELinux have to do with the 0x00 character in the log file? I was not concerned with the error message in the log.

 

[Sebahat.hadzhi]

Hi, @Azurel . This is expected behavior for PHP anonymous classes. However, I was able to replicate the behavior of WinSCP truncating the string after the NUL byte and I opened an internal case for our team to further review the error writing behavior of Plesk in such cases. I will follow up with more details as soon as possible.