Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to load cluster status with Local Setup #67

Open
sohailA-splore opened this issue Mar 1, 2024 · 4 comments
Open

Unable to load cluster status with Local Setup #67

sohailA-splore opened this issue Mar 1, 2024 · 4 comments
Assignees

Comments

@sohailA-splore
Copy link

After following the steps mentions in README.md, I am unable to view the vespa cluster status.

Steps:

  • Create a docker network
    docker network create --driver bridge vespanet
  • Run Vespa within vespanet network and vespa-container hostname :
    docker run --detach --name vespa --network vespanet --hostname vespa-container --publish 8080:8080 --publish 19071:19071 vespaengine/vespa
  • Run Vispana within vespanet network:
    docker run -p 4000:4000 --network vespanet vispana/vispana:latest
  • Access Vispana in your browser via http://localhost:4000/ and specify the config node as http://vespa-container:19071`
Screenshot 2024-03-01 at 3 33 54 PM
@sohailA-splore
Copy link
Author

I first tried with deploying a sample qa-semantic-retreival locally but didn't work.

@broknloop broknloop self-assigned this Mar 5, 2024
@broknloop
Copy link
Collaborator

broknloop commented Mar 16, 2024

Hi @sohailA-splore , sorry for the delay!
I just went through the process of connecting to a local application and I managed to connect successfully to a localhost.

A couple of questions:

  • What version of Vespa are you trying to run?
  • Are you able to index and query the vespa application you deployed (qa-semantic-retrieval)?
  • What error do you get on you vispana's container?

A way to isolate a possible network issue would be to run Vispana from source and try to connect to http://localhost:19071. It should avoid the docker network dance entirely.

@sohailA-splore
Copy link
Author

Hi @broknloop ,
I am facing this issue when trying to use docker network. Otherwise it is working for me.

@fabianotex
Copy link

I'm facing the same issue. Getting the following error:

2024-09-17T15:19:21.213Z ERROR 1 --- [mcat-handler-53] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed: java.lang.RuntimeException: java.lang.RuntimeException: Failed to get data from Vespa] with root cause

org.springframework.web.client.HttpClientErrorException$NotFound: 404 Not Found: "{"error-code":"NOT_FOUND","message":"Session 3 does not contain a file at path '/services.xml'"}"
        at org.springframework.web.client.HttpClientErrorException.create(HttpClientErrorException.java:112) ~[spring-web-6.1.1.jar!/:6.1.1]
        at org.springframework.web.client.StatusHandler.lambda$defaultHandler$3(StatusHandler.java:86) ~[spring-web-6.1.1.jar!/:6.1.1]
        at org.springframework.web.client.StatusHandler.handle(StatusHandler.java:146) ~[spring-web-6.1.1.jar!/:6.1.1]
        at org.springframework.web.client.DefaultRestClient$DefaultResponseSpec.applyStatusHandlers(DefaultRestClient.java:654) ~[spring-web-6.1.1.jar!/:6.1.1]
        at org.springframework.web.client.DefaultRestClient.readWithMessageConverters(DefaultRestClient.java:192) ~[spring-web-6.1.1.jar!/:6.1.1]
        at org.springframework.web.client.DefaultRestClient$DefaultResponseSpec.readBody(DefaultRestClient.java:641) ~[spring-web-6.1.1.jar!/:6.1.1]
        at org.springframework.web.client.DefaultRestClient$DefaultResponseSpec.body(DefaultRestClient.java:589) ~[spring-web-6.1.1.jar!/:6.1.1]
        at com.vispana.vespa.state.helpers.Request.requestGet(Request.java:10) ~[!/:0.0.1-SNAPSHOT]
        at com.vispana.vespa.state.assemblers.AppPackageAssembler.assemble(AppPackageAssembler.java:14) ~[!/:0.0.1-SNAPSHOT]
        at com.vispana.vespa.state.VespaStateClient.lambda$vespaState$4(VespaStateClient.java:33) ~[!/:0.0.1-SNAPSHOT]
        at java.base/java.util.concurrent.StructuredTaskScope$SubtaskImpl.run(StructuredTaskScope.java:889) ~[na:na]
        at java.base/java.lang.VirtualThread.run(VirtualThread.java:309) ~[na:na]

Vespa is operational and my team is using it just fine. Getting response from ports 19071 and 8080 via curl.

Any ideas?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants