DE

↑ ↓ select, Enter open, Esc close

Follow the LiteSpeed error log in real time

harmless rootLiteSpeeddebian, ubuntu
root@server
tail -f /usr/local/lsws/logs/error.log

Continuously prints new lines of the server error log, stop it with Ctrl+C. This is where configuration errors, problems with external applications such as lsphp and denied requests show up. The path applies to a default installation, individual virtual hosts may have their own logs.

Also searched as

  • litespeed error log location
  • openlitespeed show errors
  • litespeed 503 error cause
  • tail lsws log

Related one-liners

All in LiteSpeed

View PHP errors in the LiteSpeed stderr log

#tail -n 50 /usr/local/lsws/logs/stderr.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.