[Beowulf] TCP connect error: ECONNREFUSED.
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
John Hearns hearnsj at googlemail.comTue Mar 31 04:21:21 PDT 2009
- Previous message: [Beowulf] TCP connect error: ECONNREFUSED.
- Next message: [Beowulf] TCP connect error: ECONNREFUSED.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2009/3/31 John Hearns <hearnsj at googlemail.com>: > 2009/3/30 Jörg Saßmannshausen <jorg.sassmannshausen at strath.ac.uk>: >> Dear all, >> >> I am having this rather anoying problem with the parallel execution of one >> of the programs (GAMESS US version) on our cluster. The error message is: >> > As a general point - I have seen on several mailing lists folks asking > for specific help with a system. I got out on bed on the wrong side this morning. I do hope Jorg stays with the list - having expertise in computational chemistry will only add to the lists power. Maybe I should say things differently - your vendor's responsibility does not stop at hardware replacements. They often will go beyond their strictly contractual obligations and will diagnose problems with Linux kernel drivers, batch schedulers, application software etc. This is part of the "value add" which is why you (read your institution) went to a specialised cluster vendor, and not the lowest bidder.
- Previous message: [Beowulf] TCP connect error: ECONNREFUSED.
- Next message: [Beowulf] TCP connect error: ECONNREFUSED.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
