MySQL crashed – again
Just after posting the Babelfish interpretation of “Flushing Cache”, MySQL server went down. This time, it took a few hours to get up again – because I had no access to the systems. It’s been pretty much the same: value 12, “not enough core”, this time on read.
Reverse changes
I took the chance to reverse a few changes made in favout of the IDE server for Distributer Detbenas and WEBES and lowered some of the system parameters that wer increased as their requirement, but since RdB is to be installed some day, I kept an eye on the requirements. The only one needed a permanent increase comapred to the original setings, is CHANNELCNT – set to 2050, just less than twice the original amount. The rest have been restored to the original.
Next I rebooted Diana (some of them are not dynamic) but something strange happened: It looks like some command procedure has “SET VERIFY” in it and the whole listing was sped out on the screen. MySQL was started but the remains of the procedure seemed to be bypassed. Running it separately revealed no troubles at all, so what happened here, I don’t know. The log didn’t shbow anything either….
But the system is now working again.
What goes on behind the doors of the (private) data center