Written by

Question Mike Dawson · Oct 3, 2018

Worrying Console log entries

We have started to see Journal Daemon inactive and DBLatency warnings in the Console log of our Healthshare server. OS is Windows Server 2008 running in a VM. See below

10/03/18-00:46:39:344 (3840) 1 Journal Daemon has been inactive with I/O pending for 10 seconds:
gjrnoff=6642068,iocomplete=6637348,filecnt=771,fail=0
10/03/18-10:08:47:620 (6064) 1 [SYSTEM MONITOR] DBLatency(c:\intersystems\healthshare\mgr\cachetemp\) Warning: DBLatency = 2300 ( Warnvalue is 1000).
10/03/18-10:08:47:755 (6064) 1 [SYSTEM MONITOR] DBLatency(d:\databases\adtfeed\) Warning: DBLatency = 1251 ( Warnvalue is 1000).
10/03/18-10:08:47:756 (6064) 1 [SYSTEM MONITOR] DBLatency(d:\databases\bloodbank\) Warning: DBLatency = 1426 ( Warnvalue is 1000).
10/03/18-10:12:08:636 (6064) 1 [SYSTEM MONITOR] DBLatency(c:\intersystems\healthshare\mgr\) Warning: DBLatency = 1813 ( Warnvalue is 1000).

Has anyone else seen this type of warning?

MikeD

Comments

Robert Cemper · Oct 3, 2018

Check performance log and activity on your ESX or whatever your VM is running on. 
It looks like a performance problem of the virtual disk.

0
John Zarate · Sep 7, 2021

Did you every get a resolution?  We are also running VM servers and getting DBLatency errors

0
fu liyun · Sep 7, 2021

OK! DBLatency

Milliseconds to complete a random read from the listed mounted database.

0