Cant image from FOG Nodes?

[george1421]

@cojohnson Ooops you ran into a bug in rc5. I think tom posted a “you can fix it patch”. Let me see if I can find it.

[george1421]

@george1421 I think this was the fix/band-aid

https://forums.fogproject.org/topic/8238/database-update-failed-after-image-capture/3

With your favorite text editor edit /var/www/fog/lib/fog/fogmanagercontroller.class.php

“change the =& on line number 23 and remove the & symbol”
Then save and exit that file.

I’m not sure on the timing of RC6 being released, it WILL be a few days though.

[cojohnson]

Hmmmnn interesting. I used an ftp client on windows and line 23 contains =& on that file. However, when i view the SAME file on the fog server using vi, vim, and nano i do not see the =& on line 23.

Looks like i will just wait a few days and then upgrade again.

Thanks for all of your help!

[george1421]

@cojohnson Just an update here. I put a request in the developers queue to look at this thread to see if it is similar to the issue I linked. They may be related… or not.

Please wait for their feedback.

[Wayne Workman]

I’m just now reading through this thread, it’s good you updated to RC-5.

The way I’m reading the OP,

You have one node called “DefaultMember”, in an earlier picture from Location Management, it’s listed twice, with two different locations and two different storage groups. In a later picture from Storage Management, I only see one storage group, “default”.

Another thing to note is that “DefaultMember” 's max clients is set to 0 in a picture above. This would mean it would not image anything at all, because max clients is zero.

Maybe it’s best to explain what you’re trying to accomplish first?

Also, you may find this article and the video in it highly helpful:
https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin

[Tom Elliott]

@Wayne-Workman I think this is absolutely what’s happening.

The task queue is seeing 0 before that host, but since there are 0 available slots, it will NEVER make it that far. At least not for that particular node.

Remember, the location definitions are based on Group and Group/Node pairings. Do you have a second storage group named “Green”? Is there a second node that uses “Green” but is named DefaultMember?

[Wayne Workman]

@Tom-Elliott So, below he says if he sets the node to something besides 0 that things image.

But, what I’d like is screenshots taken all at once of location management listing and storage management node listing. No changes between the pictures.

And, I’d like a detailed explanation of what the OP even wants to do.

[Tom Elliott]

@Wayne-Workman The last part was a partial bug in the location plugin. It would allow a user to change the group of a node, rather than ensuring the node’s group defined the group the location was pointing it. It would also allow the user to remove the storage group AND storage node. At the least it should’ve halted editing the removal of group. Those two fixes are in RC-6 now.

[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.