I've released a new version of the check. I've changed the Windows plugin. It is now a pure Powershell script, not a command script anymore. It should run smoothly to avoid problems, which some of you had in the past running the plugin.
To update it's enough to download the new check package, install it in your check_mk instance by a command like this:
cmk -vP install Ex2010_MBDB_Info-1.3.1.mkp
and substitute the cmd file on your Exchange server by the Ex2010_MBDB_Info.ps1 file from the new package.
You can find the new version of the package at the known place at the check_mk plugin exchange site.
Subscribe to:
Post Comments (Atom)
Hi, I tried the new version, now it can't find "iis_status.ps1". Where do I get this?
Best regards,
Manfred
Anonymous
30 January, 2013 16:56Hi Manfred,
thanks for your feedback! It's been a silly typo in the agent script. I've corrected the error and put the corrected package in to Check_mk exchange. You can substitute iis_reset.ps1 with Ex2010_MBDB_Info.ps1 in the agent script, if you don't want to download the updated package.
Unknown
30 January, 2013 17:47Hi,
thanks for your quick response. I've changed the name (and removed the last } in the file) and the script now works.
But in check_mk I get the following error:
UNKNOWN - invalid output from agent, ...
In the debug-log I have this:
ValueError: invalid literal for int() with base 10: 'Database'
Agent info: [['Mailbox', 'Database', '2012100516', '24167645184', '16']]
So I assume the output is correct (name and size of the database and number of accounts), but check_mk don't know where to put it.
Best regards,
Manfred
Anonymous
31 January, 2013 09:21Hmm.. a strange thing, I've never got the error before. What is the output of the agent, if you execute it in the powershell on the Exchange server. My output is here:
[PS] C:\>& 'C:\Program Files (x86)\check_mk\plugins\Ex2010_MBDB_Info.ps1'
<<>>
Database1 123220328448 20
Database2 2692808704 5
Database3 9001041920 11
Database4 25241911296 217
Database5 8454144
Database6 1350631424 6
Database7 3632332800 9
Database8 72888680448 32
Database9 38126288896 21
Database10 10880090112 6
Database11 46045134848 22
Database12 134226182144 43
Database13 163218259968 59
Database14 234084696064 53
Does the mailbox database name of your Exchange contain a space or a non ascii char like umlaut?
Unknown
31 January, 2013 09:40Maybe that's the problem: the database name is "Mailbox Database 2012100516" (two spaces).
The output in powershell is
Mailbox Database 2012100516 24167645184 16
Anonymous
31 January, 2013 10:12Thanks for feedback, Manfred!
Yes, the spaces in the Mailbox-DB name seem to cause the problem. The check cannot parse such input. Either you change the name to something without spaces or you must wait until I've changed the check. Or you can provide your patch :-)
Unknown
31 January, 2013 10:30Just wanted to answer you with my "patch". I have only one database, so my quick fix was to replace $_.name with a static name ("HL"), so the output is now HL 24167645184 16 and everything is fine.
The other option is to change the (default) name of the database, it seems easy to do.
Thanks for your support!
Anonymous
31 January, 2013 10:38I've released a new corrected version, which should be robuster and not stumble upon spaces in mailbox database names. Please look at the newest article for more details.
Unknown
21 February, 2013 10:53Hallo,
i get an error message:
Unerwartetes Token "}" im Ausdruck oder in der Anweisung.
Bei C:\Install\Nagios-Agent_1.2.2p1\plugins\Ex2010_MBDB_Info.ps1:16 Zeichen:2
+ } <<<<
+ CategoryInfo : ParserError: (}:String) [], ParseException
+ FullyQualifiedErrorId : UnexpectedToken
This is version 1.3.1 of your script.
Marcel
16 April, 2013 08:57Auch hallo :-)
please make sure that the script's body is OK, meant: not damaged. You can look at http://poshcode.org/4110 for a hint. Or copy the script from there. Have you already seen that I published a new version some weeks ago?
Best regards
Hermann Maurer
Unknown
16 April, 2013 09:30OK it seems to be a typo? The very last "}" is definitely superfluous. The script runs after removing this character.
I now simply have the following problem:
These PS script runs fine locally and finishes very quickly.
But if I execute it through the agent, it takes 1-2 minutes to finish, and this generally causes a Nagios critical state for the "Check_MK" service.
What could cause this? If there's no solution, can I work around it by somehow increasing the agent response time out limit?
Marcel
16 April, 2013 09:45I haven't any ideas... It takes 10-11 seconds for check_mk to check each of my four servers, which have up to 20 mailbox databases. Try to execute
cmk -d and look at the output to understand what might be wrong.
Unknown
17 April, 2013 18:47Hi all,
i also tried the plugin
When I run it by hand no problem, but when i run it as plugin allot of powershell services are started and the server is going to 100 % cpu ?
what am i doing wrong
hope you can help me out :)
regards
Peter Jonkers
Anonymous
05 August, 2013 23:42I get the following output from cmk -d:
Unerwartetes Token "}" im Ausdruck oder in der Anweisung.
Bei C:\Program Files (x86)\check_mk\plugins\Ex2010_MBDB_Info.ps1:16 Zeichen:2
+ } <<<<
+ CategoryInfo : ParserError: (}:String) [], ParseException
+ FullyQualifiedErrorId : UnexpectedToken
If I remove the last } in the PowerShell-Script the output from [PS] C:\>& 'C:\Program Files (x86)\check_mk\plugins\Ex2010_MBDB_Info.ps1' looks ok. The output from cmk -d begins with:
<<>>
#< CLIXML
DB01 142671872 5
....
Anonymous
22 October, 2013 22:00