https://datahubproject.io logo
Join Slack
Powered by
Hi all, Upgrade from v0.8.41 to v0.8.45, and build...
# getting-started
f
Hi all, Upgrade from v0.8.41 to v0.8.45, and build an image through “DOCKER_BUILDKIT=1 docker build --no-cache -t xavier-web -f ./docker/datahub-frontend/Dockerfile .” Only the logo is modified, Exception occurred during deployment
Copy code
UI error:
Validation error (FieldUndefined@[analyticsChart/rows/cells/linkParams/searchParams/filters/value]) : Field 'value' in type 'Filter' is undefined
Validation error (FieldUndefined@[listRecommendations/modules/content/params/searchParams/filters/value]) : Field 'value' in type 'Filter' is undefined (code undefined)

Fornt error:
00:53:21 [application-akka.actor.default-dispatcher-25] ERROR controllers.TrackingController - Failed to emit product analytics event. actor: urn:li:corpuser:datahub, event: {"title":"Conviva Schema Center","url":"<http://xxxx/>","path":"/","hash":"","search":"","width":656,"height":971,"referrer":"<http://xxxx/>","prevPathname":"/login","type":"PageViewEvent","actorUrn":"urn:li:corpuser:datahub","timestamp":1665276799567,"date":"Sun Oct 09 2022 08:53:19 GMT+0800 (中国标准时间)","userAgent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36","browserId":"96726d31-fc24-47fd-98ff-6fa14864c04e"}
b
hey there! we recently updated our graphql schema for filter values to go from 
value
-> 
values
. ususally when you see this error it means that your frontend and gms pods are out of sync. Can you ensure that both are upgraded to the same version and that you've restarted all your pods?
f
Thank you. I’ve found this problem @bulky-soccer-26729
I have a question，Session generation failure error @bulky-soccer-26729
Copy code
15:04:31 [application-akka.actor.default-dispatcher-26] ERROR application - The submitted callback is of type: class javax.security.auth.callback.PasswordCallback : javax.security.auth.callback.PasswordCallback@2ad8e432
15:04:36 [application-akka.actor.default-dispatcher-26] ERROR application - 

! @7p9ii233f - Internal server error, for (POST) [/logIn] ->
 
play.api.UnexpectedException: Unexpected exception[RuntimeException: Failed to generate session token for user]
        at play.api.http.HttpErrorHandlerExceptions$.throwableToUsefulException(HttpErrorHandler.scala:340)
        at play.api.http.DefaultHttpErrorHandler.onServerError(HttpErrorHandler.scala:263)
        at play.core.server.AkkaHttpServer$$anonfun$1.applyOrElse(AkkaHttpServer.scala:443)
        at play.core.server.AkkaHttpServer$$anonfun$1.applyOrElse(AkkaHttpServer.scala:441)
        at scala.concurrent.Future.$anonfun$recoverWith$1(Future.scala:417)
        at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:41)
        at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:64)
        at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)
        at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:92)
        at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
        at scala.concurrent.BlockContext$.withBlockContext(BlockContext.scala:85)
        at akka.dispatch.BatchingExecutor$BlockableBatch.run(BatchingExecutor.scala:92)
        at akka.dispatch.TaskInvocation.run(AbstractDispatcher.scala:41)
        at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(ForkJoinExecutorConfigurator.scala:49)
        at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
        at akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
        at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
        at akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
Caused by: java.lang.RuntimeException: Failed to generate session token for user
        at client.AuthServiceClient.generateSessionTokenForUser(AuthServiceClient.java:99)
b
hmm this could happen for a number of reasons, but the first thing to check here would to be certain that your backend instance is up and running. can you confirm your gms pod is alive and healthy?
f
All logs are normal after startup
What kinds of problems may cause
b
it could also be an authentication configuration problem, I would check out this thread where someone was seeing the same error as you: https://datahubspace.slack.com/archives/C029A3M079U/p1652335230866129?thread_ts=1652335187.772439&amp;cid=C029A3M079U
f
The problem is that I upgraded the latest version from version 41，Whether there are data incompatibilities
47 Views
Open in Slack
PreviousNext
Powered by