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""
Database is started and populated with .dump file (from repository)
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:
On server1, installed Docker (17.05.0) and Docker Compose (1.19.)
cloned the git repository and ran the install.sh. (no configuration changes made until later)
the install.sh produced the errors in attachment "Install_Dispatch.out", .. (this would be expected)
Setting up database...
No JWT secret specified, this is required if you are using basic authentication.
NCIDENT_DAILY_SUMMARY_ONCALL_SERVICE_ID has been deprecated. Please use INCIDENT_ONCALL_SERVICE_ID instead.
No metric providers specified metrics will not be sent.
ERROR:dispatch.common.utils.cli:Something went wrong with creating plugin rows, is the database setup correctly?
:
:
On server2, installed PostgreSQL 12.3
created a new role called 'dispatch' :
su - postgres
createuser --interactive --pwprompt
Enter name of role to add: dispatch
Enter password for new role:
Enter it again:
Shall the new role be a superuser? (y/n) y
postgres=# \du
List of roles
Role name | Attributes | Member of
-----------+------------------------------------------------------------+-----------
dispatch | Superuser, Create role, Create DB | {}
postgres | Superuser, Create role, Create DB, Replication, Bypass RLS | {}
and then imported the sample .dump file from the Git repository to populate the database 'dispatch_db'
drop database dispatch_db
create database dispatch_db
sudo -u postgres -i psql -h 127.0.0.1 -U postgres -p 5432 dispatch_db < /root/dispatch-sample-data.dump
This was successful. and postgres is listening on 5432
Finally I made some configuration changes on server1
modified the .env file to include the Database information
# NOTE: Ensure that DATABASE_CREDENTIALS match the values passed to POSTGRES_USER and POSTGRES_PASSWORD
DATABASE_CREDENTIALS=postgres:<PASSWORD>
DATABASE_HOSTNAME=server2.fyre.ibm.com
DATABASE_NAME=dispatch_db
DATABASE_PORT=5432
# Used by postgres docker
POSTGRES_DB=dispatch_db
POSTGRES_PASSWORD=<PASSWORD>
POSTGRES_USER=postgres
-------------------------------------------------------------------------------------------------------
Modified the. docker-compose.yml. file (this line)
volumes:
- "dispatch-postgres:/var/lib/postgresql/12/main"
as this is where the data is stored according to command below
# sudo -u postgres psql -c "show data_directory;"
data_directory
-----------------------------
/var/lib/postgresql/12/main
(1 row)
-------------------------------------------------------------------------------------------------------
systemctl start postgresql@12-main.service
-------------------------------------------------------------------------------------------------------
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
This worked and output the query data , but ONLY after making these necessary changes on the Postgres side:
Insert line
listen_addresses = '*'
in postgresql.conf
Insert line
host dispatch_db all /24 md5
in pg_hba.conf . This is to allow connections from clients
then restart postgres service
so at this point it is possible to connect and retrieve the data from Postgres to remote computers
However I still cannot see the data coming across in the UI..
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):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
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:
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:
On server1, installed Docker (17.05.0) and Docker Compose (1.19.) cloned the git repository and ran the install.sh. (no configuration changes made until later) the install.sh produced the errors in attachment "Install_Dispatch.out", .. (this would be expected) Setting up database... No JWT secret specified, this is required if you are using basic authentication. NCIDENT_DAILY_SUMMARY_ONCALL_SERVICE_ID has been deprecated. Please use INCIDENT_ONCALL_SERVICE_ID instead. No metric providers specified metrics will not be sent. ERROR:dispatch.common.utils.cli:Something went wrong with creating plugin rows, is the database setup correctly? : :
On server2, installed PostgreSQL 12.3 created a new role called 'dispatch' :
su - postgres createuser --interactive --pwprompt Enter name of role to add: dispatch Enter password for new role: Enter it again: Shall the new role be a superuser? (y/n) y
postgres=# \du List of roles Role name | Attributes | Member of -----------+------------------------------------------------------------+----------- dispatch | Superuser, Create role, Create DB | {} postgres | Superuser, Create role, Create DB, Replication, Bypass RLS | {}
and then imported the sample .dump file from the Git repository to populate the database 'dispatch_db'
drop database dispatch_db create database dispatch_db
sudo -u postgres -i psql -h 127.0.0.1 -U postgres -p 5432 dispatch_db < /root/dispatch-sample-data.dump This was successful. and postgres is listening on 5432
Finally I made some configuration changes on server1
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:
Insert line host dispatch_db all/24 md5
in pg_hba.conf . This is to allow connections from clients
then restart postgres service
so at this point it is possible to connect and retrieve the data from Postgres to remote computers
However I still cannot see the data coming across in the UI..
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?
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.