Featured Posts

Internet to fall short of IPv4 Addresses soonInternet to fall short of IPv4 Addresses soon The word is out and it is official - Internet is going to fall short of IPv4 addresses in the next 500 days or odd. Computer experts and Industry leaders had expressed their warnings earlier but it seems...

Readmore

Remote Infrastructure Management Services (RIMs) – More to Offer than Cost SavingsRemote Infrastructure Management Services (RIMs) –... Remote Infrastructure Management (RIM) services will be the next growth engine for the offshore service industry as reported by leading consulting agencies and media. In fact, the global RIM industry has...

Readmore

Xobni – Search and Relationship Toolbar for OutlookXobni – Search and Relationship Toolbar for Outlook This is the best Outlook add-in so far from a company called Xobni located in San Francisco. “Xobni” is basically “Inbox” spelled backwards. The main idea behind the development of this plug-in...

Readmore

Open Source versus Open StandardsOpen Source versus Open Standards Everyone’s talking about open source and open standards now-a-days but hardly have I come across any who knows what exactly it contains and what the importance is. I’m putting this post in my blog...

Readmore

Installing Exchange Server 2007 SP1 on Windows Server 2008 for coexistence with Exchange Server 2003Installing Exchange Server 2007 SP1 on Windows Server... In this article I've tried to explain how to install or upgrade an organization running on Exchange Server 2003 to Exchange Server 2007 SP1 on a Windows 2008 Server. In the next post I'll be talking about...

Readmore

  • Prev
  • Next

Nagios and MSSQL 2005

Posted on : 14-07-2008 | By : Vishal Vasu | In : General

Tags:

0

Recently some of the hosts that I monitor and provide server administration support upgraded their MSSQL 2000 to MSSQL 2005. The problem started when we tried to add MSSQL 2005 database service to monitoring. Nagios would simply not check “MSSQL$SQLEXPRESS” and return a Unknown state. Obviously the $ in the middle of the service name was causing the issue. Found out later that we need to use either two $$ or quote the dollar sign so that it shows MSSQL$”$”SQLEXPRESS.

Share:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • LinkedIn
  • Slashdot
  • StumbleUpon
  • Live
  • TwitThis
  • Yahoo! Buzz
  • YahooMyWeb
  • co.mments
  • MSN Reporter
  • MyShare
  • Ping.fm
  • RSS
  • Technorati
  • Yahoo! Bookmarks

Share your views. Write a comment.