DE

↑ ↓ select, Enter open, Esc close

Follow the Apache error log in real time

harmless rootApachedebian, ubuntu
root@server
tail -f /var/log/apache2/error.log

Continuously prints new lines from the global error log, press Ctrl+C to stop. Ideal for triggering an error in the browser at the same time and seeing the message right away, such as invalid .htaccess directives or missing modules.

Note: On Plesk, errors for a domain go to /var/www/vhosts/system/<domain>/logs/error_log, so the global log mainly contains server-wide messages.

Also searched as

  • view apache error log
  • apache 500 internal server error cause
  • tail apache error log live
  • where is the apache error log debian

Related one-liners

All in Apache

Follow the LiteSpeed error log in real time

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

Check whether Apache hit MaxRequestWorkers

#grep -i "MaxRequestWorkers" /var/log/apache2/error.log* | tail -20
harmlessApache

Follow the Plesk panel log in real time

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

View PHP errors in the LiteSpeed stderr log

#tail -n 50 /usr/local/lsws/logs/stderr.log
harmlessLiteSpeed

Count running Apache processes

$ps -C apache2 --no-headers | wc -l
harmlessApache

Check the Plesk installer log after a failed update

#tail -n 100 /var/log/plesk/install/autoinstaller3.log
harmlessPlesk

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.