Hello Ilya,
Am 03/05/2013 07:35 PM, schrieb Ricardo J. Barberis:
> El Lunes 04/03/2013, Ilya Bychkov escribi�:
>> Did you use the absolute path to the config files (ConnNetFilterFile,
>>
>>> ConnInterfacesFile) in the fhgfs-client.conf, fhgfs-storage.conf,
>>> fhgfs-mgmtd.conf and the fhgfs-meta.conf.
>>
>> It looks like:
>>
>> *ConnNetFilterFile = /root/Desktop/netfile*
>>
>> Is it right or should it be a .txt - File like *
>> /root/Desktop/netfile.txt * ?
>>
>>>> _*ConnNetFilterFile*_ _*ConnInterfacesFile*_
>>>>
12.0.0.1/24 eth0
>>>>
14.0.0.1/24 eth1
I think the configuration with ConnNetFilterFile and ConnInterfacesFile
works. You description in this email shows that both IP address networks
are used. Which behaviour do you expect?
>
> I might be completely off here, but my gues is your clients are trying to
> reach your
14.0.0.1/24 servers through eth0, as that's the preferred
> interface, no matter the network (or tha's what I believe).
>
> What happens if tou define only ConnNetFilterFile?
>
>>> You are using strange IP-addresses. You are using public IP addresses
>>> and not private IP addresses. Is your fhgfs working across the internet
>>> or only in a local network?
>>
>> Why are they strange?^^ I have no connections to the public net
>> (192.x.x.x), this adresses (12.x.x.x. / 14.x.x.x.) are private, so only my
>> servers are communicating over this IP-Addresses...
The IP address which you are using are not the cause for the problem you
might have. But the IP addresses which are you using let me assume that
you are using fhgfs across the Internet. You told me you do not use
fhgfs across the Internet, so I can rule out this as cause for the
problems which you might have.
More information about the classification of IP addresses you could find
in the RFC1597 (
http://tools.ietf.org/html/rfc1597).
>
>>> Normally it works so easy. Look into the logfiles of the client, there
>>> must be a other reason why it doesn't work. Maybe the other servers are
>>> not reachable over the other interface.
>>
>> I just "tailed" the fhgfs-client.log files... It estabilishes a
>> connection to the 12.x.x.x. net and begins to write, good so far...
>> After I pull out the cable, it stops and after ~ 1 min it's
>> estabilishing a connection to the 14.x.x.x net for the one node , that has
>> lost the connection to the 12.x.x.x. net ( with fhgfs-net I can see that
>> the client is actually connected to 14.x.x.x. net, it seems to be
>> alright)...
It works as designed. The client tries several times to connect to the
used IP address. After 90 seconds the client use the other interfaces.
>> but it changes nothing, so the write process is still stopped until I
>> put the cable in, so the client can connect to the 12.x.x.x. net...
>> I am using a special tool to write/read the files, so maybe there are
>> some incompatibility problems... do you maybe have any other easy way to
>> test this feature?
You could use the program dd. But your description above shows me that
it works. Start your program, pull the cable out and wait for the
fail-over. After the fail-over your program will work again and will
finish successful.
kind regards,
Frank