Dimos: Your config file looks fine. I was able to use an IP address as the alias as well as part of the BMI address. So, no problems with PVFS there. On my system, my eth0 interface is defined with the IP address that I used in the BMI address; it is NOT defined in the /etc/hosts file. I will attach a copy of my fs.conf file and my eth0 config. The command that I used to start the server:
pvfs2-server fs.conf -a 192.168.122.37 Becky On Mon, Jan 23, 2012 at 1:42 PM, Phil Carns <[email protected]> wrote: > Hi Dimos, > > By default (unless you use the TCPBindSpecific flag in the conf file, > which you are not) the server should just try to bind to listen on *:3334, > no matter what hostname or IP address you put in the conf file. In other > words, it ignores the hostname and just listens for connections on any ip > address for port 3334. Later on when the servers are actually > communicating it is important to have the right IP addresses of course, but > just to start a server it doesn't much matter. Oddly, I think the error > message that you are posting matches what one would see if you tried to > bind to a specific (but not existent) IP address. Maybe there are other > cases that can trigger the error. For a sanity check maybe you could post > the output of "ifconfig" and make sure that the 10.10.8.2 interface is up > (because you will surely want it later anyway), but I've never seen > mismatched IP address on a PVFS server cause a problem without > TCPBindSpecific. > > This means that there is probably some other problem going on here that is > unrelated to how you have specified the IP address or alias in the conf > file, I think? > > One thing that you could try to do is install "nc" if it isn't installed > already, and try running "nc -l 3334". nc is a generic tcp server/client > program, and depending on whether it will successfully listen on 3334 or > not will tell you if there is a system-wide problem or a pvfs-specific > problem. Make sure to run this as the same user that you use to launch the > pvfs2-server process. > > ... and finally, if the above steps don't turn up anything, you can try > the following: > > strace pvfs2-server /etc/pvfs2-fs.conf -d -a 10.10.8.2 >& foo.txt > grep bind foo.txt > > You should see a line that looks something like this: > > bind(3, {sa_family=AF_INET, sin_port=htons(3334), > sin_addr=inet_addr("0.0.0.0")}, 16) = -1 EADDRINUSE (Address already in use) > > ... which will indicate exactly what port and addr are being used when it > actually tries to bind the socket, and also confirm what errno value it is > getting. > > good luck! > -Phil > > > On 01/23/2012 09:37 AM, Dimokritos Stamatakis wrote: > > Of course! > I attach the conf. > > Many thanks, > Dimos. > > > > > > Send me your pvfs2-fs.conf file and let me take a look at it. I will also > try using IP addresses and see what happens. > > Becky > > On Mon, Jan 23, 2012 at 9:30 AM, Becky Ligon <[email protected]> wrote: > >> You must also use different ports if you are bringing up multiple servers >> on the same machine (or IP address). >> >> Becky >> >> >> On Mon, Jan 23, 2012 at 9:27 AM, Becky Ligon <[email protected]> wrote: >> >>> Good. Then, 10.10.8.2 must be the hostname on that machine. What does >>> the "hostname" command show? >>> >>> Becky >>> >>> >>> On Mon, Jan 23, 2012 at 9:22 AM, Dimokritos Stamatakis < >>> [email protected]> wrote: >>> >>>> Hello and thanks for your answer. >>>> Actually my pvfs2-fs.conf contains this information about aliases: >>>> >>>> <Aliases> >>>> Alias 10.10.8.2 tcp://10.10.8.2:3334 >>>> </Aliases> >>>> >>>> >>>> So I should start the server like this, right? >>>> >>>> pvfs2-server /etc/pvfs2-fs.conf -d -a 10.10.8.2 >>>> >>>> 10.10.8.2 is the local IP address of the VM. >>>> By the way I am able to start another process that binds to 10.10.8.2 >>>> and 3334 port and waits for tcp connections. >>>> That's very strange. >>>> >>>> Many thanks, >>>> Dimos. >>>> >>>> >>>> The -a options refers to the alias assigned in your pvfs2-fs.conf. >>>> Example: >>>> >>>> <Aliases> >>>> Alias pvfs001 tcp://pvfs001-myri0:3334 >>>> </Aliases> >>>> >>>> The -a option refers to pvfs001 in the above example. >>>> >>>> Hope this helps! >>>> Becky >>>> >>>> >>>> On Mon, Jan 23, 2012 at 8:08 AM, Dimokritos Stamatakis < >>>> [email protected]> wrote: >>>> >>>>> Hello all, >>>>> >>>>> I have a problem while trying to run pvfs2 on a eucalyptus cloud. >>>>> We have tested it to physical machines and it works perfectly, but >>>>> when we move to the cloud there is a bind failure message. I try to run >>>>> the >>>>> I/O server with this command: >>>>> pvfs2-server /etc/pvfs2-fs.conf -d -a 10.10.8.2 >>>>> and I get these messages >>>>> >>>>> [S 01/23 12:45] PVFS2 Server on node 10.10.8.2 version 2.8.1 >>>>> starting... >>>>> LINE 1777 per-collection enviroment!! >>>>> Using cache style shm //pvfs2-storage-space/1375f222/ >>>>> [E 01/23 12:45] (null): can't bind socket to listening address: Cannot >>>>> assign requested address >>>>> LINE 1777 per-collection enviroment!! >>>>> [E 01/23 12:45] Error adding handle range >>>>> 3-4611686018427387904,4611686018427387905-9223372036854775806 to >>>>> filesystem >>>>> pvfs2-fs >>>>> [E 01/23 12:45] Error: Could not initialize server interfaces; >>>>> aborting. >>>>> [E 01/23 12:45] Error: Could not initialize server; aborting. >>>>> Segmentation fault >>>>> >>>>> It says it cannot bind socket to listening address... I have tested >>>>> many applications before and they can bind normally to this private >>>>> address >>>>> (10.10.8.2) . >>>>> So what is an explanation you can guess?? >>>>> >>>>> I leave the default parameters at the configuration file, except the >>>>> I/O hostname and metadata hostname where I put 10.10.8.2. >>>>> >>>>> Many thanks, >>>>> Dimos. >>>>> >>>>> _______________________________________________ >>>>> Pvfs2-developers mailing list >>>>> [email protected] >>>>> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers >>>>> >>>> >>>> >>>> >>>> -- >>>> Becky Ligon >>>> OrangeFS Support and Development >>>> Omnibond Systems >>>> Anderson, South Carolina >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> Becky Ligon >>> OrangeFS Support and Development >>> Omnibond Systems >>> Anderson, South Carolina >>> >>> >>> >> >> >> -- >> Becky Ligon >> OrangeFS Support and Development >> Omnibond Systems >> Anderson, South Carolina >> >> >> > > > -- > Becky Ligon > OrangeFS Support and Development > Omnibond Systems > Anderson, South Carolina > > > > > > _______________________________________________ > Pvfs2-developers mailing > [email protected]http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers > > > > _______________________________________________ > Pvfs2-developers mailing list > [email protected] > http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers > > -- Becky Ligon OrangeFS Support and Development Omnibond Systems Anderson, South Carolina
fs.conf
Description: Binary data
ifconfig.out
Description: Binary data
_______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
