codenotary / codenotary/immudb
clients report: Already Closed
- Dominant language
- Go
- Stars
- 9k
- Forks
- 378
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 3
Description
**What happened**
immudb running with the backend on S3 reports "Already Closed" so clients can not connect to the database.
Tested from multiple clients, including the webinterface:

Some commands still works:
```bash
./immuadmin -a immudb-grpc database create helloissue
database 'helloissue' {replica: false} successfully created
```
Others, doesn't
```bash
./immuadmin -a immudb-grpc database list
Error: rpc error: code = Unknown desc = already closed
```
**What you expected to happen**
No error message at all
**How to reproduce it (as minimally and precisely as possible)**
Not sure
**Environment**
```shell
immudb 1.9.3
Commit : 5487dd300655083ff68c4a72c2edb38ca84dd1bb
Built at: Thu, 23 May 2024 10:07:40 UTC
Static : true
```
**Additional info (any other context about the problem)**
As usual, it was running fine on S3, eventually it stopped working
Contributor guide
Research direction
Start by examining the immudb 1.9.3 setup with an S3 backend and compare the working `immuadmin ... database create helloissue` command with the failing `database list` command. Reproduce the `already closed` response if possible; done means database clients and listing commands work without that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cli, cloud, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100