Error executing GIT command git commit

Frequently observing git issue when changing existing configuration. For example deactivate / disable a connection at distributed monitoring, I observe the following git error;

Error executing GIT command git commit --author "<first.last@domain.tld>" 
-m "Activating changes of Livestatus Proxy configuration, Modified site connection esxi, 
Modified site connection esxi":

On branch master
Your branch is up to date with 'upstream/master'.
Changes not staged for commit:

(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)

modified: multisite.d/sites.mk
no changes added to commit (use "git add" and/or "git commit -a")

Command Line report, more or less the same.

OMD[mysite]:~/etc/check_mk$ git status
On branch master
Your branch is up to date with 'upstream/master'.

Changes not staged for commit:

  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)

        modified:   multisite.d/sites.mk
no changes added to commit (use "git add" and/or "git commit -a")

When I now revert the configuration, after activate in WATO, I do not observe any git issue (?) Changing anything again with the connection I got the git error again.

Any ideas, suggestions welcome.

1 Like

@robin.gierse Is this something you can also look into?
The bug brings up ui-errors if you edit distributed monitoring-settings. Also I found related ui-errors when I do the following: go to “users” (overview over all uses) and change the sorting eg. click on “last seen”.

Some information about platform and Checkmk version you guys are using?

Also, do you do modify any files on the command line?

1 Like

CheckMK Version 2.0.0p15 - Alma Linux 8.5. No changes on the command line. Very strange we only see this every second time/change.

Change something - error message - but change will be applied(?)
Change back - no message - change also will be applied

So the only problem is the message itself, that’s why it is not so serious for us at the moment.

1 Like

Did you clean up the local repository manually? Like git add /path/to/file && git commit?
Maybe something went wrong at some point and is now causing constant issues.

we do git commit -a and after that everything is fine. And after a while it starts again. Everything else is properly pushed to our git.
Only error I observed was the file: multisite.d/sites.mk

also ui-errors are gone (for a while) after committing sites.mk

Well this is tricky. Never saw such behaviour without interfering with the files.
Can you check the web.log if anything comes up around that error?
Also, please run a git diff on the file when the error comes up.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.