No luck with the tests.

I tried changing the credentials to root for testing with the same issue.
No trace in logs.

@wayne-workman I didn’t see your post, sorry for not answering until now. I will try your suggestion. But I’m afraid it doesn’t fit our needs. Actually switching the master option from one node to another will, in way, lock FOG imaging on a vlan or another. That could be troubling for users and forbid simultaneous imaging on both vans. Am I wrong ?

In your opinion, could trunk answer this need ?

@Quazz I share your doubts.

Unfortunately even after manually changing both credentials, I still have the image in /images/dev not copied to /images.
Before that I went back to the Student Node (with StudentIP@/eth1) into Student Group.

Very weird. The weirdest is that I made the manual FTP tests twice from this same client with no issue.

I have to leave now, I’ll try to check logs to find out.

Thanks for your help @Quazz and @Wayne-Workman.

@Wayne-Workman I tried your solution but with no better result. I may have misunderstood your explanation.

I put the Student Storage Node (StudentIP@/eth1) in the ‘default’ group which already contains a node named ‘DefaultMember’ with StaffIP@/eth0.
I had the first error I encountered (Mounting File System…mount : mounting 172.29.1.40:/images/dev/ on /images failed: connection timed out). It doesn’t take into account the Student Node settings and take the default one.

@Wayne-Workman Oh, ok. I’ll try it right now…

@Quazz Each time I specified an IP, I also modified the interface accordingly.

Thanks Wayne, that’s the page I mentionned in the original post.
It helped me to understand a lot better the mechanics but not to solve my problem, yet. I dive into it again…

Thanks for the quick reply Quazz.
Actually the credentials I use for the student node are the same as the DefaulMember node created by FOG which works just fine but on the staff network.
The machine I try to upload passed all FTP tests mentioned in the wiki page. Even tried in ‘/images/dev’.

I’m not really enthusiastic using trunk version more because of custom (I use Jessie, not testing ). But I will seriously consider this option if I don’t manage it.

Thanks again !

Hello,

After wandering the forum, I’ve seen many posts that look like the problem we are facing but I found no answer yet.
Here is our situation :

• we have two vlans hosting two ADs (so with their own DHCP, DNS, etc.) : one for the staff, the other for the students,
• I set up a fog server (VM) with two NICS, one in each of these vlans, so FOG has two IP addresses (staffIP@ on eth0 and studentIP@ on eth1),
• FOG is managed through the staff vlan,
• we want to be able to manage imaging on both IP segments.

FOG 1.2.0 is installed on a Jessie VM.

Naively (and also by curiosity) I tried to upload an image from the staff vlan and an other from the student vlan.
The staff vlan imaging works flawlessly. On the student side, I was happily surprised to see the station managing to boot through pxe (so with the right IP). But that was too nice, and the NFS mount crashed with this message :

• Mounting File System…mount : mounting 172.29.1.40:/images/dev/ on /images failed: connection timed out.

Well, that was with no real surprise : 172.29.1.40 is the staffIP@ of the server as 172.22.1.40 is the studentIP@.

So I tried something. I created on the same FOG server a student Storage Node with:

• 172.22.1.40 as IP,
• eth1 as NIC,
• /images as the image path,
• the same user/password as the DefaultMember Storage Node.

I attached it to a Storage group called ‘Student Group’ and then linked the station image to this ‘Student Group’.
Then the imaging seems to go without any problem :
But when I look into /images I cannot see any directory for the image, except in /images/dev where there is a directory which name is the MAC address of eth1 (student NIC on the server). This directory contains ‘d1.mbr’ and ‘d1p1.img’ files, much smaller than the original data size (the data only contains 0).

It is as if it couldn’t create the final image in /images.

I also tried to create a new directory structure for the student node under /images (/images/student and /images/student/dev) but with no more success.

The .mntcheck files are created, the /images tree is 777 and the content of /etc/exports is :
/images *(rw,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=1)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=2)

(i originally had rw for /images but put ro following the wiki and then put rw back)

Reading https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP, I had the idea to change the IP address in the DefaultMember Storage Node (ie set studentIP@ instead of staffIP@) the image upload works like a charm.
Unfortunately, I don’t want to manually change this IP each time an upload/download is necessary.
About this page, the screenshot (https://wiki.fogproject.org/wiki/index.php?title=File:Storage_Management_Interface_Name.png) has a lot more fields than I can see on my FOG install.

Obviously my problem would come from FTP settings, but I can’t figure out which one(s).
Can you help me ?

Cheers,
Erwan