Interstage Big Data Complex Event Processing Server V1.0.0 User's Guide

8.12 cepstopserv

Name

cepstopserv - CEP service stop

Format

cepstopserv

Function description

This command stops the CEP service - it stops in batch the multiple services that make up the CEP service entity.

Stop processing for those services that are already stopped will be skipped.

This command also stops a CEP engine that has been started.

The services stopped by this command are as follows:

• CEP engine

• Apache Tomcat

• PostgreSQL

• Interstage HTTP Server

• Interstage Management Console

• Interstage Java EE Node Agent service

• Interstage Java EE DAS service

• Interstage

  
  

Arguments

None

End status

The following status codes are returned:

0

Normal end

8

Abnormal end

Point

Executing this command will stop all CEP engines that are running.

Note

• If the stop of one or more of the services fails, an error message will be output and the stop of the CEP service will fail.
  To complete the stop of the CEP service, remove the cause of the error and then execute the command again.

• This product uses cron for CEP engine resource usage acquisition. This command does not stop cron (refer to "6.3.3 Applying Updates" for information on how to stop cron).

• If this command is executed twice in a row, the message below is output, but the CEP engine or Apache Tomcat is stopped, so no action is required:

  Stopping Engines.
  asadmin: ERROR: ISJEE_OM2997: Unable to connect to admin-server at given host: 
  [localhost] and port: [12001]. Please check if this server is up and running and 
  that the host and port provided are correct.
  asadmin: ERROR: ISJEE_CLI137: Command list-clusters failed.
   
  Stopping Apache Tomcat.
  /etc/init.d/FJSVcep-rest stop
  Shutting down Tomcat:                                      [Fail]

  Please note that we added newlines in the example above (line 2 and 3) for readability only - the actual message does not have a newline.

Example

Example of output at normal end

When all services stop successfully:

# cepstopserv <ENTER>
Stopping Engines.
CEP Engine is not started. EngineId=(CepEngine)
Command cepstopeng executed successfully.
 
Stopping Apache Tomcat.
/etc/init.d/FJSVcep-rest stop
Shutting down Tomcat:                                      [  OK  ]
 
Stopping PostgreSQL.
su - bdcep_postgres -c "/opt/FJSVcep/postgres/packages/FJSVpgs83/bin/pg_ctl -D /var/opt/FJSVcep/postgres/data stop"
waiting for server to shut down.... done
server stopped
 
Stopping Interstage HTTP Server.
UX:IHS: INFO: ihs01000: The command terminated normally.
 
Stopping Interstage Management Console.
UX:ismngconsolestop: INFO: is40042: The service has been terminated normally.
 
Stopping Interstage Java EE Node Agent service.
ijnastop: INFO: ijna10001: Interstage Java EE Node Agent service has stopped.
Name                             Status
-----------------------------------------
Interstage Java EE Node Agent    stopped
 
Stopping Interstage Java EE DAS service.
ijdasstop: INFO: ijdas10001: Interstage Java EE DAS service has stopped.
Name                             Status
-----------------------------------------
Interstage Java EE DAS           stopped
 
Stopping Interstage.
UX:isstop: INFO: is30160:INTERSTAGE has stopped normally.
 
Command cepstopserv executed successfully.

Example of output at abnormal end

When the Interstage Java EE DAS service cannot be stopped.

# cepstopserv <ENTER>
(...)
Stopping Interstage Java EE DAS service.
ERROR: ijdas10003: Interstage Java EE DAS service cannot be stopped.
Command cepstopserv execution failed.