https://community.hpe.com/t5/operating-system-linux/proliant-dl-385-and-scsi-snmp/m-p/3861519#M25170 Shalom,<BR /><BR />These issues are usually caused by mismatches between the OS and the actual verion of the OS with patches required by the hpasm tool. <BR /><BR />There may be more evidence in the /var/log/messages file that will let you know the actual cause of the fault. <BR /><BR />You checked the support matrix?<BR /><BR />SEP Tue, 12 Sep 2006 22:06:01 GMT Steven E. Protter 2006-09-12T22:06:01Z https://community.hpe.com/t5/operating-system-linux/proliant-dl-385-and-scsi-snmp/m-p/3861518#M25169 <!--!*#-->I'm trying to get my box to spit out SNMP traps when I have HDD failure, but I'm having difficulties. Anyone have experience with SuSE 9 and the HP hpasm package?<BR /><BR />I've installed net-snmp from HP, and install the hpasm package (7.5.1-8 sles9 x86_64). I get power supply traps ok and fan notifications if I pull one out. But the storage agents are dead on arrival.<BR /><BR />Running a /etc/init.d/hpasm status, I get the following:<BR /><BR />[root@mp-03 /]&gt;&gt; /etc/init.d/hpasm status<BR />hpasmd is running...<BR />Status of Foundation Agents (cmafdtn): cmathreshd cmahostd cmapeerd<BR />cmathreshd is running...<BR />cmahostd is running...<BR />cmapeerd is running...<BR />Status of Server Agents (cmasvr): cmastdeqd cmahealthd cmaperfd<BR />cmastdeqd is running...<BR />cmahealthd is running...<BR />cmaperfd is running...<BR />Status of Storage Agents (cmastor): cmaeventd cmaidad cmafcad cmaided cmascsid c<BR />masasd<BR />cmaeventd is stopped...<BR />cmaidad is stopped...<BR />cmafcad is stopped...<BR />cmaided is running...<BR />cmascsid is stopped...<BR />cmasasd is stopped...<BR /><BR /><BR />Ok. So looking at this, my storage agents are stopped. When I reboot, I get segment faults from the console:<BR /><BR />cmaidad[5605]: segfault at 0000000000000000 rip 0000000000000000 rsp 00000000fff<BR />fdb9c error 14<BR />cmaeventd[5630]: segfault at 0000000000000000 rip 0000000000000000 rsp 00000000f<BR />fffd54c error 14<BR />cmafcad[5632]: segfault at 0000000000000000 rip 0000000000000000 rsp 00000000fff<BR />fdb0c error 14<BR /><BR />When I plug in a monitor to the box, I get different (???) segment fault errors:<BR /><BR />cmaeventd[5628] segfault at 0000000000000000 rip 0000000000000000 rsp 000000ffffd54c error 14<BR />cmaidad[5635]: segfault at 0000000000000000 rip 0000000000000000 rsp 000000ffffdb9c error 14<BR />cmafcad[5643]: segfault at 0000000000000000 rip 0000000000000000 rsp 000000ffffdb0c error 14<BR /><BR /><BR />These ones are specifically related to storage agents.<BR /><BR />Any ideas? <BR /><BR />I noticed that it's not the first time segment faults have been found on this driver:<BR /><BR /><A href="http://h50146.www5.hp.com/products/software/oe/linux/mainstream/bin/support/doc/general/mgmt/ima/v730c/hpasm-7.3.0c-67.sles9.x86_64.rpm.txt" target="_blank">http://h50146.www5.hp.com/products/software/oe/linux/mainstream/bin/support/doc/general/mgmt/ima/v730c/hpasm-7.3.0c-67.sles9.x86_64.rpm.txt</A><BR /><BR /> Tue, 12 Sep 2006 15:38:28 GMT https://community.hpe.com/t5/operating-system-linux/proliant-dl-385-and-scsi-snmp/m-p/3861518#M25169 Christian Charette 2006-09-12T15:38:28Z https://community.hpe.com/t5/operating-system-linux/proliant-dl-385-and-scsi-snmp/m-p/3861519#M25170 Shalom,<BR /><BR />These issues are usually caused by mismatches between the OS and the actual verion of the OS with patches required by the hpasm tool. <BR /><BR />There may be more evidence in the /var/log/messages file that will let you know the actual cause of the fault. <BR /><BR />You checked the support matrix?<BR /><BR />SEP Tue, 12 Sep 2006 22:06:01 GMT https://community.hpe.com/t5/operating-system-linux/proliant-dl-385-and-scsi-snmp/m-p/3861519#M25170 Steven E. Protter 2006-09-12T22:06:01Z