From: Steve W. <st...@pu...> - 2015-01-28 17:00:15
|
Hi, Oops... it turns out that this is a false alarm! I found a typo in my hosts file which was the source of this problem. After correcting the typo, I'm able to successfully mount using the -B (mfsbind) option as before. Thanks for your replies and sorry for the false alarm. Kind regards, Steve On 01/28/2015 11:05 AM, Krzysztof Kielak wrote: > Steve, > > We’ll look into your case in more details first thing in the morning > (CET time) tomorrow and we’ll fix it, if it’s broken on our side. > > When it comes to binding on a client side, I can quote Richard Stevens > from book “UNIX Network Programming: The Sockets Networking API” that > says: > > /“Normally, a TCP client does not bind an IP address to its socket. > The kernel chooses the source IP address when the socket is connected, > based on the outgoing interface that is used, which in turn is based > on the route required to reach the server”/ > > From the above you should be fine without binding, but of course - as > I mentioned earlier - we’ll check CentOS 7 here and we’ll keep you posted. > > Best Regards, > Krzysztof Kielak > *Director of Operations and Customer Support* > Mobile: +48 601 476 440 > > > >> On 28 Jan 2015, at 16:09, Steve Wilson <st...@pu... >> <mailto:st...@pu...>> wrote: >> >> I have a generic script that is used for mounting MooseFS filesystems >> on my workstations. Some of the workstations have multiple IP >> addresses, including those workstations that also double as a MooseFS >> master server. These will have a master server IP address along with >> their normal IP address that can easily be moved to another >> workstation (i.e., the metalogger server) when I want that >> workstation to become the master server. >> >> So the script I use supplies the default hostname (as given by >> /bin/hostname) to the -B option of mfsmount. And, like I mentioned >> earlier, this has been working quite successfully for several years >> up until this installation of CentOS 7. >> >> I did find that using the IP address instead of the hostname does >> work correctly so I'll probably change my scripts to use an IP address: >>> [root@sbmonitor mnt]# mfsmount /mnt/mfs -B10.145.7.33 >>> -Hsb-data.bio.purdue.edu <http://Hsb-data.bio.purdue.edu> -S/cosit >>> mfsmaster accepted connection with parameters: >>> read-write,restricted_ip ; root mapped to root:root >> >> Thanks, >> Steve >> >> On 01/28/2015 09:32 AM, Aleksander Wieliczko wrote: >>> Hi >>> What is the reason that you want to use different IP address for >>> client binding, than your default NIC ip? >>> >>> -B IP option is the same as -o mfsbind=IP ---define source ip >>> address for connections (default: NOT DEFINED - chosen automatically >>> by OS) >>> >>> Best regards >>> Aleksander Wieliczko >>> Technical Support Engineer >>> MooseFS.com <x-msg://26/moosefs.com> >>> >>> On 01/28/2015 03:08 PM, Steve Wilson wrote: >>>> Hi, >>>> >>>> When using the -B option to mfsmount after upgrading to CentOS 7, I get >>>> the following error: >>>>> [root@sbmonitor mnt]# mfsmount /mnt/mfs -Bsbmonitor.bio.purdue.edu <http://Bsbmonitor.bio.purdue.edu> >>>>> -Hsb-data.bio.purdue.edu <http://Hsb-data.bio.purdue.edu> -S/cosit >>>>> can't bind socket to given ip ("10.147.7.33") >>>> This same command works on CentOS 6, RHEL 6, Ubuntu 12.04, and Ubuntu >>>> 14.04 but doesn't work on CentOS 7. This is my first CentOS 7 >>>> installation so I'm still learning its subtle and not-so-subtle >>>> differences. I'm not sure if this is a problem with my CentOS 7 >>>> configuration or a MooseFS problem. >>>> >>>> If I attempt to perform the mount without the -B option, it works fine: >>>>> [root@sbmonitor mnt]# mfsmount /mnt/mfs -Bsbmonitor.bio.purdue.edu <http://Bsbmonitor.bio.purdue.edu> >>>>> -Hsb-data.bio.purdue.edu <http://Hsb-data.bio.purdue.edu> -S/cosit >>>>> can't bind socket to given ip ("10.147.7.33") >>>> Any ideas what the problem could be? Can anyone reproduce this on >>>> another CentOS 7 or RHEL 7 installation? >>>> >>>> Thanks! >>>> >>>> Steve >>>> >>>> ------------------------------------------------------------------------------ >>>> Dive into the World of Parallel Programming. The Go Parallel Website, >>>> sponsored by Intel and developed in partnership with Slashdot Media, is your >>>> hub for all things parallel software development, from weekly thought >>>> leadership blogs to news, videos, case studies, tutorials and more. Take a >>>> look and join the conversation now.http://goparallel.sourceforge.net/ >>>> _______________________________________________ >>>> moosefs-users mailing list >>>> moo...@li... >>>> https://lists.sourceforge.net/lists/listinfo/moosefs-users >>> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming. The Go Parallel Website, >> sponsored by Intel and developed in partnership with Slashdot Media, >> is your >> hub for all things parallel software development, from weekly thought >> leadership blogs to news, videos, case studies, tutorials and more. >> Take a >> look and join the conversation now. >> http://goparallel.sourceforge.net/_______________________________________________ >> moosefs-users mailing list >> moo...@li... >> <mailto:moo...@li...> >> https://lists.sourceforge.net/lists/listinfo/moosefs-users > |