NEW INSTALL CENT7 DATABASE FAIL...AGAIN

Since I had problems with my production server, I decided to create another server with fresh install to see if I could replicate the problem.

As soon as I went to admin dashboard and click on restart database, the database server failed with a result of cwp failure.

THIS IS A BRAND NEW INSTALL!   WTF IS GOING ON?

No one here who cares apparently.

mysql error

 ERROR! MariaDB is running but PID file could not be found

Is this a new CentOS 7 install?
If not what distro are you trying?

Sounds like there is a problem during the CWP install pulling a needed file from a repo.

Try: yum install perl-DBD-MySQL libuuid-devel m4 pcre-devel pcre libtool zlib-devel -y

Ok, installed as recommended. Now what?

Server is centos 7, both of them.

Hi,

I have tried to replicate your problem and its just not possible.

What are your steps when installing CWP.
Did you update CentOS 7 before installing CWP ?

Hi,

I have tried to replicate your problem and its just not possible.

What are your steps when installing CWP.
Did you update CentOS 7 before installing CWP ?

I installed following instructions from centos-webpanel.com.

I can install correctly and create new user.  But stopping mysql causing mysql crash and resulting loss of cwp panel.

Two of my existing long time servers just spontaneously stopped allowing create users after CWP updated the Mysql manager user interface.  And both of those servers will crash if I stop mysql form control panel and try to start.

you should contact cwp support to check that

you should contact cwp support to check that

thats the point

bug injected to get support call

damn.. i hate to thinking like that.

you should contact cwp support to check that

I sent you an instant message last week and you never replied.

I contacted support and gave them my login details.

They never did anything about it.

I also told Sandeep about it and he said he would look into it. 

A normal install with out of the box settings will crash the instant you try to restart mysql.   And amazingly no one cares or can duplicate it.

i hope i can back to use cwp

but after read this

i think,,, it a good choices to start leave the CWP....

except if you have extra $ to pay support.... u should stay

For standart pro or free version ( i have pro and free ) must thinking twice...

Production server (commercial hosting) will losing their customer if stay with free or standart version (not support include)

there is no any bug, cwp is using mysql so if your mysql restarts too slow it will not work.
You should restart mysql from the command line or check what issue you have with the restart command

there is no any bug, cwp is using mysql so if your mysql restarts too slow it will not work.
You should restart mysql from the command line or check what issue you have with the restart command

evrything not at the place, or correct flowchart, input output
is a BUG.....

i hope i can back to use cwp

but after read this

i think,,, it a good choices to start leave the CWP....

except if you have extra $ to pay support.... u should stay

For standart pro or free version ( i have pro and free ) must thinking twice...

Production server (commercial hosting) will losing their customer if stay with free or standart version (not support include)

I fully share your mood - service and support are below everything - the users pay their contribution and there is deliberate speculation here to buy the additional managed support.


What hardware do the servers run on:

CPU
R.A.M.
HDD or SSD?

I already had the same thing years ago, when a customer tried to install a test VPS with 1GB Ram and 10 GB storage CWP and had the same problems.

if you are OLD USERS of CWP
and follow this forum

you will know.. that the massive bug came after fer weeks ago... 1 day 3-4 or 5 build released