Strange OMSA-behaviour?

Teemu Suutari temisu at utu.fi
Mon Dec 16 06:45:00 CST 2002


I'm using OMSA-client (sa v4.7) on our PE2600. It works otherwise quite
nicely but the 'dcstor32d'-process increases it's memory footprint
steadily. I think that this problem is related to the logging and/or
queuing in the snmp-system, for example all the 'eventLog*' related
entries overflow because they have more than 65k entries. Could those
be cleaned away somehow, or should I just put a cron-script that
restarts omsa weekly? Documentation about the snmp-interface seems
to be nonexistant.

Other notable thing is the actual messages that are in the
'eventLogRecord.1'. It loops randomly these 6 messages:

MIB-Dell-10892::eventLogRecord.1.1524 = STRING: "Power Supply 2 power
supply sensor returned to normal state"
MIB-Dell-10892::eventLogRecord.1.1525 = STRING: "Power Supply 2 power
supply sensor Power Supply Removed"
MIB-Dell-10892::eventLogRecord.1.1526 = STRING: "Power Supply 1 power
supply sensor returned to normal state"
MIB-Dell-10892::eventLogRecord.1.1527 = STRING: "Power Supply 1 power
supply sensor Power Supply Removed"
MIB-Dell-10892::eventLogRecord.1.1528 = STRING: "Bezel Intrusion sensor
detected an intrusion"
MIB-Dell-10892::eventLogRecord.1.1529 = STRING: "Bezel Intrusion sensor
return to normal"

We've had one blown out power-unit, could it be that loud bang
which destroyed the PO has also damaged sensors?
Does somebody else have this kind of problems?

As a symptom (or a cause) the (esm) board seems to generate a lot of
IRQ-traffic: Here's /proc/interrupts

           CPU0       CPU1       CPU2       CPU3
  0:   25837384   25838629   25838542   25838086    IO-APIC-edge  timer
  1:          1          0          0          1    IO-APIC-edge  keyboard
  2:          0          0          0          0          XT-PIC  cascade
  4:    1536490    1537144    1537775    1536916    IO-APIC-edge  serial
  8:          0          0          0          0    IO-APIC-edge  rtc
 10:    8783281    8781592    8783888    8781857    IO-APIC-edge  esm
 28:     801055     798285     800275     802249   IO-APIC-level  eth0
 56:      14805      14696      14801      14689   IO-APIC-level  aic7xxx
 57:          4          4          4          4   IO-APIC-level  aic7xxx
 72:     652923     642179     652818     653611   IO-APIC-level  megaraid
NMI:          0          0          0          0
LOC:  103350527  103350525  103350525  103350526
ERR:          0
MIS:          0

One possible explanation on the strange behaviour would be that
if I did not installed the omsa correctly since I am not running any
specific distro (and hence not rpm). And the kernel that is on use
is linux-2.4.20-pre10-ac2 with some performance/security patches and
kernel modules disabled, so I had to patch the esm-driver directly to
the kernel. Altough this task seemed to be quite straightforward, I
could have missed something... Anyway since the driver is mostly
binary-only I can't tell.

Anyway, If someone could share expiriences in troubleshooting OMSA,
I would greatly appreciate it.




More information about the Linux-PowerEdge mailing list