@cjesso Very interesting, what we posted was the exact cause of that check in message on the client.
Have you attempted again to pxe boot since you updated to 1.4.2?
@cjesso Very interesting, what we posted was the exact cause of that check in message on the client.
Have you attempted again to pxe boot since you updated to 1.4.2?
Lets focus on Centos 7.
I just setup a Centos 7 system last friday starting at DVD and it worked just fine.
Have you updated centos 7 to the latest updates?
Have you set selinux to permissive and disabled the firewalld service?
@cjesso So right now FOG_WEB_ROOT == /fog/
Did you do a fresh install of fog 1.4.1 or was it upgraded to 1.4.1?
@cjesso Its under here. FOG Configuration Page->FOG Settings->General Settings
Goto FOG settings page, and select Expand all
Then search for FOG_WEB_ROOT
on the web page.
@george1421 ok, I am on 1.4.2 now (just updated it)
Still a bug, you need to fix what Tom posted. There was an issue setting up the database that will cause the checkin issue.
As for posting images. I use firefox and just drag and drop the images from my desktop to the FOG editor.
So the first set of errors says: ERROR parsing subspaces from PCCT
Then UDHCPC: sending discover, no lease failing, Failed to get an IP via DHCP, check setup and try again.
Does the network switch where this target computer is connected, have spanning tree turned on and its not using one of the fast spanning tree protocols?
@cjesso OK you have 2 issues here. One is a bug in 1.4.1 and the second we will focus on in a minute.
@cjesso OK, I’m not so good with mind reading.
But since you have win10 installed, its probably a uefi system.
But based on what you just posted, it could be in bios mode. UEFI pxe bot should say something about a NBF file. Look in the “bios” and see if there is a software switch to change between bios (legacy) and uefi mode. Don’t change it only inspect the setting. Also if it IS in uefi mode, disable secure boot. FOG will not boot if secure boot is enabled.
As I posted before a screen shot of the error would really help.
If you use a second target computer do you get the same results?
We have see target computer with bad hard drives cause the imaging to fail.
Also if you get an error message on the target computer, please snap a clear picture of it with a mobile and post it here. The context of the error is almost as important as the error itself.
For dhcp option 66 should be the IP address of your fog server.
dhcp option 67 should be undionly.kpxe for bios (legacy) clients and ipxe.efi for uefi clients. For now pick one firmware format and load the right driver. Once you get comfortable with fog we can talk about other solutions to dynamically load the right iPXE kernel.
And just for reference you SHALL NOT use pxelinux.0. We will know if you do.
@Avaryan Now that you know your password attempt to log into your database from the linux command line mysql -u root -p fog
then provide your database password.
Its not possible to capture an image live like that. FOG uses a customized linux image that is deployed to the target computer over the network. You have to stop and properly close the image before it can be cloned. This is the same case for tools like clonezilla and to a lesser extent Symantec ghost. The target OS must be powered off.
@george1421 Next steps: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
But for you I want you to use this filter: tcpdump -w output.pcap port 67 or port 68 or port 69 or port 4011 or port 80
capture the pcap file and upload it here. I want to find out exactly what the client is being told to do. I feel you have something in your business environment that is causing strange reactions from the client.
@george1421 Never mind we already did this down below in the thread.
@maciej12203 Sorry i read too many threads to remember where we are in each one.
I remember this now your FOG server is rejecting the http request.
two things come to mind
I would test from a windows browser see if you can connect to http://192.168.4.70/fog/service/ipxe/boot.php
I’m interested in if anything is returned.
@Sequans said in Wrong current version after upgrade to 1.4.2:
You are not running the most current version of FOG!
Are you seeing this in the FOG configuration page?
@maciej12203 OK now we have something we can work with.
Since your have an existing dhcp server you do not want to run a FOG dhcp server because you will get conflicts.
If you can not modify the dhcp server configuration or request that the configuration can be changed we still have a way to make this work. On your fog server DO NOT enable the dhcp server, that will only cause you a head ache with the clients.
Since your FOG server and pxe booting clients are on the same subnet we will use dnsmasq to provide ProxyDHCP information for your location. The ProxyDHCP will supply the missing information that your main dhcp server can not provide. This ProxyDHCP server will supply the boot file and pxe booting server information to your clients.
Understand that running a ProxyDHCP server is a last choice option. The best solution is to get your dhcp server configured properly. I understand there are conditions where you can not do this, that is why FOG supports ProxyDHCP (dnsmasq) configurations.
@maciej12203 Lets take a step back here.
Does your network have an existing dhcp server?
If so are you allowed to make adjustments to this dhcp server?
Is your FOG server on a different subnet than your pxe booting client computers?
@Avaryan said in Windows 7 client reboot continuosly after task launched:
Also, why FOG 1.3.5 if it’s a brand new installation?
There is also a bug in 1.3.5 that was addressed in 1.4.0RC1 that fixes single disk. Upgrading to the current release of FOG 1.4.2 is probably a good choice here. This may not address your issue. But once you are on the latest release we can discuss more specifics. If we need to get the developers involved they will require you to be on the latest release anyway.
What computer (mfg and model) are you trying to pxe boot that is stuck in this reboot loop?