We just released a new version of our software a week and a half ago. In this version I added a palette window on the server which runs On Timer. I also added code to most every background process which updates some information every time it wakes up from a Delay Process call. The palette window checks this information and, if it sees a process that has been asleep longer than one minute, resumes the process and sends us a Slack message identifying the server and process that was asleep. If the process does not get resumed, another Slack message is sent so we can handle the issue manually before our customer knows.
Interestingly, this mechanism was triggered on Sunday morning at 1:01 AM for 9 servers. All 9 reported one or more stalled processes within a 60 second time period. -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <can...@synergyfarmsolutions.com> <www.synergyfarmsolutions.com> > On Jun 12, 2018, at 1:43 PM, Jim Crate via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Our server (macOS 10.11, 4D 16.3 HF3 64-bit) hit this bug again last week > after being up for about 22 days. There are 2 separate processes that run > periodically, both at the same time stopped waking from DELAY PROCESS. The > Server window also was not showing the 4D username in the user list, although > IP, machine name, and login date/time were displayed. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
