# 5-DRC INSIGHT - Validation and Testing

#   


**Purpose:** Confirm COS is functioning properly before live testing begins.

---

## Step 1 - Verify Services

```
sudo /opt/CentralOffice/node \
/opt/CentralOffice/setup/node_modules/forever/bin/forever -p /opt/CentralOffice list
```

**Confirm all four are running:**

- management
- relay
- proxy
- contenthosting

---

## Step 2 - Verify Ports

```
sudo ss -tulnp | grep node
```

---

## Step 3 - Validate Local HTTP Response

```
curl -I http://127.0.0.1:55223
curl -I http://127.0.0.1:55224
curl -I http://127.0.0.1:55225
```

An HTTP 404 response at the root path can still indicate a healthy service.

---

## Step 4 - Validate Content Directory

```
ls -lah /opt/CentralOffice/content_fs
```

The local content directory should populate after configuration is updated and content is downloaded.

---

## Step 5 - Confirm DRC Portal Status

- Configuration shows green
- Correct test content is selected
- Content Hosting is enabled

---

## Step 6 - Validate Chromebook Access

- Confirm device is registered to the correct ORG Unit
- Confirm Chromebook settings are correct
- Open DRC INSIGHT and verify successful registration and readiness

---

## Pre-Test Validation Checklist

- \[ \] COS registered with DRC
- \[ \] All COS services running
- \[ \] Node ports listening
- \[ \] Local content downloaded
- \[ \] Portal configuration green
- \[ \] Chromebooks registered to ORG Unit
- \[ \] Chromebook display size 100%
- \[ \] Chromebook keyboard US English

---

**Next Page:** Troubleshooting