Module: check_mk
Branch: master
Commit: b5cd92e7311b27dfe9e3e045e04580a9e253ff88
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=b5cd92e7311b27…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Thu Aug 16 12:57:56 2012 +0200
Add new bug entry
---
.bugs/723 | 12 ++++++++++++
checks/megaraid_pdisks | 2 +-
2 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/.bugs/723 b/.bugs/723
new file mode 100644
index 0000000..eecd7ef
--- /dev/null
+++ b/.bugs/723
@@ -0,0 +1,12 @@
+Title: Simulation mode overrides usewalk_hosts
+Component: core
+State: open
+Date: 2012-08-16 12:55:42
+Targetversion: 1.2.0
+Class: nastiness
+
+If you have some hosts defined as usewalk hosts so that they'll check based on their already
+recorded snmpwalks and then enable simulation_mode, it breaks usewalk for some reason.
+The result is that the snmp devices are checked against 127.0.0.1.
+
+This is a big problem if you simulate a customer site.
diff --git a/checks/megaraid_pdisks b/checks/megaraid_pdisks
index bb2f843..8b94aec 100644
--- a/checks/megaraid_pdisks
+++ b/checks/megaraid_pdisks
@@ -72,7 +72,7 @@ def megaraid_pdisks_parse(info):
try:
enclosure_devid = int(line[-1])
# this should fix inventory problems.
- #adapters[adapter][enclosure_devid] = enclosure_devid
+ adapters[adapter][enclosure_devid] = enclosure_devid
except: # no enclosure device
enclosure_devid = 0
Module: check_mk
Branch: master
Commit: e7e56b3932f1944b67d008ad870d786ab401f011
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=e7e56b3932f194…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Thu Aug 16 12:32:21 2012 +0200
livedump: extend documentation to cover recent questions
---
doc/treasures/README.livedump | 12 ++++++++----
1 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/doc/treasures/README.livedump b/doc/treasures/README.livedump
index 8946f4f..797adb2 100644
--- a/doc/treasures/README.livedump
+++ b/doc/treasures/README.livedump
@@ -17,7 +17,7 @@ Disadvantages:
How to setup livedump
---------------------
-Copy the file livedump to a conveniant place. Make sure that
+Copy the file livedump to a convenient place. Make sure that
../livestatus/api/python/livestatus.py is either in the same
directory as livedump or somewhere in the Python path.
@@ -41,14 +41,15 @@ and be in pending state.
Now create a cronjob that does the following every 1 or 5 minutes:
-1. ./livedump > cgagaga
+1. ./livedump > ca1b2c3
2. copy that file to the target system into the checkresults directory
(in OMD this is ~/tmp/nagios/checkresults)
-3. After a correct copy touch the file cgagaga.ok in that
+3. After a correct copy touch the file ca1b2c3.ok in that
directory
Nagios will now read in that file (which is containing all current
-host and service states).
+host and service states). The filename is arbitrary, but has to be
+7 characters in length, starting with a "c".
Filtering
---------
@@ -63,3 +64,6 @@ all hosts that are needed by the dumped services are also dumped:
Note: The -H headers will also be added to the service queries.
Make sure that all columns are prefixed with host_ in these.
+If you are using this is in conjunction with NSCA transport and do not
+wish to transfer the templated configuration, you can use the filter
+to only export services that have "obsess_over_service = 1" set.
Module: check_mk
Branch: master
Commit: 9131d055c588a8ccf7029078b4ce6abd86937294
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=9131d055c588a8…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Thu Aug 16 11:28:20 2012 +0200
Add manual page for cbl_airlaser.hardware. Cant add config example.
---
checkman/cbl_airlaser.hardware | 26 ++++++++++++++++++++++++++
1 files changed, 26 insertions(+), 0 deletions(-)
diff --git a/checkman/cbl_airlaser.hardware b/checkman/cbl_airlaser.hardware
new file mode 100644
index 0000000..83f9c82
--- /dev/null
+++ b/checkman/cbl_airlaser.hardware
@@ -0,0 +1,26 @@
+title: Check of runtime Status CBL Airlaser
+agents: snmp
+author: Florian Heigl <fh(a)mathias-kettner.de>
+license: GPL
+distribution: check_mk
+description:
+ The CBL Airlaser is a device to transparently transport Gigabit Ethernet
+ over an optical link with optional microwave fallback.
+
+ The check queries a list containing all known power and temperature "status"
+ information from the device.
+ If one of the status OIDs indicates an error, the check will go to {WARN} or
+ {CRIT} according to the error reported.
+ For the temperature sensors, default values are included and can be adjusted.
+ If these are exceeded, the check will also alert.
+
+ Note: Monitoring rx/tx attentuation will be added after more testing.
+
+inventory:
+ A service will be generated if the CBL-AIRLASOR-IP1000 MIB is supported by
+ the remote device.
+
+perfdata:
+ the check automatically generates performance data for all sensors that
+ monitor a temperature.
+
Module: check_mk
Branch: master
Commit: 58a346aa1923929e7f717f36ecdef7e96a004ab2
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=58a346aa192392…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Tue Aug 14 12:31:30 2012 +0200
megaraid_pdisks: prepare fix for inventory on systems with active backplanes. Backplane ID was not being inventorized
---
checks/megaraid_pdisks | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/checks/megaraid_pdisks b/checks/megaraid_pdisks
index 53abb49..bb2f843 100644
--- a/checks/megaraid_pdisks
+++ b/checks/megaraid_pdisks
@@ -47,6 +47,9 @@
# On new inventory runs the enclosure number is used as
# index and item part.
megaraid_pdisks_legacy_mode = False
+# This makes service descriptions backward compatible to match
+# inventory made by older versions that didn't support multiple
+# controllers
megaraid_pdisks_adapterstr = ['e','f','g','h','i','j','k','l']
def megaraid_pdisks_parse(info):
@@ -68,6 +71,9 @@ def megaraid_pdisks_parse(info):
elif line[0] == "Enclosure" and line[1] == "Device":
try:
enclosure_devid = int(line[-1])
+ # this should fix inventory problems.
+ #adapters[adapter][enclosure_devid] = enclosure_devid
+
except: # no enclosure device
enclosure_devid = 0
adapters[adapter][0] = 0
Module: check_mk
Branch: master
Commit: 478c787777997c3c5acf8aa4a6a8eda3e72e318d
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=478c787777997c…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Tue Aug 14 11:58:25 2012 +0200
Add new bug entry
---
.bugs/722 | 14 ++++++++++++++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/.bugs/722 b/.bugs/722
new file mode 100644
index 0000000..b0c30e3
--- /dev/null
+++ b/.bugs/722
@@ -0,0 +1,14 @@
+Title: Megaraid pdisks/ldisks naming scheme makeover
+Component: checks
+State: open
+Date: 2012-08-14 11:57:03
+Targetversion: future
+Class: cleanup
+
+after the 1.2 series we should redo the item names for the megaraid devices.
+currently we have not something sane like c0e0s0 (controller, enclosure, slot)
+but instead inject the controller id into a letter that prefixes the enclosure id.
+this is undocumented and not helpful for the end-user - but needed to stay compatible.
+We should just stop being compatible at some point.
+
+If in doubt, see megaraid_pdisks_adapterstr in megaraid_pdisks ;)
Module: check_mk
Branch: master
Commit: e47403b88a274c161923bc184884d908100bb9e5
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=e47403b88a274c…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Mon Aug 13 12:53:46 2012 +0200
Add new bug entry
---
.bugs/720 | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/.bugs/720 b/.bugs/720
new file mode 100644
index 0000000..b65ea1f
--- /dev/null
+++ b/.bugs/720
@@ -0,0 +1,13 @@
+Title: ps and ps.perf output would be much improved if it contained the search filter
+Component: checks
+State: open
+Date: 2012-08-13 12:38:53
+Targetversion: future
+Class: feature
+
+joerg suggested that ps and ps.perf could add another line of output containing the
+the search filter used for finding the process.
+That way a unix admin can immediately determine what process to fix, look for
+and if the monitoring config is correct.
+
+sounds like a great feature.
Module: check_mk
Branch: master
Commit: 7ec34bfafa123ba46a76b1545ef8627f143b03d9
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=7ec34bfafa123b…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Fri Aug 10 16:49:21 2012 +0200
add new bug entries
---
.bugs/717 | 135 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
.bugs/718 | 13 ++++++
.bugs/719 | 11 +++++
3 files changed, 159 insertions(+), 0 deletions(-)
diff --git a/.bugs/717 b/.bugs/717
new file mode 100644
index 0000000..478c3a4
--- /dev/null
+++ b/.bugs/717
@@ -0,0 +1,135 @@
+Title: MegaRaid BBU check should handle learning state
+Component: checks
+State: open
+Date: 2012-08-10 16:35:33
+Targetversion: 1.2.0
+Class: feature
+
+Most MegaRAID controllers come with a rechargable Li battery for the backup voltage.
+This voltage is used to sustain power to the cache ram should the power fail or the OS crash.
+Once the system comes up, the outstanding writes are flushed to disk before OS boot starts.
+
+The newest models use a flash memory bank instead that is fed using a supercap that lasts
+long enough to copy the ram onto flash.
+
+All non-flash models need to do maintenance on their batteries to avoid gas buildup and
+to test remaining capacity. This is called a learn cycle and occurs roughly once a month
+,but the controller does not support setting a schedule.
+
+During the learn cycle, the controller is set to write-through and then the battery is
+discharged a few times, and our check starts to look like a christmas tree.
+
+We need to handle the learn cycle which is detectable.
+If the agent reports "learn cycle requested: yes" then it will sstart at some time,
+and if it says "learn cycle active: yes" then it is running already.
+
+
+Output 1:
+BBU status for Adapter: 0
+
+BatteryType: iBBU
+Voltage: 3251 mV
+Current: -375 mA
+Temperature: 30 C
+
+Battery State : Operational
+
+BBU Firmware Status:
+
+ Charging Status : Discharging
+ Voltage : Low
+ Temperature : OK
+ Learn Cycle Requested : Yes
+ Learn Cycle Active : Yes
+ Learn Cycle Status : OK
+ Learn Cycle Timeout : No
+ I2c Errors Detected : No
+ Battery Pack Missing : No
+ Battery Replacement required : No
+ Remaining Capacity Low : No
+ Periodic Learn Required : No
+ Transparent Learn : No
+ No space to cache offload : No
+ Pack is about to fail & should be replaced : No
+ Cache Offload premium feature required : No
+ Module microcode update required : No
+
+
+
+GasGuageStatus:
+ Fully Discharged : Yes
+ Fully Charged : No
+ Discharging : Yes
+ Initialized : Yes
+ Remaining Time Alarm : Yes
+ Remaining Capacity Alarm: Yes
+ Discharge Terminated : Yes
+ Over Temperature : No
+ Charging Terminated : No
+ Over Charged : No
+
+Relative State of Charge: 0 %
+Charger System State: 49169
+Charger System Ctrl: 0
+Charging current: 100 mA
+Absolute state of charge: 0 %
+Max Error: 8 %
+
+Exit Code: 0x00
+
+
+
+Output 2:
+
+
+BBU status for Adapter: 0
+
+BatteryType: iBBU
+Voltage: 4048 mV
+Current: 139 mA
+Temperature: 27 C
+
+Battery State : Operational
+
+BBU Firmware Status:
+
+ Charging Status : Charging
+ Voltage : OK
+ Temperature : OK
+ Learn Cycle Requested : Yes
+ Learn Cycle Active : No
+ Learn Cycle Status : OK
+ Learn Cycle Timeout : No
+ I2c Errors Detected : No
+ Battery Pack Missing : No
+ Battery Replacement required : No
+ Remaining Capacity Low : No
+ Periodic Learn Required : No
+ Transparent Learn : No
+ No space to cache offload : No
+ Pack is about to fail & should be replaced : No
+ Cache Offload premium feature required : No
+ Module microcode update required : No
+
+
+
+GasGuageStatus:
+ Fully Discharged : No
+ Fully Charged : No
+ Discharging : No
+ Initialized : Yes
+ Remaining Time Alarm : No
+ Remaining Capacity Alarm: No
+ Discharge Terminated : No
+ Over Temperature : No
+ Charging Terminated : No
+ Over Charged : No
+
+Relative State of Charge: 1 %
+Charger System State: 49168
+Charger System Ctrl: 0
+Charging current: 512 mA
+Absolute state of charge: 25 %
+Max Error: 8 %
+
+Exit Code: 0x00
diff --git a/.bugs/718 b/.bugs/718
new file mode 100644
index 0000000..c40b25d
--- /dev/null
+++ b/.bugs/718
@@ -0,0 +1,13 @@
+Title: WATO tags menue has issues when deleting tags
+Component: wato
+State: open
+Date: 2012-08-10 16:42:19
+Targetversion: future
+Class: bug
+
+If you create an empty tag (desc. and tag id) and then another one the empty tag will
+corrupt the tag id's.
+It seems this faulty state is also saved:
+If you delete another tag later on, all tags below the tag you're deleting are also lost.
+
+It's already verified to be a bug ;)
diff --git a/.bugs/719 b/.bugs/719
new file mode 100644
index 0000000..765c771
--- /dev/null
+++ b/.bugs/719
@@ -0,0 +1,11 @@
+Title: if Check should track separate levels for in and out traffic bytes / levels
+Component: checks
+State: open
+Date: 2012-08-10 16:44:48
+Targetversion: future
+Class: feature
+
+Certain customers (ISP, or people with asymetric speeds on an inteface) put different focus
+on interface monitoring - they don't need to detect the 1 out of 10000 clients that has heavy
+traffic, but they need to detect bw excess in either of two directions.
+The check already tracks rx and tx but doesn't allow separate alerting like disk io would.