Not able to disable opengrok mirror feature

[kee98]

This could be similar to my previous question that I asked for suggester: #4266 (reply in thread)

I am trying to debug the performance of my container and after disabling suggestor, I see now opengrok-mirror is occuping the process. However it doesn't take much resource but I think keeps container busy and reindexing doesn't start periodically.

To disable mirror, I tried adding

            - name: NOMIRROR
              value: "true"

as environment variable of container... also created config file to disable mirror of all repos:

projects:
  .* :
    disabled: true

but still I see following commands in log:

command 'opengrok-mirror <command> failed with code -9, breaking

Am I again missing something? Kindly help.

[vladak]

This is recently introduced bug, will be fixed by PR #4274.

[jkjha]

My part of deployment.file:

      containers:
        - env:
            - name: SYNC_PERIOD_MINUTES
              value: "60"
            - name: WORKERS
              value: "50"
            - name: NOMIRROR
              value: "1"
            - name: API_TIMEOUT
              value: "60"
            - name: CHECK_INDEX
              value: "true"
            - name: OPENGROK_SCAN_REPOS
              value: "on"
            - name: OPENGROK_SCAN_DEPTH
              value: "8"
            - name: OPENGROK_GENERATE_HISTORY
              value: "on"
            - name: OPENGROK_SUGGESTTER_ENABLED
              value: "false"
            - name: P4CONFIG
              value: ".p4config"
            - name: READONLY_CONFIG_FILE
              value: "/opengrok/etc/read-only.xml"

and the container is filled with logs related to mirror (failed with error code 9) and reindexing failed with error code 1 (please check the image). I do not see any more detail about the failure to debug...but atleast mirror command should not run right, since its disabled.

[vladak]

The way NOMIRROR environment variable works is that upon seeing it is set, the Docker start program passes special environment variable to opengrok-mirror which then exits right away. So, opengrok-mirror still runs but does not do anything. At least this is how it should work.

[vladak]

The negative error code (-9) is curious, though. When opengrok-mirror detects the special environment variable, it should exit with 0.

[vladak]

Negative return value is signal number which means the opengrok-mirror was terminated with signal 9 (SIGKILL a.k.a. hard kill) for some reason.

[vladak]

Now, the command handling in the OpenGrok Python tools has the capability to terminate processes with SIGTERM and then SIGKILL if the former has no effect, however that only happens if a timeout is set which it is not in the case of the commands run in the Docker container.