Can't find any other information, kind of at a loss for what to do here.
<!-- gh-comment-id:3505799245 -->
@digital-grease commented on GitHub (Nov 8, 2025):
Every once in a while it will get interrupted with these lines:
`postgres-1 | 2025-11-07 22:02:00.008 CST [32] LOG: cron job 4 starting: SELECT documentdb_api_internal.cursor_directory_cleanup();
postgres-1 | 2025-11-07 22:02:00.020 CST [32] LOG: cron job 1 starting: CALL documentdb_api_internal.delete_expired_rows();
postgres-1 | 2025-11-07 22:02:00.060 CST [32] LOG: cron job 4 completed: 1 row`
Can't find any other information, kind of at a loss for what to do here.
@digital-grease commented on GitHub (Nov 8, 2025):
I broke it myself somewhere else entirely unrelated to komodo it turns out. Closing.
<!-- gh-comment-id:3505967749 -->
@digital-grease commented on GitHub (Nov 8, 2025):
I broke it myself somewhere else entirely unrelated to komodo it turns out. Closing.
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 @digital-grease on GitHub (Nov 8, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/968
Just migrated all of my portainer stuff to komodo, everything was going well. I'm running the compose file pretty much straight from the docs.
Out of nowhere, komodo became unavailable, and the logs are filled with this:
postgres-1 | 2025-11-07 21:48:16.748 CST [32] LOG: cron job 3 COMMAND completed: CALL postgres-1 | 2025-11-07 21:48:18.711 CST [32] LOG: cron job 2 starting: CALL documentdb_api_internal.build_index_concurrently(1); postgres-1 | 2025-11-07 21:48:18.739 CST [32] LOG: cron job 2 COMMAND completed: CALL postgres-1 | 2025-11-07 21:48:18.745 CST [32] LOG: cron job 3 starting: CALL documentdb_api_internal.build_index_concurrently(2); postgres-1 | 2025-11-07 21:48:18.776 CST [32] LOG: cron job 3 COMMAND completed: CALL postgres-1 | 2025-11-07 21:48:20.735 CST [32] LOG: cron job 2 starting: CALL documentdb_api_internal.build_index_concurrently(1); postgres-1 | 2025-11-07 21:48:20.760 CST [32] LOG: cron job 2 COMMAND completed: CALL postgres-1 | 2025-11-07 21:48:20.769 CST [32] LOG: cron job 3 starting: CALL documentdb_api_internal.build_index_concurrently(2); postgres-1 | 2025-11-07 21:48:20.796 CST [32] LOG: cron job 3 COMMAND completed: CALL postgres-1 | 2025-11-07 21:48:22.757 CST [32] LOG: cron job 2 starting: CALL documentdb_api_internal.build_index_concurrently(1); postgres-1 | 2025-11-07 21:48:22.787 CST [32] LOG: cron job 2 COMMAND completed: CALL postgres-1 | 2025-11-07 21:48:22.793 CST [32] LOG: cron job 3 starting: CALL documentdb_api_internal.build_index_concurrently(2); postgres-1 | 2025-11-07 21:48:22.825 CST [32] LOG: cron job 3 COMMAND completed: CALLNot sure what i can do about this, if anything. No changes were made between it being fully functional, and this error popping up.
@digital-grease commented on GitHub (Nov 8, 2025):
Every once in a while it will get interrupted with these lines:
postgres-1 | 2025-11-07 22:02:00.008 CST [32] LOG: cron job 4 starting: SELECT documentdb_api_internal.cursor_directory_cleanup(); postgres-1 | 2025-11-07 22:02:00.020 CST [32] LOG: cron job 1 starting: CALL documentdb_api_internal.delete_expired_rows(); postgres-1 | 2025-11-07 22:02:00.060 CST [32] LOG: cron job 4 completed: 1 rowCan't find any other information, kind of at a loss for what to do here.
@digital-grease commented on GitHub (Nov 8, 2025):
I broke it myself somewhere else entirely unrelated to komodo it turns out. Closing.