@Tom-Elliott

Okay, I’ll update and post the result here.

@iekozz I am not too sure where we are at with this multi culti topic here. I’ve just read the whole lot again. We started by fixing your image name possibly along with some other image settings, then got the non bootable media error (FOG is not able to transfer the UEFI firmware boot entries from one machine to another yet!) and talked about timezone and FTP issues.

May I kindly ask you to open a new topic and explain the current issue you are seeing at the moment. We’ll focus on fixing that and move on from there (probably in just another topic). The less we mix up topics the more other people can profit from the things we find out and write to fix their own issues.

So I am marking this solved now as we have solved the initial issue (and more). Please open a new topic and explain where you are at.

@Sebastian-Roth I have updated everything to the latest development version without issue tonight. The web gui definitely seems faster. I will watch for any oddities tomorrow while the system is in use. Thank You Guys again for all you do!

@ElNatcho We are working on this issue. Just in case you are still around. I pushed some major changes to the dev-branch a few hours ago. Should fix the flow web UI issues altogether. Please give it a try if you can and let us know.

@Sebastian-Roth Let me test it with a machine and get a specific model. I will verify the UEFI firmware is up to date as well.

@Sebastian-Roth

Your idea sounds like a good compromise. Something like delete old file on new upload checkbox that is checked by default maybe?

okay, that makes sense. I forgot that the images folder only syncs folders tied to an image in the table.

I tried your update and that fixed the file getting set to 0kb. I test when I can, as FOG has a lot of potential in my eyes and I know most if not all of you are doing this in your spare time, which means a lot. I’m hoping someday I’ll have time to learn PHP and contribute more to the project, but that’s a battle for another day.

Posted in feature request and tagged you and this post for reference.

@blindcat420 said in Cant pxe boot to fog.:

I went ahead and reran the fog installer.
That seems to have fixed it.

Sometimes it’s the simplest things… I need to remember to suggest rerunning the installer when there is strange things happening.

Got him fixed up after a long session through teamviewer. Password reset, DHCP setup, FOG server IP change, switch configuration and all the rest…

Thanks its “WORKING” so coooooool.

Thanks George and Sebastian thnx thnx thnx…

@Sebastian-Roth Yes, its working perfectly now, Thanks!

@Sebastian-Roth Hi Sir I will do so thnx

@george1421

I’ve read a lot to solve the problem, and I think that’s the quid of question:
Snapins Run as SYSTEM or root
All Snapins including SnapinPacks run as the SYSTEM or root user’s security context. If a snapin or SnapinPack runs successfully by manual execution but not via the FOG Client - this is typically related to the security context. For example, say you have a shared directory that is granted read access for all Domain Users. Well, an individual host’s local SYSTEM or root account is not a member of Domain Users. Therefore, unless alternative credentials are supplied to access the share, any script executed that tries to read this share will not work. There are a few solutions to this. Granting the share read access for anonymous users is the most simple. Specifying credentials within scripts or as arguments are viable options.

How can i specifying credentials with scripts or arguments in snapin console? Could you put an example?

Thks a lot.

@Jamaal Good to hear you figured this out. Would have been quite hard for us I reckon.

Hello mate,
Had the FOG issue: Warning: mysql_connect() [function.mysql-connect]: Access denied for user ‘root’@‘localhost’ (using password: NO) in /var/www/fog/management/index.php

This is caused by the FOG PHP session looking to connect to ‘localhost’, the correct password is not being passed causing the failure. Not having time to research the exact fix I found the following is a quick solution…

Before trying to open the FOG management webpage
Install PHPMYADMIN (this makes database management easy)
Open //localhost/phpmyadmin
Create a new user and give them ALL permissions for ALL HOSTS (basically they should be the same as ROOT
Check the user is there and the permissions are set correctly.
Go into the PERMISSIONS tab and remove the password for ROOT under localhost & 127.0.0.1
Open the FOG webmanagement page
Set up the users in FOG
Go back to PHPMyAdmin and make sure FOG has been added as a database. You will need to log on as the ‘new user’ above
Reset the root password to something secure (as per pre install???)
Open the FOG database
Go to Permissions and BLANK the root password for localhost & 127.0.0.1
That should solve the issue.
Best regards
Arso

@Cameron-w A couple of things that come to mind skipping through that video:

FOG 1.2.0 is very old. Make sure you install the most current version which is 1.5.5 as of writing. From you question it seems like you already have - just wanted to stress this point. (K)Ubuntu 14.04 is dated as well. I would advise you to use a more recent one as well. Changing the FOG server’s IP address is more an advanced thing and not something I would advise new users to do! Better make sure you can have a setup with internet access and static IP address right from the start. Saves you some headaches. If you really want to do an IP change use Wayne’s script found here. This way you don’t have to worry about FOG_WOL_HOST and the others this guy is changing. Just go with a static address for your first lessons and you can completely skip that changing part of the video (20:00 to 31:00).

The rest of the video seems ok, although talking about an old FOG version. Have fun.

Marking as solved. @JiC Please let us know if you see it replicating the same image files over and over - definitely shouldn’t.

@p4cm4n In the case of storage nodes, the fog server that hosts the database has to be updated with the remote node’s new IP address. So to answer your question, No. Though since the database credentials are present on the storage node, some alterations to the scripts could make this possible.

dhcp general settings on LAN:

0_1542798476261_2368dc54-6215-4e93-855b-ada35d7e0f02-image.png

dhcp settings on other VLAN:

0_1542798558095_52779031-4102-4b2d-84c6-f1b69ab59a94-image.png

@Keating178 Please schedule the same task again but tick the checkbox for debug task this time. When you get to the shell start it using command fog and step through.

It will fail again I am sure but will drop you back to the shell. Now run the sgdisk you see on screen to get the full error…

A fog “image” consists of 2 parts.

The raw image files stored in /images The metadata stored in the mysql database.

You can copy all of the raw image files simply by the copy command. The metadata can easily be exported from the webgui into a csv file. With the raw data and metadata you can rebuid the images on a new fog server or whatever. If you don’t have the metadata but the raw image files you could rebuild the metadata if you are careful on how you name your images and are a good guesser for the rest. Point being, backup the image metadata with the raw data files and you will be good.