New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
buyshared lu04 mysql down
I just discovered that there are a lot of error logs on my website
When I checked the logs I found the following error message
[2023-12-16 21:28:42] local.ERROR: SQLSTATE[HY000] [2002] No such file or directory
Then I try to open phpmyadmin in cpanel
but got the same error
mysqli_sql_exception: No such file or directory
Also, I tried reselecting mysqli and nd_mysqli from php selector
The problem is still not solved
Comments
Maybe open a ticket?...
A ticket has been opened
Haven't received a reply yet
But my log file increases by 1M every second.
while true; do rm -rf log && sleep 30; done
Master of one-liners
while :; do rm -rf log; sleep 30; doneor
while sleep 30; do rm -rf log; doneThank you for contacting LowEndSupport, your waiting time has been doubled.
https://linux.die.net/man/8/logrotate
mysql server restored
After checking the logs, it was found that this problem began to appear on November 15th.
Then it appears in the logs of November 15th, November 30th, December 08th, December 09th, December 14th, and December 16th.
ssh brute-force? running out free space (or inodes) due log/temp files?
)
edit: nvm ... too long for typing (somehow distracted with other work
Sorry about that.
Mateus sorted it, but not sure why it didn’t auto restart. If it was down. I’ll have to check the cpanel logs since it should’ve caught that.
Francisco
...to check cpanel is always good, also regarding upgrades to the current version
@Francisco
It was cPanel
But not a version issue.
We disabled MySQL monitoring on this node many many years ago it seems, back when cPanel was having ongoing issues with systemd. I never enabled it again after that and I guess its been fine since then. Really curious what the uptime on the process was.
Anyway, that's re-enabled at this point.
Francisco
tl;dr: frandammit
Why would you disable monitoring? I don't know much about cPanel btw
its like 1000 different shit grouped up to make up 1 shit for grandpa's and grandma's to edit and host their sites.
Whatcha expect?
one time, my cpkeyclt failed, and somehow magically cpsrvd got corrupted during an update, and I had to do a reinstall (cP support couldnt figure it out either, luckily it wasn't hosting anything). It was back in 2020, stuff could've changed.
cPanel had some nasty bugs in the move to CentOS 7 and systemd where it was constantly rebooting processes because it couldn't monitor them properly. It was doing it to Litespeed as well leading to quite a lot of long outages.
I seem to recall talking about it way back in the day when it was happening.
Disabling the auto restart addressed it at the time and it kinda fell to the wayside.
Francisco
f you need, I can provide laravel's log before the 16th, which will contain the time when the error occurred.
I have deleted the log on the 16th because it was too big.
I have deleted the log on the 16th because it was too big.
Nope, no need at all suh
MySQL crashed, and cPanel didn't restart it. The 'dont restart' was intentional on our part, but was to address a bug probably 4 years ago. We never re-enabled the process monitoring in all that time.
Our fault, sorry about that.
Francisco
Troubleshooting steps:
1. Blame fran
2. No need for a step 2
I’ve started doing it soley by reflex
Sometimes I realize ”wait, my oven not working simply can’t be Frans fault”
But most of the time, it just is, no matter how unlikely