Client shows uploading but server says no image
-
I have a Debian 7.5 OS with fog 1.2.0, I have changed permission to /images for fog to 755 and /images/dev to 777. I am able to register the Client PC associated a image with it, and tasked it to upload it starts and goes through the upload process as shown in the attached photo. Also the management screen shows the size of the client disk but the size on server shows 0. When I open the images/dev folder there is one folder named f8bc12770f94 which is the MAC of the pc I upload the image from and 3 folders (assume for the 3 partitions on the image). I don’t think it is associating that with the image profile I created in image management. Thoughts questions, concerns. I am just getting back into Linux so be gentle please. Any help or suggestions are appreciated.[ATTACH=full]1206[/ATTACH][ATTACH=full]1207[/ATTACH][ATTACH=full]1208[/ATTACH]
[url=“/_imported_xf_attachments/1/1206_fog_image.png?:”]fog_image.png[/url][url=“/_imported_xf_attachments/1/1207_fog upload.jpg?:”]fog upload.jpg[/url][url=“/_imported_xf_attachments/1/1208_fog_image_folder.png?:”]fog_image_folder.png[/url]
-
You can copy that folder f8c12770f94 to your /images/ folder, you will then want to rename the folder to OP3020-base. Now if you chmod 0777 the images folder your image should be available and reporting the correct size.
To complete this action issue the following commands under the root terminal in Debian:
[code]
sudo mv /images/dev/f8c12770f94 /images/OP3020-base
sudo chmod -R 0777 /images
[/code]This will allow your image to be utilized.
I’m curious if using chown will allow you to image correctly. Debian is a bit more secure than is Ubuntu counterpart, we may need to tweak the permissions. I am also curious if after running the commands I listed above if it does not solve your issue, please try a test image upload and let me know if it gets stuck in the dev folder again!
-
/images in it’s entirety always should be 777, unless you give full ownership to the user fog.
Otherwise, the normal owner is root:root. So 777 allows any user, should you need it, to work properly. 755 means it’s rwx for the Owner (7) and rw- for both group and “other” (5). As the fog command has to execute commands to the directory, the copy task can’t occur because execution is not allowed.
-
Well moving and renaming it worked for one pc to image, I have multiple models of Dell optiplex 3010, 3020, and latitudes E5510, E5520, E5530. not all of them see the TFTP in order to get download the image or upload an image. Not sure if it would be a Kernel issue that I will have to get fixed before the imaging issue will work. Love it when issues compound on each other…
-
if some can reach the tftp and others can’t, it’s almost certainly a network issue
-
it was working fine with 0.32/ubuntu 12.04 and my older optiplex’s ie. 755, 780, 3010’s I upgraded due to the 3020 and E5540’s would just give me a black screen when trying to register or image. I haven’t touched me network yet.
-
I also found that the windows 7 desktops (some not all didn’t have the tftp feature installed)
-
no tftp software needs to be loaded on the windows desktops
the network card rom loads the network boot file by tftp before windows loads -
tanks Junk that is good to know, I tried to upload another image like Driver had asked and the PC is flashing this error at me. The PC was able to register just fine. Would you like me to start a different thread for this?
[ATTACH=full]1219[/ATTACH]
[url=“/_imported_xf_attachments/1/1219_fog upload error.jpg?:”]fog upload error.jpg[/url]
-
Why is your bzImage labeled as: DEFAULT
-
that is an excellent question…I don’t know, what should it be? Sorry if I seem a bit “blonde”, been a bad sys admin day. I don’t have any images labeled default, the only thing I have labeled/listed "default is the Storage Group
-
If you can change it to bzImage, and see if you get better luck. it sounds to me like it’s loading file names it can’t find, which would explain the error you’re seeing.
-
Location of the filenames to make sure are set properly:
FOG Configuration->FOG Settings->TFTP Server->FOG_TFTP_PXE_KERNEL (this should be bzImage)
FOG Configuration->FOG Settings->TFTP Server->FOG_TFTP_PXE_KERNEL_32 (this should be bzImage32)
FOG Configuration->FOG Settings->TFTP Server->FOG_PXE_BOOT_IMAGE (this should be init.xz)
FOG Configuration->FOG Settings->TFTP Server->FOG_PXE_BOOT_IMAGE_32 (this should be init_32.xz) -
[B]This is what I see when I go to /tftpboot basically the same when I go to /var/www/fog/service/ipxe.[/B]
e [ATTACH=full]1220[/ATTACH]
[B]Also what my FOG setting looks like.[/B]
[ATTACH=full]1221[/ATTACH]
FYI, I love this software, and haven’t really had to touch it for a couple years.[url=“/_imported_xf_attachments/1/1220_bzimage.png?:”]bzimage.png[/url][url=“/_imported_xf_attachments/1/1221_fog_setting.png?:”]fog_setting.png[/url]
-
if you see the same files in /tftpboot and /var/www/fog/service/ipxe
then you have problems -
I am sorry, like I said yesterday was a bad day to be the net/sys admin. Below it what the ipxe folder looks like.
[ATTACH=full]1225[/ATTACH][url=“/_imported_xf_attachments/1/1225_ipxe.png?:”]ipxe.png[/url]
-
what do the permissions look like on those files?
-
[ATTACH=full]1226[/ATTACH]
[url=“/_imported_xf_attachments/1/1226_ipxe_permission.png?:”]ipxe_permission.png[/url]
-
What if you run LS – L a
-
what do you see if you go to this address [url]http://172.25.0.99/fog/service/ipxe/boot.php?mac=<mac[/url] address of the computer you’re trying to image>&arch=x86_64
