# DBIS Services Status Check

**Date**: 2026-01-02  
**Purpose**: Comprehensive check of application services status and configuration for all DBIS containers after IP address changes

---

## Summary

This document provides a detailed status check of all application services running inside DBIS containers to verify they are properly configured and running after the IP address changes.

---

## Container Status Overview

| VMID | Service Type | Container Status | Application Service Status | Notes |
|------|-------------|------------------|---------------------------|-------|
| 10100 | PostgreSQL Primary | ✅ Running | ⏳ To be checked | Database server |
| 10101 | PostgreSQL Replica | ✅ Running | ⏳ To be checked | Database replica |
| 10120 | Redis Cache | ✅ Running | ⏳ To be checked | Cache server |
| 10130 | Frontend | ✅ Running | ⏳ To be checked | Web interface |
| 10150 | API Primary | ✅ Running | ⏳ To be checked | Backend API |
| 10151 | API Secondary | ✅ Running | ⏳ To be checked | Backend API (HA) |

---

## Detailed Service Checks

### VMID 10100 - PostgreSQL Primary

**Container IP**: 192.168.11.105/24  
**Expected Service**: PostgreSQL on port 5432

**Status**:
- Container: ✅ Running
- PostgreSQL Service: ⏳ Check in progress
- Port 5432: ⏳ Check in progress
- Configuration: ⏳ Check in progress

**Action Required**:
- Verify PostgreSQL is installed and running
- Check if service needs to be started
- Verify configuration files reference correct IP (192.168.11.105)

---

### VMID 10101 - PostgreSQL Replica

**Container IP**: 192.168.11.106/24  
**Expected Service**: PostgreSQL on port 5432

**Status**:
- Container: ✅ Running
- PostgreSQL Service: ⏳ Check in progress
- Port 5432: ⏳ Check in progress
- Configuration: ⏳ Check in progress

**Action Required**:
- Verify PostgreSQL is installed and running
- Check replication configuration
- Verify configuration files reference correct IP (192.168.11.106)

---

### VMID 10120 - Redis Cache

**Container IP**: 192.168.11.120/24  
**Expected Service**: Redis on port 6379

**Status**:
- Container: ✅ Running
- Redis Service: ⏳ Check in progress
- Port 6379: ⏳ Check in progress
- Configuration: ⏳ Check in progress

**Action Required**:
- Verify Redis is installed and running
- Check if service needs to be started

---

### VMID 10130 - Frontend

**Container IP**: 192.168.11.130/24  
**Expected Service**: Nginx/web server on ports 80/443

**Status**:
- Container: ✅ Running
- Web Service: ⏳ Check in progress
- Ports 80/443: ⏳ Check in progress
- Configuration: ⏳ Check in progress

**Action Required**:
- Verify Nginx/web server is running
- Check API endpoint configuration (should reference new API IPs)
- Verify configuration files reference correct API IPs (192.168.11.155, 192.168.11.156)

---

### VMID 10150 - API Primary

**Container IP**: 192.168.11.155/24  
**Expected Service**: Node.js API on port 3000

**Status**:
- Container: ✅ Running
- API Service: ⏳ Check in progress
- Port 3000: ⏳ Check in progress
- Health Endpoint: ⏳ Check in progress
- Configuration: ⏳ Check in progress

**Action Required**:
- Verify Node.js application is running
- Check database connection string (should reference 192.168.11.105)
- Verify health endpoint is accessible
- Check for any hardcoded IP references to old addresses

---

### VMID 10151 - API Secondary

**Container IP**: 192.168.11.156/24  
**Expected Service**: Node.js API on port 3000

**Status**:
- Container: ✅ Running
- API Service: ⏳ Check in progress
- Port 3000: ⏳ Check in progress
- Health Endpoint: ⏳ Check in progress
- Configuration: ⏳ Check in progress

**Action Required**:
- Verify Node.js application is running
- Check database connection string (should reference 192.168.11.105)
- Verify health endpoint is accessible
- Check for any hardcoded IP references to old addresses

---

## Configuration Files to Check

### Database Connection Strings

Applications that connect to PostgreSQL should use:
- **Old IP**: `192.168.11.100` (no longer valid)
- **New IP**: `192.168.11.105`

**Locations to check**:
- Environment variables: `DATABASE_URL`, `DB_HOST`
- Configuration files: `.env`, `config/*.yaml`, `config/*.json`
- Application code: Any hardcoded connection strings

### API Endpoint Configuration

Frontend and other services connecting to API should use:
- **Old IPs**: `192.168.11.150`, `192.168.11.151` (no longer valid)
- **New IPs**: `192.168.11.155`, `192.168.11.156`

**Locations to check**:
- Environment variables: `VITE_API_BASE_URL`, `API_URL`
- Nginx configuration: Proxy pass directives
- Configuration files: Any API endpoint references

---

## External Connectivity Test

Test if services are accessible from outside containers:

| Service | IP:Port | Expected | Status |
|---------|---------|----------|--------|
| PostgreSQL Primary | 192.168.11.105:5432 | Accessible | ⏳ To test |
| PostgreSQL Replica | 192.168.11.106:5432 | Accessible | ⏳ To test |
| API Primary | 192.168.11.155:3000 | Accessible | ⏳ To test |
| API Secondary | 192.168.11.156:3000 | Accessible | ⏳ To test |
| Redis | 192.168.11.120:6379 | Accessible | ⏳ To test |

---

## Next Steps

1. ✅ Run comprehensive service status checks
2. ✅ Verify configuration files for old IP references
3. ⏳ Start services if not running
4. ⏳ Update configuration files with new IPs if found
5. ⏳ Test service connectivity
6. ⏳ Verify database connections
7. ⏳ Verify API endpoints

---

**Last Updated**: 2026-01-02  
**Status**: ⏳ **IN PROGRESS** - Running checks
