Image won't deploy
-
so your <imagename> is changed to be that of your actual image name? And the path in the image is not literally <imagename>?
-
I know you have to ask that, Tom.
Yes, the path in the WebUI and the actual filesystem path now match, letter for letter, as /images/MyImage. Capitalization verified. Do I need a .mntcheck file in that directory? Right now,m the only things in the image directory are the sys.img.000 (big file) and d1.mbr (tiny file).
-
Being kicked out of my office for the evening. Will take whaqt ever steps you suggest in the morning.
-
Tom? Junkhacker? Anyone? What next?
-
Bruce,
I have no problems helping you out, but I have other things that need being done as well. I try to help out as quickly as I can, but I donāt know every particular scenario to play out.
My questions arenāt to belittle or keep you at bay.
If youāre certain the imagepath is absolutely correct, and the server ftp settings (username and password) are correct within the storage node. Then I donāt know where to begin with troubleshooting anymore.
-
Hi everybody.
Iām sorry for the UP but i have exactly the same problem : after the upload, i connect to the NAS by FTP and i move the files into ā¦/fogimages/dev/@MAC to ā¦/fogimages/āfolder named in FOG interfaceā.
After that, the download task works with Linux Mint, Windows XP ā¦ but with Windows 7, i have this error message :
[QUOTE]Dowload task failed for Computer-xxx with image Computer_win7-test. To setup download task, you must first upload an image[/QUOTE]
I donāt understand why this error only appear with the Seven OS ā¦
Basic informations :
FOG Version : 1.1.1 on Debian 7
OS Client : Windows 7 PRO. -
[quote=āJonathan Cool, post: 35859, member: 24834ā]Hi everybody.
Iām sorry for the UP but i have exactly the same problem : after the upload, i connect to the NAS by FTP and i move the files into ā¦/fogimages/dev/@MAC to ā¦/fogimages/āfolder named in FOG interfaceā.
After that, the download task works with Linux Mint, Windows XP ā¦ but with Windows 7, i have this error message :I donāt understand why this error only appear with the Seven OS ā¦
Basic informations :
FOG Version : 1.1.1 on Debian 7
OS Client : Windows 7 PRO.[/quote]FOG didnāt created the directory and didnāt moved the files from the dev into the image folder. I had this problem, too and had no success in fixing that.
Installed a new Ubuntu 14.04 system with last revision 2230. I had to restart the system and the mysql service, before I could start testing.
Did a few tests with upload and deploy and everything works fine. I tried then to use a image from the older fog server and copied into the created folder, added a image definition and tried to deploy that image. but that fails with the same error:
[CODE]Dowload task failed for Computer-xxx with image Computer_win7-test. To setup download task, you must first upload an image[/CODE]@Tom.Elliott
Is there is a new setting in the fog database, that will be set trough an upload process? And If that setting is not valid a image from the older fog server will not deploy?Trying now this on my new system and try to find which setting I have to change, that I can use my old images on my new fog server.
regards,
Albatros -
It sounds, to me, more that because youāre moving the image from another system, that the permissions are the issue. You could verify by setting the copied over image permissions to be owned by fog:root:
[code]sudo chown -R fog:root /images/<imagename>[/code] -
[quote=āTom Elliott, post: 35900, member: 7271ā]It sounds, to me, more that because youāre moving the image from another system, that the permissions are the issue. You could verify by setting the copied over image permissions to be owned by fog:root:
[code]sudo chown -R fog:root /images/<imagename>[/code][/quote]Should have mention that, sorry. Yes I checked the permission and they are fine.
Edit: Okay. Tested it again, now it shows the size of the image and I can create a download test. Will test a few images. Ty Tom.
Edit 2: The deploy of images works fine now on my side, but the upload not correctly. The upload of every partition runs twice o_O
-
Any idea why the upload process for every partition runs twice?
-
[quote=āAlbatros, post: 35898, member: 16710ā]
Did a few tests with upload and deploy and everything works fine[/quote]
Hi Albatros.
iām going crazy ā¦ now, i can- upload a windows 7 image of an Optiplex 7010 (optiplex7010-master).
- download the image sucessfully on the Optiplex 7010.
but ā¦ if i add an other Optiplex 7010 and i choose a dowload task with the optiplex7010-master image, i have the message ādownload task failed ā¦ā.
Can you describe your few tests ?
I think itās a permission issue but why the permissions are not good if the computer is not the master of image ?
[U]Edit[/U] :
i donāt understand anymore ā¦ none of download tasks work ā¦
if a try a donwload task on the optiplex7010 master, i have the error message.
if a try a download task on a other optiplex7010, i have the error message.
if a try a dowload task with other computer (and an other image), i have the error message ā¦ -
[quote=āAlbatros, post: 35912, member: 16710ā]Any idea why the upload process for every partition runs twice?[/quote]
I didnāt know they were running twice.
-
[quote=āJonathan Cool, post: 35940, member: 24834ā]Hi Albatros.
iām going crazy ā¦ now, i can- upload a windows 7 image of an Optiplex 7010 (optiplex7010-master).
- download the image sucessfully on the Optiplex 7010.
but ā¦ if i add an other Optiplex 7010 and i choose a dowload task with the optiplex7010-master image, i have the message ādownload task failed ā¦ā.
Can you describe your few tests ?
I think itās a permission issue but why the permissions are not good if the computer is not the master of image ?
[U]Edit[/U] :
i donāt understand anymore ā¦ none of download tasks work ā¦
if a try a donwload task on the optiplex7010 master, i have the error message.
if a try a download task on a other optiplex7010, i have the error message.
if a try a dowload task with other computer (and an other image), i have the error message ā¦[/quote]Iām not fully understanding.
If you upload the image, then deploy the image to the same machine all works?
If you register another system (7010) and assign the image, schedule deploy, it says it canāt start?
-
[quote=āTom Elliott, post: 35946, member: 7271ā]Iām not fully understanding.
If you upload the image, then deploy the image to the same machine all works?
If you register another system (7010) and assign the image, schedule deploy, it says it canāt start?[/quote]
In fact, download tasks do not works for Windows 7 OS ā¦
For Linux and Windows XP OS, download tasks work but not with Windows 7.
-
ātasks do not worksā gives us no useful information to troubleshoot why this isnāt working for you.
i have deployed hundreds of windows 7 images, many on dell optiplex 7010 computers -
Iām sorry, i will try to give more informations ā¦ :
First :
/var/log/foginstall : [url]http://pastebin.com/uRiN9x3c[/url]
/var/log/apache2/error.log :
[CODE][Thu Sep 04 15:37:00 2014] [error] [client 10.44.xx.xxx] PHP Warning: mysqli::query(): Couldnāt fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 89, referer: http://10.44.xx.xx/fog/management/index.php?node=tasks
[Thu Sep 04 15:37:00 2014] [error] [client 10.44.xx.xxx] PHP Warning: MySQL::sqlerror(): Couldnāt fetch mysqli in /var/www/fog/lib/db/MySQL.class.php on line 180, referer: http://10.44.xx.xx/fog/management/index.php?node=tasks[/CODE]Storage used to stock the images : NAS Buffalo LinkStation Dui (with full root ssh access): 10.44.xx.xxx:/mnt/array1/images
(i can mount the NFS share /images with a debug download task)- I can upload an Win7 image to the NAS
- I have to move the image files to ā¦/images/dev/@MAC to ā¦/images/<image name>
- I have checked the image path
- I have checked the image and OS type in FOG : Windows 7 and Single Partition Resizable
- I have chmoded 777 -R /mnt/array1/images on the Buffalo NAS
- I have chowned -R fog:root /mnt/array/images on the Buffalo NAS
- I have checked FTP password.
I think, iām not so far ā¦
An idea ?
If you want more information, tell me ! (sorry for my english, iām a french user) -
Some of the issue youāre seeing Jonathan: As I finally had a minute to read through some of the posts in this thread. Your issue is not āexactlyā the same as the contents of this particular thread unless Both Albatros and Bruce are having the same issue with the upload not working due to them having NAS stations to work with.
There are some known limitations using external NAS systems to perform the image upload. First is that it seams NASās donāt like to use direct path FTP systems. The FTP system, when connected, links you to a specified Home folder of the user logging in. So the local FOG user on your NAS machine might have a default home location of:
/array1/images Where your actual path connects through /mnt/array1/images.Why is this an issue?
Because when FOG attempts to FTP the contents of the folder from: /mnt/array1/images/dev, the actual path doesnāt exist during the FTP process on the LAN.
So when it tries to FTP the file from:
/mnt/array1/images/dev/<macfoldername> /mnt/array1/images/<imagepathname> Things āsucceedā as neither folder or path technically exist according to the FTP. Itās all too easy to rename/move folders that donāt exist in the linux world. It simply fails successfully which makes fog think itās succeeded in general. This would explain why youāre not seeing any issues in the imaging process and the task appears to complete perfectly fine.In the NASās eyeās, when FTP connects, /mnt/ doesnāt even exist. And seeing as /mnt/array1/images is being called, nothing can actually happen.
How to fix? I havenāt yet figured out a nice method. You would probably have more luck if you looked up the NASās FTP functions to find out how to keep FTP from jailing you to a specified Home folder. NFS works perfectly, but FTP fails miserably. I donāt know how else to explain it.
-
This post is deleted! -
Wow ā¦ many thankās for the answer. I think i understand what happen ā¦ tell me if iām right :
- for the upload task, itās the NFS protocol who is used : no problem with path, direct path ā¦
- for the download task, itās the FTP protocol who is used ā¦ :
ā> when I connect to the server by FTP (with traditionnal client like fileZilla), i see /array1/images
ā> when I connect to the server by SSH, i see [B]/mnt/[/B]array1/images
ā> when I declare the NAS into the Storage Management of WebIU, i need to write the full path, /mnt/array1/images
but ā¦
ā> when FOG run a download task, itās used the fog user on the NAS and seen only /array1/images ā¦ and itās fail.
Itās right ?
If itās right, i have some ideas :
- used /mnt/array1/images into the FOG Storage Management for upload task
- move by a classic client ftp to the right folder (/array1/dev/@MAC --> /array1/<image_name>
- Change the NAS declaration to /array1/images
- try a Download Task on clients ā¦
Itās not very clean but maybe it will work ā¦
-
[quote=āJonathan Cool, post: 36302, member: 24834ā]Wow ā¦ many thankās for the answer. I think i understand what happen ā¦ tell me if iām right :
- for the upload task, itās the NFS protocol who is used : no problem with path, direct path ā¦
- for the download task, itās the FTP protocol who is used ā¦ :
ā> when I connect to the server by FTP (with traditionnal client like fileZilla), i see /array1/images
ā> when I connect to the server by SSH, i see [B]/mnt/[/B]array1/images
ā> when I declare the NAS into the Storage Management of WebIU, i need to write the full path, /mnt/array1/images
but ā¦
ā> when FOG run a download task, itās used the fog user on the NAS and seen only /array1/images ā¦ and itās fail.
Itās right ?
If itās right, i have some ideas :
- used /mnt/array1/images into the FOG Storage Management for upload task
- move by a classic client ftp to the right folder (/array1/dev/@MAC --> /array1/<image_name>
- Change the NAS declaration to /array1/images
- try a Download Task on clients ā¦
Itās not very clean but maybe it will work ā¦[/quote]
Sort of.
Creating a download task is failing to me trying to help make FOG a slight bit more friendly.
Itās not failing because of the NFS/FTP share directly on the creation of a download task, but rather because the FTP call to check if the folder exists isnāt linking to the proper folder.
