Server

Why debug.log Files Matter Performance impact: Large log files can eat up disk space and slow down file operations. Backup bloat: If your backups include debug.log, they can become unnecessarily large. Security risk: Debug logs may contain sensitive paths, plugin names, or even database queries. If exposed publicly, attackers could use this information. Maintenance signal:…

for ((i=1; i<=5; i++)); do history -d $(history 1 | awk ‘{print $1}’); done to get rid of the last 5 lines / commands

You might need to calculate average amount of memory used by each Apache process for several reasons. One being deciding on MaxRequestWorkers . You can do it by running: ps -ylC httpd –sort:rss | awk ‘{x += $8;y += 1} END {print “Apache Memory Usage (MB): “x/1024; print “Average Process Size (MB): “x/((y-1)*1024)}’ Apache Memory…

While optimizing our MySQL server we noticed our mysqld.log was huge in size – 1GB+ – and it was filling every moment with the below message: [Warning] [MY-013360] [Server] Plugin mysql_native_password reported: ”mysql_native_password’ is deprecated and will be removed in a future release. Please use caching_sha2_password instead’ Below article explains the issue https://support.cpanel.net/hc/en-us/articles/16550190886935-MySQL-log-warning-mysql-native-password-is-deprecated-and-will-be-removed-in-a-future-release But it…