MQTT Broker errors following k8s guide about devops HOT 3 CLOSED

@dusanb94
Again thank you for the push in the right direction. After seeing that mainflux was attempting to verify the publisher in the database, we stepped through the cURL steps here to make a user, a thing, and channel, add the thing to the channel, and were able to successfully publish a mqtt message.

It looks like I was having a false positive with minikube and localhost. Mosquitto was running a broker locally the entire time so I though I was talking to mainflux on minikube when I was not.

from devops.

Can you, please, share Things service logs, as well.

from devops.

@dusanb94 of course and thanks for that direction.

{"level":"warn","message":"Method identify for token 123 and thing took 1.683339ms to complete with error: non-existent entity : sql: no rows in result set.","ts":"2021-07-06T14:54:16.330675531Z"}

It appears its trying to look up or auth whatever is connecting. tried this on mqtt over websockets as well.
Minikube however does not seem to care who is talking. Its logs are:

{"level":"info","message":"gRPC communication is not encrypted","ts":"2021-07-01T15:45:54.2312722Z"}
{"level":"info","message":"Things service started using http on port 8182","ts":"2021-07-01T15:45:54.2335351Z"}
{"level":"info","message":"Things service started using http on port 8182","ts":"2021-07-01T15:45:54.2337532Z"}
{"level":"info","message":"Things gRPC service started using http on port 8183","ts":"2021-07-01T15:45:54.23382Z"}

from devops.