New FOG server will not start the image upload
-
Question. Is what type of image are you trying, single disk resizable multiple part single disk or multiparty all disk.
-
single disk, multi part, non-resize
-
The correct directory is is /tftpboot/pxelinux.cfg/ the permissions should be checked for this directory. Also check the host for an appropriate OS assigned.
-
[quote=“Tom Elliott, post: 15994, member: 7271”]The correct directory is is /tftpboot/pxelinux.cfg/ the permissions should be checked for this directory. [/quote]
What should the permission be?
[quote=“Tom Elliott, post: 15994, member: 7271”]Also check the host for an appropriate OS assigned.[/quote]
Been checked, double checked, and triple checked. I will check it again. lol
-
Is this windows xp windows 7 or Linux.
-
Perms on tftpboot should be 755 fog.root on all.
-
chown fog:root -R /tftpboot; chmod 755 -R /tftpboot
Sorry about poor grammar and no code I’m on cellphone.
-
I have a Win7-64 box to my left and a Mint-13 box to my right.
-
Try running task with debug mode. This is different than booting into debug mode. I’ll explain when I get home on appropriate hardware.
-
Thx. The server is at the high school. More debugging will have to wait until Monday.
-
The reason why you need to create the task with debug is it enables the output of information within a viable task.
If you don’t, but boot into debug mode directly from the pxe menu, there is no task, therefore no OS ID sent to the system.
-
[quote=“Tom Elliott, post: 15998, member: 7271”]chown fog:root -R /tftpboot; chmod 755 -R /tftpboot [/quote]
FOR THE WIN!!!
Thanks.
-
Glad I could be of help.
-
Broken again. Now it will not start any task.
I was uploading and downloading fine when I tried to multicast. The multicast task did not launch (skipped straight to the FOG menu when booting). I made the changes found here in the troubleshooting section: [url]http://www.fogproject.org/wiki/index.php/Multicasting[/url]
then rebootedNow it will not launch any tasks at all. They appear in /tftpboot/pxelinux.cfg but the clients just boot straight to the FOG menu - even when you launch in Debug-Deploy
When you select Debug from the FOG menu we are back to the “Unable to determine operating system type” stuff.
-
For now, I’d say don’t do multicast jobs. Remove the area’s of the pxelinux.cfg/default file that you added and perform a test task. Then slowly work into multicast troubleshooting.
-
The reason running in debug gives you an “Unable to determine operating system type” message is because the task doesn’t exist. Although you do have the jobs, are the correlating with the proper MAC’s of the systems you’re trying to deploy the task to? With that, do they have the proper permissions? What I mean, is the files being created having the same permissions you placed on the directory. You can find out by performing :
[CODE]ls -l /tftpboot/pxeconfig.cfg[/CODE]This should show the permissions of the files. The first field will look something like:
[CODE][root@fogstorage ~]# ls -l /tftpboot/pxelinux.cfg
total 4
-rw-r–r-- 1 fog root 2908 Sep 2 13:03 default[/CODE]The -rw-r–r-- part is the actual permissions. The 1 is the number of links to the file in question. the fog root part is the owner and group.
My system states the default file is owner: fog group: root as we discussed earlier. It sounds like whatever is actually creating the tasks may not be giving ownership of the created tasks to fog:root as we did earlier.
When you did the install, did you install as root or another user?
Maybe try reinstalling the server to see if this will help you out at all.
-
prosigna@FOGMAN:/tftpboot$ ls -l /tftpboot/pxelinux.cfg
total 8
-rw-r–r-- 1 fog fog 427 Sep 16 13:24 01-44-37-e6-a9-a8-f2
-rwxr-xr-x 1 fog root 2356 Sep 16 13:16 default -
And:
44-37-e6-a9-a8-f2 is the correct MAC for the system you’re trying to deploy? When the system is booting from PXE, this is the MAC that shows?
-
This post is deleted! -
Yes, it even reacts to Wake-On-LAN.
