Hi everyone,
# spicedb
t
Hi everyone, I'm struggling with an error: "connection error: desc = error reading server preface: EOF" I used the spicedb operator on my server and it worked perfectly when using in-memory datastore. Then, I choose to use MySQL and now only some request work as expected. For exemple, I can write relation that are correctly added to MySQL DB (inside relation_tuple table). But I've got this error when checking permission. To check that the problem was coming from mysql, I reproduce in local, I used authzed/spicedb:v1.31.0 image and mysql:8.0 and it worked without any problem. Some more context if needed : -I'm gRPC newbee -I used TLS on the server -I'm making request through @authzed/authzed-node library -MySQL DB is managed by my cloud provider. -MySQL user has read and write permission. Does anyone already encounter this error ?
v
when write works, but a check does not, it suggests misconfigured dispatch. Can you set replica count to 1 and see if your requests succeed?
what managed MySQL are you using?
can you post your
SpiceDBCluster
definition?
t
I scale down replicat set from 2 to 1 and request still not succeed, however, the error change, now, I've got "context canceled" after 30 seconds :
Copy code
json
{
"grpc.service":"authzed.api.v1.PermissionsService",
"grpc.method":"LookupResources",
"grpc.method_type":"server_stream",
"grpc.code":"Canceled",
"grpc.error":"rpc error: code = Canceled desc = context canceled",
"grpc.time_ms":30000
}
MySQL DB is managed by my cloud provider Scaleway.
My SpiceDBCluster definition look like this :
Copy code
yaml
apiVersion: v1
kind: Secret
metadata:
  name: dev-spicedb-config
  namespace: application
stringData:
  preshared_key: "my-super-preshared-key"
  datastore_uri: "my-user:my-pwd@tcp(my-ip:my-port)/authzed_spicedb?parseTime=True"
---
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: authzed
  namespace: application
spec:
  config:
    logLevel: debug
    datastoreEngine: mysql
    tlsSecretName: tls-my-company-name
  secretName: dev-spicedb-config
v
have you tried enabling trace log?
11 Views