@george1421 ok, that makes everything alot clearer, thank you for your help!

You could also disable the nodes you want to delay replication for via Storage Management.

@pdehombreux Sorry for leaving you alone for such a long time on your very first post. It’s been a very busy time and I just couldn’t get my head around your post when I first read it and so kept on putting off to look into this.

I think we need to get into the logs to see what’s actually happening when you try to update the AD information. First check the apache error and php-fpm logs right after (or while) you update the client’s AD information. See my signature on where to find those.

If that does not shed a light (I suppose it won’t) then I may ask you to enable mysql query logs. For that it’s probably best to turn off as many components as possible first. Shut down clients that have the FOG client installed and make sure you are the only person on the FOG web UI for that moment. Just trying to keep the logs to a minimum.

See here on how to enable mysql query logging: https://www.pontikis.net/blog/how-and-when-to-enable-mysql-logs

Before you enable it, get the web interface ready. Navigate to the right host, select AD settings and change OU and username for example. Then turn on logging, restart mysql, update the client settings and switch off mysql logging again. Upload the full log here (make sure it does not contain any sensitive data …)

@p4cm4n said in install fails - adding repository... failed:

when it gets to adding distro it fails.

I guess you meant “adding repository” here, right?

For Mint and Ubuntu we add ondrej repos (commands add-apt-repository ppa:ondrej/php and add-apt-repository ppa:ondrej/apache2).

Debian is different, here we only add a repo for Debian 7 which shouldn’t be used anymore anyway.

In the same directory where you have the FOG installer script there is a subdirectory called “error_logs”. There you find log files with specific error messages. Please take a look and post here if you can’t figure it out on your own.

The way both iPXE and FOS work is it will stop searching when it finds an ‘up’ interface. So if you want it to pxe boot place the pxe boot network in the first interface position and then use the second or what ever else for the network where you have no control.

@vincityhn1 said:

When we try send a image stored in node A, the Fog Server search this image in both nodes A and B.

What exactly do you mean by “try send a image”? Send where? Pushing the image to the client? And what do you mean by “Fog Server search this image…”? Can you be more specific on this. Maybe take a picture of what you see on screen and post here.

@fogofwar said in "Operation not supported" tftpboot failing - please help:

Only one problem now that we got past that I am getting this error about “No configuration method succeeded” but only on a VM. I will have to look at that next.

This is only on reboot I am fairly sure! Shut down the VM completely, bring it up again and PXE boot will work nicely. This is a known bug in virtualbox.

@jherron The information is split in two different tables. Host information and MAC information. So you need to commands to clean that host’s information from the database:

mysql> DELETE FROM hostMAC WHERE hmHostID = 1272; ... mysql> DELETE FROM hosts WHERE hostID = 1272; ...

But I still wonder why we only see one entry while FOG seems to find duplicates. Would you be keen enough to add some more error output to the PHP code so we see which MAC it sees as duplicated? If yes, I should be able to help you with the code. Let me know.

@kwilson7392 said in FOG Capture Task keeps rebooting:

This is my first capture task…

So my guess is you might still be thinking in different concepts. Ghost for example did some modification to the boot loader on disk and joined into the task when rebooted from disk. But FOG is different. It’s based on PXE booting the client. If a job is scheduled then the PXE loader will bring up the FOS system to do that task on your machine and if there is no task it will chainload from disk to boot the OS.

Have you setup your machine to PXE boot?

I agree. Fog should tell you “these images won’t really be deleted, I’m just going to pretend… you’ll need to ssh in and clean up”

I revived this thread, because I’m seeing this issue. I see other threads saying it works, but I am on
FOG 1.5.4 kernel 4.18.3 and have to ssh to actually delete the files.

@Jim-Holcomb said in http 500 error:

uncaught error: call to a member function lastInsertID()

This is usually due to a database connection issue. Please read through this: https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy

problem solved!
In fog settings >> Ad default OR I have filled in the fields in small as an example:
or = xxxx, dc = yyy, dc = zzz
Thank you all

@gabbas said in Snapin not working as a Batch file xcopy:

everyone has read and execute permission to this folder

Is it really everyone as in anonymous without authentication or is it all users/group members of your organization? I ask because the FOG client is running as service and won’t have the same auth tokens as if you run the script as user.

Hi,
I tried the password fix and it didn’t help.
Did you manage to overcome this issue?

The Fog Client and Fog Server are up to date and database is fixed.

Now the Fog Server working properly now.

Thank You for your help.

@Cire3 Hey I’m glad you have it worked out. You found one of the gotchas with naming (No special characters as the first character in the names).

@Wayne-Workman thanks i was able to figure it out, and yes im an old fog user and installer. I had to changed the fogstorage mysqlpassword on my storage node on the .fogsettings (/opt/fog/.fogsettings) Once i changed it to the one provided by the Fog Server everything worked.

@matijn Don’t edit core files for this. (they’ll be overwritten at next update)

Instead update your /opt/fog/.fogsettings file with the credentials and rerun the fog install script.