Hi,

When you run your netstat check to see if anything is using port 9000, you should probably run it with these arguments:

        netstat -tan | grep 9000

The "-n" part of the netstat command line is important to make sure that you get numerical port numbers rather than symbolic names for them. The "-t" makes it only show tcp ports, which are the only ones that matter to PVFS.

IANA indicates that port 9000 could possibly be used by something called "cslistener". If opensuse happens to include that in their /etc/services file then you would see <host>:cslistener rather than <host>:9000 when checking netstat without the "-n" argument, and the grep would miss it.

http://www.iana.org/assignments/port-numbers

-Phil

Scully wrote:
Sorry, both nodes use port 9000

On Tue, 2008-01-22 at 16:19 -0500, Scully wrote:
Hi,
I am trying to setup a PVFS2 system in two nodes, suse64(x86_64) and OpenSUSE-desktop(i386), each has a io server and meta server. Both of them are using kernel: 2.6.16.53-0.8. Both use port 3334.

The server can start correctly on suse64, but on OpenSUSE-desktop, it's another story.
It looks ok when I run:
{
OpenSUSE-desktop:/usr/local/bin #/etc/init.d/pvfs2-server start
Starting PVFS2 server: [S 01/22 15:44] PVFS2 Server on node OpenSUSE-desktop version 2.7.0 starting...
}
But when I check the log, I get
{
OpenSUSE-desktop:/usr/local/bin # cat /tmp/pvfs2-server.log
[D 01/22 15:44] PVFS2 Server version 2.7.0 starting.
[E 01/22 15:44] Error: BMI_sockio_bind_sock: Address already in use
[E 01/22 15:44] Error: tcp_server_init() failure.
[E 01/22 15:44] Error: BMI_initialize: Address already in use
[E 01/22 15:44] Error: Could not initialize server interfaces; aborting.
[E 01/22 15:44] Error: Could not initialize server; aborting.
}
I think port 9000 is available:
{
OpenSUSE-desktop:/usr/local/bin # netstat | grep 9000
OpenSUSE-desktop:/usr/local/bin # } When I set a new port to the server in the /etc/pvfs2-fs.conf, say 9001, there is no problem to start the server. But, next time, I have to use another port. I guess pvfs2 doesn't work this way.

When stopping a server and re-setup a new one, I do:
{
#/etc/init.d/pvfs2-server stop
#/usr/local/sbin/pvfs2-server /etc/pvfs2-fs.conf -r
If above instruction can not delete the storage space, I do it manully
#rm -fr /pvfs2-storage-space.
}
The configure files are the same in both nodes
{
OpenSUSE-desktop:/usr/local/bin # cat /etc/pvfs2-fs.conf
<Defaults>
        UnexpectedRequests 50
        EventLogging none
        LogStamp datetime
        BMIModules bmi_tcp
        FlowModules flowproto_multiqueue
        PerfUpdateInterval 1000
        ServerJobBMITimeoutSecs 30
        ServerJobFlowTimeoutSecs 30
        ClientJobBMITimeoutSecs 300
        ClientJobFlowTimeoutSecs 300
        ClientRetryLimit 5
        ClientRetryDelayMilliSecs 2000

        StorageSpace /pvfs2-storage-space
        LogFile /tmp/pvfs2-server.log
</Defaults>

<Aliases>
        Alias OpenSUSE-desktop tcp://OpenSUSE-desktop:9000
        Alias suse64 tcp://suse64:9000
</Aliases>

<Filesystem>
        Name pvfs2-fs
        ID 2061359039
        RootHandle 1048576
        <MetaHandleRanges>
                Range OpenSUSE-desktop 3-2305843009213693953
                Range suse64 2305843009213693954-4611686018427387904
        </MetaHandleRanges>
        <DataHandleRanges>
Range OpenSUSE-desktop 4611686018427387905-6917529027641081855
                Range suse64 6917529027641081856-9223372036854775806
        </DataHandleRanges>
        <StorageHints>
                TroveSyncMeta yes
                TroveSyncData no
        </StorageHints>
</Filesystem>
}


Did I do something wrong? Thanks.

------------------------------------------------------------------------

_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users

_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users

Reply via email to