@Scott-Adams Latest trunk version is around 65xx. Maybe this has been addressed already? As hostname changes happen through the client I suppose it would be interesting to know which client version you use right now and which you have used back then?

@Tom-Elliott said:

Can you update to the latest and see if this is still happening?

Updating to 6549 seems to have worked, funny it didn’t ask me to update/upgrade the database, just went straight to login. But I’m deploying an image so I’m happy! Thank you!! I will try that first next time, just thought if it was working yesterday it should still be working if I didn’t make any changes.

Working great now after moving to the Trunk. I was pleasantly surprised with how well the upgrade process worked. All I had to do after the update was reconfigure some of my settings for dnsmasq and then I was up and running.

Thank you for your help @Wayne-Workman !

@boeleke In your screen shots, it looks like the Image Path and the FTP Path are backwards. Usually, the FTP Path contains the entire path, while the NFS Path starts in the exact shared NFS Folder.

-EDIT-
Just read that @ch3i solved it. Good job ch3i!

ok guys. first of all… tnx for the quick responses!

dont blame me. i rebooted the machine and tried once more… exactly the same… and it worked !!!

no clue, what happened… but tnx for your replies - u are quicker than a gunshot 😉

@Tom-Elliott The only issue I see is that what ever utility the OP has to change the bios boot order, it has to be a linux program. I know off the top of my head, dell and lenovo have windows/cmd base versions of these programs. If the FOS kernel was based on winpe, then there would be a higher chance a program would exist. I use the Dell Command and Configure to change the boot order with my bios update flash drive. So I know its possible at least with Dell business hardware.

I’m told by Tom that this is fixed, I assume it was a bug of some sort in the web GUI.

Hopefully image capture works now.

We have some brand-new Dell Optiplex 7040s in and after the update today they were just hanging on “Saving Partitions” although that might not be the exact message, this is just from memory. I really have no other clues than that… Will look into it further tomorrow though.

@Wayne-Workman Yeah I know, me either…its a SanDisk 64 GB…SDSSDP-064G. I’m assuming it’s one of their first models. We bought them close to 3 years ago.

Updated to ver 6525 before updating the image again.
This time around it worked flawlessly as it should.

@jquilli1 That’s because the inventory list is not associated with the same hosts any more.

We don’t export hosts with their originating ID’s as reimporting them to a new server could steal other Host’s id’s.

I’d venture to say a simple solution would be to just schedule the systems that don’t have inventory data to perform an inventory task.

yep it’s ok.

The problem was the nfs mount…via QNAP. FTP access was not right, it’s ok now.

@Tom-Elliott said:

@Tom-Elliott I’m more impressed that it hasn’t been noticed more often, but glad it was simple enough find and fix.

Thank you for your time.

@george1421 said:

@gwhitfield said:

I stopped being prompted for the IP address and I hope that’s a good thing, I’m pretty sure that happened when I changed the DHCP policies.

wiki hint: Under efi booting, if we are getting the ipxe kernel being delivered to the target computer but the ipxe kernel either doesn’t get the next server, boot file, or possibly an IP address we should dig into what architecture is being requested and what the dhcp server’s policy is configured to deliver. @Wayne-Workman

Added a note: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Step_3

This fixed it. Thanks again!

@george1421 /tftpboot/default.ipxe just points to the server where the boot.php web file is hosted.

the boot.php file dynamically generates a configuration for every host that queries it.

Also - apologies for editing your post. I’m half here today.

@fl0pp Synology NAS have different NFS and FTP paths. NFS starts in the exported directory, in your case that’s /images but the FTP path is likely /something/images

I’m not sure if this will solve your issue, but this is something you have to set on Synology NAS for them to work 100% correctly with transferring images from /dev to /images, for FTP Image Size, and for replication too probably

@Albertus At this time there is no defined release date for 1.3.0 stable. The developers are working hard to get the trunk version to the stable level.

The situation is the more people we can get into the trunk version to find the bugs, the quicker the bugs can be identified and resolved. If people not upgrade waiting for the stable release the longer it will take to find the bugs. So the best situation is to get as many people as possible into the trunk stream to identify issues faster. This will make the 1.3.0 release come faster too.

Understand when I say bugs, the trunk is not unstable today. There are many updates to fog per week as the code is fine tuned for best performance. So you will need to update your fog code frequently to take advantage of the performance improvements.

Great, thanks for your feedback! I will try your suggestions and will post the results here on the forum.

@Tom-Elliott I’m breaking my install with upgrade process 😞

I’ll try to fix and would do a new installation on a different server 🙂

@Tom-Elliott Installation worked, but I’m getting

Type: 2, File:/var/www/html/fog/lib/fog/fogftp.class.php, Line:104, Message: ftp_login():Login incorrect.

This is what I see for both nodes when going into log viewer.

I checked the .fogsettings file and password in GUI under storage mgmt with no luck.

UPDATE– Nevermind I forgot to change the password for the fog user as well.