CAS status
To open the Configuration Auditing System Status page, browse to
Displays the CAS status, and the status of each CAS instance for each database server that is configured as the active Guardium® host and where CAS is installed and running.
Hover your mouse over the status lights to display the status text.
Component | Description |
---|---|
CAS System Status indicator light |
Indicates whether CAS is actively running on the Guardium system. Red - CAS is not running on this Guardium system. Green - CAS is active on this Guardium system. |
CAS agent status indicator lights |
Indicate whether the individual CAS agent is connected to a Guardium system. Identify each CAS agent by referencing the IP address that appears before the row of status indicator lights. Red - Either the host, the CAS agent, or both are offline or unreachable. Green - Host and CAS agent are online. Yellow - The Guardium system is a secondary for the CAS host. |
Reset |
Reset the CAS agent on this monitored system, which stops and restarts the CAS agent on the database server. Note: Reset also resets checkpoint files; allowing for a fresh start and rescan of files from
scratch.
|
Delete (X) |
Remove this monitored system from CAS and delete the data on the Guardium system that is associated with the CAS client. Delete is unavailable if the CAS agent is running on this system. To delete the monitored system, stop the CAS agent first. For more information, see Stopping and starting the CAS agent. |
Red/Yellow/Green light | Indicates the status of a CAS instance on the monitored system. If the owning monitored
system status is red (indicating that the CAS agent is offline), ignore this set of status
lights. Red - The instance is disabled. Green - The instance is enabled and online, and its configuration is synchronized with the Guardium system configuration. Yellow - The instance is enabled, but the instance configuration on the Guardium system does not match the instance configuration on the monitored system (that is, the instance is updated in Guardium, but the monitored system is not updated). |
Refresh |
Update the status of all servers in the list. Refresh does not stop or restart CAS on a database server.Refresh checks only the connection between CAS on the Guardium system and CAS on each database server. |
Stopping and starting the CAS agent
Several situations exist where you might need to stop or start the CAS agent on a monitored system.
- Stopping CAS on a UNIX host
-
- Edit the file /etc/inittab.
- Find the CAS respawn
line:
, cas:2345:respawn:/usr/local/guardium/guard_stap/cas/bin/run_wrapper.sh /usr/local/guardium/guard_stap/cas/bin
- Insert a number sign (
#
) in the first character position to comment out the line. - Save the file.
- Enter the following commands and note the PID of each listed process.
init -q ps -er | grep cas
- For each process, issue the following command,
kill -9 <pid>
- In the Configuration Auditing System Status window, make sure that the status light for this CAS host is red, and that the Remove button is enabled. If needed, click Remove to remove data from this CAS host from the Guardium system internal database.
- Starting CAS on a UNIX host
- Restart the CAS agent only if it was stopped by editing the /etc/inittab
file as described in Stoping CAS on a UNIX
host.
- Edit the file /etc/inittab.
- Find the respawn
line:
, #cas:2345:respawn:/usr/local/guardium/guard_stap/cas/bin/run_wrapper.sh /usr/local/guardium/guard_stap/cas/bin
- Remove the
#
in the first character position to uncomment the line.Note: Depending on your operating system, the comment character might be different. - Save the file.
- Enter the following command to restart the CAS agent, init -q.
- Starting and Stopping CAS on a Windows Host
- On Windows, CAS runs as a system service.
- In the Windows Services window, highlight the Configuration Auditing System Client item.
- Select either Start or Stop from the Action menu.