Host/Group replication between FOG Servers
-
I am also getting stuck here on PXE. I am at the remote location trying to register a host, but I cannot get past this part. just sits with a blinking cursor
-
@adukes40 The replication error is likely permissons or SELinux.
with the iPXE stuff, did you put in the correct main server IP during installing the storage node? You must also put in the correct MySQL fogstorage password for the storage node during installation too.
-
@Wayne-Workman said in Host/Group replication between FOG Servers:
@adukes40 The replication error is likely permissons or SELinux.
with the iPXE stuff, did you put in the correct main server IP during installing the storage node?
===Yes, it is the IP of the new main server I created.You must also put in the correct MySQL fogstorage password for the storage node during installation too.
===I have placed all the needed passwords. Here are the SS’s to show:Main server info:
Remote storage info:
Storage Node information from the /.fogsettings file:
What is typed into the management gui (copy and pasted):
Username: fog
Password: hXFzePJJGCBLw7uudEVDry9gGWL9AcO70FOtAblUxF4=i assume each node is supposed to have different storage management passwords? Because when i compare the two nodes, the Password is different.
-
This post is deleted! -
Also are permissions something I will need to set on all remote sites?
-
@adukes40 said in Host/Group replication between FOG Servers:
i assume each node is supposed to have different storage management passwords?
Correct. At this point, we need more details. Exactly what version of FOG trunk are you running, and what Linux distribution and version?
-
Ubuntu 14.04 LTS
Fog 7713
Fresh installed last night… between 8pm - 11pm EST.
-
@adukes40 Are the storage nodes the same version of FOG? It does matter. Also, you said you previously had a full fog server at each site? Are you using those or did you build fresh?
-
Also, to see if FTP credentials are right and pathing is correct, security is correct, firewall is correct, you can connect from the main fog server to the node via FTP to test credentials.
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP
-
@Wayne-Workman I shut off any other instances of FOG last night. there are currently only 2 instances running, The main server which is across town, and the storage instance located here at my shop. the 10.103 address is the main server, and the 10.106 address is the storage location at my location. both were setup exactly the same. Only difference is the DCHP server address, gateway, and local IP of the fog servers themselves. both runnin Ubuntu 14.04, FOG 7713. I was making them side by side last night to hopefully keep them the same version and they are. I download the install using this:
sudo svn co http://svn.code.sf.net/p/freeghost/code/trunk I left the mysql password blank when setting up the Main as well. -
Here is what the permissions look like on the Main:
and here is the storage only:
-
it looks like firewall is disbaled, I was able to send a file from the remote server to the main server manually. this is what i get for the remote location still:
Error communicating with the database. Error: SQLSTATE[HY000] [1045] Access denied for user ‘fogstorage’@‘localhost’ (using password: YES)
-
@adukes40 make sure the fog storage password is correct on the storage node. If it’s not, change it in /opt/fog/.fogsettings and rerun the installer on the storage node.
You can test MySQL credentials from the node to the main by connecting to it via something like this:
MySQL -u fogstorage -h x.x.x.x -p
Not sure if that syntax is right but its close. you can Google examples.
-
Also to clarify, for the ftp test, you should have been on the main server testing ftp ccredentials to the node. Testing from the node to the main doesn’t tell you if the nodes ftp credentials are good because you weren’t testing them.
And, the MySQL test should be run from the node.
You can use SSH to be “in” whatever server you need to run the tests.
-
@adukes40 I gave you the long explanation because you seem detail oriented but I’ll put it more plainly.
In a multi-server setup with one main tied to one or many nodes, all registrations are stored in one place. On the main. Everything is managed from one place, on the main. Everything is contained in one spot, on the main. If a host is registered anywhere, it’s registered everywhere. Because the main holds everything and is the controller for everything, and the communication point for everything everywhere.
The point of nodes is to increase imaging capacity, decrease load over the WAN, and to overcome broadcast domain related issues.
-
when the storage node installed it gave me that long password, is that the password to use, or do i need to change it to the long password the Main uses? right now they are different.
-
Ok, i just conducted ftp from the main to the node. i created a test.txt on the node, then on the main i used ftp to view the file directory, then delete the file, the dir again to verify it is gone.:
techinstall@MSDCATS09:/$ ftp
ftp> open 10.106.2.149
Connected to 10.106.2.149.
220 (vsFTPd 3.0.2)
Name (10.106.2.149:techinstall): fog
331 Please specify the password.
Password: <long password from setting up node>
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> cd /images
250 Directory successfully changed.
ftp> dir
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
drwxrwxrwx 2 0 0 4096 May 19 02:34 dev
drwxrwxrwx 2 0 0 4096 May 19 02:34 postdownloadscripts
-rw-rw-r-- 1 1000 1000 7 May 19 19:58 test.txt
226 Directory send OK.
ftp> del test.txt
250 Delete operation successful.
ftp> dir
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
drwxrwxrwx 2 0 0 4096 May 19 02:34 dev
drwxrwxrwx 2 0 0 4096 May 19 02:34 postdownloadscripts
226 Directory send OK.
ftp> exit
221 Goodbye.
techinstall@MSDCATS09:/$ -
now i get this for the storage node
Error communicating with the database. Error: SQLSTATE[HY000] [2002] Connection refused
I think i will update the Main, and do another fresh install of the node and see what happens.
-
Just rebuilt it, looking like it is connecting now as well. I will keep updating.
-
Here is what I am getting now: