Hi Bryce,

Thanks for the response. I spoke with the programmer and he did not make any updates to the database. We are going to look into what tables and fields need to be updated.

Thanks.

Hi Bryce,
We have a program that uses FOG to re-image 2 machines at its completion. I ran that program yesterday and did a tail -f on our apache error_log. Nothing appeared in the apache error_log while that program ran. The following 2 entries were placed in our apache error_log about 25 minutes before I ran the program:
[Thu Jul 25 10:04:01 2013] [error] [client xx.xx.xx.xx] PHP Notice: Undefined variable: Proxy in /var/www/fog/commons/functions.include.php on line 3506, referer: [url]http://ourComputer.com/fog/management/index.php?node=logout[/url]
[Thu Jul 25 10:04:02 2013] [error] [client xx.xx.xx.xx] PHP Notice: Undefined variable: Proxy in /var/www/fog/commons/functions.include.php on line 3506, referer: [url]http://ourComputer.com/fog/management/index.php?node=logout[/url]
NOTE: I changed the IP Address to xx.xx.xx.xx and I changed the beginning of the URL to ourComputer.com

(1) I don’t believe these errors tell us why the machines can’t be imaged but I am listing them here since they did show up in the apache error_log

I noticed that if I log into FOG’s GUI and deploy images to our 2 machines that they are imaged with no issue. However, when our program runs and initiates the imaging, the machines do not get imaged. Instead, they both say “No job found for MAC address xx:xx:xx”. I then have to go into /tftpboot/pxelinux.cfg/, delete the 2 config files and then go into the FOG GUI and manually deploy the images to the 2 machines.

When I manually run the re-imaging from FOG’s GUI, it placed the 2 config files for the 2 machines being imaged into /tftpboot/pxelinux.cfg/. Those 2 config files each have the following ownership: fog:fog. The have the following permissions on them: 644

When we run the program, it placed the 2 config files for the 2 machines being imaged into /tftpboot/pxelinux.cfg/. Those 2 config files each have the following ownership: root:root. They also have the following permissions on them: 644.

I pointed out to the programmer that we should make the ownership of the 2 config files fog:fog. The programmer ended up changing the program so that the permissions were 777. The program still has the ownership as root:root.

I ran the modified program but still got the “No job found for MAC address xx:xx:xx” error message on the 2 machines that FOG is supposed to re-image. I looked in /tftpboot/pxelinux.cfg/ and saw that the permissions for both config files were 777 and the ownership was still root:root.

I believe that if this were an ownership / permissions problem that changing the permissions to 777 should have resolved that issue.
(2) Do you think changing the ownership of the config files from root:root to fog:fog could still resolve our issue?

(3) Do you have any other ideas what could be causing this issue?

Thanks.

Hi Bryce,
I will use FOG Server tomorrow to re-image my machines and will do a tail -f on the apache error log to see what comes up. I’ll let you know what I find. Thanks.

Hi Bryce,

Thanks for replying. My first thought is that it may be a permissions issue as well. So, I ran chmod -R 777 /tftpboot/ yesterday but still have the same problem. I looked at the ownership for both /tftpboot and /tftpboot/pxelinux.cfg/ is fog:root.

Where can I find the log files for FOG? I saw “Log Viewer” in the GUI but they didn’t seem to be of much value.

Thanks.

[quote=“BryceZ, post: 10155, member: 2”]It seems like the boot files for those MAC addresses never got cleaned up. You’ll need to browse to /tftpboot/pxelinux.cfg/ on your FOG server and delete the files named 01-<MAC Address> with the MAC addresses of the netbooks that you’re having problems with.[/quote]

Hi Bryce,

I am running into this same issue. I have FOG version 0.32 installed on a 64-bit Ubuntu 12.04 machine. Is there some reason that FOG is not deleting the config files in /tftpboot/pxelinux.cfg/? Is it a known bug in FOG?

Hi,

I am pretty new to FOG. I am using FOG version 0.32 installed on a 64-bit Ubuntu 12.04 machine. It seems like I am constantly having to delete the boot files in /tftpboot/pxelinux.cfg for the 2 machines that FOG is currently controlling. If I don’t, I will get the following error on these machines: ““No job found for MAC address xx:xx:xx”
If I go into FOG and try to deploy a new image, it will give me the following error message:
“None of the machines were able to be queued!”
“[machine1] Unable to upload file.”

1. Is there a bug in FOG that is causing the boot file to not be deleted from /tftpboot/pxelinux.cfg by FOG?

2. If there isn’t a bug, what can I do to resolve this issue?

Thanks.

Hi All,

I ended up blowing away the VM that had FOG on it. I then installed a new VM and re-installed FOG Server. I haven’t done the imaging yet with FOG but I don’t expect to have this same problem as I specified the correct IP Address during the initial installation.

Hi CVernon,

Thanks for replying. I just checked that file and it only has the new / correct IP Address in it and does not have the old IP Address in it.

Do you know any other config files for FOG that could contain the old IP Address?

Thanks again.

Hi All,

I am new to FOG. I setup my FOG server on an Ubuntu 12.04 VM (using 0.32 version) and was trying to image my first machine (a Windows 7 machine VM).

I ran the FOG Prep as administrator on the Windows 7 VM. I then rebooted the Windows 7 VM. The imaging job started but died with this error:

*Preparing to send image file to server.
*Mounting File System…mount: RPC: Remote system error -
Network is unreachable.
mount: mounting xx.xx.xxx:/images/dev/ on /images failed: Bad file descriptor
Done

A few things to note:

1. I changed the numbers in the IP Address to x’s.
2. I can reach my FOG server from both the address listed in the error above as well through a different IP Address. The other IP Address, I purposely put in as the IP Address for the FOG server. I did this by logging into the FOG GUI and going to “Other Information” -> “FOG Settings”.
   I put that other IP Address in the following fields:
   a) FOG_WOL_HOST
   b) FOG_TFTP_HOST
   c) FOG_PXE_IMAGE_DNSADDRESS
   d) FOG_WEB_HOST

I also have that other IP Address listed for both “next-server” and “domain name servers” in /etc/dhcp/dhcpd.conf on the FOG VM.
3) I can log into my FOG server by putting both the original IP Address (which is the IP Address noted in the error above) and the new IP Address (which is is the IP Address I changed the FOG Server to in the GUI and in /etc/dhcp/dhcpd.conf.

#3 above tells me that the old address is still listed in one or more config files. Does anyone know exactly which config files I need to change in order to completely change the IP Address of the FOG Server? Until I can do that, it appears I won’t be able to use FOG to image any machines.

Thanks.

Thanks for your help