Unable to get Datafari 3.1 running on Debian 8.7

[Kay Goldinger]

Hi There

I'm trying to setup Datafari 3.1 on a fresh installed Debian 8.7 VM using the Deb package.

After installing the dependencies the installation runs smooth, but If I try to start Datafari by "start-datafari.sh", I end up with the following messages:

Configure ELK

[sudo] password for solag:

[2017-03-02 21:51:34,631][INFO ][node                     ] [Negasonic Teenage Warhead] version[2.0.2], pid[850], build[6abf5d8/2015-12-16T12:49:58Z]

[2017-03-02 21:51:34,654][INFO ][node                     ] [Negasonic Teenage Warhead] initializing ...

[2017-03-02 21:51:34,704][INFO ][plugins                  ] [Negasonic Teenage Warhead] loaded [], sites []

[2017-03-02 21:51:34,953][INFO ][env                      ] [Negasonic Teenage Warhead] using [1] data paths, mounts [[/ (rootfs)]], net usable_space [5.3gb], net total_space [8.1gb], spins? [unknown], types [rootfs]

[2017-03-02 21:51:37,187][INFO ][node                     ] [Negasonic Teenage Warhead] initialized

[2017-03-02 21:51:37,187][INFO ][node                     ] [Negasonic Teenage Warhead] starting ...

[2017-03-02 21:51:37,453][INFO ][transport                ] [Negasonic Teenage Warhead] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300}, {[::1]:9300}

[2017-03-02 21:51:37,464][INFO ][discovery                ] [Negasonic Teenage Warhead] elasticsearch/-qy8MwkeSpG1Y3taZZQ7Ag

[2017-03-02 21:51:40,499][INFO ][cluster.service          ] [Negasonic Teenage Warhead] new_master {Negasonic Teenage Warhead}{-qy8MwkeSpG1Y3taZZQ7Ag}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-join(elected_as_master, [0] joins received)

[2017-03-02 21:51:40,552][INFO ][http                     ] [Negasonic Teenage Warhead] publish_address {127.0.0.1:9200}, bound_addresses {127.0.0.1:9200}, {[::1]:9200}

[2017-03-02 21:51:40,553][INFO ][node                     ] [Negasonic Teenage Warhead] started

[2017-03-02 21:51:40,617][INFO ][gateway                  ] [Negasonic Teenage Warhead] recovered [1] indices into cluster_state

 log   [21:51:50.334] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready

 log   [21:51:50.353] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch

 log   [21:51:50.363] [info][status][plugin:kbn_vislib_vis_types] Status changed from uninitialized to green - Ready

 log   [21:51:50.365] [info][status][plugin:markdown_vis] Status changed from uninitialized to green - Ready

 log   [21:51:50.366] [info][status][plugin:metric_vis] Status changed from uninitialized to green - Ready

 log   [21:51:50.368] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready

 log   [21:51:50.371] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready

 log   [21:51:50.373] [info][status][plugin:table_vis] Status changed from uninitialized to green - Ready

 log   [21:51:50.423] [warning][pid] pid file already exists at /opt/datafari/bin/../pid/kibana.pid

 log   [21:51:50.425] [info][listening] Server running at http://0.0.0.0:5601

 log   [21:51:50.536] [info][status][plugin:elasticsearch] Status changed from yellow to green - Kibana index ready

parse error: Invalid numeric literal at line 3, column 0

Is this a known issue? Any hint is very appreciated!

Thanks and best regards

Kay

[julien....@francelabs.com]

Hi Kay,

 

Based on the screenshot you provided, the configuration phase of Datafari fails to reach Elasticsearch because an instance is already running on your system.

Try to run the ‘stop-datafari.sh’ script, then search for any Elasticsearch and Kibana processes with the following commands :
- ‘ps aux | grep elasticsearch’

- ‘ps aux | grep kibana’
And kill any existing one with a ‘sudo kill [pid]’ command.

Then run again the start-datafari.sh script. If it fails again, that means that after starting Elasticsearch to perform some configuration, the script is unable to contact Elastic search on localhost:9200, this case mostly happens when you have configured an http proxy on your machine and did not disable the proxy when the host is 127.0.0.1 or localhost (if you set the http_proxy environment variable, this is exactly the case).

 

By the way, we are aware that this case can happen and will handle it properly in the next version of Datafari with an explicit error message and a clean stop of Elasticsearch and Kibana to avoid having ‘phantom’ instances.

 

Looking forward for your answer.

Regards,
Julien Massiera

 

De : Kay Goldinger
Envoyé le :vendredi 3 mars 2017 12:47
À : Datafari
Objet :Unable to get Datafari 3.1 running on Debian 8.7

--
You received this message because you are subscribed to the Google Groups "Datafari" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datafari+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

 

Garanti sans virus. www.avast.com

[Kay Goldinger]

Hi Julien 

Adding the missing proxy exception did the trick, problem solved!

Thanks a lot and best regards

Kay