No Job found for MAC address
-
I’ve just started getting into using FOG and have already multicast and performed individual deployment on 200+ netbooks and desktop units.
Last week I tried to multicast approx 26 netbooks. 3 of them failed to cast and everytime I turn them on, they try to find the task and then give me the message “No job found for MAC address xx:xx:xx” It doesnt appear there is any other screen I can get to at this point.
Any suggestions greatly appreciated.
-
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=“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?
-
Are you getting any error messages after successfully deploying an image? What are the file permissions on /tftpboot/pxelinux.cfg/ and the files inside?
I’ve encountered this issue a few times, and it seems like it’s generally due to the web server or FTP server being unavailable when the task completes. However, I’ve never had time to dig into the cause of their unavailability when it happens, so it’s hard to be sure. There was at least one time that I came across this where tasks had been created and then the ftp user account had it’s password changed but not updated in FOG. There was also a time when permissions on the directory were modified so that root was the only user allowed to modify files.
I’ve never found any systemic issues with FOG that would indicate a bug, but I’ve found plenty of these little scenarios where for one reason or another the files are created but not deleted. If this is a consistent issue that is easily reproducible then I’d be very curious about your configs/permissions.
-
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.
-
Apart from the logs in the log viewer there are no central “FOG logs”; this issue would most likely appear in either your apache logs or your vsftpd logs, so I would check you configs on those two services to make sure they are logging properly, and then start digging.
-
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,
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.
-
OK, so you have another program creating the FOG tasks? If that’s the case then it sounds like it’s creating the files just fine but the database entries aren’t being added for the tasks.
-
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.