OpsDB runs on two servers, named appropriately xxxxxx-opsdb01.geant.net and xxxxx-opsdb02.geant.net where xxxxx = prod, uat, or test
The following points may help troubleshot any issues that arise with this application.
Check Apache.
- Has apache failed? Is it running?
Log into the appropriate VM
As Root user issue the following command at the command line:
systemctl status httpd
(or)
service httpd status
(If no root user, prefix both commands by sudo)
You should see output something like this:
[mark.golder@test-opsdb01 ~]$ sudo service httpd status
httpd (pid 18768) is running...
[mark.golder@test-opsdb01 ~]$
- Start / Restart Apache
If you need to Start / Restart the httpd (apache) server issue the following command at the command line:
systemctl restart httpd
(or)
service httpd restart
(If not root user, prefix both commands by sudo)
This should start or restart the http server (apache) on the VM – please perform this on both VMs separately.
Check MySQL.
- Is the MySQL instance running?
Log into the appropriate VM
As Root user issue the following command at the command line:
systemctl status mysqld
(or)
service mysqld status
(If no root user, prefix both commands by sudo)
- Start / Restart MySQL
If you need to Start / Restart MySQL issue the following command at the command line:
systemctl restart mysqld
(or)
service mysqld restart
(If not root user, prefix both commands by sudo)
This should start or restart MySQL on the VM – please perform this on both VMs separately.
Recovery of MySQL Data
Currently MySQL data backups are stored in the /opt/vackups/mysql folder within each VM.
Each day the daily DB dump, from each server, is also copied to an appropriate place on the Data Warehouse machine.
To restore any of these instances of data, locate the appropriate DB dump and go through the mysql restore procedure (documented elsewhere in MySQL documentation)
Change the Domain Name System (DNS) entry for OpsDB
Currently we direct all the OpsDB public domain URI calls to the ‘01’ instance of the appropriate OpsDB VM.
If required (i.e. the 01 instance of a VM is down) we can change the DNS to point our public domain URI to the 02 VM service whilst the 01 VM is being fixed – this should ensure they service continues to be available to the public.
To do this will require changes to be made by the systems administrator and is documented elsewhere.
Security Updates with underlying software and operating systems
OpsDB is, in terms of software, an ‘old lady’ now, awaiting retirement.
It is currently written using PHP 5.3.3, HTML, JavaScript, and runs in a Linux system environment (Centos).
Centos - CentOS-6 updates until November 30, 2020
PHP 5.3.3 FINISHED being officially supported, but being supported via centos back porting of PHP security releases – end of life same as centos 6 system.
HTML / Javascript are currently supported and have no future planned support end dates, in fact older versions are more supported than the latest ones!.
Check disk usage
Is the VM disk full?
Is the allocated OpsDB disk space full.
This should already be being monitored and reported upon if it is becoming full , so this scenario should never occur.