One of the solution which came to mind is to use the identifier prefix for that identifier type (" Manage Patient Identifier Sources" → “Configure OpenMRS ID” → prefix).
We didn’t notice that issue before, kindly create the bug for that in the project Jira space.
If you have any idea how to fix those issue feel free to made changes.
I’m adding to this thread as it seems to attract the right audience.
The server running sync servers is running out of disk for docker. You seem to have 2 containers that each one has almost 10GB of size (sync3refapp_openmrs-referenceapplication_1 and sync1refapp_openmrs-referenceapplication_1).
There’s nothing I can actually delete, so maybe you want to destroy/redeploy those containers before they eat all the disk
Thank you very much for the information. I could take care of it.
However, 10GB (for each one) is a very huge size for those containers (those aren’t databases). Could you first try to identify what exactly consume those memories space? Or maybe can I get ssh access for those servers?
There’s nothing inside those containers that are making them particularly big, so I think you might have a file or folder you are constantly writing and it’s not a docker volume. Maybe logs? Or something. It’s a little bit tricky for me to know which folders are constantly changing (and are on the container, not as a volume).
This seems wrong to me. I still seem to have enough free memory on the system to not think it’s garbage collection. Would you have any idea what’s the JVM/openmrs app is doing using so much CPU?
This is the command. I think you might be reaching your JVM limit. I think you need to increase the memory configuration a little bit (in theory, you still have 4GBs free on the machine in total).
So I checked, and what’s happening is that the docker process is generating a lot of logs. Like, we are talking around more than 8GBs of logs per container.
A little bit excessive if you ask me
There are a lot of exceptions. I’d recommend you redeploy your containers, and make sure they are not so verbose.
Thank you for the update. I redeployed the containers again and decreased the log level. I hope this should help but if you noticed the issue please let me know.
Has anyone done any successful manual push on child nodesync2.openmrs.org previously ?
It keeps throwing a “504 Gateway Time-out” , am thinking it has some issues and needs to be re-deployed .
My self and @irenyak1 have experienced same error trying to reproduce different use cases .