From: Gengbin Zheng (gzheng_at_ks.uiuc.edu)
Date: Wed Oct 20 2004 - 10:24:09 CDT
Hi Marek,
first try to run it sequentially before you try something else, just
run it without charmrun:
./namd2 namdconfig
In most case this will tells you what error you get (like missing shared
library due to incompatable kernel library, etc)
If this works, run it parallel but only on your local desktop, like:
./charmrun +p2 ./namd2 namdconfig ++local
If this still run, it is likely the problem of your cluster setup that
prevent you from running charmrun across different machines.
Gengbin
Marek Dynowski wrote:
>On Wednesday 20 October 2004 15:27, you wrote:
>
>
>> I'm running namd in a opteron cluster with fedora 2.0 x86_64. I was
>>also not able to compile it due to similar problems, but the binary
>>
>> NAMD_2.5_Linux-i686-TCP
>>
>>which is available in the namd site runs well. Of course, it runs as a
>>32bit application.
>> Leandro.
>>
>>
>>
>>
>>
>
>Hi Leandro / all,
>
>thanks for the quick answer. I tried the binary NAMD_2.5_Linux-i686-TCP, but
>now I get the following error message:
>
>
>Charmrun: error on request socket--
>Socket closed before recv.
>
>I found the same error message in the Charm++ FAQ:
>
>Charmrun: error on request socket--
>Socket closed before recv.
>This means that the node program died without informing charmrun about it,
>which typically means a segmentation fault while in the interrupt handler or
>other critical communications code. This indicates severe corruption in
>Charm++'s data structures, which is likely the result of a heap corruption
>bug in your program. Re-linking with "-memory paranoid" may clarify the true
>problem.
>
>So I tried to compile NAMD/Charm to solve the error above ?
>Do you have any suggestions ?
>
>
This archive was generated by hypermail 2.1.6 : Wed Feb 29 2012 - 15:37:55 CST