Starting or Stopping Web Security Services

Applies to

Web Filter 7.6

Web Security 7.6

Web Security Gateway 7.6

Web Security Gateway Anywhere 7.6

In this topic

Overview

Manually stopping and starting services (Windows)

Manually stopping and starting services (Linux)

Stopping and starting principal components

Overview

By default, Websense services are configured to start when the machine starts.

Occasionally, you may need to stop or start a Websense service. For example, Filtering Service must be stopped and started after customizing default block messages.

 

Note  When Filtering Service is started, CPU usage can be 90% or more for several minutes while the Websense Master Database is loaded into local memory.

Manually stopping and starting services (Windows)

Use the Windows Services console to stop and start one or more Websense services:

1.	Open the Windows Services console (Start > All Programs > Administrative Tools > Services).

2.	Right-click a service name, and then select Start, Stop, or Restart. Restart stops the service, then restarts it again immediately from a single command.

Refer to Stopping and starting principal components for the correct order to use when stopping or starting multiple Websense services.

 

Warning  Do not use the taskkill command to stop Websense services. This may corrupt the services.

Manually stopping and starting services (Linux)

Stop, start, or restart Websense services (daemons) from the command line on a Linux machine.

Restarting stops a daemon, then restarts it immediately from a single command. If Websense components are spread across multiple machines, be sure that Policy Broker and the Policy Database are stopped last and started first. See Stopping and starting principal components for the preferred stopping and starting order.

There are two scripts to stop and start Websense services:

WebsenseAdmin: can stop, start, or restart all Websense components together.

WebsenseDaemonControl: can stop or start individual components.

 

Warning  Do not use the kill command to stop Websense services. This may corrupt the services.

Stopping, starting, or restarting all services

1.	Go to the Websense installation directory (/opt/Websense/, by default).

2.	Use the following commands to stop, start, or restart all Websense services in the correct order:

./WebsenseAdmin stop

./WebsenseAdmin start

./WebsenseAdmin restart

3.	View the running status of all Websense services with the following command:

./WebsenseAdmin status

Stopping or starting individual services

1.	Go to the Websense installation directory (/opt/Websense/, by default).

2.	Enter the following command: ./WebsenseDaemonControl.

A list of installed components is displayed, showing whether each process is running or stopped.

3.	Enter the letter associated with a component to start or stop the associated process.

To refresh the list, enter R.

4.	When you are finished, enter Q or X to exit the tool.

Stopping and starting principal components

When stopping individual components on Windows machines, or when stopping components spread across multiple machines, stop the optional components first, and then the principal components, ending with the following, in the order shown:

1.	Websense Network Agent

2.	Websense Filtering Service

3.	Websense User Service

4.	Websense Policy Server

5.	Websense Policy Broker

6.	Websense Policy Database

7.	Websense Control Service

When starting services, reverse this order. It is especially important that you begin with the following services, in the order shown:

1.	Websense Control Service

2.	Websense Policy Database

3.	Websense Policy Broker

4.	Websense Policy Server

Also remember that if you are stopping and starting services on the TRITON Unified Security Center machine, you may need to stop or start the following as well:

Websense Web Reporting Tools

Websense TRITON - Web Security