LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 641
Reporting
Stop or restart the derbydb (if you are using the Derby demo database), jobdt, plc,
and
purger services. If your cluster does not have PERF controlled by EGO, you use
the
perfadmin command to stop or restart these services.
1 In the command console, stop the service by running perfadmin stop.
perfadmin stop service_name
2 If you want to restart the service, run
perfadmin start.
perfadmin start service_name
Disable automatic startup of the reporting services
Prerequisites: Your cluster must be EGO-enabled.
When disabling the reporting feature, disable automatic startup of the derbydb (if
you are using the Derby demo database),
jobdt, plc, and purger services. When
moving from the Derby demo database to a production database, disable automatic
startup of the
derbydb service.
Disable automatic startup of these services by editing their service configuration
files (
jobdt.xml, plc_service.xml, purger_service.xml, and
derby_service.xml for the jobdt, plc, purger, and derbydb services,
respectively).
1 In the command console, open the EGO service directory.
◆ UNIX: cd
LSF_CONFDIR/ego/cluster_name/eservice/esc/conf/services
◆ Windows: cd LSF_CONFDIR\ego\cluster_name\eservice\esc\conf\
services
2 Edit the service configuration file and change the service type from automatic
to manual.
In the
<sc:StartType> tag, change the text from AUTOMATIC to MANUAL.
3 Stop the service.
4 In the command console, restart EGO on the master host to activate these
changes.
egosh ego restart master_host_name
View the status of the loader controller
Use the loader controller client tool to view the status of the loader controller.
1 Launch the loader controller client tool with the -s option.
❖ In UNIX, run $PERF_TOP/version/bin/plcclient.sh -s.
❖ In Windows, run %PERF_TOP%\version\bin\plcclient -s.