Installing and Using the Worker Node Client From RPMs

About This Guide

The OSG Worker Node Client is a collection of software components that is expected to be added to every worker node that can run OSG jobs. It provides a common environment and a minimal set of common tools that all OSG jobs can expect to use. See the reference section below for contents of the Worker Node Client.

It is possible to install the Worker Node Client software in a variety of ways, depending on what works best for distributing and managing software at your site:

  • Install using RPMs and Yum (this guide) - useful when managing your worker nodes with a tool (e.g., Puppet, Chef) that can automate RPM installs
  • Install using a tarball - useful when installing onto a shared filesystem for distribution to worker nodes
  • Use from OASIS - useful when worker nodes already mount OASIS on your worker nodes

This document is intended to guide system administrators through the process of configuring a site to make the Worker Node Client software available from an RPM.

Before Starting

As with all OSG software installations, there are some one-time (per host) steps to prepare in advance:

Install the Worker Node Client

Install the Worker Node Client RPM:

[root@client ~]$ yum install osg-wn-client


Fetch-CRL is the only service required to support the WN Client.

Software Service name Notes
Fetch CRL fetch-crl-boot and fetch-crl-cron See CA documentation for more info

fetch-crl-boot will begin fetching CRLS, which can take a few minutes and fail on transient errors. You can add configuration to ignore these transient errors in /etc/fetch-crl.conf:

As a reminder, here are common service commands (all run as root):

To … Run the command …
Start a service service SERVICE-NAME start
Stop a service service SERVICE-NAME stop
Enable a service to start during boot chkconfig SERVICE-NAME on
Disable a service from starting during boot chkconfig SERVICE-NAME off

Validing the Worker Node Client

To verify functionality of the worker node client, you will need to submit a test job against your CE and verify the job's output.

  1. Submit a job that executes the env command (e.g. Run condor_ce_trace with the -d flag from your HTCondor CE)
  2. Verify that the value of OSG_GRID is set to /etc/osg/wn-client

How to get Help?

To get assistance please use this Help Procedure.


Please see the documentation on using yum and RPM, the best practices for using yum to install software, and using yum repositories.

Worker node contents

The worker node may be updated from time to time. As of OSG 3.3.21 in February 2017, the OSG worker node client contains:

  • OSG Certificates
  • curl
  • Fetch CRL
  • FTS client
  • gfal2
  • globus-url-copy (GridFTP client)
  • globus-xio-udt-driver
  • ldapsearch
  • MyProxy
  • osg-system-profiler
  • osg-version
  • UberFTP
  • vo-client (includes /etc/vomses file)
  • VOMS client
  • wget
  • xrdcp

To see the currently installed version of the worker node package, run the following command:

[user@client ~]$ rpm -q --requires osg-wn-client

Click here for more details on using RPM to see what was installed

Topic revision: r41 - 09 Mar 2017 - 00:25:32 - MatyasSelmeci
Hello, TWikiGuest!


TWiki | Report Bugs | Privacy Policy

This site is powered by the TWiki collaboration platformCopyright by the contributing authors. All material on this collaboration platform is the property of the contributing authors..