I am trying to install datahub in docker using "da...
# troubleshootw
worried-animal-81235
03/12/2023, 11:13 PMI am trying to install datahub in docker using "datahub docker quickstart". I keep getting this error even the status show datahub-gm is already running:
[+] Running 12/12
⠿ Container elasticsearch Running 0.0s
⠿ Container zookeeper Running 0.0s
⠿ Container mysql Running 0.0s
⠿ Container elasticsearch-setup Started 0.5s
⠿ Container mysql-setup Started 0.5s
⠿ Container datahub-upgrade Running 0.0s
⠿ Container broker Running 0.0s
⠿ Container datahub-gms Running 0.0s
⠿ Container schema-registry Running 0.0s
⠿ Container kafka-setup Started 0.5s
⠿ Container datahub-datahub-actions-1 Running 0.0s
⠿ Container datahub-frontend-react Running 0.0s
..............
Unable to run quickstart - the following issues were detected:
- datahub-gms is still starting
a
astonishing-answer-96712
03/13/2023, 8:01 PMHi phil- you can always try
datahub docker nuke--version=v0.X.X.Xw
worried-animal-81235
03/13/2023, 9:17 PMThanks Paul, tried nuke command and it was the same. Do you know if any particular version that might work?
a
astonishing-answer-96712
03/13/2023, 9:20 PM0.10.0.0 has been stable
w
worried-animal-81235
03/13/2023, 9:39 PMGot error with:
Pulling docker images...This may take a while depending on your network bandwidth.
/Error response from daemon: manifest for linkedin/datahub-frontend-react:v0.10.0.0 not found: manifest unknown: manifest unknown
Error while pulling images. Going to attempt to move on to docker compose up assuming the images have been built locally
worried-animal-81235
03/13/2023, 10:56 PMLooks like the latest released stable version is 0.10.0. It is pulling the image now and will take a while. The image:
acryldata/datahub-actions head
show as "head" instead of version 0.10.0. It is 6.29GB--huge. Wondering why it so huge. Still downloading rest of the images.
But it successfully pulled all the images. Unfortunately, there is no difference though. The same errors as before.
Here is the logs:
b
better-orange-49102
03/14/2023, 1:12 PMFor the -setup containers that are still running/started, can you check the logs to see why they're not finished?
w
worried-animal-81235
03/16/2023, 12:35 AMFor kafka:
2023-03-15 203204 DATAHUB_PRECREATE_TOPICS=false
2023-03-15 203204 Pre-creation of topics has been turned off, exiting
worried-animal-81235
03/16/2023, 12:39 AMdatahub-actions
2023-03-15 203832 2023/03/16 003832 Problem with request: Get "http://datahub-gms:8080/health": dial tcp 172.19.0.88080 connect: connection refused. Sleeping 1s
worried-animal-81235
03/16/2023, 12:46 AMMysql-setup keep on restart, don't see obvious errors in the log. But on mysql server, we have:
023-03-15 203704 2023-03-16 03704 96 [Warning] Aborted connection 96 to db: 'unconnected' user: 'unauthenticated' host: '172.19.0.6' (This connection closed normally without authentication)
2023-03-15 203735 2023-03-16 03735 98 [Warning] Aborted connection 98 to db: 'unconnected' user: 'unauthenticated' host: '172.19.0.7' (This connection closed normally without authentication)
2023-03-15 203803 2023-03-16 03803 100 [Warning] Aborted connection 100 to db: 'unconnected' user: 'unauthenticated' host: '172.19.0.6' (This connection closed normally without authentication)
worried-animal-81235
03/16/2023, 12:48 AMelasticsearch-setup also don't see any obvious error:
2023-03-15 203734 datahub_analytics_enabled: true
2023-03-15 203734
2023-03-15 203734 >>> GET _ilm/policy/datahub_usage_event_policy response code is 200
2023-03-15 203633 2023/03/16 003633 Command finished successfully.
2023-03-15 203703 2023/03/16 003703 Waiting for: http://elasticsearch:9200
2023-03-15 203703 2023/03/16 003703 Received 200 from http://elasticsearch:9200
2023-03-15 203704 2023/03/16 003704 Command finished successfully.
2023-03-15 203734 2023/03/16 003734 Waiting for: http://elasticsearch:9200
2023-03-15 203734 2023/03/16 003734 Received 200 from http://elasticsearch:9200
2023-03-15 203734 2023/03/16 003734 Command finished successfully.
2023-03-15 203802 2023/03/16 003802 Waiting for: http://elasticsearch:9200
2023-03-15 203802 2023/03/16 003802 Received 200 from http://elasticsearch:9200
2023-03-15 203803 2023/03/16 003803 Command finished successfully.
2023-03-15 203734 >>> _ilm/policy/datahub_usage_event_policy already exists ✓
2023-03-15 203734
2023-03-15 203734 >>> GET _index_template/datahub_usage_event_index_template response code is 200
2023-03-15 203734 >>> _index_template/datahub_usage_event_index_template already exists ✓
2023-03-15 203734
2023-03-15 203734 >>> GET _data_stream/datahub_usage_event response code is 200
2023-03-15 203734 >>> _data_stream/datahub_usage_event already exists ✓
2023-03-15 203802 going to use protocol: http
2023-03-15 203802 going to use default elastic headers
2023-03-15 203802 not using any prefix
2023-03-15 203802
2023-03-15 203802 datahub_analytics_enabled: true
2023-03-15 203803
2023-03-15 203803 >>> GET _ilm/policy/datahub_usage_event_policy response code is 200
2023-03-15 203803 >>> _ilm/policy/datahub_usage_event_policy already exists ✓
2023-03-15 203803
2023-03-15 203803 >>> GET _index_template/datahub_usage_event_index_template response code is 200
2023-03-15 203803 >>> _index_template/datahub_usage_event_index_template already exists ✓
2023-03-15 203803
2023-03-15 203803 >>> GET _data_stream/datahub_usage_event response code is 200
2023-03-15 203803 >>> _data_stream/datahub_usage_event already exists ✓
worried-animal-81235
03/16/2023, 12:55 AMset environment variable to DATHUB_PRECREATE_TOPICS=true. The kafak_setup is no longer show error, but it keep on running and see warnings like this:
2023-03-15 205039 WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
b
better-orange-49102
03/16/2023, 12:57 AM Copy code
2023-03-15 20:50:39 WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.better-orange-49102
03/16/2023, 12:57 AMES-setup looks fine. mysql-setup looks off. Not sure if GMS can connect to mySQL too
better-orange-49102
03/16/2023, 12:58 AMthere shd be a line in gms logs that says it is attempting to connect to mysql, not sure if it succeeds
better-orange-49102
03/16/2023, 12:59 AMsomething like
Copy code
Waiting for: <tcp://mysql:3306>
Connected to <tcp://mysql:3306>w
worried-animal-81235
03/16/2023, 2:04 AMb
better-orange-49102
03/16/2023, 2:06 AMcan you
Copy code
docker exec -it mysql /bin/shbetter-orange-49102
03/16/2023, 2:06 AMthere shd be a empty metadata_aspect_v2 table inside the datahub schema, that is the purpose of the mysql-setup job
w
worried-animal-81235
03/16/2023, 2:10 AMyes, the table is there. There are 2 tables. In addition to metadata_aspect_v2, there is also a metadata_index table.
b
better-orange-49102
03/16/2023, 2:11 AMso is gms running normally now?
w
worried-animal-81235
03/16/2023, 2:11 AMLooking at the gms log, it took long time to connect to mysql and even longer time to connect to ES.
worried-animal-81235
03/16/2023, 2:12 AM2023-03-13 181256 2023/03/13 221256 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.19.0.39200 connect: connection refused. Sleeping 1s
2023-03-13 181257 2023/03/13 221257 Received 200 from http://elasticsearch:9200
worried-animal-81235
03/16/2023, 2:14 AMHow can I tell if gms is running normally?
b
better-orange-49102
03/16/2023, 2:14 AMjust try to access localhost:9002 now?
w
worried-animal-81235
03/16/2023, 2:15 AMI am able to get the GUI prompt, but cannot login with datahub/datahub
b
better-orange-49102
03/16/2023, 2:15 AMand what does the gms logs say now, in that case?
w
worried-animal-81235
03/16/2023, 2:17 AMIt says nothing. I started the gms 2 days ago. It didn't show new logs for a while. The last logs:
023-03-13 181324 2023-03-13 221324.199INFOoeja.AnnotationConfigurationmain Scanning elapsed time=11884ms
2023-03-13 181326 2023-03-13 221326.533INFOoejshC.ROOTmain 1 Spring WebApplicationInitializers detected on classpath
2023-03-13 181326 2023-03-13 221326.741INFOoejs.sessionmain DefaultSessionIdManager workerName=node0
2023-03-13 181326 2023-03-13 221326.742INFOoejs.sessionmain No SessionScavenger set, using defaults
2023-03-13 181326 2023-03-13 221326.883INFOoejs.sessionmain node0 Scavenging every 600000ms
2023-03-13 181326 2023-03-13 221326.992INFOoejshC.ROOTmain Initializing Spring root WebApplicationContext
2023-03-13 181327 2023-03-13 221327,088 [main] INFO o.s.web.context.ContextLoader:271 - Root WebApplicationContext: initialization started
2023-03-13 181339 2023-03-13 221339,699 [main] INFO c.l.m.m.r.ConfigEntityRegistry:82 - Loading bare config entity registry file at /datahub/datahub-gms/resources/entity-registry.yml
2023-03-13 181354 2023-03-13 221354,456 [main] WARN c.l.m.m.r.PluginEntityRegistryLoader:44 - /etc/datahub/plugins/models directory does not exist or is not a directory. Plugin scanning will be disabled.
worried-animal-81235
03/16/2023, 2:18 AMHere is the front-end log:
worried-animal-81235
03/16/2023, 2:19 AM2023-03-15 221816 Caused by: org.apache.http.conn.HttpHostConnectException: Connect to datahub-gms:8080 [datahub-gms/172.19.0.8] failed: Connection refused (Connection refused)
2023-03-15 221816 at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:156)
2023-03-15 221816 at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)
2023-03-15 221816 at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
2023-03-15 221816 at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
2023-03-15 221816 at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
2023-03-15 221816 at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
2023-03-15 221816 at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
2023-03-15 221816 at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
2023-03-15 221816 at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
2023-03-15 221816 at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
2023-03-15 221816 at client.AuthServiceClient.generateSessionTokenForUser(AuthServiceClient.java:89)
2023-03-15 221816 ... 46 common frames omitted
2023-03-15 221816 Caused by: java.net.ConnectException: Connection refused (Connection refused)
2023-03-15 221816 at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
2023-03-15 221816 at java.base/java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:412)
2023-03-15 221816 at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:255)
2023-03-15 221816 at java.base/java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:237)
2023-03-15 221816 at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
2023-03-15 221816 at java.base/java.net.Socket.connect(Socket.java:609)
2023-03-15 221816 at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:75)
2023-03-15 221816 at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
2023-03-15 221816 ... 56 common frames omitted
b
better-orange-49102
03/16/2023, 2:20 AMit feels like gms hung or something.
better-orange-49102
03/16/2023, 2:21 AMi have no other suggestions other than to try a
nukew
worried-animal-81235
03/16/2023, 2:27 AMThanks @better-orange-49102 for your help. I have already tried nuke multiple times and the same result. Will try again one more time tomorrow. Report back. Thank you 🙏
worried-animal-81235
03/16/2023, 11:45 PMI see this exception in the gms:
worried-animal-81235
03/16/2023, 11:45 PM2023-03-16 194237 2023-03-16 234237,695 [R2 Nio Event Loop-1-1] WARN c.l.r.t.h.c.c.ChannelPoolLifecycle:139 - Failed to create channel, remote=localhost/127.0.0.1:8080
2023-03-16 194237 io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:8080
2023-03-16 194237 Caused by: java.net.ConnectException: Connection refused
2023-03-16 194237 at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
2023-03-16 194237 at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:777)
2023-03-16 194237 at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:337)
2023-03-16 194237 at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
2023-03-16 194237 at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:776)
2023-03-16 194237 at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
2023-03-16 194237 at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
2023-03-16 194237 at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
2023-03-16 194237 at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
2023-03-16 194237 at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
2023-03-16 194237 at java.base/java.lang.Thread.run(Thread.java:829)
2023-03-16 194240 2023-03-16 234240,089 [R2 Nio Event Loop-1-2] WARN c.l.r.t.h.c.c.ChannelPoolLifecycle:139 - Failed to create channel, remote=localhost/127.0.0.1:8080
2023-03-16 194240 io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:8080
2023-03-16 194240 Caused by: java.net.ConnectException: Connection refused
2023-03-16 194240 at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
2023-03-16 194240 at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:777)
2023-03-16 194240 at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:337)
2023-03-16 194240 at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
2023-03-16 194240 at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:776)
2023-03-16 194240 at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
2023-03-16 194240 at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
2023-03-16 194240 at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
2023-03-16 194240 at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
2023-03-16 194240 at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
2023-03-16 194240 at java.base/java.lang.Thread.run(Thread.java:829)
2023-03-16 194244 2023-03-16 234244,389 [R2 Nio Event Loop-1-3] WARN c.l.r.t.h.c.c.ChannelPoolLifecycle:139 - Failed to create channel, remote=localhost/127.0.0.1:8080
2023-03-16 194244 io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:8080
2023-03-16 194244 Caused by: java.net.ConnectException: Connection refused
2023-03-16 194244 at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
2023-03-16 194244 at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:777)
2023-03-16 194244 at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:337)
2023-03-16 194244 at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:776)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
2023-03-16 194244 at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
2023-03-16 194244 at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
2023-03-16 194244 at java.base/java.lang.Thread.run(Thread.java:829)
2023-03-16 194244 2023-03-16 234244,543 [pool-14-thread-1] ERROR c.d.m.ingestion.IngestionScheduler:244 - Failed to retrieve ingestion sources! Skipping updating schedule cache until next refresh. start: 0, count: 30
2023-03-16 194244 com.linkedin.r2.RemoteInvocationException: com.linkedin.r2.RemoteInvocationException: Failed to get response from server for URI http://localhost:8080/entities
2023-03-16 194244 at com.linkedin.restli.internal.client.ExceptionUtil.wrapThrowable(ExceptionUtil.java:135)
2023-03-16 194244 at com.linkedin.restli.internal.client.ResponseFutureImpl.getResponseImpl(ResponseFutureImpl.java:130)
2023-03-16 194244 at com.linkedin.restli.internal.client.ResponseFutureImpl.getResponse(ResponseFutureImpl.java:94)
2023-03-16 194244 at com.linkedin.common.client.BaseClient.sendClientRequest(BaseClient.java:51)
2023-03-16 194244 at com.linkedin.entity.client.RestliEntityClient.list(RestliEntityClient.java:365)
2023-03-16 194244 at com.datahub.metadata.ingestion.IngestionScheduler$BatchRefreshSchedulesRunnable.run(IngestionScheduler.java:220)
2023-03-16 194244 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
2023-03-16 194244 at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
2023-03-16 194244 at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
2023-03-16 194244 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2023-03-16 194244 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2023-03-16 194244 at java.base/java.lang.Thread.run(Thread.java:829)
2023-03-16 194244 Caused by: com.linkedin.r2.RemoteInvocationException: Failed to get response from server for URI http://localhost:8080/entities
2023-03-16 194244 at com.linkedin.r2.transport.http.common.HttpBridge$1.onResponse(HttpBridge.java:67)
2023-03-16 194244 at com.linkedin.r2.transport.http.client.rest.ExecutionCallback.lambda$onResponse$0(ExecutionCallback.java:64)
2023-03-16 194244 ... 3 common frames omitted
2023-03-16 194244 Caused by: com.linkedin.r2.RetriableRequestException: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:8080
2023-03-16 194244 at com.linkedin.r2.transport.http.client.common.ChannelPoolLifecycle.onError(ChannelPoolLifecycle.java:142)
2023-03-16 194244 at com.linkedin.r2.transport.http.client.common.ChannelPoolLifecycle.lambda$create$0(ChannelPoolLifecycle.java:97)
2023-03-16 194244 at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:590)
2023-03-16 194244 at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:583)
2023-03-16 194244 at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:559)
2023-03-16 194244 at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:492)
2023-03-16 194244 at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:636)
2023-03-16 194244 at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:629)
2023-03-16 194244 at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:118)
2023-03-16 194244 at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.fulfillConnectPromise(AbstractNioChannel.java:321)
2023-03-16 194244 at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:337)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:776)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
2023-03-16 194244 at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
2023-03-16 194244 at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
2023-03-16 194244 ... 1 common frames omitted
2023-03-16 194244 Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:8080
2023-03-16 194244 Caused by: java.net.ConnectException: Connection refused
2023-03-16 194244 at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
2023-03-16 194244 at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:777)
2023-03-16 194244 at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:337)
2023-03-16 194244 at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:776)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
2023-03-16 194244 at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
2023-03-16 194244 at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
2023-03-16 194244 at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
2023-03-16 194244 at java.base/java.lang.Thread.run(Thread.java:829)
2023-03-16 194249 2023-03-16 234249,966 [main] INFO o.s.web.servlet.DispatcherServlet:547 - Completed initialization in 16434 ms
worried-animal-81235
03/17/2023, 12:06 AMI still have the same error after waiting the datahub docker quickstart --version=v0.10.0 command, but I am able to login to the GUI this time!!!
Unable to run quickstart - the following issues were detected:
- kafka-setup is still running
If you think something went wrong, please file an issue at https://github.com/datahub-project/datahub/issues
or send a message in our Slack https://slack.datahubproject.io/
Be sure to attach the logs from /var/folders/4c/23js2gfn1k706flzzr8rhnh80000gn/T/tmprob_vj8n.log
b
better-orange-49102
03/17/2023, 12:08 AMHmm what does kafka setup say now though, without it completing successfully your ingestions will probably have problems
w
worried-animal-81235
03/17/2023, 12:19 AMYou are right. Try to ingest sample data. Get the following errors:
[2023-03-16 201718,158] ERROR {datahub.ingestion.run.pipeline:63} - failed to write record with workunit file///var/folders/4c/23js2gfn1k706flzzr8rhnh80000gn/T/tmpktw4ohe0.json97 with ('Unable to emit metadata to DataHub GMS', {'exceptionClass': 'com.linkedin.restli.server.RestLiServiceException', 'stackTrace': 'com.linkedin.restli.server.RestLiServiceException [HTTP Status400] Failed to find entity with name query in EntityRegistry\n\tat com.linkedin.metadata.restli.RestliUtil.badRequestException(RestliUtil.java:84)\n\tat com.linkedin.metadata.restli.RestliUtil.toTask(RestliUtil.java:35)', 'message': 'Failed to find entity with name query in EntityRegistry', 'status': 400, 'id': 'urnliquery:test-query'}) and info {'exceptionClass': 'com.linkedin.restli.server.RestLiServiceException', 'stackTrace': 'com.linkedin.restli.server.RestLiServiceException [HTTP Status400] Failed to find entity with name query in EntityRegistry\n\tat com.linkedin.metadata.restli.RestliUtil.badRequestException(RestliUtil.java:84)\n\tat com.linkedin.metadata.restli.RestliUtil.toTask(RestliUtil.java:35)', 'message': 'Failed to find entity with name query in EntityRegistry', 'status': 400, 'id': 'urnliquery:test-query'}
[2023-03-16 201718,725] ERROR {datahub.ingestion.run.pipeline:63} - failed to write record with workunit file///var/folders/4c/23js2gfn1k706flzzr8rhnh80000gn/T/tmpktw4ohe0.json98 with ('Unable to emit metadata to DataHub GMS', {'exceptionClass': 'com.linkedin.restli.server.RestLiServiceException', 'stackTrace': 'com.linkedin.restli.server.RestLiServiceException [HTTP Status400] Failed to find entity with name query in EntityRegistry\n\tat com.linkedin.metadata.restli.RestliUtil.badRequestException(RestliUtil.java:84)\n\tat com.linkedin.metadata.restli.RestliUtil.toTask(RestliUtil.java:35)', 'message': 'Failed to find entity with name query in EntityRegistry', 'status': 400, 'id': 'urnliquery:test-query'}) and info {'exceptionClass': 'com.linkedin.restli.server.RestLiServiceException', 'stackTrace': 'com.linkedin.restli.server.RestLiServiceException [HTTP Status400] Failed to find entity with name query in EntityRegistry\n\tat com.linkedin.metadata.restli.RestliUtil.badRequestException(RestliUtil.java:84)\n\tat com.linkedin.metadata.restli.RestliUtil.toTask(RestliUtil.java:35)', 'message': 'Failed to find entity with name query in EntityRegistry', 'status': 400, 'id': 'urnliquery:test-query'}
b
better-orange-49102
03/17/2023, 12:19 AMWhat kind of system specs do you have?
w
worried-animal-81235
03/17/2023, 12:22 AMI have a MacBook Pro with Apple M1 Max processor and 32GB memory. I use Mac Desktop Docker and with 16GB memory allocated to the docker. Here is the kafka setup log:
2023-03-16 194511 1 got work_id=MetadataChangeProposal_v1 topic_args=--topic MetadataChangeProposal_v1
2023-03-16 194511 2 got work_id=FailedMetadataChangeProposal_v1 topic_args=--topic FailedMetadataChangeProposal_v1
2023-03-16 194511 4 got work_id=PlatformEvent_v1 topic_args=--topic PlatformEvent_v1
2023-03-16 194527 WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
2023-03-16 194528 WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
2023-03-16 194528 WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
2023-03-16 194528 WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
2023-03-16 194530 1 got work_id=DataHubUpgradeHistory_v1 topic_args=config retention.ms=-1 --topic DataHubUpgradeHistory_v1
2023-03-16 194530 3 got work_id=DataHubUsageEvent_v1 topic_args=--topic DataHubUsageEvent_v1
2023-03-16 194530 2 done working
2023-03-16 194530 4 done working
2023-03-16 194538 WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
2023-03-16 194538 WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both.
2023-03-16 194540 1 done working
2023-03-16 194540 3 done working
2023-03-16 194540 Topic Creation Complete.
2023-03-16 194548 Completed updating config for topic _schemas.
b
better-orange-49102
03/17/2023, 12:25 AMHmm I can't decide if it looks ok or not, v0.10 looks very different from 0.8.45 which I'm running. Pinging @astonishing-answer-96712 to get someone to take a look
better-orange-49102
03/17/2023, 12:26 AMResource wise, it should be okish
w
worried-animal-81235
03/17/2023, 12:36 AMThanks @better-orange-49102 for your help. It does seem this release is not quite stable, maybe only for Mac M1 system as it's likely the least tested platform if developers are not using the same platform.
a
aloof-gpu-11378
03/17/2023, 5:34 PMHi @worried-animal-81235, could you try pinning the version with
--version=v0.10.0w
worried-animal-81235
03/17/2023, 6:45 PMI did Paul and I am running the v0.10.0
a
aloof-gpu-11378
03/17/2023, 8:27 PMAh ok, and you’ve also tried the nuke?
w
worried-animal-81235
03/17/2023, 8:28 PMyes
a
aloof-gpu-11378
03/17/2023, 8:28 PMthis may be docker desktop letting a container hang- you could go into the UI and stop it manually, that works sometimes
w
worried-animal-81235
03/17/2023, 8:30 PMdo you mean restart the Docker desktop?
a
aloof-gpu-11378
03/17/2023, 9:38 PMyes
w
worried-animal-81235
03/18/2023, 1:22 AMno luck and also tried nuke after restarted docker.
a
aloof-gpu-11378
03/20/2023, 7:28 PMwe see this occasionally for some M1 setups- the most expedient thing may to run this on a linux vm sadpanda
9 Views