Skip to main content

A system didn't register, or registered twice

Two things can go wrong after you install the HyperView Server: the system never shows up, or it shows up twice. Work through the checks below in order, starting with the quickest.

Two things can go wrong after you install the HyperView Server: the system never shows up, or it shows up twice. Work through the checks below in order, starting with the quickest.

If nothing appeared on the Systems screen

Check 1 - Make sure the list isn't filtered

  1. On the Systems screen, set the view to All systems.

  2. Set Folder to All and clear the search box.

If the system now appears, it was registered all along. It just didn't match the view. See The Systems screen.

Check 2 - Confirm the command ran as administrator

Installation needs administrator (Windows) or root (Linux, macOS) rights. Without them the install can fail without a clear error. Run the command again from an elevated prompt.

Check 3 - Confirm the installation key is active

  1. Go to Admin > Installation Keys and find the key you used.

  2. Make sure it's in the Active keys list. A deactivated key can't register new systems.

If you installed from a script, the error tells you which: ERR_INSTALLATION_KEY_NOT_ACTIVE means the key is deactivated; ERR_INSTALLATION_KEY_NOT_FOUND means the key string is wrong.

Check 4 - Confirm the machine had network access when it ran

Cloud start-up scripts sometimes run before the network is fully up. Check the instance's cloud-init or boot log for a failed download.

The machine also needs outbound port 443 to *.readytech.com. See Check 1 - Port 443 is open at both ends.

Check 5 - Confirm the HyperView service is running

On the machine itself, check that the HyperView service is installed and running.

NOTE: Get logs in the console only works for a registered system. Until the system registers, read the HyperView Server log on the machine itself.

If one machine appears twice

A system proves it's the same machine using a fingerprint. In rare cases, where the fingerprint no longer matches the console's record, the console can't safely treat it as the same system, so it registers again.

Clean up the duplicate

  1. Compare the two entries' Last Heartbeat and IPv4 Address. The one with the recent heartbeat is live.

  2. On the stale entry, open the ⋮ menu.

  3. Choose Block access to keep the record but make it unreachable, or Delete system to remove it. Delete system is only available once the system is offline.

For more about both actions, see Act on a system.

System statuses

Status

Meaning

ACTIVE

Registered and checking in

INACTIVE

Registered, but not checking in right now

BLOCKED

Access has been blocked

UNREGISTERED

Not registered

CONFLICTED

Identity conflict, usually a fingerprint mismatch

The Systems screen has built-in Conflicted and Pending deletion views that list these cases.

Related articles

Did this answer your question?