Interesting.  I did some more digging and here is what I’ve found.

I have 13 Macs that run up to 10 databases on each machine of differing 4D 
versions  (usually 4Dv13.4, 4Dv15R5 and 4Dv16.0) - all are 32 bit.  I focused 
on 2.

Machine 1 - uptime 158 days

I have 10 databases running on this machine.  3 are running using 4D v13.4, 2 
are running v15R5 and the other 5 are running v16.0.

The ones running v13.4 are not having this issue.  All of the other ones are.
 
Machine 2 - uptime 86 days

I have 9 databases running on this machine.  3 are running 4Dv13.4 and 6 are 
running 4Dv16.0.

None of the 4Dv13.4 databases have the problem.   None of the 4Dv16.0 databases 
on this machine have experienced this problem.


Jeff: I can confirm that the 4D Server UI monitor for graphs does stop updating 
when this occurs.  On Machine 1, the only one that is working now is the one I 
manually resumed the processes for.  On machine 2, all of the graphs are 
working just fine.

The code dealing with these server processes has been running just fine for 
many, many years.

Thanks!

David Conley
By The Book, Inc.
Office: 815-234-7530
Direct Line: 815-406-5502
Fax: 815-234-7532
http://www.bythebook.com




> On Oct 25, 2017, at 9:37 AM, Cannon Smith via 4D_Tech <[email protected]> 
> wrote:
> 
> Hi Keith,
> 
> Yes, that’s why I was curious about the machine up time. It would be curious 
> if it was close to 24.86 days, for example.
> 








This email was sent to [email protected] (mailto:[email protected])
unsubscribe from this list 
(http://emailclicks.bythebook.com/track/unsub.php?u=30055319&id=9677e92f5f6e4a8c99f800ea10e5b871.6uKpduIsjJ%2FEqVQ1r%2BdLr66Tu1w%3D&r=https%3A%2F%2Fmandrillapp.com%2Funsub%3Fmd_email%3D4d_tech%2540lists.4d.com)
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:[email protected]
**********************************************************************

Reply via email to