Question
Daniel Kutac · Feb 7, 2020

InterSystems IRIS for Health 202.1 Preview - Docker issue

Hi guys,

I thought I test the InterSystems IRIS for Health 2020.1, the Docker image. but for some reason, the container only lives for about 10 seconds and I can see from the message.log file that as soon as IRIS starts it then performs shutdown thus ending also container. Anyone else seen this?

 

here is the message.log part

 

*** Recovery started at Fri Feb  7 14:37:02 2020
     Current default directory: /durable/iris-config/mgr
     Log file directory: /durable/iris-config/mgr/
     WIJ file spec: /durable/iris-config/mgr/IRIS.WIJ
Recovering local (/durable/iris-config/mgr/IRIS.WIJ) image journal file...
Starting WIJ recovery for '/durable/iris-config/mgr/IRIS.WIJ'.
  0 blocks pending in this WIJ.
Exiting with status 3 (Success)
02/07/20-14:37:02:433 (760) 0 [Generic.Event] Automatically configuring buffers
02/07/20-14:37:02:494 (760) 0 [Generic.Event] Allocated 1528MB shared memory: 1024MB global buffers, 300MB routine buffers
02/07/20-14:37:02:495 (760) 0 [Crypto.IntelSandyBridgeAESNI] Intel Sandy Bridge AES-NI instructions detected.
02/07/20-14:37:02:532 (760) 0 [WriteDaemon.UsingWIJFile] Using WIJ file: /durable/iris-config/mgr/IRIS.WIJ
02/07/20-14:37:02:532 (760) 0 [Generic.Event] No journaling info from prior system
02/07/20-14:37:02:533 (760) 0 [Generic.Event] InterSystems IRIS is started with NOSTU option.
02/07/20-14:37:02:546 (761) 0 [WriteDaemon.Started] Write daemon started.
02/07/20-14:37:02:636 (760) 0 [Generic.Event] 
Startup of InterSystems IRIS [IRIS for UNIX (Ubuntu Server LTS for x86-64 Containers) 2020.1 (Build 197U) Thu Jan 23 2020 10:15:13 EST]
    in /usr/irissys/bin/
    with mgr: /durable/iris-config/mgr
    with wij: /durable/iris-config/mgr/IRIS.WIJ
    from: /durable/iris-config/mgr/
  OS=[Linux], version=[#30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020], release=[5.3.0-28-generic], machine=[x86_64]
  nodename=[iris].
  numasyncwijbuf: 0, swdwrtmax: 0, wijdirectio: off, synctype: 3
  System Initialized.
02/07/20-14:37:02:656 (792) 0 [Database.MountedRW] Mounted database /durable/iris-config/mgr/ (SFN 0) read-write.
02/07/20-14:37:02:660 (761) 1 [Generic.Event] Cannot lock /usr/irissys/mgr/irislib/ err(13): will try accessing readonly
02/07/20-14:37:02:661 (792) 0 [Database.MountedRO] Mounted database /usr/irissys/mgr/irislib/ (SFN 1) read-only. File or filesystem allows read-only access. 
02/07/20-14:37:02:666 (792) 0 [Database.MountedRW] Mounted database /durable/iris-config/mgr/irislocaldata/ (SFN 2) read-write.
02/07/20-14:37:02:670 (792) 0 [Generic.Event] init_gcr_seed:  gen_crypt_rand seeded from /dev/urandom:  64 bytes.
02/07/20-14:37:02:708 (799) 0 [Utility.Event] Shutting down InterSystems IRIS
02/07/20-14:37:02:708 (799) 0 [Utility.Event] Notifying Clients
02/07/20-14:37:02:709 (799) 0 [Utility.Event] No user shutdown routines to execute
02/07/20-14:37:02:709 (799) 0 [Utility.Event] Stopping User Jobs
02/07/20-14:37:02:710 (799) 0 [Utility.Event] Stopping Network Servers
02/07/20-14:37:02:710 (799) 0 [Utility.Event] Withdrawing from License Domain
02/07/20-14:37:02:711 (799) 0 [Utility.Event] Waiting for users to stop
02/07/20-14:37:02:711 (799) 0 [Utility.Event] Stopping Client Networking
02/07/20-14:37:02:711 (799) 0 [Utility.Event] Removing database locks
02/07/20-14:37:02:711 (799) 0 [Utility.Event] Updating Journal File
02/07/20-14:37:02:712 (799) 0 [Utility.Event] Journal restore not required at next startup
02/07/20-14:37:02:712 (799) 0 [Utility.Event] Transaction rollback not required at next startup
02/07/20-14:37:04:713 (799) 0 [Utility.Event] Waiting for database updates to complete
02/07/20-14:37:04:713 (799) 0 [Utility.Event] Database updates complete
02/07/20-14:37:04:713 (799) 0 [Utility.Event] Stopping System Jobs
02/07/20-14:37:04:814 (771) 0 [Generic.Event] EXPDMN exited due to system shutdown
02/07/20-14:37:04:815 (763) 0 [Generic.Event] JRNDMN exited due to system shutdown
02/07/20-14:37:04:815 (762) 0 [Generic.Event] GARCOL exited due to system shutdown
02/07/20-14:37:04:916 (764) 0 [Generic.Event] SWRTDMN #1 exited due to system shutdown
02/07/20-14:37:04:916 (767) 0 [Generic.Event] SWRTDMN #2 exited due to system shutdown
02/07/20-14:37:04:917 (765) 0 [Generic.Event] SWRTDMN #3 exited due to system shutdown
02/07/20-14:37:04:917 (768) 0 [Generic.Event] SWRTDMN #4 exited due to system shutdown
02/07/20-14:37:04:917 (766) 0 [Generic.Event] SWRTDMN #5 exited due to system shutdown
02/07/20-14:37:04:917 (770) 0 [Generic.Event] SWRTDMN #6 exited due to system shutdown
02/07/20-14:37:04:917 (769) 0 [Generic.Event] SWRTDMN #7 exited due to system shutdown
02/07/20-14:37:05:420 (761) 0 [Generic.Event] No blocks pending in WIJ file
02/07/20-14:37:05:420 (761) 0 [Generic.Event] WRTDMN exited due to system shutdown
02/07/20-14:37:05:519 (760) 0 [Generic.Event] CONTROL exited due to system shutdown
02/07/20-14:37:06:619 (799) 0 [Utility.Event] Shutdown complete

 

thank you for suggestion where else to search for the source of issue.. I admit I may have something wrong with my docker configuration script as standard kits work just fine.

 

Dan
 

 

 

00
0 3 131 1

Replies

Hi Dan.

Sometimes it happens because you are out of resources in docker desktop.

Different options of docker prune could help. E.g.

docker system prune -f

Read more in @Dmitriy Maslennikov article. 

Unfortunately, that did not help. I'll investigate further.

it turned out to be access privileges issue with license file, what a silly mistake of mine. Anyway, thank you Evgeny for pointing me to some useful info, anyway!