Health-Screen

Last update on . Missing something? sysadmin@accelerated.de

Overall Status

Currently monitoring services.

25%

Yellow indicates that there are at least 2 failover systems; Red that there is at least one component without enough failover systems.

Quick Links, Documentation

Documentation
- DB-Stack
- WI-Cluster
Gitlab
- Webinterface
- Health Screen

Desaster Recovery

Try to verify that the problem is not at the loadbalancers by circumventing them: enter 192.168.202.101 admin.accelerated.de into your /etc/hosts, close your browser, re-open it and check if the interface works. Do the same for 192.168.202.102 and 192.168.202.103.

Try to verify that the problem is not at the psql instances: connect to them through mysql -h 192.168.202.101 -p 6032 -u .. -p . Try the same for 192.168.202.102 and 192.168.202.103.

Status FCTS1

Status FCTS2

Status FCTS3

Redis1 Instant Operations per sec

This redis handled Commands so far.

Redis2 Instant Operations per sec

This redis handled Commands so far.

Redis3 Instant Operations per sec

This redis handled Commands so far.

Redis1 Active Connections

This redis handled Connections so far.

Redis2 Active Connections

This redis handled Connections so far.

Redis3 Active Connections

This redis handled Connections so far.

Global Query Command Statistics

Tests Database

#	State	Test	Description
1	web1 web2 web3	Connection Test	This test establishes a new connection to the database server in order to check whether connecting is successful.
2	web1 web2 web3	Write Test	This test truncates a test table and fills 100 rows with test data in order to check whether writing to the database is successful.
3	web1 web2 web3	Read Test	This test reads 100 rows from a test table (and creates them prior to running this test). In order to check whether reading is successful it compares the row contents with pre-defined values.
4	web1 web2 web3	Integrity Test	This test checks whether a few key tables are present, namely `language`, `user`, `c_server`, `serviceReports`, `projects`, `global_vars`, `userPermissions`, `userRights` and `vlans`. All tables must exist in order for the test to be successful.

Tests Redis

#	State	Test	Description
1	web1 web2 web3	Connection Test	This test establishes a new connection to the Redis cluster in order to check whether connecting is successful.
2	web1 web2 web3	Write Test	This test writes 100 key-value pairs in order to check whether writing to the redis cluster is successful.
3	web1 web2 web3	Read Test	This test reads 100 key values (and creates key-value pairs prior to running the test). In order to check whether readins is successful it compares the values with pre-defined ones.

Tests DNS

#	State	Test	Description
1	web1 web2 web3	DNS Internal	This test attempts to resolve the host `wi-lb1.vm.serv` in order to check internal name resolution.
2	web1 web2 web3	DNS External	This test attempts to resolve the host `google.com` in order to check external name resolution.