Windows Service has a trademark symbol in the name...

[dpasacritacrown]

Hi everyone, so I'm in a bit of a pickle. I'm trying to set up monitoring for some services on a server we have here, but I'm running into a problem. Three of the services have a trademark symbol in their name. Like "Company® Service." This is so annoying to me on so many levels, but anyway the big problem is that I'm not able to check the service through Nagios because I can't get it to look for the ® symbol.

Here's my query here:

Code: Select all

$USER1$/check_nt -H $HOSTADDRESS$ -s "password" -p 12489 -v SERVICESTATE -l "BWTI Proship® Enterprise Queue System" -d SHOWALL

With or without the trademark symbol it doesn't work, the output of the test is the same, it just searches for the name without and fails to find anything. I've tried escaping it with \, but no go. What can I do in this situation? Is there anyway to have it look for a wildcard? Thanks!

[lmiltchev]

Do you have "@" in both, the "Service name", and "Display name"?

Services->Right-click->Properties

Have you tried wrapping the name in single quotes?

Code: Select all

'BWTI Proship® Enterprise Queue System'

[dpasacritacrown]

Hmm, so an issue was me not being aware that Windows Services actually had two different names, the display name and the actual name, like you said. The actual name for the service has no trademark symbol, so we're good! Thanks!

But while setting up further monitoring I ran into another problem actually. MSSQL has a "$" in the actual service name for it. Is there any way around that one?? I've tried both double and single quotes and neither help any.

[lmiltchev]

Try the "workaround" below:

https://support.nagios.com/kb/article.php?id=168

[rkennedy]

I believe double quotes and double $$ will escape it as well (in place of the single $). "$$"

[dpasacritacrown]

Oh awesome that worked!!! The thing was I was using the Test Check Command and it wasn't working, but apparently special characters will break that, whereas the actual check will function properly. Monitoring is all set now, you can close this ticket.