Page History

If you are setting up a distributed architecture, after completing the Shinken installation on your servers, you will have to configure each daemon (names and IP address, realm, spare, Poller tags, retentions...).

Automatic installation:

./install.sh

Please launch: 
/tmp/shinken-enterprise_V02.05.XXX-LANGUAGE/tools/install-vmware-sdk.sh
And follow the instructions in order to install it and allow VMWare communication

shinken-healthcheck

A warning is issued as expected to say the Shinken Enterprise license key is not installed. Head over to the License key section further down on this page to install your license key.

Once Shinken Enterprise installed, the Configuration UI can be accessed via a web browser at the address displayed during the installation:

• By default, the Configuration UI is available via the 7766 port (HTTP protocol). For instance: http://192.168.0.1:7766

See the Configuration UI page for more information.

Once Shinken Enterprise installed, the Configuration UI can be accessed via a web browser at the address displayed during the installation:

• By default, the Configuration UI is available via the 7767 port (HTTP protocol). For instance: http://192.168.0.1:7767

See the Visualization UI page for more information.

• Automatic partial installation (only enables selected daemons):
  • Extract the package archive
    • tar zxvf shinken-enterprise_V02.05.XXX-LANGUAGE.tar.gz
    • This will create a new directory containing the installation script and dependencies required for the installation.

  • Move to the shinken-entreprise directory (cd shinken-enterprise_V02.05.XXX-LANGUAGE) and execute the install.sh script, passing the following options based on the daemons you want to enable:

    • --pollernode: Enables the Poller daemon (responsible for check execution)

    • --reactionnernode: Enables the Reactionner daemon (responsible for notifications and event handlers)

    • --schedulernode: Enables the Scheduler daemon (responsible for the planification of the checks execution)

    • --arbiternode: Enables the Arbiter daemon (responsible for the central distribution of configuration and informations)

    • --receivernode: Enables the Receiver daemon (responsible for receiving results for passive checks)

    • --synchronizernode: Enables the Synchronizer daemon (responsible for configuration management)

    • --brokernode: Enables the Broker daemon (responsible for presenting the checks results and data the the world: Visualization UI, SLA)

You can for example install Shinken Enterprise and enable only the Scheduler and Pollers daemons by launching the command:

./install.sh --schedulernode --pollernode

• To check that the selected daemons are up to date, correctly configured and running, launch the following command:

shinken-healthcheck

The shinken-healthcheck checks that Shinken Enterprise configuration is correct and coherent, and is running (only for enabled daemons)

• After the initial installation, if you want to enable/disable daemons, use the activation commands detailed in the TODEL Daemons listing/enable/disable page.
• When updating, the update.sh scripts updates all daemons, even if they are disabled. Their enabled/disabled state will be kept intact.

The different addons are automatically enabled during the installation:

• nagvis-shinken-architecture: Enabled on installations with an Arbiter enabled (more details in the dedicated documentation page: Activation et configuration de la fonctionnalité)
• nagvis: Enabled on installations with an Broker enabled (more details in the dedicated documentation page: NagVis ( Addon ))

You can enable Chiffrement des données sensibles automatically when launching the installation.

An encryption key is generated during the installation and the Synchronizer database will be encrypted.

To enable this feature, launch the following command:

./install.sh --activate-encryption <nom de clé>  --disable-important-notices-user-input

• The --activate-encryption parameter enables the encryption: the key name is optionnal; it will be asked during the installation process if not specified in the parameter.
• The--disable-important-notices-user-input parameter disables interactive prompts during the installation process.

The shinken-healthcheck can be used to check the daemons configuration and encryption status.

./update.sh

• This script updates Shinken Enterprise but does not overwrite files in /etc/shinken, avoiding overwriting configuration defined by the Shinken administrator. Instead of overwriting your configuration files, "*.rpmnew" files are added, that may contain new configuration properties. It is advised to check these files after updating to report possible new features in your existing configuration files.
• Before updating, a backup of configuration and user data is done and placed into /tmp. These backup follow the following naming convention: "backup-preupdate-version-NUMERO_VERSION"

In case of an error during the update, the update.sh script may stop so that you can fix the problem. The most common errors are as follows:

Check that it is started:

Under CentOS or RHEL 6 

service mongod status

Under CentOS or RHEL 7

systemctl status mongod 

Restart mongod if the daemon is stopped

Under CentOS or RHEL 6  

service mongod start

Under CentOS or RHEL 7 

systemctl start mongod

En cas de doute, n'hésitez pas à contacter votre support.

shinken-healthcheck

During Shinken Enterprise installation, lots of checks (via Packs Shinken, Linux, Windows,.. templates) are imported in the Configuration UI. These elements, grouped into packs, are available and importedusing the "cfg-file-shinken" source.

When updating, these elements may be updated, but these changes are not automatically integrated into your monitoring configuration to avoid unintentional behaviour or breaking changes. To see the changes, make sure the "cfg-file-shinken" source is enabled and import the source. The changed elements will appear with the "New" of "Difference" status.

Image Removed