DE

↑ ↓ select, Enter open, Esc close

View PHP errors in the LiteSpeed stderr log

harmless rootLiteSpeeddebian, ubuntu
root@server
tail -n 50 /usr/local/lsws/logs/stderr.log

Under LiteSpeed, messages that PHP processes write to stderr end up in a separate file instead of the server error log. With blank pages or 500 errors and nothing in error.log, this file is worth a look. It shows the last 50 lines.

Note: If PHP has its own error_log configured, PHP errors go there instead.

Also searched as

  • php errors litespeed log
  • lsphp crashed
  • white screen litespeed php error
  • litespeed stderr.log

Related one-liners

All in LiteSpeed

Follow the LiteSpeed error log in real time

#tail -f /usr/local/lsws/logs/error.log
harmlessLiteSpeed

Follow the Apache error log in real time

#tail -f /var/log/apache2/error.log
harmlessApache

Follow the Plesk panel log in real time

#tail -f /var/log/plesk/panel.log
harmlessPlesk

Check if LiteSpeed Cache serves a page from cache

$curl -s -o /dev/null -D - https://example.com/ | grep -iE "^(server|x-litespeed-cache[a-z-]*):"
harmlessLiteSpeed

Check the status of the LiteSpeed web server

#/usr/local/lsws/bin/lswsctrl status
harmlessLiteSpeed

Gracefully restart LiteSpeed

#/usr/local/lsws/bin/lswsctrl restart
cautionLiteSpeed

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.