13.2.4 Starting and stopping

The starting and stopping of the system can be initiated with the start_stop_pvsr command located in the utils directory, or through the WEB user interface. If there are many (more than 100K) measurements for a collector group and that group has more than one collector server then it is strongly recommended to use the command line form: either with the start_group parameter or with the start parameter but without any additional parameter.

If we wish to execute this from the command line, then we can use one of the following types of parameters. In case of a Linux server installation the TAB key can be used to autocomplete the command parameters.

• Host level parameters: the command is valid for all components of a given machine
• start_host, stop_host, restart_host or host_status: start, stop, restart or status
• host name
• Tenant level parameters: the command is valid for all components of a given tenant
• start_tenant, stop_tenant, restart_tenant or tenant_status: start, stop, restart or status
• tenant name
• Server group level parameters: the command is valid for all components of a given server group
• start_group, stop_group, restart_group or group_status
• server group ID (it can be found under the Settings -> Servers -> Groups menu item)
• Extra WEB modul parameters: this is only needed if we want to have an additional WEB server for PVSR, because in such a case the image and the Javascript chart generator modules must run on that server as well. In this case these command must be ran on the additional WEB server:
• start_extra_ui, stop_extra_ui, restart_extra_ui or extra_ui_status: start, stop, restart or status
• Non-server level parameters: the command is valid for all components of the given machine or only for the one or more selected by optional server ids
• start, stop, restart or status
• server id: if this is not specified, then the operation is executed for all servers, we can specify more than one server id as separate arguments

The command has other options as well:

·       check_version [host_name]: checks the PVSR versions on the registered servers or on just the specified host

·       disableds: shows the disabled server modules

For the collector modules PVSR offers a “without-database” mode for starting or stopping them or to query their status. To use this the string _no_db or _no_db_force must be appended to the start, stop or status parameter, for example “./start_stop_pvsr start_no_db” or “./start_stop_pvsr stop_no_db_force 123” (123 is a server id example). It is strongly recommended not to use these commands if the database is reachable. For this purpose the _no_db commands first test the database connection before running and if the database is reachable then they ask a confirmation from the user before continuing. The _no_db_force command skip this database reachability test.

Stopping the application from the command line produces an output similar to the one below:

Stopping Application manager (ID=1) on host antares in directory /opt/pvsr

Stopping SQLLDR (ID=2) on host antares in directory /opt/pvsr

Stopping Threshold processing (ID=3) on host antares in directory /opt/pvsr

Stopping Job processing (ID=4) on host antares in directory /opt/pvsr

Stopping Report calculation (ID=5) on host antares in directory /opt/pvsr

Stopping Data compression (ID=6) on host antares in directory /opt/pvsr

Stopping Data migration (ID=7) on host antares in directory /opt/pvsr

Stopping Chart server (ID=8) on host antares in directory /opt/pvsr

Stopping Partition creation (ID=9) on host antares in directory /opt/pvsr

Stopping ANTARES SNMP Collector (ID=10) on host antares in directory /opt/pvsr

Stopping Nem fut (ID=11) on host antares in directory /opt/pvsr

Starting the application from the command line produces an output similar to the one below:

Starting Application manager (ID=1) on host antares in directory /opt/pvsr

Starting SQLLDR (ID=2) on host antares in directory /opt/pvsr

Starting Threshold processing (ID=3) on host antares in directory /opt/pvsr

Starting Job processing (ID=4) on host antares in directory /opt/pvsr

Starting Report calculation (ID=5) on host antares in directory /opt/pvsr

Starting Data compression (ID=6) on host antares in directory /opt/pvsr

Starting Data migration (ID=7) on host antares in directory /opt/pvsr

Starting Chart server (ID=8) on host antares in directory /opt/pvsr

Starting Partition creation (ID=9) on host antares in directory /opt/pvsr

Starting ANTARES SNMP Collector (ID=10) on host antares in directory /opt/pvsr

Starting Nem fut (ID=11) on host antares in directory /opt/pvsr

Querying the status of the application from the command line produces an output similar to the one below:

R  Application manager (ID=1) on host antares in directory /opt/pvsr

R  SQLLDR (ID=2) on host antares in directory /opt/pvsr

R  Threshold processing (ID=3) on host antares in directory /opt/pvsr

D  Job processing (ID=4) on host antares in directory /opt/pvsr

R  Report calculation (ID=5) on host antares in directory /opt/pvsr

R  Data compression (ID=6) on host antares in directory /opt/pvsr

R  Data migration (ID=7) on host antares in directory /opt/pvsr

R  Chart server (ID=8) on host antares in directory /opt/pvsr

R  Partition creation (ID=9) on host antares in directory /opt/pvsr

R  ANTARES SNMP Collector (ID=10) on host antares in directory /opt/pvsr

U  Nem fut (ID=11) on host antares in directory /opt/pvsr

The meanings of the first characters are:

• R: running
• D: down
• U: unknown

The meaning of the individual status codes, and the starting, stopping and querying of the status through the WEB user interface are discussed in detail in Subsection 5.4.

The command also has a check_version parameter with an optional host name parameter. Using this one can check the version of PVSR running on the different servers. Important: all the versions should be the same!

On Linux servers the PVSR installer places a script called pvsr into the /etc/init.d directory, with the following possible parameters:

·       start_pvsr and stop_pvsr: starts and stops all locale PVSR modules. On the central server the start option also starts all the remote PVSR modules as well

·       start_apache and stop_apache: starts and stops the Apache WEB server for PVSR, if the Apache configuration was done during the installation

·       start_oracle and stop_oracle: starts and stops the Oracle server for PVSR if specified so during the installation

·       start and stop: the same as all the start_... and stop_... options in the right order, except when PVSR is configured in the backup mode, in which case the start option does not start the PVSR modules

The operating system uses this script, with start or stop parameter respectively when starting or stopping. However it is important to note that on Linux 8 or later operating system it is absolutely necessary to manually stop PVSR before we shut down the operating system, using either the “/etc/init.d/pvsr stop” or the “systemctl stop pvsr” commands. Otherwise the operating system might kill some of the processes before it starts the stop command, resulting in an unwanted result.