CPanel PHP Error Logs

[CincinnatiWebTec]

Hello,
We recently installed Litespeed on a few servers of ours that are running WHM/Cpanel and AlmaLinux. When running Apache, each user can access their PHP error logs in their home/ACCOUNT/logs directory. But once we switch over to Litespeed, those logs stop. I understand Litespeed logs to one central log file located at /var/log/apache2/error_log - but is there a way to have the same behavior as Apache? And log to the home/ACCOUNT/logs directory for each account?

Thanks,
Chris

 

[serpent_driver]

Is your question about LSWS or OLS?

 

[CincinnatiWebTec]

LSWS

 

[serpent_driver]

If you have LSWS and WHM/cPanel nothing has to be done. cPanel provides access_log and error_log for each user/account. If it is different with your installation please contact cPanel support.

 

[CincinnatiWebTec]

Where are those logs found though for each CPanel account? In the /home/ACCOUNT/logs folder like they used to be? Or is everything compiled into 1 log now in the /var/log/apache2/error_log?

 

[serpent_driver]

Where are those logs found though for each CPanel account? In the /home/ACCOUNT/logs folder like they used to be?

For access_log yes. error_log location depends on configuration in LSWS WebAdmin.

Check this in cPanel.

 

[CincinnatiWebTec]

I believe that's with CloudLinux. We are running MultiPHP Manager.

PHP Error logging is configured correctly inside the MultiPHP Manager because as soon as I turn LSWS off, it goes back to logging everything perfectly fine for all accounts. But as soon as I turn LSWS on, it stops logging PHP errors to the accounts. From everything I've read, LSWS is supposed to use what's in the MultiPHP Manager. Well - that's not happening and I can't figure out why. Could there be a permissions issue?

 

[serpent_driver]

If you use LSWS with cPanel, then cPanel controls where the error.log is stored, but you have to enable error logging. If it isn't enabled no errors are logged.

 

[CincinnatiWebTec]

I've explained though that it IS enabled. When you turn LSWS off, it works just fine. So it's not an issue on the CPanel side in my opinion.

 

[serpent_driver]

As said, if cPanel is used with LSWS, then cPanel controls error logging, so it seems to be better to ask cPanel support.

 

[CincinnatiWebTec]

Okey Dokey. I'll see what they have to say. Thanks.

 

[serpent_driver]

Okey Dokey. I'll see what they have to say. Thanks.

Please give us feedback if cPanel has solved the problem.

 

[CincinnatiWebTec]

Well - I figured out the issue. I feel a little stupid, but it may help someone else. PHP-FPM stores the PHP error logs in the home/$user/logs directory. It does not use the settings from the php.ini file. When you switch over to LiteSpeed, it pulls the log location from the php.ini file which is typically set to the root public_html folder. So the logs were simply switched to whatever is specificied in the php.ini file and I kept looking in the /home/$user/logs directory thinking they weren't working.

 

[soland]

Well - I figured out the issue. I feel a little stupid, but it may help someone else. PHP-FPM stores the PHP error logs in the home/$user/logs directory. It does not use the settings from the php.ini file. When you switch over to LiteSpeed, it pulls the log location from the php.ini file which is typically set to the root public_html folder. So the logs were simply switched to whatever is specificied in the php.ini file and I kept looking in the /home/$user/logs directory thinking they weren't working.

The main problem is that /home/$user/logs is not supported like FPM.