Running the Policy Server start-all shell script creates a .java_pid#### file under the /tmp directory
search cancel

Running the Policy Server start-all shell script creates a .java_pid#### file under the /tmp directory

book

Article ID: 37960

calendar_today

Updated On:

Products

CA Single Sign-On SITEMINDER

Issue/Introduction

This document explains a UNIX/Linux Policy Server ‘start-all’ shell script behavior.

Environment

Release: R12.8 ANY
Component: Policy Server

Cause

When the Policy Server starts up by ‘start-all’, a temporary file .java_pid#### (#### is process id) is created under /tmp. However, when it stops by ‘stop-all’ script, the file is not removed.

# ls -la /tmp

srw-------.  1 smuser smuser  0 Apr  2 12:05 .java_pid####

 

Resolution

The ‘start-all’ shell script invokes two processes:

(1) smpolicysrv (Policy Server)

(2) smmon (Health Monitor)

 

The ‘smmon’ is a Java process and creates such a temporary file /tmp/.java_pid#### of socket type. The PID file can be deleted after a Policy Server shutdown.

Note that the smmon process is the OneView Monitor used for performance monitoring and metrics collection of the Policy Servers and Agents.

Additional Information

On the other hand, ‘smpolsrv’ command does not create such a temporary file. If you need to start (1) smpolicysrv (Policy Server) only, you may use ‘smpolsrv’ command with option “-start”. Here is a usage information.

# pwd

/opt/CA/siteminder

# ./smpolsrv -h

Usage :

        smpolsrv -start (to start server)

        smpolsrv -stop (to stop server)