Seeing lots of messages like this in my syslog on the machine that's running core and periphery (latter via systemd):
Aug 28 09:08:15 xxxx sh[1730507]: #033[2m2025-08-28T08:08:15.650005Z#033[0m #033[33m WARN#033[0m #033[2mperiphery::api::router#033[0m#033[2m:#033[0m request f5a151e4-cf37-472a-ab27-3bb8a5ea4a98 | type: GetLatestCommit | error: failed to get long commit hash
Any ideas what I can do to get rid of this?
Originally created by @lnlyssg on GitHub (Aug 28, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/780
Seeing lots of messages like this in my syslog on the machine that's running core and periphery (latter via systemd):
`Aug 28 09:08:15 xxxx sh[1730507]: #033[2m2025-08-28T08:08:15.650005Z#033[0m #033[33m WARN#033[0m #033[2mperiphery::api::router#033[0m#033[2m:#033[0m request f5a151e4-cf37-472a-ab27-3bb8a5ea4a98 | type: GetLatestCommit | error: failed to get long commit hash`
Any ideas what I can do to get rid of this?
Oof, not a great log message there, I can see that issue for sure. But I don't think I have seen this log in practice and not sure what would cause that to fail on valid repo. As to what is going on, are any of your resources not working? Is there a repo folder on you could try deleting and allow it to recreate?
<!-- gh-comment-id:3234050373 -->
@mbecker20 commented on GitHub (Aug 28, 2025):
Oof, not a great log message there, I can see that issue for sure. But I don't think I have seen this log in practice and not sure what would cause that to fail on valid repo. As to what is going on, are any of your resources not working? Is there a repo folder on you could try deleting and allow it to recreate?
I've just spotted that one of my repos I have defined has some permissions issues... I switched to using a dedicated komodo user for my periphery set-up yesterday and the last pull repo failed with:
fatal: detected dubious ownership in repository at '/etc/komodo/repos/compose-files'
To add an exception for this directory, call:
git config --global --add safe.directory /etc/komodo/repos/compose-files
but I'm not sure if this is related to the to "long commit hash" message?
<!-- gh-comment-id:3234128142 -->
@lnlyssg commented on GitHub (Aug 28, 2025):
I've just spotted that one of my repos I have defined has some permissions issues... I switched to using a dedicated `komodo` user for my periphery set-up yesterday and the last pull repo failed with:
```
fatal: detected dubious ownership in repository at '/etc/komodo/repos/compose-files'
To add an exception for this directory, call:
git config --global --add safe.directory /etc/komodo/repos/compose-files
```
but I'm not sure if this is related to the to "long commit hash" message?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @lnlyssg on GitHub (Aug 28, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/780
Seeing lots of messages like this in my syslog on the machine that's running core and periphery (latter via systemd):
Aug 28 09:08:15 xxxx sh[1730507]: #033[2m2025-08-28T08:08:15.650005Z#033[0m #033[33m WARN#033[0m #033[2mperiphery::api::router#033[0m#033[2m:#033[0m request f5a151e4-cf37-472a-ab27-3bb8a5ea4a98 | type: GetLatestCommit | error: failed to get long commit hashAny ideas what I can do to get rid of this?
@mbecker20 commented on GitHub (Aug 28, 2025):
Oof, not a great log message there, I can see that issue for sure. But I don't think I have seen this log in practice and not sure what would cause that to fail on valid repo. As to what is going on, are any of your resources not working? Is there a repo folder on you could try deleting and allow it to recreate?
@lnlyssg commented on GitHub (Aug 28, 2025):
I've just spotted that one of my repos I have defined has some permissions issues... I switched to using a dedicated
komodouser for my periphery set-up yesterday and the last pull repo failed with:but I'm not sure if this is related to the to "long commit hash" message?
@mbecker20 commented on GitHub (Aug 28, 2025):
Yeah the dubious ownership sound like it would do it
@lnlyssg commented on GitHub (Aug 28, 2025):
I deleted the repo and re-cloned it and now all is OK