php error logs gone? And logs in general...

cornflakes

Hello, my server got hit really hard this morning by something unknown, and it ended up killing my MariaDB process. A reboot of the server got everything up and running again. From the stats and syslogs, I can see at one particular time, one of my sites was getting hit with an overwhelming amount of requests.

But that's about all I know as I just discovered access logs are kept for only minutes (whyyyyyy?!?!?!) this behavior is crazy to me because I often check access logs to figure out what's causing problems with a site, potential security issues, and on occasion, I can also use it to troubleshoot (catch my clients lying) about what they've done to the site.

But fine, I see there's mention of this getting changed in the future.

However, I also discovered my php error logs are gone from the home directories of the websites. I remember seeing them at one point. But now I don't see them at all. In the home directories all I see are the public_html directories.

Did they get moved? I did upgrade to 12.0 about 2 months ago but I'm pretty sure I saw them more recently than that... Thank you.

cPFence

cornflakes

Yes, access logs aren't permanent on Enhance yet.

Make sure you apply the package resource limits mentioned here.

This can help prevent a single site from overloading or crashing your server.

gmakhs

cornflakes Probably OOM killed the DB or litespeed enteprise 🙂
Both Common issues if you search the forum

xyzulu

gmakhs Probably OOM killed the DB or litespeed enteprise

A completely normal Ubuntu action when a server is out of resources.

cornflakes my php error logs are gone from the home directories of the websites

Are you on the latest version? I see php error logs across our entire cluster.

gmakhs

xyzulu indeed is normal, i just wanted to pointed out the common reasons it can happen for him 🙂

Adam

php-error.log is only created the first time PHP throws an error and only if the error_log directive has not been changed in php.ini or using ini_set() at runtime. It is wiped when the container is restarted to avoid excessive growth. This behaviour has not changed since version 10.0.0.