Actually, I can do it - but it turns out that's not the whole story.
So, by putting the short name in the config file the server finds the
entry, but on my system the short name is not known so it doesn't work
when we try to communicate. I *must* use the long name, and thus the -a
option.
At a minimum we need to alert the installer that the short name is used
in the search, but that they must use a valid name, and the -a if that
is not a short name.
OR get rid of the name stripping, or allow both (search w/o stripping,
and if not found strip and search again).
I don't know how common it is for distributions to use a long hostname
with no short alias - I know I've seen this on other systems. We should
probably ask the group if we should change any stripping behavior, and
in any case document it well.
----------------------------
So here is the summary (for the group to decide)
current behavior - server uses gethostname and then strips the
domainname to get a short alias before searching the config file for its
data.
Some machines do not use a short alias for address resolution so a long
name must be used in the config file - the auto search will not find it.
The -a option allows you to override.
Possible options:
1) leave it and document it
2) remove the stripping, document that a valid network name must be used
3) let auto search use both stripped and unstripped version for
convenience - document accordingly
Opinions?
Walt
Sam Lang wrote:
Sounds good. Do you want to update the install guide? I'm not sure
what text you're referring to exactly. Its in CVS at
doc/pvfs2-quickstart.tex. If you just want to send me the paragraph to
add I can throw it in there.
-sam
On Feb 24, 2009, at 12:59 PM, Walter Ligon wrote:
Ah, yes, the function guess_alias in pvfs2-server seraches for the
first period in the hostname and truncates the hostname there.
Thus, we need to update the install guide to this fact, that the
proper thing to use in the genconfig script is the name returned by
hostname up to but not including the first period. Unless they plan
to use the -a flag, in which case they can use whatever they want.
Walt
Sam Lang wrote:
I think the hostname command uses the uname system call rather than
gethostname. We could add a match for whatever uname returns as well.
-sam
On Feb 24, 2009, at 10:50 AM, Walter Ligon wrote:
ah, so you're saying the command line hostname and the library call
the server uses aren't returning the same thing? That makes sense.
I ended up removing the domain from the config file and it worked.
Must be an oddity of the way my machine is configed that the name is
reported two different ways.
If there isn't a more robust mechanism (which there may not be) then
maybe the install guide should simply warn the user that it might be
an issue.
Thanks for you help Sam!
Walt
Sam Lang wrote:
Hi Walt,
With the single config file in place now, the server has to be told
(with the -a command line option) or guess which server it is. It
guesses by simply using the hostname, and you may have run into a
bug. I'll play with it and see if I can make it more robust. In
the meantime, you can use: -a 172-22-9-126.lwapp.clemson.edu
-sam
On Feb 24, 2009, at 10:06 AM, Walter Ligon wrote:
I probably did something wrong, but I got this error:
sh-3.2# sbin/pvfs2-server /etc/pvfs2-fs.conf -f
[S 02/24 10:58] PVFS2 Server on node 172-22-9-126 version
2.7.1pre1-2009-01-27-183824 starting...
[E 10:58:18.292013] Configuration file error. No host ID specified
for alias 172-22-9-126.
[E 02/24 10:58] Could not find handle range for host (null)
[E 02/24 10:58] Please make sure that the host names in
/etc/pvfs2-fs.conf are consistent
[D 02/24 10:58] PVFS2 Server: storage space created. Exiting.
here is my config file:
<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 172-22-9-126.lwapp.clemson.edu
tcp://172-22-9-126.lwapp.clemson.edu:3334
</Aliases>
<Filesystem>
Name pvfs2-fs
ID 43450330
RootHandle 1048576
<MetaHandleRanges>
Range 172-22-9-126.lwapp.clemson.edu
3-4611686018427387904
</MetaHandleRanges>
<DataHandleRanges>
Range 172-22-9-126.lwapp.clemson.edu
4611686018427387905-9223372036854775806
</DataHandleRanges>
<StorageHints>
TroveSyncMeta yes
TroveSyncData no
</StorageHints>
</Filesystem>
and for reference:
sh-3.2# hostname
172-22-9-126.lwapp.clemson.edu
Should I have dropped the domain name when I created the config
file? The install instructions don't say anything about that.
Walt
_______________________________________________
Pvfs2-developers mailing list
Pvfs2-developers@beowulf-underground.org
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
_______________________________________________
Pvfs2-developers mailing list
Pvfs2-developers@beowulf-underground.org
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
