HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (
-   ISPConfig 3 Priority Support (
-   -   multiserver - problem with db password for remote user (

radim_h 6th May 2013 00:39

multiserver - problem with db password for remote user
this is not question of priority support but problem with in multiserver setup.

i have reported here:[0]=&sev[0]=&due[0]=&cat[0]=&status[0]=open&percent[0]=&reported[0]=
but my post was long and maybe nobody have read it untill last comment where error is desribed:

Problem appears in multiserver setup when you change db user password and after it you change IP acces configuration for remote DB user

when database user password is changed in gui:
it gets changed in master ispconfig database in web_database_user,
passwords for both users (local and remote) in mysql user table on remote server are created correctly

But PASSWORD IN DATABASE ON SLAVE SERVER web_database_user table IS NOT CHANGED - is created new row with sys_userid and sys_groupid both set to 0
This new duplicate rows are overwrited when next db user is created and master db synced to slave server (but old password for remote user in slave web_database_user stays forever..)

Then when acces to db is changed IP<->% or another ip added, password for remote user is probably taken from this slave web_database_user and it is set wrongly in mysql user table, so remote access is not working then

till 6th May 2013 11:45


thank you for making a bugreport for the issue. We will check this for the next patch release.

radim_h 17th May 2013 11:01

Hello guys,

please is somebody solving this problem?

It's more serious
First i solved the issue that i removed that part of web templete which allows users setting remote access to db...

But as i found now, when someone change password for pre-3.0.5 user whos databse is not bound to webpage, then even simple password change fails

I'm getting phone calls from clients who changed password for db users every day :||

radim_h 17th May 2013 11:10

simpliest fix will be to tell on slave server to get passwords from master server web_database_user instead of slave, as master db is chnaged properly on update, but i don't know ho to do it :(

till 17th May 2013 13:07

The issue has been forwarded to the developer which implemented the new client database plugin.

Did you choose to reconfigure permissions un master database at the time you updated your slave servers?

All times are GMT +2. The time now is 22:37.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.