{"id":3487,"date":"2018-01-29T05:38:34","date_gmt":"2018-01-29T13:38:34","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=3487"},"modified":"2022-05-01T22:44:08","modified_gmt":"2022-05-02T05:44:08","slug":"restart-idle-application","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/restart-idle-application\/","title":{"rendered":"Q & A: Can AlwaysUp Kill & Restart my Idle Application?"},"content":{"rendered":"
\"Q<\/div>\n
\n  I’m using ncrack<\/a> to monitor our network. I recently started running it as a windows service under AlwaysUp<\/a>. Everything is working perfectly except that sometimes ncrack stops capturing traffic. The CPU goes to zero and nothing else is written to the log files. Is there some way to get AlwaysUp to terminate ncrack and start a fresh instance?<\/b><\/p>\n

— Michael<\/p>\n<\/div>\n

\nHi Michael. AlwaysUp doesn’t have an “idle CPU” monitor built in, but you can use a Sanity Check Plugin<\/a> to solve your problem.\n<\/p>\n

\nWhat is a “Sanity Check Plugin” you ask?\n<\/p>\n

\nThe Sanity Check feature allows AlwaysUp to detect arbitrary problems with your application running as a windows service. At its heart is a special plugin (a script or executable) that informs AlwaysUp when decisive action — such as restarting your application or rebooting the machine — is necessary. Dig into the technical details at the Sanity Check page<\/a>.\n<\/p>\n

\nOur pre-configured CheckForCPUActivity<\/a> plugin will empower AlwaysUp to restart ncrack if it sits idle for too long. Here is how to set it up:\n<\/p>\n

    \n
  1. \n

    \nFirst, make sure that you have AlwaysUp version 10.2 or later on your machine. That release (from June 2017) introduced important enhancements to the Sanity Check feature.\n<\/p>\n

    \nSelect Help > About AlwaysUp…<\/b> to check what version of AlwaysUp you have installed:<\/p>\n

  2. \n

    \nNext, download the CheckForCPUActivity utility<\/a> from our web site. Save it in your AlwaysUp installation folder, usually C:\\Program Files (x86)\\AlwaysUp\\<\/nobr><\/b>\n<\/p>\n<\/li>\n

  3. \n

    \nEdit your application in AlwaysUp.\n<\/p>\n<\/li>\n

  4. \n

    \nSwitch to the Monitor<\/b> tab. Check the Whenever it fails a “sanity check”<\/b> box and click the triple-dots button:<\/p>\n

  5. \n

    \nWorking with the “Configure Sanity Check” window that comes up:\n<\/p>\n

      \n
    1. \n

      In the Run<\/b> field, enter the following command line:<\/p>\n

      "C:\\Program Files (x86)\\AlwaysUp
      \n\\CheckForCPUActivity.exe" $ALWAYSUP_PID 60<\/b><\/p><\/blockquote>\n

      \nThis will check ncrack for any CPU activity over 60 seconds.\n<\/p>\n<\/li>\n

    2. \n

      Using the Every<\/b> controls, specify how often AlwaysUp should inspect ncrack. Every 10 minutes should be sufficient but feel free to tune as you like.<\/p>\n

    3. \n

      \nClick the OK<\/b> button.\n<\/p>\n<\/li>\n<\/ol>\n<\/li>\n

    4. \n

      \nAnd finally, click the Save >><\/b> button to record your changes.\n<\/p>\n<\/li>\n<\/ol>\n

      <\/p>\n

      \nWith these settings in place, AlwaysUp will launch CheckForCPUActivity every 10 minutes. Each run will watch ncrack for 60 seconds and if no CPU activity is detected over that period, AlwaysUp will restart ncrack.\n<\/p>\n

      <\/p>\n

      \nA note to other customers: This approach will work with any application where minimal CPU usage indicates a failure.<\/b> The solution presented is not specific to ncrack.\n<\/p>\n

      <\/p>\n

      \nBest of luck with your windows service!<\/p>\n