Unable to change env variable MAX_COMMIT_ITERATIONS in Docker Container

We are currently running GenieACS from a docker container Image. I Followed this instalation tutorial:

My current version is: v1.2.13+2407184eca

I used docker-compose for setting up the application. Here are my enviroment variables:

- GENIEACS_UI_JWT_SECRET= ---

- GENIEACS_CWMP_ACCESS_LOG_FILE=/var/log/genieacs/genieacs-cwmp-access.log

- GENIEACS_NBI_ACCESS_LOG_FILE=/var/log/genieacs/genieacs-nbi-access.log

- GENIEACS_FS_ACCESS_LOG_FILE=/var/log/genieacs/genieacs-fs-access.log

- GENIEACS_UI_ACCESS_LOG_FILE=/var/log/genieacs/genieacs-ui-access.log

- GENIEACS_DEBUG_FILE=/var/log/genieacs/genieacs-debug.yaml
            
- GENIEACS_EXT_DIR=/opt/genieacs/ext

- GENIEACS_MONGODB_CONNECTION_URL=mongodb://mongo/genieacs
            
- GENIEACS_MAX_COMMIT_ITERATIONS=512
            
- GENIEACS_EXT_TIMEOUT=30000

I ran into the fault “too many commits iterations” after running a heavy provision script. I tried changing several times the value of GENIEACS_MAX_COMMIT_ITERATIONS but the provision returned the same error at the same part of the script. It appears this doesn’t make any change.

I ran the same script in a test server that has GenieACS installed directly with npm acording to installation process in docs. The script ran into the same error until I changed GENIEACS_MAX_COMMIT_ITERATIONS=64 in genieacs.env.

In my docker image, i kept falling into commits fault even with GENIEACS_MAX_COMMIT_ITERATIONS=512.

After changing the evn variables in docker-compose.yml I executed docker restart.

Can any one help me with this issue.

You need to solve the actual issue. Changing the MAX_COMMIT_ITERATIONS to a value 16x the default is not going to work.

For the CPE in question, enable debug logging, then look through the values being sent to the CPE. You will find that one of the parameters is being set to a changing value.