Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

webui backend showing stat output for deletion #203

Open
justinclift opened this issue May 3, 2023 · 2 comments
Open

webui backend showing stat output for deletion #203

justinclift opened this issue May 3, 2023 · 2 comments

Comments

@justinclift
Copy link
Member

Just noticed several instances of this showing up in the webui's backend log file.

Note that the user and database name have been replaced for privacy.

May 03 03:22:37 dbhub.io webui[190641]: 2023/05/03 03:22:37 [DELETE] 'webUI' removed Minio database object 'USERNAME/DATABASE', using bucket 'live-cua8zty58i' and id 'kuaya8'
May 03 03:22:37 dbhub.io webui[190641]: 2023/05/03 03:22:37 stat /home/dbhub/.dbhub/live_databases/USERNAME/DATABASE/live.sqlite: no such file or directory

The stat output there is making me wonder if perhaps we have the deletion running in the wrong order, or perhaps the verification of the deletion is going wrong.

So, I'm not sure there's anything wrong here than possibly over-logging, but we should look into it just in case.
justinclift added a commit that referenced this issue May 3, 2023
@justinclift
live: Workaround for a weird stat error when deleting from Live nodes
10b8b63 
Addresses #203, which I've not been able to replicate
in testing (so far).

Lets keep the issue open for now though, for future
follow up.
@justinclift
Copy link
Member Author

The error message seems to be coming from here:

dbhub.io/live/main.go

Line 440 in b542dc1

log.Println(err)

I've just committed a workaround, but will leave this open for now, so I can look into it more properly later.

@justinclift
Copy link
Member Author

Hmmm, this is still showing up in our backend logs occasionally.

One possibility popped into mind... maybe it's something to do with a foreign key constraint stopping the deletion from occurring. eg missing CASCADE or similar

Something along these lines would fit the behaviour we're seeing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@justinclift