search

VIDA-NYU / domain_discovery_tool_deprecated

Seed acquisition tool to bootstrap focused crawlers
23 stars 8 forks source link

DDT - Standalone; ddt (exit status 1; not expected) #72

Closed mikew77 closed 8 years ago

mikew77 commented 8 years ago

Hi folks, am getting some issues with the stand alone deployment. The package builds (make) and then can run ddt, but can't open the application on localhost:8084. The terminal shows this pattern of starting, then exiting ddt roughly every three minutes. A sample is pasted below:

2016-03-16 12:10:40,956 INFO success: ddt entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-03-16 12:13:00,284 INFO exited: ddt (exit status 1; not expected) 2016-03-16 12:13:01,357 INFO spawned: 'ddt' with pid 28709 2016-03-16 12:13:02,359 INFO success: ddt entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-03-16 12:16:51,898 INFO exited: ddt (exit status 1; not expected) 2016-03-16 12:16:52,901 INFO spawned: 'ddt' with pid 28849 2016-03-16 12:16:53,903 INFO success: ddt entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Log files are attached; not sure if this is a local config issue with the system I'm using (Ubuntu 14.04), but thought I'd raise to as I checked the other issues and couldn't find anything similar. Any advice or suggestions would be much appreciated! Thanks.

ddt-stderr---supervisor-SV4uTK.log.txt

yamsgithub commented 8 years ago

I ran ddt with the supervisord command. All seemed to work fine for me. Looks like there was an issue with connecting to elasticsearch. Could you please check if the elasticsearch is running fine. You can look at the logs for DDT and elasticsearch using the link localhost:9001 (if you are running on localhost)

mikew77 commented 8 years ago

Hi Yams; this seems to be working now - I agree looked like an elasticsearch issue. I found another issue which I resolved by a full system rebuild but will raise for review separately.