Image hosting on NFS server, process uncompleted?

[arnaudrigole]

Hi @george1421

Oh ok so i think you’re right; but

You wanna say FTP or TFTP?
I don’t see any “ftp configuration” in the fog web gui ?

i set the same password on
fog tftp user,
fog unix user ,
fog filezilla server user,
fog management username on storage node,

still don’t work

[george1421]

No its the ftp password. Maybe I’m thinking of the older version of the trunk under fog configurations. Please look instead under the storage node configuration for the ftp password. I know its there and it IS the ftp user. Sorry its early here and I haven’t quite finished my first cup of coffee.

[arnaudrigole]

@george1421
Ahah, no problem.
I run version 1.2 of FOG, and there is the node configuration:

The “management username” and “management password” are the same as the filezilla user.

Look at what’s displayed on filezilla , it can’t copy files because the script looks can’t create the directory in /images :

I verified the rights on fog ftp user, it has full RW rights (+create directories), i tested to create a directory in /images with filezilla, logged with “fog” user and it worked…

Do you think the problem could come with the fog script?
for the test, i created manually the directory in /images and launched another upload task, actually loading, we will see … !

[arnaudrigole]

The transfer of *.img files doesn’t work after i’ve manually created the correspondant /images directory

[george1421]

@arnaudrigole Hmmm interesting.

The images are created in the /images/dev folder but not moved. You should not have to pre-create the directory in /images for the target upload.

What are your linux permissions on the /images directory? Are they 777 or something else? Right, wrong, or otherwise, on my production server I have images set to 777. Not sure if the installer script did that or I did when I relocated the actual image files.

You said you are running 1.2.0, is this a fresh install? If so, I wonder why you are not using the trunk version to get better hardware and win10 support?

[Sebastian Roth]

@arnaudrigole The image name in the logs is looking a bit weird. Is it really named P7510Win7prox64CAOEXT?

Run ls -al /images/ | grep P7510Win7 on your FOG server and show us the output.

[arnaudrigole]

@george1421
the permissions on /images are set to full RW rights to “anonymous” and “everyone” (Windows NFS server)

This is a fresh install in production in my company, can’t use trunk now, need to test it and i’ve already encountered other issues with it, actually i need to make a stable environment to simply upload/deploy images with unicast&multicast

@Sebastian-Roth
Nothing returned by the cmd, because the img is not stored on the local fog server, this is an external NFS storage i created on a Windows server 2008r2 :

[george1421]

@arnaudrigole You may need to explain how you have this setup because you configuration is surely not standard.

Is the 2008 server setup as a storage node, or do you have the fog server NFS mounting the share?

[arnaudrigole]

@george1421
The 2008 server is the storage node, which is defined directly with its @ip on a fog storage node/group

This is not standard because the only storage location i have in my company (for IT service only) is a dell disk bay managed by Windows 2008r2. We have a netapp managed by unix too but no NFS licence, and no IT datas on it so, i’m forced to use this configuration !

[Junkhacker]

it looks to me like maybe your ftp root isn’t right

[Wayne Workman]

@arnaudrigole on the FileZilla server thing, at the CLI, go to your images directory and issue the pwd command. What does it say?

[george1421]

@arnaudrigole said:

@george1421
The 2008 server is the storage node, which is defined directly with its @ip on a fog storage node/group

Ok that explains why things are not working!! I started setting up how to do this with Server 2012, but ran out of time. The root of your issue is that you need to install FTP on the Windows storage node to move the files. This guide should get you started: https://forums.fogproject.org/topic/6941/windows-server-as-fog-storage-node-reboot Understand this is for 2012 but 2008 is very similar. I used powershell for the copy and paste reasons.

[Wayne Workman]

@george1421 Yup. You’re exactly correct. It’s also worth noting here that FileZilla is un-necessary. Windows Server has all the necessary components available already.

[arnaudrigole]

@Wayne-Workman @george1421
I’m sorry, i don’t understand what you try to say me …
Wayne, what is the CLI? whats the pwd command on a 2008 server?

George, i followed this guide to setup the nfs server, but the powershell commands aren’t the same on 2008 and 2012, i adapted it by search on microsoft an equivalent.(i stopped to follow the guide on that step, because i use FILEZILLA SERVER for ftp)

I don’t understand my problem ; i need to install FTP on my Windows storage node more than filezilla server ?..

It look very complicated, it works just with filezilla + nfs role , but it just can’t create the directory on /images…

[Wayne Workman]

@arnaudrigole I thought your node was a linux node… You can disreguard. FYI the acronym for CLI is Command Line Interface.

Also - I’m a purist. I will not install third party anything if the base-OS can do it natively. This solves a lot of maintenance issues, update issues, and reduces complexity overall.

[arnaudrigole]

@Wayne-Workman
i hope this is why you ask me:
i just opened a cmd, when type the following cmds:

c:\windows\system32> ftp 10.1.11.64 <-- windows storage node
ftp> use fog
331 password required for fog
ftp> fogpassword
230 Logged on
ftp> cd /informatique/Service_info/FOG/images
250 CWD successful. “/informatique/Service_info/FOG/images” is current directory
ftp> pwd
257 “/informatique/Service_info/FOG/images” is current directory

[Wayne Workman]

@arnaudrigole said in Image hosting on NFS server, process uncompleted?:

/informatique/Service_info/FOG/images

That’s your FTP path.

FOG Trunk supports independent FTP paths, which you need.

[arnaudrigole]

@Wayne-Workman
OK so … what i’ve to do ?..
If i upgrade to trunk, I’ll need to redo all my images, and get pxe boot problems what i’ve already encountered in test environment…

[Junkhacker]

you won’t lose your images on an upgrade, and what pxe problems did you have? i’m sure we can fix them

[arnaudrigole]

@Junkhacker

Ok i’ll try to snapshot my fog vm before upgrade, then try to upgrade.

Seeing that the early uses it generated more problems than I already was in , I preferred board on version 1.2 . I do not remember exactly , but it was impossible to automatically inventory a machine, it had to be done manually , and after it was impossible to launch any task.