My experience with clusters is limited to Windows so my advice might not be relevant, but I offer it with the hope that it will help. Nodes in a cluster use a dedicated connection between them, called the heartbeat, to determine what nodes are alive or dead. When a node is down the other nodes continue to send packets through the heartbeat connection, but because it is down there is no response. That, I think, is the cause of you error message. If the error is on the interface you are using as the heartbeat and it disappears once the other node is up, then you can ignore it. Good luck.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Eggleston Sent: Thursday, February 27, 2003 10:39 AM To: [EMAIL PROTECTED] Subject: [Ltsp-discuss] very slow booting and nfs mounting I'm working on my cluster. One problem I have been having is I get a lot of 'portmap: server localhost not responding, timed out' messages as one node boots. I'm using ltsp 3 on a biostar m7vkq with 128mb. The head has redhat 7.3. Mike ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
