my system is fully pached using rug with the oes channel.
I am using compat dl380 with 2 cpu's connected to an eva.
The nss volumes stay active, but the command line cluster commands
fail to respond. The system requires a reboot. It seems to happen every
time I connect with imanager. I have been trying to eliminate the crashes
and upgraded to imanager 2.6 and upgraded the plugins. Anyone else seeing
this message? Anyone know why novell put xml parsing in the kernel?
Regards,
Martin Roby


Feb 15 10:59:01 linuxgw01 /USR/SBIN/CRON[19975]: (root) CMD ( rm -f
/var/spool/cron/lastrun/cron.hourly)
Feb 15 11:01:43 linuxgw01 ncs-configd: updateResourcesXmlFile:
cn=clusterii,ou=GWCLUSTER_ONE,ou=albany,o=test
Feb 15 11:01:44 linuxgw01 ncs-configd: importClstrlibCall failed:
exceptions.SyntaxError
Feb 15 11:01:44 linuxgw01 ncs-configd: -98 failed: exceptions.TypeError
Feb 15 11:02:34 linuxgw01 kernel: Unable to handle kernel paging request at
virtual address 30343535
Feb 15 11:02:34 linuxgw01 kernel: printing eip:
Feb 15 11:02:34 linuxgw01 kernel: fa8fde48
Feb 15 11:02:34 linuxgw01 kernel: *pde = 00000000
Feb 15 11:02:34 linuxgw01 kernel: Oops: 0002 [#1]
Feb 15 11:02:34 linuxgw01 kernel: SMP
Feb 15 11:02:34 linuxgw01 kernel: CPU: 0
Feb 15 11:02:34 linuxgw01 kernel: EIP: 0060:[<fa8fde48>] Tainted: PF
Feb 15 11:02:34 linuxgw01 kernel: EFLAGS: 00010286 (2.6.5-7.283-bigsmp
SLES9_SP3_BRANCH-20061129165553)
Feb 15 11:02:34 linuxgw01 kernel: EIP is at
CmaUtcToYearMonthDayHourMinuteSecond+0x48/0x60 [cma]
Feb 15 11:02:34 linuxgw01 kernel: eax: ffffffff ebx: 30343535 ecx:
00000000 edx: 00000000
Feb 15 11:02:34 linuxgw01 kernel: esi: d6003339 edi: d66f9dc8 ebp:
f392a8a4 esp: d66f9d64
Feb 15 11:02:34 linuxgw01 kernel: ds: 007b es: 007b ss: 0068
Feb 15 11:02:34 linuxgw01 kernel: Process owcimomd (pid: 20678,
threadinfo=d66f8000 task=f44e8010)
Feb 15 11:02:34 linuxgw01 kernel: Stack: d66f9dd0 d66f9dd4 d66f9dd8
d66f9ddc 4c43574e 5f525453 54637455 616d436f
Feb 15 11:02:34 linuxgw01 kernel: 65746144 54646e41 3d656d69
31373131 30343535 fa003339 d66f9dd8 fa8fe180
Feb 15 11:02:34 linuxgw01 kernel: d66f9dd0 d66f9dd4 d66f9dd8
d66f9ddc 00000001 00000000 f953dce8 00000000
Feb 15 11:02:34 linuxgw01 kernel: Call Trace:
Feb 15 11:02:34 linuxgw01 kernel: [<fa8fe180>]
CmaFormatDateAndTimeForXML+0x80/0xe0 [cma]
Feb 15 11:02:34 linuxgw01 kernel: [<fa901a3a>]
CMA_VfsResourceInfoCallback+0x1ea/0x210 [cma]
Feb 15 11:02:34 linuxgw01 kernel: [<fa8fe683>]
CMA_VfsResourceCallback+0x3/0x10 [cma]
Feb 15 11:02:34 linuxgw01 kernel: [<fa8fe408>]
CmaResourceCallback+0x48/0xe0 [cma]
Feb 15 11:02:34 linuxgw01 kernel: [<fa8fff60>]
CMA_VfsResourceConfigCallback+0x0/0x80 [cma]
Feb 15 11:02:34 linuxgw01 kernel: [<fa97032b>]
clstrconf_cluster_resources+0x2b/0x30 [clstrlib]
Feb 15 11:02:34 linuxgw01 kernel: [<fa8eb556>] CrmResourceApi+0x2b6/0x690
[crm]
Feb 15 11:02:34 linuxgw01 kernel: [<fa9071f1>]
CMA_VfsClusterManageCmd+0x341/0x600 [cma]
Feb 15 11:02:34 linuxgw01 kernel: [<c01407b4>]
ckrm_invoke_event_cb_chain+0x24/0x30
Feb 15 11:02:34 linuxgw01 kernel: [<c012e18a>] do_exit+0xa5a/0xd00
Feb 15 11:02:34 linuxgw01 kernel: [<f953a899>]
af_call_kernel_space_thread+0xa9/0xb0 [adminfs]
Feb 15 11:02:34 linuxgw01 kernel: [<f953a7f0>]
af_call_kernel_space_thread+0x0/0xb0 [adminfs]
Feb 15 11:02:34 linuxgw01 kernel: [<c0107005>] kernel_thread_helper+0x5/0x10
Feb 15 11:02:34 linuxgw01 kernel:
Feb 15 11:02:34 linuxgw01 kernel: Code: ff 0b 8b 5c 24 30 8b 74 24 34 8b 7c
24 38 83 c4 3c c3 8d b6