Netflix / dispatch

All of the ad-hoc things you're doing to manage incidents today, done for you, and much more!
Apache License 2.0
5.09k stars 507 forks source link

Cannot see dispatch views being populated with data, after configuring database correctly! #501

Closed mccannm1 closed 4 years ago

mccannm1 commented 4 years ago

Describe the bug This similar to issue: https://github.com/Netflix/dispatch/issues/416

Problem: I start the dispatch server: docker-compose up -d When I hit the URL http://server1.fyre.ibm.com:8000/dashboard I do see the page rendering but the views/dashboards are not getting populated and a message appears saying "Something has gone very wrong please retry or inform your admin you are receiving this error""

To Reproduce Steps to reproduce the behavior:

  1. Go to http://server1.fyre.ibm.com:8000/dashboard
  2. Database is started and populated with .dump file (from repository)
  3. No data in dispatch UI See error "Something has gone very wrong please retry or inform your admin you are receiving this error""

What I have done (below)

Hello Kevin I have been requested to investigate the possibility of using Netflix Dispatch as a new Incident Management solution in my organization. I have TWO Fyre Virtual machines server1, server2. The former is where the dispatch server is being installed and the second hosts the Postgres database that Dispatch relies on. I presume it is ok to have the server and DB on two separate machines? Both servers have Ubuntu OS. I have performed the following actions:

I tried running the ./install.sh again.... but I still get the same error in the UI... the views are not getting populated.

I investigated further and used a small java application on server1 to connect to 'dispatch_db' and run a query on the database. e.g SELECT ID,NAME,DESCRIPTION FROM INCIDENT_PRIORITY

java -cp ./postgresql-42.2.14.jre7.jar:. Testserver1 //server2.fyre.ibm.com:5432/dispatch_db postgres

This worked and output the query data , but ONLY after making these necessary changes on the Postgres side:

QUESTIONS:
As far as I can see the database is ok.. Is there some other change I need to make to get the data across to the dispatch machine?

    How is the CLI enabled?  or how to use it.....
    when I run dispatch I get command not found.   (on the dispatch server)

From looking at the other GitHub issues. >dispatch upgrade database is necessary 
How do you start the CLI?  

Any help appreeciated 
Thanks 
/Martin

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Smartphone (please complete the following information):

Additional context Add any other context about the problem here.

mccannm1 commented 4 years ago

ok thanks @kevgliss @mvilanova .. will re-review deployment setup