• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question on MySQL Database Replication

R

rank1st

Guest
We are running a load balanced environment with two servers. We don't have a need for mysql clustering, but we did setup mysql database replication.

This seems to work fine - except:
Within the plesk interface on the slave server the databases do not show up. We can log in via a shell and see that the databases have replicated and that data is there, the slave updates fine whenever we change data in the main server.

What is kind of weird about this is that we did a test earlier with one of the databases (no databases were defined on the slave at all), started replication and that database shows up in the plesk interface however the subsequent additional databases are not there.

Anyone have any ideas?
 
Back
Top