Bug with DF under Linux RedHat

[Michael H.W. Weber]

Hi Howard,
someone from our team has a problem with running DF under Linux RedHat. On two independent systems (both AMD Duron 1200, 320 MB RAM, Red Hat 6.2 and 7.1) the client crashes after calculating correctly for around half a day.

The error message displayed was:

"Handle found. Using 5ti925cu. To change, hit 'C' and wait 5 seconds...[foldtrajlite] FATAL ERROR: [001.008] Cannot open rotamer library
Hit Return"

And the "error.log" reads:

========================[ Jun 10, 2002 11:46 AM ]========================
FATAL ERROR: [001.010] {randwalk.c, line 989} Unable to find atom 2HZ in dictionary entry 34

========================[ Jun 10, 2002 9:54 PM ]========================
ERROR: [001.001] {foldtrajlite.c, line 1067} Caught sig 11

========================[ Jun 10, 2002 10:30 PM ]========================

========================[ Jun 10, 2002 11:34 PM ]========================

========================[ Jun 11, 2002 12:39 AM ]========================
ERROR: [-04.000] {rotlib.c, line 100} Bzip decompression of SCWRL library error occurred
FATAL ERROR: [001.008] {foldtrajlite.c, line 3433} Cannot open rotamer library

Any suggestions what is going on here?

Thanks a lot,
Michael.

[Michael H.W. Weber]

Additional clarification: Both clients (written for RedHat 7.1 and 6.2) were launched under RedHat 7.3. The client for 7.1 crashed after approx. a day and because it was told somewhere that it does not run properly with RedHat 7.3, the other client designed for 6.2 was tested. This one then gave the error detailed above.

Michael. (sorry, I could not modify the message above to add this stuff)

[Brian the Fist]

It appears you are receiving random errors perhaps due to a faulty memory chip. If anyone else can verify this error on a second machine I'll look further. As for the Intel compiler one, it may not work on AMD CPUs properly. If problems continue on RedHat 7.3 Ill release a third version or discontinue the 6.2 support but Id like to avoid this if possible.

[Michael H.W. Weber]

Hi Howard,
as stated above, the bug appeared on two independent AMD Duron machines and therefore a hardware defect such as a faulty memory chip appears to be excluded.

Michael.