• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Plesk Obsidian - Version 18.0.50 - Database Servers Missing

emailco

New Pleskian
Server operating system version
AlmaLinux 9.1 x86_64
Plesk version and microupdate number
Plesk Obsidian 18.0.50.0
Hi, after upgrading plesk to 18.0.50, it looks like the database support isn't working anymore or there is a gui problem.

Product version: Plesk Obsidian 18.0.50.0
OS version: AlmaLinux 9.1 x86_64
Database version: 10.5.16-2.e19_0

Code:
plesk repair mysql
Checking MySQL database servers ..................................... [OK]
Repair databases on available servers ............................... [OK]
Repair database users on available servers .......................... [OK]
Error messages: 0; Warnings: 0; Errors resolved: 0

Admin Area
Tools & Settings -> Database Server = Looks like there's nothing here!


plesk_screen_1.png

Customer Area
"Here you can create new or manage existing databases" but there are no buttons.

plesk_screen_2.png
 
Perhaps also needed as info...

System packages:
mariadb 3:10.5.16-2.el9_0
mariadb-common 3:10.5.16-2.el9_0
mariadb-connector-c 3.2.6-1.el9_0
mariadb-connector-c-config 3.2.6-1.el9_0
mariadb-errmsg 3:10.5.16-2.el9_0
mariadb-server 3:10.5.16-2.el9_0
plesk-libmariadbclient-3.1 3.1.8-0redhat.9.220912.1011
 
Had the same issue after a broken install, turns the PSA database was broken, the repair does not cares about that so here is a quick fix what I hope going to work.

plesk db
SQL:
USE psa;
SELECT * FROM `DatabaseServers`;

Empty set (0.000 sec)
If shows an empty result you have to create the entries for the available databases, of course you should modify this according to your needs:

SQL:
INSERT INTO `DatabaseServers` (`id`, `host`, `port`, `type`, `server_version`, `admin_login`, `admin_password`, `parameters_id`, `last_error`, `fork`) VALUES
(1, 'localhost', 3306, 'mysql', '10.5.18', 'admin', '******', NULL, 'no_error', 'mariadb'),
(2, 'localhost', 5432, 'postgresql', NULL, '', '', NULL, 'credentials_not_set', NULL);
 
Hey thanks for the response, I can't emphasize enough what a great product Plesk is and thank you for all the hard work you guys are putting into it.

Are we sure that this method checks these tables?
Here is what was tried:

plesk repair installation
plesk repair all -y
./bootstrapper.sh repair
In that case it would probably be
# plesk repair installation

Believe me I spent a few hours figuring out what went wrong. In this case nothing shows up in the logs, what is understandable.
Installing postgresql as secondary db didn't do the trick.
Due to IPv6 enabled on Debian 11 the installer runs with some heavy delays (we had 5-20sec dns response times) which is unlikely to be the fault of the installer. By a complete dumb move the first installer was ctrl+x-ed and for whatever reason it was still running in the background, a second installer was started what hang at some point with the usual error what we get when the proper plesk installer finds and other installer process. It just didn't displayed anything so we had to check the logs and make the first one exit.

Most of the errors that this accident generated were fixed by the "plesk repair" (or we believe so :), but this problem with the missing database server remained.
 
Back
Top