2-DRC INSIGHT - Ubuntu COS Installation
Purpose: Install the COS Service Device on Ubuntu and verify the core services start correctly.
Prerequisites
- Ubuntu 22.04 or 24.04
- Sudo/root access
- Internet access
- Installer package from the DRC portal
Step 1 - Update Ubuntu
sudo apt update && sudo apt upgrade -y
Step 2 - Install Required Dependencies
sudo apt install -y \
libxcb-xinerama0 \
libalt-getopt-complete-perl \
libxcb-icccm4 \
libxcb-image0 \
libxcb-keysyms1 \
libxcb-render-util0 \
libxcb-xkb1 \
libxkbcommon-x11-0
Critical:
If these packages are missing, COS may install incompletely, fail silently, or launch only partial services.
If these packages are missing, COS may install incompletely, fail silently, or launch only partial services.
Step 3 - Fix /tmp Permissions
sudo chmod 1777 /tmp
ls -ld /tmp
The COS installer writes temporary lock files to /tmp. Incorrect permissions can break the installer.
Step 4 - Clean a Failed Installation (If Needed)
sudo rm -rf /opt/CentralOffice
sudo rm -f /tmp/coinstaller*.lock
Step 5 - Run the Installer
chmod +x silent-linux.sh
sudo ./silent-linux.sh
DRC recommends using the default install locations. During installation, save the setup URL displayed by the wizard, because it can be used to resume or complete the process. :contentReference[oaicite:3]{index=3}
Step 6 - Verify Installation Files
ls /opt/CentralOffice
Expected folders include:
- management
- relay
- proxy
- contenthosting
- setup
Step 7 - Verify Running Services
sudo /opt/CentralOffice/node \
/opt/CentralOffice/setup/node_modules/forever/bin/forever -p /opt/CentralOffice list
Expected:
- management
- relay
- proxy
- contenthosting
Step 8 - Check Active Ports
sudo ss -tulnp | grep node
DRC training shows COS uses a base port, commonly 55222, and assigns consecutive ports from there. In this deployment, the active ports observed were 55223, 55224, and 55225. :contentReference[oaicite:4]{index=4}
Step 9 - Test Local Response
curl -I http://127.0.0.1:55223
Expected Result:
HTTP 404 on the root path is acceptable. It confirms the service is alive even if the root URL is not the correct application route.
HTTP 404 on the root path is acceptable. It confirms the service is alive even if the root URL is not the correct application route.
Next Page: DRC Portal Configuration