ERROR: resource temporarily unavailable for all keys operations using CLI after REST server is started

[kwunyeung]

After starting REST server with gaiacli advanced rest-server, all operations with gaiacli keys will give this error.

ERROR: resource temporarily unavailable

Stop the REST server and those operations work using CLI again. This doesn't happen for other modules.

[ebuchman]

Thanks for reporting.

Do you have a real use case for needing this? If you're running the REST server already, can't you use those endpoints?

I think we might just not support this for now unless there's a very compelling reason to.

[ebuchman]

At least we should change the error message to indicate what the problem is. We can for sure do that :)

[davekaj]

I was getting the exact same error when implementing a go levelDB. leveldb will return "resource temporarily unavailable" if you have two routines trying to access the db. If this is the error it can be fixed by inserting db.Close() at the end of the functions accessing the db.

not sure if the REST server is even using leveldb , but I thought I'd add it since I saw the exact same error

[fkbenjamin]

Can confirm that this error still exists and that while running the REST-server it will return:

ERROR: resource temporarily unavailable

However the problem is, that the REST endpoint doesn't seem to work either. When using it like /keys/create?name=cosmos&password=cosmos
it will return

Key create not found

So you can't use the REST endpoints to create keys while running the REST server. It also seems that all (or at least most) REST endpoints that use POST are not working correctly.

[alexanderbez]

@fkbenjamin these are all the key endpoints I'm aware of (I'm also aware some of the docs are invalid/outdated):

func RegisterRoutes(r *mux.Router) {
	r.HandleFunc("/keys", QueryKeysRequestHandler).Methods("GET")
	r.HandleFunc("/keys", AddNewKeyRequestHandler).Methods("POST")
	r.HandleFunc("/keys/seed", SeedRequestHandler).Methods("GET")
	r.HandleFunc("/keys/{name}", GetKeyRequestHandler).Methods("GET")
	r.HandleFunc("/keys/{name}", UpdateKeyRequestHandler).Methods("PUT")
	r.HandleFunc("/keys/{name}", DeleteKeyRequestHandler).Methods("DELETE")
}

I was successfully able to create a key on the latest develop (POST @ /keys)

[fkbenjamin]

@alexanderbez Thx for that info! Was able to create a key using your info...

I was looking at the docs for
v0.24.0 (here) and develop (here). Both show wrong information.

[cwgoes]

This behavior is currently expected, since the open database is locked - if this is a problem for clients, I guess we can close the DB after every operation, the speed penalty doesn't matter much.