{"id":12477,"date":"2024-05-13T05:53:26","date_gmt":"2024-05-13T12:53:26","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=12477"},"modified":"2024-05-13T05:53:26","modified_gmt":"2024-05-13T12:53:26","slug":"version-10-released","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/service-protector\/version-10-released\/","title":{"rendered":"Service Protector 10: Advanced Sanity Checks for 100% Uptime"},"content":{"rendered":"
\"Service<\/div>\n

After months of coding and testing, we released Service Protector<\/a> 10.0 on May 10. Here’s a quick rundown of what’s new in this release:<\/p>\n

Restart your Windows Service if a specific drive letter isn’t available<\/h2>\n

Does your Windows Service use files or folders on a mapped drive?<\/p>\n

Or is your service responsible for mapping a drive letter?<\/p>\n

If so, you should use Service Protector’s newest sanity check to detect when the drive mapping fails and promptly restart your service.<\/p>\n

With Service Protector watching the drive, you won’t need to rely on calls from your customers to alert you of a problem. And you won’t have to dial in at all hours to fix your failing software.<\/p>\n

How to monitor a drive mapping<\/h3>\n

The “check drive mapping” sanity check is very easy to use. For example, here’s how to verify that the P drive is always available:<\/p>\n

    \n
  1. \n

    Edit your service in Service Protector (or add a new one if you like).<\/p>\n<\/li>\n

  2. \n

    Switch to the Monitor<\/b> tab.<\/p>\n<\/li>\n

  3. \n

    Check the Whenever it fails a periodic sanity check<\/b> box and click the Set<\/b> button to the right:<\/p>\n

  4. \n

    In the window that comes up, select the Check that a drive is mapped<\/b> entry and click Next<\/b> to proceed:<\/p>\n

  5. \n

    Select the “P” drive:<\/p>\n

  6. \n

    After clicking the Next<\/b> button, specify how often Service Protector should check that the P drive is available. Every 5 minutes is probably good enough:<\/p>\n

  7. \n

    Finally, confirm that the sanity check is configured as you expect. Click Add<\/b> if you’re satisfied:<\/p>\n

  8. \n

    Save your changes in Service Protector.<\/p>\n<\/li>\n<\/ol>\n

    And that’s it. With the sanity check keeping watch, Service Protector will automatically recycle your service if your drive mapping fails.<\/p>\n

    Set a timeout when checking that a HTTP\/HTTPS web server is responding<\/h2>\n

    The web server sanity check now accepts a timeout parameter, to indicate how long to wait for a response from the server before failing the request.<\/p>\n

    Why the change?<\/h3>\n

    Previous versions of Service Protector waited indefinitely for the web server to answer. However, that caused a problem for a customer monitoring Microsoft’s IIS service<\/a>.<\/p>\n

    For some unknown reason, his IIS would occasionally stop serving pages. When that happened, his users accessing the site from a browser would see an error indicating that the site was inaccessible. He configured Service Protector to check his site every couple of minutes and restart IIS if the URL stopped responding.<\/p>\n

    But it didn’t work! Service Protector reported that the service was functioning fine — even when the browser said otherwise.<\/p>\n

    After investigating, we figured out what was going wrong. IIS wasn’t refusing to serve web pages. It was returning the data just fine — but it was taking over 5 minutes to do so!<\/p>\n

    When IIS takes so long to respond, the browser gives up waiting and displays an error. That’s what the users were seeing.<\/p>\n

    But Service Protector would wait patiently for IIS to respond and declare the lengthy process a success. That’s why it wasn’t restarting IIS.<\/p>\n

    We introduced the new timeout option to fix the mismatch. You set the value (in seconds) right below the URL:<\/p>\n

    \"Set<\/a><\/div>\n

    Once the customer configured a 30-second timeout, Service Protector was able to detect the sluggishness and promptly restarted IIS. Problem solved!<\/p>\n

    Easily test if your Windows Service has open TCP\/IP network connections<\/h2>\n

    You couldn’t easily test the TCP\/IP network connections sanity check in previous version of Service Protector. Because of that, the Check now<\/b> button was disabled.<\/p>\n

    Service Protector 10 activates the feature, allowing you to verify the selected service on demand:<\/p>\n

    \"Check<\/a><\/div>\n

    You may find that helpful as you decide how to deploy the sanity check in your environment.<\/p>\n

    For example, here are the results of checking the Print Spooler Windows Service on our machine:<\/p>\n

    \"Print<\/a><\/div>\n

    You can see that the Spooler service has an open listening TCP\/IP connection, as expected.<\/p>\n

    Other fixes & improvements<\/b><\/h2>\n