- Log in to post comments
User bio
404 bio not found
Member since Aug 26, 2022
Posts:
Replies:
Looks compliant - and was running fine for a month or so before the 10th of June. Looks suspiciously like a crash of some description (whether Iris specifically, or the laptop more generally that impacted the running Iris).
- Log in to post comments
*** Recovery started at Mon Jun 22 15:43:29 2026
Current default directory: c:\intersystems\irishealth\mgr
Log file directory: .\
WIJ file spec: c:\intersystems\irishealth\mgr\IRIS.WIJ
Recovering local (c:\intersystems\irishealth\mgr\IRIS.WIJ) image journal file...
Starting WIJ recovery for 'c:\intersystems\irishealth\mgr\IRIS.WIJ'.
0 blocks pending in this WIJ.
Exiting with status 3 (Success)
06/22/26-15:43:30:375 (26160) 0 [Generic.Event] Global buffer setting requires attention. Auto-selected 25% of total memory.
06/22/26-15:43:31:101 (26160) 2 [Generic.Event] Failed to allocate 9938MB shared memory using large pages. Switching to small pages.
06/22/26-15:43:31:103 (26160) 0 [Generic.Event] Allocated 9938MB shared memory
06/22/26-15:43:31:105 (26160) 0 [Generic.Event] 8107MB global buffers, 810MB routine buffers, 64MB journal buffers, 633MB buffer descriptors, 300MB heap, 5MB ECP, 18MB miscellaneous
06/22/26-15:43:31:109 (26160) 0 [Crypto.IntelSandyBridgeAESNI] Intel Sandy Bridge or AMD x8 AES-NI instructions detected.
06/22/26-15:43:31:110 (26160) 0 [SIMD] SIMD optimization level: DEFAULT
06/22/26-15:43:31:214 (26160) 2 [Generic.Event] c:\intersystems\irishealth\mgr is locked from
06/22/26-15:43:31:215 (26160) 2 [Generic.Event] WIJ directory locked - System not started
06/22/26-15:43:36:234 (26160) 0 [Generic.Event] Unknown job type exited due to normal termination
06/22/26-15:43:36:718 (34856) 3 irisctl.dll (error during startup):(289) IRIS failed to start. IRIS Control Process terminated abnormally (exit code = 0).This is the content of C:\InterSystems\IRISHealth\mgr\messages.log from when I started from command line.
- Log in to post comments
Certifications & Credly badges:
Followers:
Following:
Colin has not followed anybody yet.
Thanks @Silas Keeter. I did manage to resolve this short of doing a complete reinstall:
The instance then started up correctly, and the single previously setup namespace was present as expected.
In this case (no real data involved) it was just a helpful exercise in troubleshooting, rather than a major panic. I can only presume something happened to the laptop that stopped Iris in such a way it didn't shut down properly and clear its locks - but I don't know what that was. And it was a developer's laptop, not a running server, so I'm not worried!