github-starred/komodo
2
0
Fork 0
mirror of https://github.com/moghtech/komodo.git synced 2025-12-05 19:17:36 -06:00
Code Issues 258 Packages Projects Releases 10 Wiki Activity

Deleted stack keeps generating log errors ' failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e' #244

New Issue
Closed
opened 2025-10-31 15:06:05 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-10-31 15:06:05 -05:00
Owner
Copy Link

Originally created by @crazyelectron-io on GitHub (Mar 8, 2025).

I removed a Stack using the Komodo UI and it looks like it is not completely deleted. The log is full of these messages.

  ...
2025-03-08T11:03:15.599775Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e
2025-03-08T11:03:30.599377Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e
2025-03-08T11:03:45.603058Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e
2025-03-08T11:04:00.603428Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e
2025-03-08T11:04:15.595976Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e
2025-03-08T11:04:30.607546Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e
  ...

I'm not sure what 67cac444e572d24bb7daeb8e is referring to, but I think it is the deleted Stack because I have not seen these messaged before I deleted the Stack.

Is there a way to clean this up?

Originally created by @crazyelectron-io on GitHub (Mar 8, 2025). I removed a Stack using the Komodo UI and it looks like it is not completely deleted. The log is full of these messages. ```shell ... 2025-03-08T11:03:15.599775Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e 2025-03-08T11:03:30.599377Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e 2025-03-08T11:03:45.603058Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e 2025-03-08T11:04:00.603428Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e 2025-03-08T11:04:15.595976Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e 2025-03-08T11:04:30.607546Z ERROR core::monitor::alert::stack: failed to get stack from db | did not find any Stack matching 67cac444e572d24bb7daeb8e ... ``` I'm not sure what `67cac444e572d24bb7daeb8e` is referring to, but I think it is the deleted Stack because I have not seen these messaged before I deleted the Stack. Is there a way to clean this up?
GiteaMirror commented 2025-10-31 15:06:06 -05:00
Author
Owner
Copy Link

@malbert911 commented on GitHub (Mar 18, 2025):

I was having a similar issue. I had made some changes on a remote host directly on the docker-compose file in SSH, instead of Komodo web UI, and after restarting Komodo I had the same output like you.

To fix it, I did a docker-compose stop, docker-compose rm and docker-compose up -d on the Komodo docker-compose and it worked again

@malbert911 commented on GitHub (Mar 18, 2025): I was having a similar issue. I had made some changes on a remote host directly on the docker-compose file in SSH, instead of Komodo web UI, and after restarting Komodo I had the same output like you. To fix it, I did a `docker-compose stop`, `docker-compose rm` and `docker-compose up -d` on the Komodo docker-compose and it worked again
GiteaMirror commented 2025-10-31 15:06:06 -05:00
Author
Owner
Copy Link

@crazyelectron-io commented on GitHub (Mar 20, 2025):

yes, I fixed it too with some clean, but I post it here to let the maintainer(s) know I case they want to fix it in some future release.

@crazyelectron-io commented on GitHub (Mar 20, 2025): yes, I fixed it too with some clean, but I post it here to let the maintainer(s) know I case they want to fix it in some future release.
GiteaMirror commented 2025-10-31 15:06:06 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (Aug 27, 2025):

This should be fixed in last couple releases, internal cache clearing issue

@mbecker20 commented on GitHub (Aug 27, 2025): This should be fixed in last couple releases, internal cache clearing issue
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.19.0
1.19.1
1.19.2
1.19.3
1.19.4
bug
documentation
done
enhancement
help wanted
info
pull-request
Mirrored from GitHub Pull Request
question
security
seen 👀
setup
thinking 🤔
ui
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#244
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?