Cant image from FOG Nodes?

[cojohnson]

@Tom-Elliott @Wayne-Workman Thanks for looking into this. I manage 2 school district which is why i was trying to implement 2 locations. “default” being the main district and “GREEN” being the second district.
Originally, The goal was to set up a server to be hosted on site at GREEN but that never happened. Consequently, we do all of the imaging from our building and I currently have all of the “GREEN” images also assign to the “default” storage group.
I do all of the imaging currently at our building.

I set the master to handle clients so I can image for now. This is sufficient for the moment.

Should I upgrade to RC-6

[Wayne Workman]

@cojohnson said in Cant image from FOG Nodes?:

Should I upgrade to RC-6

No. Not right now, there’s line ending problems. Wait on it until things are fixed.

[Tom Elliott]

@Wayne-Workman They’re already fixed.

[cojohnson]

@Tom-Elliott
are the line ending problems fixed in RC-6 or will it be in the next release?

[Quazz]

@cojohnson Should be fixed in RC6. They patched RC6 to resolve the issue, so it’s safe to update.

[cojohnson]

I just upgraded the FOG server to RC-6. I looked at ALL of my nodes immediately after upgrading the server and they are not happy… they are saying “FOGService: FOGService- Waiting on mysql to become available”

What might be causing this?

[Tom Elliott]

@cojohnson Did you update all nodes?

Line endings have nothing to do with the error you’re seeing. From the sounds of things, the node’s simply cannot connect to the mysql server (which should be the Main fog server).

[cojohnson]

@Tom-Elliott I did update all nodes to RC-5 and only 1 node and the server to RC-6

[cojohnson]

@Tom-Elliott is there a config file i can check to verify the mysql username is “fogstorage” and the password is set proper?

[Tom Elliott]

@cojohnson If you can login to the gui, the FOG Storage Node mysql user and password will be found at:

FOG Configuration Page->FOG Settings->FOG Storage Nodes

However, you should test connecting by cli once you know the information.

Something along the lines of:

mysql -u fogstorage -p -h<IPOFFOGSERVER> fog

Use the fogstorage user’s password.

[cojohnson]

@Tom-Elliott
I am having troubles with this command…

What is “fog” used for in the last part of the command and what password should i enter if i am prompted again like my last photo.

Sorry for being uneducated.

[Tom Elliott]

@cojohnson if you’re doing inline password passing, the mysql command needs the password directly next to the -p argument
so you would need to do:
sudo mysql -u fogstorage -pfs18692474601 -h10.21.0.105 fog

The trailing fog of the command brings you directly into the fog database.

[cojohnson]

@Tom-Elliott Thank You for the explanation. It is greatly appreciated!

I will try this command on Tuesday when I am back in the office.

[cojohnson]

This post is deleted!

[cojohnson]

@Tom-Elliott I ran this command on the server and one node and i had an error on both saying
Error 2003 Cant connect to MySQL server. Do you have any more ideas?

[Wayne Workman]

@cojohnson Can you check the space on the main server, please? df -h

[cojohnson]

@Wayne-Workman

[Tom Elliott]

@cojohnson This is most likely because of Ubuntu/Debian variant OS’s.

They typically have a default mysql configuration that only allows connections from the localhost (127.0.0.1, localhost, 127.0.1.1, localdomain, etc…)

Do this:

sudo -i #insert password if prompted to
cd /etc
grep -rl -- bind-address

The file that shows up (any of them please), edit them and comment (usually prepend the line before the text on that line displays with a # symbol).

Save, restart mysql services. Rejoice as the nodes start being able to connect (hopefully that is).

[cojohnson]

@Tom-Elliott
I ran that “grep -rl – bind address” command. it found a file /etc/mysql/my.cnf
I used vi to comment out the line that included “-- bind address”
That fixed the imaging from the nodes issue.
I tested this from a hyper-v host.

On Tuesday, i noticed a new problem when i network boot my devices. They are ALL saying that the hosts are not registered with FOG. I try to register them and recieve output saying “A hostname with that name already exists”. It will give me this error no matter what hostname I type.

[Tom Elliott]

@cojohnson Does the host already exist? Can you update to 1.3.0-RC-8 too btw please?