Our development server stopped updating its user interface today. Same symptoms as the DELAY PROCESS bug - the admin graphs like CPU usage stop, the list of connected users goes out of date, uptime calculations reflect the time the internal clock stopped.
Normally we start getting alerts on our production servers because we're in a mirrored enviornment and the journal files start stacking up. Today was the first time that our development server, running interpreted with no mirror code, just stopped updating. > On Jun 18, 2018, at 11:32 AM, Kirk Brooks via 4D_Tech <[email protected]> > wrote: > > Justin, > Yeah, after I responded to you I read Miyako's comment - and your reply. > It's an incredibly frustrating place to be when you do everything right and > the wrong thing still happens. Unlucky. > > I bet the bug is actually someplace else and is manifesting in this DELAY > PROCESS bit. Which doesn't help you find it at the moment, though. Is the > method running this process one of those big, complicated, gnarly types > with all sorts of convoluted branchings and calls to numerous plugins and > dependencies on lots of IP vars? ********************************************************************** 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:[email protected] **********************************************************************
