update v0.1 -> v1.0, what to remove?

jaap....@gmail.com

unread,

Jan 14, 2022, 6:52:37 AM1/14/22

to OpenREM

So I'm running v1.0 on the same server as v0.1 was running (ubuntu server).

As expected, running docker-compose for the first time, resulted in a few errors, due to occupied ports.

To fix this, I manually disable orthanc (systemctl disable orthanc) and nginx. But off course the are more things running. Any suggestions for removing v0.1 completely?

Kind regards, Jaap

Ed McDonagh

unread,

Jan 14, 2022, 5:22:09 PM1/14/22

to jaap....@gmail.com, OpenREM

I would also stop flower, celery and RabbitMQ, if you haven't already.

You could potentially uninstall RabbitMQ and Erlang I'm not sure if uninstalling the one automatically pulls the other, as I think Erlang would have been installed as a dependency of RabbitMQ.

If you have any suggestions for improving the docs, please say! I need to get them finished.

--
You received this message because you are subscribed to the Google Groups "OpenREM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrem+u...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/openrem/5d20a1f1-2157-4831-a882-16ed3137c283n%40googlegroups.com.

jaap....@gmail.com

unread,

Jan 26, 2022, 6:53:56 AM1/26/22

to OpenREM

So a few suggestions for improving the docs.

My situation: Openrem V0.10 running on an offline Ubuntu 18.04 server, every day a cronjob is running to import SR files from our PACS. I installed v1.0 on the same server.

Steps:

1) Offline installation of docker. That can be done with a few hints on e.g. stackoverflow and consists of downloading a few deb files, transferring them to your server and install them. No problem there. However make sure you install docker-compose as well. It does not come standard with an offline docker installation.

2) Offline installation of openrem v1.0 oflline. No problem, the instructions are clear.

3) Stop running services. Use systemctl stop orthanc.service/nginx/rabbitmq-server/openrem-flower/openrem-celery

4) Disable the services. Use systemctl disable orthanc.service/nginx/rabbitmq-server/openrem-flower/openrem-celery. otherwise the services start next time you reboot.

5) Start up openrem v1.0. I could not get this to work due to docker-compose wanting to pull the nginx image (see other thread), so I asked the IT department to open the firewall to docker.io and docker.com temporarily. That solved it. And everything was running

6) Change the cronjobs. The docs suggest a script to automatically import from the PACS, however I ran into 2 problems. First of all docker-compose could not be found by my bash script. This was solved by using absolute filepaths (so /usr/local/bin/docker-compose instead of just docker-compose). Second of all I got an error message stating something about a console. It probably has something to do with the output of the docker container not able to write. I could fix this by adding -T to the script. My bash script works using:

/usr/local/bin/docker-compose -f /home/openrem/openrem_offline/openrem-docker/docker-compose.yml exec -T openrem openrem_qr.py 1 1 -ct -mg -fl -dx -f $WEEKAGO -t $WEEKAGO -e "IMPORT"