@jonathanho92 said in Help in deleting image in fog server:

When i try to click delete they prompt me for credential i am not sure which credentials to key in to delete the image

That’s the same credentials you use to login to the FOG web UI. It’s just a safety thing to prevent people from deleting image files in a rush.

@jbandy Edit C:\Program Files (x86)\FOG\settings.json on the client machine. Then restart the service called “FOGService” or the computer.

@jbandy said in SSL Issue srvpublic.crt:

... "GET /fog/management/other/ssl/srvpublic.crt HTTP/1.1" 302 631 "-"

What we see in all those access log line is status code 302. So really, each and every request is not being answered directly but redirected.

Maybe this is something special Ubuntu is doing to push SSL/HTTPS forward? I am not sure. To try and see where this is coming from we need to start digging through the apache configs. First post the contents of the file /etc/apache2/sites-available/001-fog.conf here in the forums.

How do you change the url it’s using to communicate?

Edit C:\Program Files (x86)\FOG\settings.json on the client machine. Then restart the service called “FOGService” or the computer.

@george1421 said in iPXE iso vs iPXE FOG:

Something isn’t working as we know it should.

I’m going to try and find a second PC with the same motherboard to test with but currently, they are all in service.

@tom-elliott
@Sebastian-Roth

Thank you all. It is solved now in 1.5.9.78 with HTTPS on.

/var/log/apache2/other_vhosts_access.log

80 "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 302 599 443 "GET //fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111 443 "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111

/opt/fog/log/fogscheduler.log for Power Management Task

[04-29-21 6:16:25 am] * 1 task found. [04-29-21 6:16:25 am] * 0 scheduled task(s) to run. [04-29-21 6:16:25 am] * 1 power management task(s) to run. [04-29-21 6:16:25 am] * Power Management Task run time: Thu, 29 Apr 2021 06:16:00 +0000 [04-29-21 6:16:25 am] * This is a cron style task that should run at: 1619676960. [04-29-21 6:16:25 am] * Found a wake on lan task that should run. [04-29-21 6:16:25 am] | Task sent to fcaa-https

/opt/fog/log/fogscheduler.log for Scheduled Task:

[04-29-21 6:22:26 am] * 1 task found. [04-29-21 6:22:26 am] * 1 scheduled task(s) to run. [04-29-21 6:22:26 am] * 0 power management task(s) to run. [04-29-21 6:22:26 am] * Scheduled Task run time: Thu, 29 Apr 2021 06:22:00 +0000 [04-29-21 6:22:26 am] * This is a cron style task that should run at: 1619677320 [04-29-21 6:22:26 am] * Found a scheduled task that should run. [04-29-21 6:22:26 am] - Is a host based task. [04-29-21 6:22:26 am] - Unicaset task found! [04-29-21 6:22:26 am] - Host fcaa-https [04-29-21 6:22:26 am] - Task started for host fcaa-https!

Thank you again! Now our school can wake-up on Schedule

Peter

@tom-elliott So to clarify that last point Tom, the SQL should reflect under ngName both the Storage group name AND the Storage node name? DCSTORAGE in this case is the name of the Storage node master server for the Storage Group 3 storage group.

I’ve compared to the other image(s) which are only hosted on (and are being replicated from) the Master node and they only reflect the main storage group under ngName.

I’ve made note of the replicator service restart command, cheers. I went a bit neanderthal and just rebooted all my servers just now to see if that kicked things into life.

Checking the Image Replicator logs under FOG Configuration > Log Viewer it only references DCMASTER and the 2 nodes in its storage group. Does replication from the Storage master of the other storage group show in these logs? Or do we need to check local log files on the server itself?

cheers Tom

@sebastian-roth In the back of my mind I was knowing that its something at a lower layer … I am the only admin on this network so I dont know how it self destructed from 1 day to the next, might consider a windows update, but moving dhcp off windows would rule that out. Will try a pcap.

@londonfog said in Use http instead of tftp for fetching kernel and initrd:

and as long as directory above is in /var/www (ubuntu server here) it will work?

Yes. Your actual files will need to be in /var/www/os/ubuntu/20.04/casper/ If all you are doing is changing the protocol.

I agree that tftp over to a remote site will be painfully slow.

If your remote site has a web server available, it may be faster to host this iso locally at the remote site:
url=http://{fog-ip}/os/20.04/ubuntu-20.04.1-live-server-amd64.iso so you don’t have to copy that iso across your WAN link.

@george1421 said in dnsmasq won't start automatically. [SOLVED]:

@fog_newb Well there are really two commands you need to use.

Enable the service to start every reboot systemctl enable dnsmasq To start the service now systemctl start dnsmasq

These are two distinct actions and one doesn’t depend on the other.

@george1421

Thanks. I have used both of those commands before trying to get it to autostart on boot. I haven’t used them since running sudo systemctl enable dnsmasq , which was the one that got dnsmasq starting on boot for me. Perhaps since I used those commands prior it is all good?

I went through my bash history and saw I almost used sudo systemctl enable dnsmasq I had the syntax messed up though. I used sudo systemctl dnsmasq enable

I am really starting to like Linux. I digress, I am mostly a casual so I doubt I will ever have it on my daily driver but I am thinking about trying it on a laptop. I don’t know though, sometimes, I just like to point and click.

@londonfog Just wondering out loud but if that python script can hit the FOG API, and register that new host and then select image deploy when the target computer boots up for the first time and it pxe boots, it will boot right into imaging. So if you already have the image defined, then you would create one curl api call to register the new server’s name and mac address with fog, then a second curl api call to deploy your image.

ref: https://forums.fogproject.org/topic/11184/api-powershell-create-host-and-deploy-task-script

@stephane The directory listing and settings look fine. No idea why it shows “No such file or directory”. What kind of DHCP server do you use? Settings?

Can you please capture a packet dump and upload a PCAP to a fileshare and post link here? https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

@jcyrus_rti said in Unable to locate image store:

Did I do something out of sequence or something? Why would it create the directory with the mac address name instead of the unique name I listed in the directory?

When everything works as expected the capture goes to the MAC address named directory in /images/dev first. Then when the client sends the final ok to the FOG server it’s moved to /images and re-named. If that did not happen it’s likely the final step has failed. So I suggest you pay close attention to the last messages on the PC/VM’s screen when you capture next time.

@sebastian-roth Great job, the installation tests are looking beautiful today.

@sebastian-roth

It was just a hiccup. Running the installer again without git pull there weren’t any errors.

foginstall.log

Update!

So I upgraded to Ubuntu 18.04 which did not resolve the issue. I then updated FOG to 1.5.9.71 which must have been release today . After completing the FOG update, the services are running and I was able to successfully deploy 2 machines using multicast. I rebooted the server and verified that the services started after a reboot. Thanks for your help and working on this awesome software!

@robertkwild “better” is a relative term. I suggest following the command because we know it will do what it needs to do properly.

@d2freak82 said in Error on first PXE boot:

later popped an error that the drive was unclean on 2 different laptops

This is expected if you did not shutdown the computer properly before image capture. The shutdown command from the start menu is not sufficient.

You have the following options to properly power off the computer for image capture.

Run the following command from a command prompt shutdown -s -t 0 Use sysprep to power off the computer using the proper command line switch. Turn off fast startup in windows.

The kernel version I’m referencing is for FOS Linux (what get downloaded to the target computer), not the host OS kernel version. You can see the kernel version using the web ui FOG Configuration->Kernel update.

i have resolved this issue. I am not sure but when i was looking into ubuntu it did not update the images correctly. I moved them again and this time it was working correctly

i used FTP software , filezilla , to see the files where not on the ubuntu server but the gui was saying it was there .

@sebastian-roth
Yes, and yes.

Yes, that solved it. Thanks for the quick work, @Sebastian-Roth!
How do I mark a topic as Solved? Or is that a moderator-only task?