Skip to content
myosicam.us

Fleet View

MyOsicam is designed to give you one control point for every OScam server you run, no matter how many you operate. The fleet view is the panel’s central overview: each server appears as a managed install with its own status, reader count, runtime state, and linked users — all visible from a single screen without SSH-ing into individual machines.

Opening the fleet view

  1. Log in to the panel.
  2. In the left sidebar, click OSCam Installs.

The OSCam Installs table is your fleet view. It lists every OScam install that has been registered with the panel, with columns for:

ColumnWhat it shows
NameThe human-readable name you gave this install when registering it.
Base PathThe filesystem path where OScam’s config files live on the server.
panel_usersThe directory path for panel-managed user files (panel_users/).
PID FilePath to OScam’s PID file, used to determine whether OScam is running.
HTTP PortThe port OScam’s built-in WebIF is listening on.
DependenciesNumber of OScam users linked to this install.
ActionsEdit and Delete links for this install.

What “registered” means

An install is registered in the panel by providing its filesystem location. The panel does not discover installs automatically from the fleet view — discovery is handled by the agent (see Install the Agent). The fleet view shows whatever you have registered, whether managed by an agent or registered manually.

When an agent syncs an OScam instance to the panel, the instance appears in the install list with its runtime state up to date. When there is no agent (older manual registrations), the panel knows the configured paths and port but relies on the WebIF being reachable to determine whether OScam is currently running.

Runtime status

For installs managed by an agent, runtime status is derived from the agent’s most recent sync:

  • Running — the agent confirmed OScam is alive and the PID file is present.
  • Stopped — OScam’s process is not running according to the agent’s last check.
  • Unreachable — the agent itself has not sent a heartbeat recently (the agent may be down or the server may be offline).

For manually registered installs (no agent), the panel checks the WebIF directly using the stored credentials. If the WebIF does not respond, the install is shown as unreachable.

Registering a new install

If you have an OScam server that is not yet tracked by the panel, register it manually:

  1. Click Register first install (if the list is empty) or the equivalent create button.

  2. The Register OSCam Install modal opens. Fill in:

    FieldNotes
    Install nameA friendly label for this server or instance, up to 120 characters.
    Base pathAbsolute path to OScam’s configuration directory, e.g. /usr/local/etc/oscam-main.
    panel_users pathAbsolute path to the panel_users/ directory, e.g. /srv/shared/panel-users/main. Can be outside the base path.
    PID file pathPath to OScam’s PID file (optional). Used to detect if OScam is running.
    HTTP portThe port OScam’s WebIF listens on.

  3. Click Register Install.

Acting on an install

From the Actions column of each row you can:

  • Edit — update the install’s name, paths, PID file, HTTP port, or group assignment.
  • Delete — remove the install from the panel. This does not affect OScam on the server; it only removes the panel’s record of this install.

Day-one single pane of glass

After an agent syncs for the first time, every OScam instance on that server appears in the fleet view immediately — with no re-configuration, no migration, and no downtime. Your existing OScam setup keeps running exactly as-is; the panel just gains visibility into it.