hey everyone - potentially a dumb question.. whats...
# troubleshoota
adamant-pharmacist-61996
08/30/2021, 11:30 PMhey everyone - potentially a dumb question.. whats the best way to set the logging levels in the ui and gms containers? I’d like to be able to set the level to debug
b
big-carpet-38439
08/31/2021, 12:32 AMNot a dumb question. Currently we don't expose a way to do it like on deploy of the container. That being said, we do save a standard info, error, warn log to a local directory when running along with a DEBUG-only log file kept for the last 24 hours
big-carpet-38439
08/31/2021, 12:32 AMa
adamant-pharmacist-61996
08/31/2021, 12:35 AMah cool. thanks! I’ll try ssh into the pod. I’m seeing some weird configuration error where data looks like its ingested properly but won’t show up in the UI.
adamant-pharmacist-61996
08/31/2021, 12:36 AMMost likely associated with quirk in teh way we’ve set things up
b
big-carpet-38439
08/31/2021, 12:42 AMOh interesting -- are they showing up when you query for them directly?
a
adamant-pharmacist-61996
08/31/2021, 12:42 AMI can see the results in MySQL (metadata_aspect_v2 table), just trying to get access to elastic now (I’m restricted in that namespace). The GMS logs all look healthy
adamant-pharmacist-61996
08/31/2021, 12:43 AMit could be a kafka thing too because of teh ACLs applied, just trying to debug which queries are being fired. Weirdly teh analytics queries return results
b
big-carpet-38439
08/31/2021, 12:44 AMOh well that means you're talking to elastic
a
adamant-pharmacist-61996
08/31/2021, 12:46 AMyeah, this is an odd one! we’ve probably done something strange
adamant-pharmacist-61996
08/31/2021, 2:21 AMhmm. this is odd.
datasetindex_v2metadata_aspect_v2adamant-pharmacist-61996
08/31/2021, 2:44 AM(there doesn’t appear to be anything in neo4j either)
b
big-carpet-38439
08/31/2021, 3:46 AMHmmm it. It could be that your MAE consumer is not running. How are you deploying this?
a
adamant-pharmacist-61996
08/31/2021, 6:57 AMDeployment through a helm chart, running version V0.8.10, I’ve just checked and we dont actually have an MAE consumer running. I’ve just been using a GMS pod and hitting the restful endpoint
adamant-pharmacist-61996
08/31/2021, 6:58 AMat the moment my best guess is that there is something odd going on with the kafka schema registry, and we’re not passing through the correct security configuration. Should all the topics we create be registered with the schema registry?
adamant-pharmacist-61996
08/31/2021, 7:31 AM Copy code
org.apache.kafka.common.errors.GroupAuthorizationException: Not authorized to access group: generic-mce-consumer-job-client
07:11:51.745 [generic-mce-consumer-job-client-0-C-1] ERROR o.s.k.l.KafkaMessageListenerContainer$ListenerConsumer - Fatal consumer exception; stopping containeradamant-pharmacist-61996
08/31/2021, 7:32 AMhmmm.. just spotted this in our logs. Should that actually kill the container?
b
big-carpet-38439
08/31/2021, 2:05 PMYes it should kill the container since kafka is mission critical :(
a
adamant-pharmacist-61996
08/31/2021, 8:47 PMI think what happens in our case is that the producers subscribe but we've set up the security layer for Kafka incorrectly within the pod for the consumer, so we end up in an odd state where the restapi received the data and then can't do anything with it
b
big-carpet-38439
08/31/2021, 11:12 PMThat sounds about right
r
red-waitress-53338
01/16/2023, 8:08 PMHI @adamant-pharmacist-61996
How did you manage to solve this issue?
Copy code
org.apache.kafka.common.errors.GroupAuthorizationException: Not authorized to access group: generic-mce-consumer-job-client
07:11:51.745 [generic-mce-consumer-job-client-0-C-1] ERROR o.s.k.l.KafkaMessageListenerContainer$ListenerConsumer - Fatal consumer exception; stopping container28 Views