Originally Posted by falko
That looks like an MD5 encrypted password. Have you tried to replace it with the cleartext password?
In the 3 machines that I have ISPConfig 3 installed on, all 3 of them have an MD5 password in that config.inc.php file. I did not try changing the password to a cleartext password.
I needed to get my SSL cert working, so I created a new machine and have transferred the one particular web site that needed the SSL Cert to the new machine and as soon as I can get the rest of the sites transferred, I will start again fresh with 2 other machines.
I tried to get the mirror working 3 times before I went with the standalone machine. Out of the 3 tries, twice a mysql table was corrupted right after I installed ispconfig3 on the slave. They were not the same one each time.
Also, you have in the manual to add the backports repository and then do an apt-get install of the debian-backports-keyring, before you do an apt-get update. so of course, it doesn't find the app until after you do an apt-get update. Just something you may want to reverse on an update to the manual.
Just to make sure I am doing it right, there are not that many things that are different on the slave vs the master server.
The Server Name, IPAddress, Copying the files from mysql_bak to mysql and www_bak to www only on the master, copying the debian.cnf from the master to the slave, create the root user for the slave server in mysql and grant options and then on the master, set the slave as the mirror. Everything else is all the same, correct?
When setting up the glusterfs server configuration files and volume files, is it ok to create the files on the master and then just copy them to the slave?
I'd like to say Thanks to You and Till for all the patience and hard work you guys do on this project. I for one would still be using Windoze for my internet servers if not for you guys.
Thank You Thank you Thank you