Git Auto export all not pushing to Repository

[#1]

We currently experience the problem that on one of our morpheus appliance the auto export all feature of a git integration stops working for an unknown reason.
I can’t find explicit logs to it in the administration → health logs.
We have the same repo but with a different access token integrated in our other environment and the same setup/config for the provisioning → code → repositories part(different subpath within the repo though).
I noticed, that when I manually export all resources, it shows that commits were made according to the 4 hour schedule, but for some reason never pushed.

Where could I find extend logs for that?
Also tried to readd the integration and setup the auto export all part but it still doesnt work.
Currently running: v. 7.0.6-4 in both environments

[tyboyd]

Interesting. In that case it may be better to put in a support ticket. I would need to see the logs myself to get a idea as I have not see this issue myself.

If I get some time I can try and dig into this a little more at let you know what I find.

[Ollie-Phillips]

If you can access the appliance(s) you may find it easier to capture the logs from their linux path

/var/log/morpheus/morpheus-ui

The current file will contain the latest logs.

[#4]

I found there is
/var/opt/morpheus/morpheus-local/repo/git/* which shows the integrated git repos, and the commits being made by morpheus-app.
I then found in
/var/opt/morpheus/morpheus-ui/* that I get the following:

current:243010:2024-10-30_11:03:22.97846 ''[2024-10-30 11:03:22,985] [appJobLow-12] INFO  c.m.i.GitRepoService - commit results: commit 2ec64f7ea62fe15e929637cf440386969ae80486 1730286202 ------p
current:249018:2024-10-30_11:03:31.71256 ''[2024-10-30 11:03:34,424] [appJobLow-12] INFO  c.m.i.GitRepoService - push results - [org.eclipse.jgit.transport.PushResult@b9e3a9d]
current:249019:2024-10-30_11:03:34.42453 ''[2024-10-30 11:03:34,532] [appJobLow-12] INFO  c.m.i.GitRepoService -   response: <org.eclipse.jgit.transport.PushResult@b9e3a9d remoteUpdates=[refs/heads/main:RemoteRefUpdate[remoteName=refs/heads/main, REJECTED_NONFASTFORWARD, b66875aee0c3989e7a452453ce73e1e931b69242...2ec64f7ea62fe15e929637cf440386969ae80486, srcRef=refs/heads/main, message=null]] advertisedRefs=[refs/heads/main:Ref[refs/heads/main=b66875aee0c3989e7a452453ce73e1e931b69242(-1)]] uri=giturl/foobar/morpheus-backup.git updates=[refs/remotes/origin/main:TrackingRefUpdate[refs/heads/main -> refs/remotes/origin/main (forced) 2360791..2ec64f7]] messageBuffer=null peerUserAgent=git/2.45.2>

I assume the “REJECTED_NONFASTFORWARD” is because I have another environment exporting all Ressources to the same repository but different path.
What I don’t get is why the export All works in the other environment. It shouldn’t afftect each other because they do commits to different paths.

repo/
  environmentA/
  envrionmentB/

We have them in the same repo to import/export ressources between environments. Is there some sort of best practice?

[tyboyd]

I wouldn’t have two different environments export to the same repo if that is what you are doing. I would guess you have a conflict of some kind and Morpheus is unable to push to origin.

[#6]

I would like to dig into the logs myself, but I can’t manage to filter them properly in the administration → health tab. What keywords should i look out for? Also any logs on the appliance hosts related to git integration?

[#7]

Any specific words to look out for? Like git integration or repository or the used url maybe?
This file tends to be pretty crowded.

[#8]

But they are pushing to different paths, why would they get into conflict?
If there would be a conflict, wouldnt there be any logs.
Also manually exporting all resources works without conflicts.
Also it worked for a period perfectly and then stopped.