Problem with single % character in UNC test name

When you post information about some problem, please include the following details: - OS version (e.g. Windows 2000 Professional SP3); HostMonitor version; problem description.
Post Reply
CapQwerty
Posts: 36
Joined: Wed Dec 14, 2005 3:58 pm

Problem with single % character in UNC test name

Post by CapQwerty »

We've encountered a bug when using a single % character in the test name of a UNC test.

We are using the UNC free space test to check the amount of free space on an Unix mount point. In the alert profile, we have an action to execute an external program which sends out an alert. The command line to execute includes the %TestName% macro so we know which test has gone bad.

- If the test name has no % characters in it then everything works fine (e.g. the test name comes through to the command line as "machine /var free space")
- If the test name has a single % character in it then the command line turns into gibberish where the % character should be (e.g. "machine /var 9:57 AM9r10499ol25]]><-57a210><9:57 AMi210><![2010-02-25 09:57:49 AM25A9:57 AMA[2010-02-25 09:57:49 A2]]><-9:57 AMi210><499:57 AMa9:57 AMu49....")
- If the test name has a double % character (%%) then everything works fine and it comes through as a single % character (e.g. "machine /var % free space")
- Any macros in the test name (e.g. %agent%) work fine
- If the test type is something other than UNC (e.g. CPU, WMI) then using a single % character in the name is fine

We are running HostMonitor v. 8.32 as a service on Windows Server 2003 R2 Enterprise Edition w/ SP2. The test is being executed by an RMA running on AIX.
KS-Soft
Posts: 13012
Joined: Wed Apr 03, 2002 6:00 pm
Location: USA
Contact:

Post by KS-Soft »

We cannot reproduce the problem. May we see your settings? You may send HML file with tests and actions.lst file to support@ks-soft.net
If the test type is something other than UNC (e.g. CPU, WMI) then using a single % character in the name is fine
Actually all variables processed by the same module, %TestName% variable works in the same way for all test methods...

Regards
Alex
Post Reply