On-Prem - Central Server Prerequisites Checks
Dinesh
Last Update 10 days ago
1. Download the binary
Download the latest SecOps Readiness Check binary on the Central Server:
Download the latest SecOps Readiness Check binary on the Central Server:
2. Run the binary
3. Follow On-Screen Menu
Once the binary starts, you will see an interactive menu. Select:
- Option 1 → On-Premise Deployment
- Option 1 → Central Server Prerequisite Check
4. Expected Output Summary
After the Central Server Prerequisite Check completes, you will see a summary similar to the screenshot below.
After the Central Server Prerequisite Check completes, you will see a summary similar to the screenshot below.
If a check fails, the output shows what was found and the exact steps to fix it. The same list is repeated under ACTION REQUIRED at the end of the run. For example:
5. Checks Performed
Operating system and users
Operating system and users
- OS_VERSION (Blocker) → Ubuntu Server 24.04 LTS.
- CPU_ARCHITECTURE (Blocker) → x86_64 (amd64).
- SERVER_EDITION (Blocker) → Ubuntu Server, no desktop environment.
- SYSTEMD_AVAILABLE (Blocker) → systemd is running.
- PRIMARY_USER_EXISTS (Blocker) → user ubuntu exists.
- PRIMARY_USER_PASSWORD (Blocker) → the password of ubuntu is Secops@2024, not locked and not expired.
- SUDO_PRIVILEGES (Blocker) → ubuntu has full sudo rights and sudo works with its password.
- CLEAN_INSTALL (Blocker) → no snap Docker or conflicting Docker packages, no running containers and no previous SecOps installation.
- CPU_COUNT (Blocker) → at least 4 vCPUs.
- RAM_TOTAL (Blocker) → at least 8 GB assigned to the VM (the OS reports slightly less, for example 7.2 to 7.7 GiB, which is fine).
- DISK_SPACE (Blocker) → 200 GB in total (or /var 120 GB and /home 80 GB when separate). If unused LVM or disk space exists, the output prints the exact commands to extend the filesystem.
- DISK_UNALLOCATED (Warning) → disk space that is available but not in use.
- DISK_WRITE_SPEED (Warning) → at least 100 MB/s write speed.
- DEFAULT_GATEWAY (Blocker) → a default gateway is configured and reachable.
- HOSTNAME_RESOLUTION (Warning) → the hostname resolves quickly to this server.
- REQUIRED_PORTS_FREE (Blocker) → ports 49430, 49431, 58080, 58443, 5679 and 5680 are free (remote desktop ports 13022, 13389 and 13903 as a warning).
- HOST_FIREWALL (Warning) → if ufw is active, it allows the SecOps ports.
- PROXY_CONFIGURATION (Warning) → a proxy, if used, is configured system-wide (not only for apt or the current shell).
- APT_REPOSITORIES (Blocker) → apt-get update works.
- REQUIRED_DOMAINS (Blocker) → HTTPS to the domains needed for installation, directly or through the proxy. If a domain fails, the output names the cause (firewall, DNS, proxy authentication, proxy refusal, SSL inspection).
- OPTIONAL_DOMAINS (Warning) → Ubuntu mirrors, Microsoft patch sites and SecOps downloads.
- SSL_INSPECTION (Blocker/Warning) → TLS to SecOps domains is not re-signed by an SSL inspection proxy.
- NETWORK_LATENCY (Warning) → HTTPS round trip to the SecOps cloud under 3 seconds.
- NETWORK_BANDWIDTH (Warning) → download speed of at least 5 Mbps.
- IPV6_CONNECTIVITY (Warning) → no broken IPv6 route.
- TIME_SYNC (Blocker/Warning) → the clock is synchronized and within 5 minutes of the SecOps cloud.
Important:
- No Blockers should be present in the output before the SecOps installation.
- Warnings are acceptable but should be reviewed.
- If the server uses a proxy, configure it system-wide in /etc/environment and /etc/environment.d; PROXY_CONFIGURATION shows the exact lines to add.
- The full output, including details of passing checks, is written to the log file.