@Sebastian-Roth the installer will not run without internet connectivity. It hangs on the line adding repository, I think. I’ve left it for 30 minutes with no change.

This behavior is new, because I’ve always deleted the .fogsettings file and rerun the installer to change the ip.

Outside the settings in the web ui I had to manually change the ip set in the tftpboot folder.

@dinagaran7007 Please open a new topic and post all your details there: FOG version, install error log, …

@Sebastian-Roth There were still some duplicated MACs on my network removed then from the database and it worked, this issue was caused by myself, there were some pending macs to aprove and I didn’t paid attention to then and approved then all, but lots of them were from Virtual machines.

@IdahoTech said in Updated Ubuntu and now cannot get to fog gui:

So let me ask this to all who answered do you have a password on your sql? Seems to be a problem with ‘no password’ mysql installations…

Just as an FYI, this issue is being addressed in the soon to be released FOG version 1.5.8. In 1.5.8 there will be tighter controls on the database side. The downside is that the FOG admin will need to remember the root password for mysql since it won’t be recorded anywhere in FOG. FOG shouldn’t need the root user’s password for mysql except the first time FOG is installed, it need’s root’s password to setup the FOG database. After that there is a foguser created that interacts with the FOG database even during upgrades.

@FuriousGamer065 You probably should run through the tutorial to ensure that all of the bits are in the right spot and then rerun the fog installer.

Understand this will only address the ftp issue. There still may be the issue related to unable to find the storage node. That’s on the NFS site of the image upload.

@george1421 thanks for the info I’ll get that done Monday and I’ll left you know what we find

@Schuede said in Xps15 Fail to deploy image - Ipxe / Uefi:

listen-address=127.0.0.1

Sebastian, good point I skipped right over that. In this case that command is telling dnsmasq to bind to the loopback interface. So only DHCP DISCOVERS on the loopback interface would get a response. Probably not what the OP wants. While that’s not the issue in the picture it would be the cause of the other issues reported.

@DeRo93

I’m curious, what drives are inside your HP 840 G6s? We currently have the same laptop at my company, but our drives included in our G6 are Western Digital PC SN520 NVMe SSD. I know there is a configuration with OPAL drives (so they are already encrypted by default)

Hi,

Thanks george1421. The second storage node was running 1.5.6. As it is still in a test environment, I completely rebuilt it from scratch. All working fine now.

Yes, the remote storage node is a full FOG server, so I will export / import the metadata.

Thanks again 🙂

@kmonroe79 said in Starting cmain( )...:

This now brings my screen to black with flashing cursor 😞 I can’t seem to find a happy balance

Using which settings exactly??

@kburns Yes, George is probably right. Take a look at /tftpboot/default.ipxe text file and put in the correct IP. It’s important you read this wiki artikle: https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address

@cammykool It can do remote execution, printer management, power management, login recording, and other things. I’ve used it to run scripts, deploy software, and other things. Check out these wiki articles below, they might help you understand the capabilities.

There’s also a ton of stuff on the forums about printer management. Here is one with some detail: https://forums.fogproject.org/topic/8051/printer-deployment?page=1 though there’s probably hundreds of topics about printers.

Updated the URL in the official code (ref).

@ITCC Switch your DHCP config to point to ipxe.pxe instead of undionly.kpxe and the issue should go away.

@george1421
Changing the settings in the default.ipxe file worked! Man this community is great! I’m going to update my documentation to make note of this so in the event we move subnets again we can tackle this same day!

@doubleve You only need tftp if you want to boot from the nas. If you have a real fog server on the same network you can use that. For a storage node you only need NFS and FTP service.

thanks, i figure up what’s the problem, i’ve add corrupted lines on /etc/fstab.
thanks for everything.
everything is working now.
🙂

@Beyondlimitation said in PXE Client tries to find wrong file:

By the way, if i copy “undionly.kpxe”, paste it in directory “/tftpboot” and rename it to “undionly.kpxe.0”
pxe boot successfully works

While I see you have it sorted out, requiring the boot file to end in a “.0” was a requirement of DNSMASQ before 2.76 (as well as syslinux). With 2.76 and later its just the file name. The “.0” requirement was removed since that is a bios related thing. What version of dnsmasq are you running (i.e. dnsmasq -v)

@kwisher Well life may be better on the dev branch. Why I asked if you were on 1.5.7.55 or later, stay there. FOG 1.5.8 is almost release. 1.5.7 had a few bugs where 1.5.7.55+ in the dev branch fixed.

@Spicoli Thanks! RAID to AHCI worked for me.