We can't start Maui because it was sigfaulting right after start on:
(gdb) r
Starting program: /opt/maui/sbin/maui
Program received signal SIGSEGV, Segmentation fault.
0x00000032b7f721e3 in memcpy () from /lib64/tls/libc.so.6
(gdb) bt
#0 0x00000032b7f721e3 in memcpy () from /lib64/tls/libc.so.6
#1 0x000000000045b6ca in MResAdjustDRes (JName=0x0, ForceEval=0) at MRes.c:7302
#2 0x000000000043e4c6 in MSchedProcessJobs (OldDay=0x7fbffff0e0 "",
GlobalSQ=0x7fbfffb0e0, GlobalHQ=0x7fbfff70e0) at MSched.c:6955
#3 0x0000000000403a33 in main (ArgC=1, ArgV=0x7fbffff208) at
Server.c:192
So we added JRE memory check into MRes.c and were able to start maui:
--- ../BUILD/maui-3.2.6p21/src/moab/MRes.c 2008-12-09 21:55:26.000000000
+0100
+++ MRes.c 2009-02-09 17:02:25.397267670 +0100
@@ -7255,7 +7255,15 @@
if (CRE == NULL)
{
- DBG(4,fCORE) DPrint("ALERT: cannot allocate memory in %s\n",
+ DBG(4,fCORE) DPrint("ALERT: cannot allocate memory for CRE in %s\n",
+ FName);
+
+ return(FAILURE);
+ }
+
+ if (JRE == NULL)
+ {
+ DBG(4,fCORE) DPrint("ALERT: cannot allocate memory for JRE in %s\n",
FName);
return(FAILURE);
Ofcourse after we started MAUI with this patch we got lot of "cannot allocate
memory for JRE". We are not sure what it can be related to because there was no
any changes in configuration files, so we suspect maybe some job which leaded
to this error?
--
Alexander Oltu
System Engineer
Parallab, Bergen Center for Computational Science, Unifob
Thormøhlensgt.55
N-5008 Bergen, Norway
phone: +47 55584083
_______________________________________________
mauiusers mailing list
[email protected]
http://www.supercluster.org/mailman/listinfo/mauiusers
