Escaping special characters in analysis.cfg 🔗 link

Hi all,

I'm trying to monitor the Windows Internal Database service. The Service 
Name is the following:
MSSQL$MICROSOFT##WID

However, thanks to the ## it shows all the characters that follow as 
comment so I added this line with regex to my analysis.cfg
SVC ^MSSQL\$MICROSOFT##WID status=started

This gives following (wrong) output on my webpage:
^MSSQL\$MICROSOFT: No matching service - want started/Any

Is there a way I can monitor this particular service?

Kind regards,

Timothy

On Wed, March 25, 2015 1:00 am, Timothy wrote:

Timothy,

Can you try SVC %^MSSQL\$MICROSOFT\#\#WID as well?


HTH,

-jc

Hi J.C.

still doesn't work. It gives following red alert:
%^MSSQL\$MICROSOFT\: No matching service - want started/Any

In the overview of services however, I see the service as this:
MSSQL$MICROSOFT##WID    automatic    started    Windows Internal Database

Kind regards,

Timothy

On 03/25/2015 09:28 AM, J.C. Cleaver wrote:

SVC %^MSSQL\$MICROSOFT\#\#WID

On 25/03/15 7:00 PM, Timothy wrote:

I have the following working fine:

         SVC "MSSQL$MICROSOFT##WID" startup=automatic status=started

David.

-- 
David Baldwin - Senior Systems Administrator (Datacentres + Networks)
Information and Communication Technology Services
Australian Sports Commission          http://ausport.gov.au
Tel 02 62147830 Fax 02 62141830       PO Box 176 Belconnen ACT 2616
user-cbbf693f2c89@xymon.invalid          1 Leverrier Street Bruce ACT 2617
Our Values: RESPECT + INTEGRITY + TEAMWORK + EXCELLENCE


Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au

This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.

I have a slightly different issue with special characters in analysis.cfg.  Although, I get errors - both tests work fine.

On one server (which was 4.3.0 and recently upgraded to 4.3.18 on Ubuntu 64bit) I get the following errors in xymonlaunch.log:
2015-03-26 11:24:29 xgetenv: Cannot find value for variable MYSERVERNAME1

The only place this seems relevant is from the analysis.cfg file entry:
HOST=myservername1
        SVC IISADMIN status=started
        SVC ReportServer$MYSERVERNAME1 status=started

On a separate Xymon server (4.3.13 Ubuntu 32bit) I do not get errors like those above, the entries in analysis.cfg look like:
HOST=anotherserver1
        SVC MSSQL$SQL_2012 status=started
        SVC SQLAgent$SQL_2012 status=started

Again, both tests work, just one seems to throw errors.

Thanks,
John
Upcoming PTO:

John Rothlisberger
IT Strategy, Infrastructure & Security - Technology Growth Platform
TGP for Business Process Outsourcing
Accenture
XXX.XXX.XXXX office

-----Original Message-----
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of David
Baldwin
Sent: Wednesday, March 25, 2015 5:07 PM
To: Timothy; xymon at xymon.com
Subject: Re: [Xymon] Escaping special characters in analysis.cfg

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy.

www.accenture.com

On Thu, March 26, 2015 5:21 am, user-7adce57665bb@xymon.invalid wrote:

This is being caused by attempted variable substitution in the files
present. "$MYSERVERNAME1" presumably isn't present in the environment, and
libxymon is complaining since it doesn't have an internal default for it
either.

Does encasing that field in quotes solve the problem for you? That might
be the easiest option, as I believe escaping the '$' there will send the
escape downstream.


Regards,

-jc

Alright, that did the trick!

Timothy

On 03/25/2015 11:07 PM, David Baldwin wrote: