Author Topic: Custom Alerts Stopped Working...  (Read 256 times)

jg

  • Strong Breeze
  • ***
  • Posts: 146
Custom Alerts Stopped Working...
« on: January 07, 2018, 12:34:03 PM »
Every few months my custom alerts stop working and I have to reboot weathercat, but the monthly/annual records are still being sent (which rules out a problem with the mail server/queue).  Anyone else having this problem?  Most of mine are for wind speeds, rainfall and exceeded temperature thresholds. I'm running 2.44 on a Mac Mini OS 10.11.6

elagache

  • Global Moderator
  • Storm
  • *****
  • Posts: 4891
    • DW3835
    • KCAORIND10
    • Canebas Weather
  • Station Details: Davis Vantage Pro-2, MacBook Pro (Early 2011)
How long do you run WeatherCat? (Re: Custom Alerts Stopped Working...)
« Reply #1 on: January 08, 2018, 12:02:09 AM »
Dear jg and WeatherCat troubleshooters,

Every few months my custom alerts stop working and I have to reboot weathercat, but the monthly/annual records are still being sent (which rules out a problem with the mail server/queue).  Anyone else having this problem? 

Every few months!?!??  You might have the record for the longest running WeatherCat processes!  Congratulations on that.  Alas, that means we probably can't help with this problem.  These days I have to reboot usually less than once a week because I run out of free memory.

Anyone else have a thought?

Cheers, Edouard

jg

  • Strong Breeze
  • ***
  • Posts: 146
Re: Custom Alerts Stopped Working...
« Reply #2 on: January 08, 2018, 02:54:37 PM »
Is there an easy way to automate the reboot process of WeatherCat (i.e, every Sunday at 1AM or something)?

xairbusdriver

  • Storm
  • *****
  • Posts: 2116
    • EW7115 (E7115)
    • KTNGERMA20
    • Mid-South Weather
  • Station Details: Davis VP2 wireless + remote Anemometer/2014 Mac min - 10.13.4/WC 3.0
Re: Custom Alerts Stopped Working...
« Reply #3 on: January 08, 2018, 03:54:50 PM »
If you really want to do that, you could create a launch daemon (basically a plist used by the OS). There are several GUI-based apps that make that a very simple task. My favorite one is LaunchControl.app. This site has over a dozen other alternatives.

It may be a bit more difficult since WC needs to 'see' the Quit command twice. However, the Manual suggests a very simple AppleScript that can handle that for you and that the launch daemon can initiate.

I'm not sure why you would want to limit this operation to just WC. You already have the ability to schedule a complete Shut Down and Start up process with the Energy Saver System Prefs. Using that process would eliminate 'problems' from not only WC but any and all other apps (as well as System tasks) that may be creating memory leaks, etc.

I think the majority of WC users operate the app on computers running 24/7. Many of us use dedicated, older Macs and only Quit WC when the OS requires an update. I think the better solution is to determine the 'illness' rather than 'treating the symptoms'.  :) [tup]