When you installed Linux, did you create the fog user or let the installfog.sh file create it? You may have to go through the password synchronization steps on the wiki to get the fog username and password fixed for all the different places it’s used.

Are the similar machines at another location using this same FOG server? I’m trying to track down the differences between the two groups and why the speeds would be so different.

Yes, FOG is alive and kicking.

looks like we can convert $process into an array of resources, iterate through all the storage nodes in the group that are not the master storage node, and kick off the popen() for each one, storing the resulting resource into the $process array. iterate through the $process array to output the fgets() info for each ftp transfer call, and then iterate through it again outside the for loop to call pclose for each element in $process array.

It might be a a week or two before I can test out the parallel. Might be easier to get the node info into an array so we don’t rely on the $conn staying open for hours with no activity. Your images will sync very slowing, waiting on one to finish before beginning the next, but you’ll at least have them.

Maybe an option to specify you have slow WAN links to your storage nodes and to use parallel syncing can be added to the UI.

It’s not currently possible. You can only have 1 master storage node per storage group and this node will receive all uploaded images and then distribute them to the other storage nodes in the same storage group.

Look at [U][COLOR=#0000ff][URL=‘http://www.fogproject.org/wiki/index.php/Fog_deployment_nodes’][U][COLOR=#0000ff]this article[/COLOR][/U][/URL][/COLOR][/U] from the wiki and see if you can modify it to meet your needs. Take notes and we’ll incorporate your experience back into the documentation if possible.

I’m assuming you added the NFS server to take over hosting of the /images of the main FOG server. Is this correct?

If you have enabled FTP on your existing NFS server, then you will want to tell the main fog server what the username and password should be when the main fog server connects to the storage node. Looks like it pulls the information for the FTP call from the values in the FOG WebUI - Other Information - FOG Settings - TFTP Server: FOG_TFTP_FTP_USERNAME and FOG_TFTP_FTP_PASSWORD.

I’m betting the MySQL connection is timing out because it is taking so long to push the image files to the first storage node.

Looking at /opt/fog/service/FOGImageReplicator/FOGImageReplicator script line 88, the variable $res is a resultset from the mysql_query() call above it. Right below it is the call to transfer the image file to the first node via ftp and wait for the transfer to complete before moving on. This is taking 6 hours for you, during which time the $conn used by $res is probably closed since it has not been actively used for a very long time.

The solution is probably to either run the node FTP updates in parallel OR bring the result set of the query into a multidimensional array and then close the connection since it will not be needed anymore. Then you can take your time “while’ing” through the list of storage nodes and sending the images via FTP.

If I can figure out the code I’ll post it with instructions. I also need to look at the dev code to see how it’s being handled in 0.33 to see if that code could be handled better.

I think a lot of what you are trying to do can be accomplished by properly configuring your quick image options in the WebUI - Other Information - FOG Settings - FOG Quick Registration

Play with it and see.

Are you using a single FOG server or a Normal server plus one or more FOG servers installed in storage mode?

I’m thinking you need to make sure the FOG client running on the clients of the FOG 0.32 server are using the client from the FOG 0.32 server. Also, use the FOGCrypt from the 0.32 server to re-encrypt your password for AD joining and update your hosts.

This is all assuming you have not recompiled the HostNameChanger.dll to use a different passkey for encrypting your AD passwords.

wrap your log file in the code tags:
[CODE] log file data no smilies and we can read this[/CODE]

[quote=“darthanubis, post: 5212, member: 1659”]I see and can edit the file, but no one mentions where in the file the text is located or what it looks like to be edited?[/quote]

FOG version 0.32, edit the /opt/fog/service/etc/config.php on the [B]STORAGE[/B] node. The mysql username and password will be the ones displayed in the WebUI of the [B]NORMAL/MAIN[/B] fog server under Other Information, Fog Settings, Fog Storage Nodes. Usually “fogstorage” and “fs####” where #### is a random number between 0000 and 9999.

Once you update the /opt/fog/service/etc/config.php on the storage node, restart the scheduler service:
[CODE]sudo /etc/init.d/FOGScheduler restart[/CODE]

tail the log file and see if the error is resolved.

unmanaged switches don’t allow switch admins to misconfigure them…

Check the processor statistics on the switches to see if they are overloaded. There may be too many rules, or rules that are invalid or detrimental.

If you are allowed and technically able, backup the running config and then reset the switch to factory settings. If it works without issue, compare the configs until you find the issue.

holy thread resurrection Batman! You’re post is ambiguous. Post more details if this problem is the exact same as the OP, or better yet start your own thread including information about your FOG server OS, FOG version, etc.

multicast will only go as fast as the slowest client. I also think multicast requires much more RAM on the server, so a low RAM server will perform subpar when multicasting vs unicasting.

Using a kernel with best/optimized drivers for the HP 6000 sff may also help, since you do better on another vlan with other machines.

[quote=“wpsd, post: 5195, member: 1641”]FWIW, I was having the same issue until I set the password of the ‘fog’ user on the second node to what was displayed in /opt/fog/.fogsettings. Sync began immediately after I restarted the replicator service.[/quote]

To which /opt/fog/.fogsettings are you referring? The one on the main FOG server or the storage node?

Check your apache log. Seems like it may be having problems rendering some of the page. Also, try a different browser. Firefox seems to work best for me, just to make sure it isn’t a client side problem.

What OS are you using for your Fog server?

When the storage node is first installed using the “S” option in the Fog Installer, it creates the fog user and password and the rights it needs to allow tftp access to the storage node (itself). Once you tell the main "N"ormal Fog server what the IP, management username and password are, tftp FROM the main server TO the storage node should work. If you’d like some help, maybe we could do a join.me session or other remote support and I could look through your fog setup.

Check your networking equipment if you can. Try a different patch cable from the fog server to the switch. Try a different NIC in the fog server next.

For Fog to just stop working is quite unusual. Something may be getting changed in the background due to automatic security updates if you have that enabled. Also, if you are using Ubuntu 12.04, watch out for the tftpd-hpa service not starting after a reboot.

you may be able to chroot/fakeroot with the fog kernel and init.gz, but I am not experienced with that enough to tell you how.

The MBR on the target drive is overwritten with a clone of the MBR from the source computer via the imaging process.