```datahub-gms | 2021-09-29 03:08:50...
# troubleshoot
c
Copy code
datahub-gms               | 2021-09-29 03:08:50.361:WARN:oejs.HttpChannel:qtp544724190-15: /health
datahub-gms               | javax.servlet.ServletException: javax.servlet.UnavailableException: Servlet Not Initialized
datahub-gms               |     at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:162)
datahub-gms               |     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
datahub-gms               |     at org.eclipse.jetty.server.Server.handle(Server.java:494)
datahub-gms               |     at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:374)
datahub-gms               |     at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:268)
datahub-gms               |     at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
datahub-gms               |     at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
datahub-gms               |     at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
datahub-gms               |     at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)
datahub-gms               |     at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)
datahub-gms               |     at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)
datahub-gms               |     at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)
datahub-gms               |     at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:367)
datahub-gms               |     at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:782)
datahub-gms               |     at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:918)
datahub-gms               |     at java.lang.Thread.run(Thread.java:748)
datahub-gms               | Caused by:
datahub-gms               | javax.servlet.UnavailableException: Servlet Not Initialized
datahub-gms               |     at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:822)
datahub-gms               |     at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:544)
datahub-gms               |     at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
datahub-gms               |     at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:536)
datahub-gms               |     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
datahub-gms               |     at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
datahub-gms               |     at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1581)
datahub-gms               |     at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
datahub-gms               |     at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1307)
datahub-gms               |     at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
datahub-gms               |     at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:482)
datahub-gms               |     at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1549)
datahub-gms               |     at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
datahub-gms               |     at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1204)
datahub-gms               |     at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
datahub-gms               |     at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:221)
datahub-gms               |     at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
datahub-gms               |     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
datahub-gms               |     at org.eclipse.jetty.server.Server.handle(Server.java:494)
datahub-gms               |     at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:374)
datahub-gms               |     at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:268)
datahub-gms               |     at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
datahub-gms               |     at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
datahub-gms               |     at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
datahub-gms               |     at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)
datahub-gms               |     at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)
datahub-gms               |     at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)
datahub-gms               |     at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)
datahub-gms               |     at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:367)
datahub-gms               |     at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:782)
datahub-gms               |     at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:918)
datahub-gms               |     at java.lang.Thread.run(Thread.java:748)
e
@curved-magazine-23582 Can you post the whole logs? The actual error should be before this one.
c
k thanks for following up. do I need to copy docker log file? older logs already rolled off screen. 😞
e
Yes! That would be great. the other way would be to do a redeploy
the above error msg is shown because it tries to hit the health endpoint every few seconds, and fails because gms didn’t spin up correctly
Following up here. Did you resolve this issue?
c
thanks for following up! think the stacks are up, UI seem to be working. Thanks for the help!
running into another issue with rest.li api, seems like the api endpoints/models all changed?
instead of /dataset?action=ingest, etc. it is just /entities?action=ingest for everything, correct?
e
Yes! That was part of the v0.8 changes
we don’t have entity specific endpoints but rather generic endpoints that take the type as a parameter
In the future, if you want API access, we are trying to move to using graphQL apis (which have been moved to gms as well) cc @big-carpet-38439
c
oh, cool didn't know that. will check out graphQL APIs. thanks for the info.
e
b
@curved-magazine-23582 One major reason to do this is that Rest.li is difficult to work with as a public contract. Please let us know how working with GraphQL goes, we are trying to add additional functionality as needed so also let us know if it's missing what you need
👍 1