[youssefbasha]

Hello guys,
Again and again
I have faced a new OGP Problem
It was working fine and suddenly i got "Could not connect to the database."

[Pacific Spirit]

Check the Database settings and in your cpanel. Make sure that your DB's are connected with each privelliges! That should fix the issue.

[youssefbasha]

Check the Database settings and in your cpanel. Make sure that your DB's are connected with each privelliges! That should fix the issue.

I tried to start MySQL Manually from the vps and it gave me errors
root@vps570089:~# systemctl start mariadb.service
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
root@vps570089:~# systemctl stats mariadb.service

Unknown operation stats.

[Mashiro]

You can see the error message or better said the reason for the failure of the MariaDB process startup by running the command that is suggested by systemd to see more details. journalctl (frontend for journald) is basically a log of all operations executed through/in systemd environment including errors.

To get the entry of the error you have to execute the startup of MariaDB again even if it fails and right after that run the journalctl command. So run these two commands and post the full output here for debugging.

Start MariaDB service:

Code: (Select All)

systemctl start mariadb

Get the journalctl log:

Code: (Select All)

journalctl -xe -l

[Honey]

Furthermore, googling the issue as to why MariaDB "suddenly" stopped working should help you figure out what's the issue. My guess would be that something messed up with Maria when u were installing something else, and due to that it now fails to start.

[youssefbasha]

You can see the error message or better said the reason for the failure of the MariaDB process startup by running the command that is suggested by systemd to see more details. journalctl (frontend for journald) is basically a log of all operations executed through/in systemd environment including errors.

To get the entry of the error you have to execute the startup of MariaDB again even if it fails and right after that run the journalctl command. So run these two commands and post the full output here for debugging.

Start MariaDB service:

Code: (Select All)

systemctl start mariadb

Get the journalctl log:

Code: (Select All)

journalctl -xe -l

root@vps570089:~# systemctl start mariadb
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
And the journalctl command gave me long log so i took ss from it and iam uploading it now

[Mashiro]

You can redirect the output into a file with a simple redirection pipe ">".

journalctl -xe -l > journalctl.log

[youssefbasha]

When i use journalctl -xe -l > journalctl.log nothing happens
It just give me [root@hostname~ folder]

[Mashiro]

The log provided in your screen is of no use because it only contains the first lines. You can notice that there is a field/button like element in the bottom left corner that says "More". You would have to use navigation keys to go down until you reach the end of the log with the latest log entries (most likely containing information about the MariaDB startup failure).

The later command I told you has no console output because as I said it redirects the output of the whole command to a file instead of the console.

Try these please:

Code: (Select All)

systemctl start mariadb
journalctl -xn -l > mariadb-fail.log

Open the mariadb-fail.log file after the two commands and show the content here or upload that log file to a file hosting site.

[youssefbasha]

I uploaded it here https://firex-hosting.com/mariadb-fail.log