I just noticed something odd and am looking for ideas...
As you can see from the top snippet below, snmpd is getting hammered
by something. As a comparison, the load averages for this quad-core
box are usually close to zero.
I'm not even sure I'm using snmpd for anything... not even sure
On Wed, Nov 19, 2008 at 10:57:50AM -0500, John Almberg wrote:
I just noticed something odd and am looking for ideas...
As you can see from the top snippet below, snmpd is getting hammered by
something. As a comparison, the load averages for this quad-core box are
usually close to zero.
On Nov 19, 2008, at 11:49 AM, Jeremy Chadwick wrote:
On Wed, Nov 19, 2008 at 10:57:50AM -0500, John Almberg wrote:
I just noticed something odd and am looking for ideas...
As you can see from the top snippet below, snmpd is getting
hammered by
something. As a comparison, the load averages
taking up 2621MBytes of memory (RSS),
BTW, after restarting, the process was a much more reasonable size.
Another indicator that something had gone seriously wrong with it.
41659 root1 960 23072K 6636K select 0 0:05 0.34% snmpd
Luckily, Monit alerted me to the problem
On Wed, Nov 19, 2008 at 12:11:36PM -0500, John Almberg wrote:
On Nov 19, 2008, at 11:49 AM, Jeremy Chadwick wrote:
On Wed, Nov 19, 2008 at 10:57:50AM -0500, John Almberg wrote:
I just noticed something odd and am looking for ideas...
As you can see from the top snippet below, snmpd is
Now I'm curious about snmp, so perhaps I'll try to figure out how
to get
it to something useful. This machine has 8 hard drives, and is
located in
Manhattan, so I would certainly like to be informed if one of the
raid
drives went on the blink. That was one of the things he was trying
to
On Wed, Nov 19, 2008 at 12:34:55PM -0500, John Almberg wrote:
Now I'm curious about snmp, so perhaps I'll try to figure out how to
get
it to something useful. This machine has 8 hard drives, and is
located in
Manhattan, so I would certainly like to be informed if one of the
raid
drives
This machine has an Intel motherboard and a hardware raid controller.
From what I can tell, there is some Intel software installed on the
machine that makes hardware faults visible to snmp.
That would require Net-SNMP to be linked to that software (or library)
directly. Two things can't just
On Wednesday 19 November 2008 20:37:05 John Almberg wrote:
This machine has an Intel motherboard and a hardware raid controller.
From what I can tell, there is some Intel software installed on the
machine that makes hardware faults visible to snmp.
That would require Net-SNMP to be
On Wed, Nov 19, 2008 at 02:37:05PM -0500, John Almberg wrote:
This machine has an Intel motherboard and a hardware raid controller.
From what I can tell, there is some Intel software installed on the
machine that makes hardware faults visible to snmp.
That would require Net-SNMP to be linked
The card in the box is a
Intel 18E PCI-Express x8 SAS/SATA2 Hardware ROMB RAID with 128MB
Memory
Module and 72 Hour Battery Backup Cache
$625 as shown on the packing list, so I hope it's a good one.
Ah, I think it's hardware RAID, and PCIe to boot. Yes, I would
recommend keeping that!
On Wed, Nov 19, 2008 at 03:47:05PM -0500, John Almberg wrote:
The card in the box is a
Intel 18E PCI-Express x8 SAS/SATA2 Hardware ROMB RAID with 128MB
Memory
Module and 72 Hour Battery Backup Cache
$625 as shown on the packing list, so I hope it's a good one.
Ah, I think it's hardware
John Almberg wrote:
If not, how would I find the driver info? Typical line in fstab:
/dev/mfid0s1a / ufs rw 1 1
Hey!
# mount
to see what is mounted
# sysctl dev.mfi
to see mfi information
I am using mfi in one of my systems. Mfi is LSI
On Nov 19, 2008, at 4:09 PM, Ott Köstner wrote:
John Almberg wrote:
If not, how would I find the driver info? Typical line in fstab:
/dev/mfid0s1a / ufs rw
1 1
Hey!
# mount
to see what is mounted
I did this, but /dev/mfid0s1a didn't
14 matches
Mail list logo
