search

usc-isi-i2 / dig-etl-engine

Download DIG to run on your laptop or server.
http://usc-isi-i2.github.io/dig/
MIT License
101 stars 39 forks source link

Dig UI not being displayed #282

Open darkfire5900 opened 4 years ago

darkfire5900 commented 4 years ago

As a disclaimer this could be an issue with the fact I haven't used Docker before*

I followed the installation instructions, etc, everything seems to be installed fine with no errors, the web server starts up, when I navigate to it on Chrome, the Dig UI is completely blank, when I view the source there is certainly something being loaded, however it doesn't seem to be displayed.

jgerardsimcock commented 4 years ago

I am running on a Mac with High Sierra OS. The Flask Server is registering 200 response code's so the requests are making it there.

Screen Shot 2020-05-17 at 2 14 22 PM
jgerardsimcock commented 4 years ago

@saggu Do you have any sense of why the UI is not loading?

Also, what is the status of this project? I see no new updates for about 18 months. Are there subsequent projects that have more active code contribution that we should be paying attention to?

saggu commented 4 years ago

@jgerardsimcock there has been some issues after chrome update 80. We are currently working on a new version. There will be a new release soon.

jgerardsimcock commented 4 years ago

Thank you very much @saggu

aindilis commented 3 years ago

I can confirm I am having the same issue. I am running Dig inside a libvirt virtual machine using Vagrant. I set the DOMAIN in .env to the IP of the VM. Initially started docker with sudo /etc/init.d/docker start and thus had to run as superuser with: sudo ./engine.sh up. Later I figured out that by running sudo systemctl start docker instead (and possibly, by having my user added to the docker group) I could just run as ./engine.sh up. Not sure if initially running as root damaged my installation. However, in both cases, when I point to http://IP:12497/mydig/ui I get a blank screen (which I initially did from Firefox, but then from Chrome). If I go to /mydig/ui/static/new.html it will load a lot of bower_components. If I go to /mydig it will show "MyDIG Web Service" and if I go to / it will show "DIG ETL Engine myDIG UI Github Repository". I will continue trying to get it to work, but I was wondering if there was any update with this bug. I am really looking forward to trying out this system. I am trying to determine if it will work for my use case of building a comprehensive software ontology by scraping (academic) websites and extracting names of software systems and relating them to other mentioned entities / artifacts like author names, licenses, downloaded URLs, etc. Thanks for making your system available!

mayanklal commented 3 years ago

Any update regarding this?

I am getting following errors:

kibana_1 | {"type":"log","@timestamp":"2020-10-29T08:17:24Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}

logstash_1         | [2020-10-29T08:16:05,574][ERROR][logstash.agent           ] failed to fetch pipeline configuration {:message=>"No config files found: /usr/share/logstash/pipeline. Can you make sure this path is a logstash config file?"}
dig_logstash_1 exited with code 1

I'm using Firefox as my default browser.

Nareshmn982 commented 3 years ago

@saggu .....

Getting the above errors at my end. installed desktop docker and trying to up the DIG project.

1) No config files found in path {:path=>"/usr/share/logstash/pipeline/*"}

[2021-06-17T07:20:10,521][ERROR][logstash.agent ] failed to fetch pipeline configuration {:message=>"No config files found: /usr/share/logstash/pipeline. Can you make sure this path is a logstash config file?"}

2) initialized

[2021-06-17T07:19:58,681][INFO ][o.e.n.Node ] [wfXSPoP] starting ...

[2021-06-17T07:19:59,145][INFO ][o.e.t.TransportService ] [wfXSPoP] publish_address {172.19.0.3:9300}, bound_addresses {0.0.0.0:9300}

[2021-06-17T07:19:59,175][INFO ][o.e.b.BootstrapChecks ] [wfXSPoP] bound or publishing to a non-loopback or non-link-local address, enforcing bootstrap checks

ERROR: [1] bootstrap checks failed

[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

[2021-06-17T07:19:59,219][INFO ][o.e.n.Node ] [wfXSPoP] stopping ...

[2021-06-17T07:19:59,371][INFO ][o.e.n.Node ] [wfXSPoP] stopped

[2021-06-17T07:19:59,372][INFO ][o.e.n.Node ] [wfXSPoP] closing ...

[2021-06-17T07:19:59,415][INFO ][o.e.n.Node ] [wfXSPoP] closed

Help me to come out the issue.

Nareshmn982 commented 3 years ago

@saggu / @szeke In chrome Browser i am getting blank page when i logged in DIG UI. Please suggest some info to get the Proper to get log in.

donaq commented 2 years ago

The reason the UI is not working is because mydig-webservice/frontend relies on HTML imports, a feature that was only ever implemented on Chrome browser and which even Chrome has since deprecated. The following workaround works for me.

  1. Change the image for mydig_ws in docker.yml to this:
image: mydig_ws

  1. Clone the mydig-webservice repo.

  2. Add the following line in the <head> section of frontend/templates/projectDetailsUpdate.html and frontend/templates/updateIndex.html.

  3. Create Dockerfile.local in the root of your mydig-webservice repo with the following content:

FROM uscisii2/mydig_ws:2.0.4

COPY frontend /app/mydig-webservice/frontend
  1. Create the docker image. cd to the repo root and run the following command.
docker build -t mydig_ws -f Dockerfile.local .
  1. ./engine.sh up should work now.