System Administrator Guide for CEMon for EMI-3

1 Installation and Configuration

1.1 Prerequisites

1.1.1 Operating system

The following operating systems are supported:

  • SL5 64 bit
  • SL6 64 bit

It is assumed that the operating system is already properly installed.

1.1.2 Node synchronization

A general requirement for the Grid nodes is that they are synchronized. This requirement may be fulfilled in several ways. One of the most common one is using the NTP protocol with a time server.

1.2 Plan how to deploy CEMon

1.2.1 Choose the authorization model

CEMon can be configured to use as authorization system:

  • the ARGUS authorization framework


  • the grid Java Authorization Framework (gJAF)
In the former case a ARGUS box (usually at site level) where to define policies is needed.

To use ARGUS as authorization system, yaim variable USE_ARGUS must be set in the following way:


In this case it is also necessary to set the following yaim variables:

  • ARGUS_PEPD_ENDPOINTS The endpoint of the ARGUS box (e.g."")
  • CREAM_PEPC_RESOURCEID The id of the CREAM CE in the ARGUS box (e.g. "")
If instead gJAF should be used as authorization system, yaim variable USE_ARGUS must be set in the following way:


1.2.2 Repositories

For a successful installation, you will need to configure your package manager to reference a number of repositories (in addition to your OS);

  • the EPEL repository
  • the EMI middleware repository
  • the CA repository

and to REMOVE (!!!) or DEACTIVATE (!!!)

  • the DAG repository The EPEL repository

On sl5_x86_64, you can install the EPEL repository, issuing:

rpm -Uvh

On sl6_x86_64 instead issue:

rpm -Uvh The EMI middleware repository

On sl5_x86_64 you can install the EMI-2 yum repository, issuing:

wget TBD
yum install ./TBD

TBC The Certification Authority repository

The most up-to-date version of the list of trusted Certification Authorities (CA) is needed on your node. The relevant yum repo can be installed issuing:

wget -O /etc/yum.repos.d/egi-trustanchors.repo Important note on automatic updates

An update of an RPM not followed by configuration can cause problems. Therefore WE STRONGLY RECOMMEND NOT TO USE AUTOMATIC UPDATE PROCEDURE OF ANY KIND.

Running the script available at (implemented by Giuseppe Platania, INFN Catania) yum autoupdate will be disabled

1.2.3 Installation of CEMon

In EMI, CEMon is installed as part of the CREAM-CE. So please refer to the installation instructions for the whole CREAM CE available at:

1.2.4 Installation of the CEMon CLI

The CEMon CLI is part of the EMI-UI. To install it please refer to the EMI UI installation documentation.

1.3 Configuration

1.3.1 Using the YAIM configuration tool

For a detailed description on how to configure the middleware with YAIM, please check the YAIM guide.

The necessary YAIM modules needed to configure a certain node type are automatically installed with the middleware.

1.3.2 Configuration of CEMon using yaim

In EMI, CEMon is installed and configured as part of the CREAM-CE Install host certificate

The CREAM CE node requires the host certificate/key files to be installed. Contact your national Certification Authority (CA) to understand how to obtain a host certificate if you do not have one already.

Once you have obtained a valid certificate:

  • hostcert.pem - containing the machine public key
  • hostkey.pem - containing the machine private key

Make sure to place the two files in the target node into the /etc/grid-security directory. Then set the proper mode and ownerships doing:

chown root.root /etc/grid-security/hostcert.pem
chown root.root /etc/grid-security/hostkey.pem
chmod 600 /etc/grid-security/hostcert.pem
chmod 400 /etc/grid-security/hostkey.pem Configure the siteinfo.def file

Set your siteinfo.def file, which is the input file used by yaim. Documentation about yaim variables relevant for CREAM CE is available at

Be sure that USE_CEMON is set to true. Run yaim

After having filled the siteinfo.def file, run yaim as explained in the CREAM system administrator guide available at:

1.3.3 Configuration of the CEMon CLI

The CEMon CLI is part of the EMI-UI. To configure it please refer to the EMI UI documentation.

2 Operating the system

2.1 How to start the CEMon service

A site admin can start the CEMon service just starting the tomcat container.

On sl5_x86_64:

service tomcat5 start

On sl6_x86_64:

service tomcat6 start

To stop the CEMon service, it is just necessary to stop the CEMon container.

On sl5_x86_64:

service tomcat5 stop

On sl6_x86_64:

service tomcat6 stop

2.2 Configuration files

Information about configuration files in the CEMonis available at

2.3 Log files

Information about log files in the CREAM CE is available at

2.4 Network ports

Information about ports used in the CREAM CE is available at

2.5 Security related operations

2.5.1 Security recommendations

Security recommendations relevant for CEMon is available at

2.5.2 How to block/ban a user

Information about how to ban users is available at

2.5.3 How to block/ban a VO

To ban a VO, it is suggested to reconfigure the service via yaim without that VO in the siteinfo.def

2.6 How to add/remove sensors

CEMon sensors that must be plugged in CEMon are defined in the CEMon configuration file (/etc/glite-ce-monitor/cemonitor-config.xml). Each active sensor is identified by a section that has the following format:

 <sensor id=xxx

To enable/disable a specific sensor, it is just necessary to uncomment/comment the sensor definition in the CEMon configuration file.

2.7 How to add a static subscription

There are two types of subscriptions:

  • subscriptions created by an authorized user (using e.g. the glite-ce-monitor-subscribe command)
  • static subscriptions, created by the CEMon system administrator

Static subscriptions can be created editing the CEMon configuration file /etc/glite-ce-monitor/cemonitor-config.xml.

An example of static subscription settings is this one:

  <subscription id="subscription-1"
    <topic name="CREAM_JOBS">
      <dialect name="CLASSAD" />
    <policy rate="60" />

Topic revision: r1 - 2013-02-21 - PaoloAndreetto
This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback