Creating root after databases already exists makes whole REST API insane

[ExtReMLapin]

As suggested here : #2058 (comment)

To be able to change the root password on the fly, i use this pr : #2149
And on each boot i remove the root line in the users jsonl file.

Now when i do this there is something REALLY WEIRD going on :

'list databases' returns []

'create database test1' returns ok

re run 'list databases' still returns [] but

run again 'create database test1' and it returns Database 'test1' already exists

Postman_tEaOC57Y4B.mp4

[ExtReMLapin]

console.sh corretly lists it

> list databases

Databases:
- yoloooo1
- TITI
- test1
- titi
- AAAAAAAAAAAAA
- YOLO
- TOTO

[gramian]

May be the server script is run from the wrong folder. Can you post the contents of the entrypoint.sh?

BTW: you could consider using the ready endpoint /api/V1/ready for the healthcheck

[ExtReMLapin]

I found the issue cause, will rename the issue, it's when creating root session when databases already exists it completly makes it unworking.

As suggested here #2058 (comment)

The idea was to kill the root line in the jsonl file but it makes the whole arcadedb server unusable (see first message)

[gramian]

This could be due to file permissions. You can temporarily give all the files in the mounted folders all permissions like 777 and see if it works. I ran into this in another context where mounted files where made by a root but another UID then the container root.

[ExtReMLapin]

Pushed a fix to the PR

[lvca]

@ExtReMLapin sorry I lost track of this. Where is the PR? Is it already merged? Issue fixed?

[ExtReMLapin]

@lvca very likely this PR #2149 and this specific commit ExtReMLapin@95047eb

As far as I know the issue is not fixed

[lvca]

That PR is about recreating the root user, but as commented it was not a good idea. Did you find a workaround for this? Can I close this?

[ExtReMLapin]

Let's close it for now, if we end up meeting the issue again, i'll make another issue