zrml / ccontainermain Goto Github PK

Hi,
when i run the container i have this error:
docker run -p 57779:57772 -p 1979:1972 cachedb:2017
2017/11/13 09:40:32 Starting Caché...
2017/11/13 09:40:34 Something is preventing Caché from starting in multi-user mode,
2017/11/13 09:40:34 You might want to start the container with the flag -cstart=false to fix it.
2017/11/13 09:40:34 Error: Caché was not brought up successfully.

Hi there,

Thanks so much for providing this code! I'm working on building a Cache + HealthShare container for a development environment and this repo is helping me a lot. Just wanted to leave a note here for others that might have run into a similar problem as me:

When trying to install Cache 2016.2 beta on CentOS 7, I kept getting a "gzip is required for Cache installation error" which was confusing because gzip was already installed. The actual issue was that which was not installed, and one of the checks in the installation script was using which to decide if gzip was installed or not. Adding which to my yum -y install line in the Dockerfile solved the problem!

I think in case when Caché can't be started in normal mode, this container should exit as not started. Because it is difficult to see whats going wrong, while you don't see logs.

fhir-ensemble_1  | Cache is started in single user mode.
fhir-ensemble_1  | To log into Cache, type:
fhir-ensemble_1  |     ccontrol session ENSEMBLE -B
fhir-ensemble_1  | and D ^STURECOV for help recovering from this error.
fhir-ensemble_1  | 09/26/16-14:36:13:485 (36) 0 Write daemon started with strategy #1
fhir-ensemble_1  | 2016/09/26 14:36:13 Something is preventing Caché from starting in multi-user mode,
fhir-ensemble_1  | 2016/09/26 14:36:13 You might want to start the container with the flag -cstart=false to fix it.
fhir-ensemble_1  | 2016/09/26 14:36:13 Caché is up.

Sometime I see that running container can't finish.

daimor@daimor-pc:~$ docker run -it zrml/intersystems-cachedb:2016.2.0.619.0 -shmem=1024
2016/03/19 14:02:07 Starting Caché...

and I can't stop or kill such container, only reboot may help in this case

when I starting container it would be good, if I may see what's going wrong by looking at cconsole.log content in docker's logs.

Travis took ages to go through all the Github projects (I think it was all the private ones linked to the company) ... I left it overnight.

This morning I created a push and the build was successful. I can see it has used the makefile and the .travis.yml.

However, I do not see a new compiled exe where we told it to put.
It's still the old one from September :-(

I have a feeling that the new executable is indeed created in the DIR we specify in the Makefile:
distribution/linux/executable file name
but
it just creates it where it's building it, or in the Travis container :)

I think we would like to have it here in Github

Do we need any other command or trick in the Makefile or other directives in the Travis YML file?

Thanks

How to be if I want to change some settings such as global/routines buffers or anything else.
Sure, I can use my pre-configured cache.cpf file stored outside from container, but it means that I should care about all of this content.
Looks like we need something like path for cache.cpf file just only with some changes

[config]
globals=0,0,1024,0,0,0
routines=128

and before starting caché it may extend original config file