Skip to content
This repository has been archived by the owner on Apr 7, 2021. It is now read-only.

Could you tell me use this? #25

Open
applideveloper opened this issue Dec 2, 2017 · 4 comments
Open

Could you tell me use this? #25

applideveloper opened this issue Dec 2, 2017 · 4 comments

Comments

@applideveloper
Copy link

applideveloper commented Dec 2, 2017

Reference

https://developer.lightbend.com/docs/cinnamon/2.6.x/visualizations/vizceral.html

Set up

git clone https://github.com/lightbend/cinnamon-ui.git
cd cinnamon-ui/cinnamon/vizceral
docker-compose up

Error log

web_1            | webpack: Compiled successfully.
backend_1        | ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
backend_1        | [error] a.VizceralDataActor - RestClient failure during communication with Elasticsearch on host: http://elasticsearch:9200

?

2017-12-02 21 52 45

I want to use this.

Could you tell me use this?

@henrikengstrom
Copy link
Contributor

If you look at the last couple of lines you can see that there is an error when the Vizceral backend service tries to communicate with Elasticsearch. What services do you see if you type docker ps?

@applideveloper
Copy link
Author

applideveloper commented Dec 9, 2017

@henrikengstrom

vizceral araki$ docker ps
CONTAINER ID        IMAGE                                                                          COMMAND                  CREATED             STATUS              PORTS                    NAMES
fa5498888161        lightbend-docker-registry.bintray.io/cinnamon/cinnamon-vizceral-frontend:0.1   "npm run dev"            17 minutes ago      Up 17 minutes       0.0.0.0:8080->8080/tcp   vizceral_web_1
2ecf12bf3462        lightbend-docker-registry.bintray.io/cinnamon/cinnamon-vizceral:0.1            "bin/cinnamon-vizc..."   17 minutes ago      Up 17 minutes       0.0.0.0:8999->8999/tcp   vizceral_backend_1
vizceral araki$ docker images 
REPOSITORY                                                                 TAG                 IMAGE ID            CREATED             SIZE
lightbend-docker-registry.bintray.io/cinnamon/cinnamon-vizceral            0.1                 f730cb81ef5f        5 weeks ago         886MB
lightbend-docker-registry.bintray.io/cinnamon/cinnamon-vizceral-frontend   0.1                 c86233ec8748        5 weeks ago         344MB
docker.elastic.co/elasticsearch/elasticsearch                              5.6.3               865b21b970de        8 weeks ago         657MB

@applideveloper
Copy link
Author

applideveloper commented Dec 9, 2017

vizceral araki$ docker exec -it 2ecf12bf3462 bash

daemon@2ecf12bf3462:/opt/docker$ vi conf/application.conf 
bash: vi: command not found
daemon@2ecf12bf3462:/opt/docker$ cat conf/application.conf 
# https://www.playframework.com/documentation/latest/Configuration

# Disables the security filters to enable the Vizceral javascript functionality
play.filters.enabled=[]

play.http.secret.key="cinviz"

# Run this process on a non-default port to not collide with other Play apps
play.server.http.port = 8999

cinnamon-vizceral {
  data-backend {
    frequency = 10 seconds
  }

  elasticsearch-backend {
    host =  "elasticsearch" // Maybe this!
    port = 9200
    retrieval-window = 30s // should have format xs, xm, xh, etc. where x is a number 1-n.
    max-size = 1000
    max-retry-timeout-millis = 10000
    user = "elastic"
    password = "changeme"
  }
}

daemon@2ecf12bf3462:/opt/docker$  sed -i -e "s/elasticsearch/localhost/" conf/application.conf 

2017-12-09 19 15 59

@ghost
Copy link

ghost commented Mar 25, 2018

@applideveloper according to docker ps, your elasticsearch and kibana instances are not running. Verify that your cinnamon docker network is created with docker network ls, then run the following:

  • start elasticsearch container (-d for daemon mode)
    docker container run -d -p 9200:9200 -p 9300:9300 --name elasticsearch --network cinnamon elasticsearch:5.6.3

  • check container logs for elasticsearch container to ensure it started OK
    docker logs elasticsearch

with elasticsearch running on the cinnamon network, all the other containers on the cinnamon network will be able to communicate with it using the network alias elasticsearch on port 9200 and 9300.

I have a feeling your elasticsearch container failed to start OK. good luck! and let me know if your issues persist. I'm about to start working with this project myself.

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

No branches or pull requests

2 participants