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.
Becky On Mon, Jan 23, 2012 at 9:30 AM, Becky Ligon <li...@omnibond.com> wrote:
You must also use different ports if you are bringing up multiple servers on the same machine (or IP address).
BeckyOn Mon, Jan 23, 2012 at 9:27 AM, Becky Ligon <li...@omnibond.com> wrote:
Good. Then, 10.10.8.2 must be the hostname on that machine. What does the "hostname" command show?
BeckyOn Mon, Jan 23, 2012 at 9:22 AM, Dimokritos Stamatakis <dimsta...@gmail.com> wrote:
Hello and thanks for your answer. Actually my pvfs2-fs.conf contains this information about 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> </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 <dimsta...@gmail.com> 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
Pvfs2-developers@beowulf-underground.org
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 list
Pvfs2-developers@beowulf-underground.org
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
