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
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
Hello,
did you test the case that you use native IPs?
I changed the hostname to debianvm1, I added an entry debianvm1 10.10.8.2
to the /etc/hosts and I used the debianvm1 alias for the I/O server, but again
the same error... It cannot bind to this address!
Thanks.
> Le Mon, 23 Jan 2012
Le Mon, 23 Jan 2012 16:33:39 +0200
Dimokritos Stamatakis écrivait:
> Yes, I edited the /etc/hosts file before, as a possible solution, but
> nothing happened.
>
> I actually wrote :
> 10.10.8.2 debianvm1
That's fine, but now you need to set your hostname accordingly:
hostname debianvm1
t
Of course!I attach the conf.Many thanks,Dimos.
pvfs2-fs.conf
Description: Binary data
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.BeckyOn Mon, Jan 23, 2012 at 9:30 AM, Becky Ligon wrote:
You must also u
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 wrote:
> You must also use different ports if you are bringing up multiple servers
> on the same machine (or IP address).
>
Yes, but this is the first step, when I try to start the first I/O server...
Thanks.
> 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 wrote:
> Good. Then, 10.10.8.2
Yes, I edited the /etc/hosts file before, as a possible solution, but nothing
happened.
I actually wrote :
10.10.8.2 debianvm1
and then I used debianvm1 as an alias...
Do I have to provide the actual IP of the physical machine?? 10.10.8.2 is the
IP of the virtual machine.
Dimos.
> Le Mo
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 wrote:
> Good. Then, 10.10.8.2 must be the hostname on that machine. What does
> the "hostname" command show?
>
> Becky
>
>
> On Mo
The hostname command shows "debian". But with using the -a option you choose
your own alias, right?
If I run pvfs2-server /etc/pvfs2-fs.conf -d
I get:
[S 01/23 14:29] PVFS2 Server on node debian version 2.8.1 starting...
[E 14:29:14.618851] Configuration file error. No host ID specified for alias
Le Mon, 23 Jan 2012 16:22:26 +0200
Dimokritos Stamatakis écrivait:
> 10.10.8.2 is the local IP address of the VM.
Ideally it would work much better if you'd set up hostnames; assign
names to the machines, edit /etc/hosts accordingly, and use hostnames
instead of raw ip addresses.
I guess that us
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
wrote:
> Hello and thanks for your answer.
> Actually my pvfs2-fs.conf contains this information about aliases:
>
>
> Alias 1
Hello and thanks for your answer.
Actually my pvfs2-fs.conf contains this information about aliases:
Alias 10.10.8.2 tcp://10.10.8.2:3334
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 th
That example might be confusing. The alias is the pvfs001 BEFORE the word
tcp.
Becky
On Mon, Jan 23, 2012 at 9:08 AM, Becky Ligon wrote:
> The -a options refers to the alias assigned in your pvfs2-fs.conf.
> Example:
>
>
> Alias pvfs001 tcp://pvfs001-myri0:3334
>
>
> The -a option r
The -a options refers to the alias assigned in your pvfs2-fs.conf. Example:
Alias pvfs001 tcp://pvfs001-myri0:3334
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
wrote:
> Hello all,
>
> I have a pr
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.
16 matches
Mail list logo