- Home
- Logs
Reading the logs
Something returns a 500 and the page says nothing useful. The answer is in a log file, and finding it should not mean remembering where VXOST keeps them.
Gigabytes open instantly
Only the last 256 KB of a file is read, never the whole thing. A MySQL error log that has grown past three gigabytes, which happens, quietly, over a couple of years, opens as fast as an empty one.
- System logs first, then one entry per virtual host
- Filter by text to keep only the lines that matter
- Follows the file as it grows, if you were already at the bottom
- Opens with ⌘L from anywhere in the app
When a log will not open
MySQL's error log belongs to the _mysql user, and your account
cannot read it. Rather than showing an empty window, the viewer says so and
offers a one-off read with administrator rights. Automatic refresh switches
off at that point, so you are not asked for a password every two seconds.
Per-project logs
Each virtual host writes its own error and access log, and they appear in the selector under the system ones. When a single site misbehaves you can go straight to it instead of reading everything at once.
⚠️ Logs grow silently
Nothing rotates them by default. On the machine this app was built on, the MySQL error log had reached 3.6 GB without anyone noticing. The viewer opens it regardless, but a file that size usually means an error repeating thousands of times a day, and it is worth reading.
Stop guessing what broke
Open the log, filter for the error, read the line.