mysqli_error()

[Igor S.]

Are you serious? NEVER delete anything you do not understand!
I hope everybody understands you kidding

[marthaneilson]

One can try "yum install mariadb-server" and see what happens. Your database is affected or deleted by / var / lib / mysql, so we hope you didn't miss anything. Anyway, it was a big mistake and I hope you get your backup.

[Fisnik Myrtezaj]

 /etc/systemd/system/mariadb.service.d
           `-migrated-from-my.cnf-settings.conf
   Active: activating (start) since Thu 2020-11-12 02:42:09 EST; 173ms ago
     Docs: man:mariadbd(
           https://mariadb.com/kb/en/library/systemd/
  Process: 17985 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
  Process: 17982 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 17996 ((mariadbd))
   CGroup: /system.slice/mariadb.service
           `-17996 (mar

[Igor S.]

/etc/systemd/system/mariadb.service.d
           `-migrated-from-my.cnf-settings.conf
   Active: activating (start) since Thu 2020-11-12 02:42:09 EST; 173ms ago
     Docs: man:mariadbd(
           https://mariadb.com/kb/en/library/systemd/
  Process: 17985 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
  Process: 17982 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 17996 ((mariadbd))
   CGroup: /system.slice/mariadb.service
           `-17996 (mar

And what do you think we can see there?

[cinique]

And what do you think we can see there?

LOL 
Someone who doesn't wrap code in tags, is the only error that I can spot. 

[Igor S.]

@cynique do not advise if you do not understand what are you talking about!

[cinique]

Igor S.
You are normally one of the better ones here - you're beginning to sound like one of the other members of the Team.
I was actually complimenting you, on your reply.

[bluebrad]

i checked my passwords and there the same?

1) You must restart mariadb server with the mariadb unit.
The command is:
(for CentOS7):

Code Select Expand


# systemctl restart mariadb


or
(for CentOS6):

Code Select Expand


# service mariadb restart


2) ** Important (as your error message itself):
===========================================================================================
**Check your MySQL root password in: /usr/local/cwpsrv/htdocs/resources/admin/include/db_conn.php and /root/.my.cnf
===========================================================================================

This means the root password in file:
     /usr/local/cwpsrv/htdocs/resources/admin/include/db_conn.php
and in the file:
     /root/.my.cnf
must be exactly the same.

Regards,
Netino

[Igor S.]

> i checked my passwords and there the same?

Then check if you are able to connect as root to MySQL with the password.
Make sure you have enough disk space also.

[jk22]

I solved the problem.
Thank you all.
Now everything works.

Can you tell me how you solved the problem ?

[heart2hack]

I am getting the issue today and mariadb is not starting, upon investigating the issue I was getting mariadb corrupt table, so I insert

Code Select Expand

innodb_force_recovery = 5
into the my.cnf file. what it did was, all my site are up.

but now, I am getting issue with cwp admin login. so I reset the mysql root password, it was successfully reset, and also change the root password, but still getting the above message

[heart2hack]

when I insert

Code Select Expand

innodb_force_recovery = 5
in configuration file of mysql, all the websites get up and databases get up, but cwp admin panel login doesn't work after that and getting error.

[overseer]

You need to get mariadb fully functional before CWP will function properly. You may need to repair your tables, delete your log files (ib_logfile0 and ib_logfile1), or roll back to a backup (or recreate the root_cwp database) in order to get fully stabilized.