6-DRC INSIGHT - COS Troubleshooting


Purpose: Resolve the most common Linux COS installation, service, and Chromebook issues.


Issue 1 - Installer Fails or Stops Early

Symptoms:

Fix:

sudo chmod 1777 /tmp
sudo rm -rf /opt/CentralOffice
sudo rm -f /tmp/coinstaller*.lock
sudo ./silent-linux.sh

Issue 2 - Only Proxy Runs

Symptoms:

Likely Cause:

Fix:


Issue 3 - Relay Heartbeat Error

Error:

CO API - Heartbeat returned undefined

Likely Cause:

Fix:


Issue 4 - Services Show "active (exited)"

This can be normal. COS uses forever to launch Node services in the background, so the systemd wrapper may show as exited while the Node processes continue running.

Use this command as the truth source:

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

Issue 5 - Chromebooks Cannot Connect

Check:


Issue 6 - Content Does Not Download

Check:


Useful Commands

# Check runtime services
sudo /opt/CentralOffice/node \
/opt/CentralOffice/setup/node_modules/forever/bin/forever -p /opt/CentralOffice list

# Check ports
sudo ss -tulnp | grep node

# Check content directory
ls -lah /opt/CentralOffice/content_fs

# Follow content hosting logs
sudo journalctl -u centralofficecontenthosting -f

# Follow relay logs
sudo journalctl -u centralofficerelay -f

Support Contacts


End of Troubleshooting SOP


Revision #1
Created 18 April 2026 13:30:26 by joliveira@cornerstonephiladelphia.com
Updated 18 April 2026 13:30:44 by joliveira@cornerstonephiladelphia.com