Hi, friends!
Is it normal for Orthanc to logs some things twice during initialisation? Does it have anything to do with the jobs engine?
Recently I’ve noticed some logs were logged two times. For instance:
(…)
2019-04-11 11:44:41,937 INFO — [140191671908096] Orthanc.ServerIndex : Starting the monitor for stable resources (stable age = 60)
2019-04-11 11:44:41,937 INFO — [140191680300800] Orthanc.ServerIndex : Starting the database flushing thread (sleep = 10)
2019-04-11 11:44:41,937 INFO — [140191883720640] Orthanc.LuaJobManager : Lua: DICOM associations will be closed after 5 seconds of inactivity
2019-04-11 11:44:41,937 INFO — [140191883720640] Orthanc.LuaScripting : Initializing Lua for the event handler
2019-04-11 11:44:41,939 WARN — [140191883720640] Orthanc.LuaContext : Lua says: Lua toolbox installed
2019-04-11 11:44:41,939 INFO — [140191883720640] Orthanc.LuaScripting : Installing the Lua scripts from: /tmp/orthanc/usr/local/share/orthanc/lua/MirthIntegration.lua
2019-04-11 11:44:41,940 INFO — [140191883720640] Orthanc.LuaJobManager : Lua: DICOM associations will be closed after 5 seconds of inactivity
2019-04-11 11:44:41,941 INFO — [140191883720640] Orthanc.LuaScripting : Initializing Lua for the event handler
2019-04-11 11:44:41,942 WARN — [140191883720640] Orthanc.LuaContext : Lua says: Lua toolbox installed
2019-04-11 11:44:41,942 INFO — [140191883720640] Orthanc.LuaScripting : Installing the Lua scripts from: /tmp/orthanc/usr/local/share/orthanc/lua/MirthIntegration.lua
2019-04-11 11:44:41,943 WARN — [140191883720640] Orthanc.ServerContext : Disk compression is disabled
2019-04-11 11:44:41,943 INFO — [140191883720640] Orthanc.ServerContext : Storing MD5 for attachments: yes
(…)
It started when I began installing scripts. I suppose it’s relating to the jobs engine because it starts with 2 threads and among the lines above you see “LuaJobManager”. So, for all intents and purposes this is actually a hunch.
Thanks!