Manually restarting the Infobright PI repository (for Linux) (4307854)

Manually restarting the Infobright PI repository (for Linux)

How to restart the Infobright Performance Investigator (PI) repository on Linux?

Please refer to KB 304050 for the recommended stop and restart order for Foglight components using SQL PI.

Manual Restart

1. From the database "Administration" page, disable the PI extension of database agents
   
   Note: In case you do not know all the agents names, you can choose all agents in the "Global View" and once you enter to the SQL PI admin dashboard select the relevant FglAM with its database agents.
   
   
2. Navigate to "Administration | Agents | Agent Status" and deactivate the SPI agent (SPIRepository-...)
   
   
3. Navigate to "Administration | Agents | Agent Status" and deactivate theDBSS-SPI agent (DBSS-SPIRepository-i…) and DBO-SPI agent (DBSS-SPIRepository-i…) from the Agent Manager
   
   
4. Remotely connect into to the PI repository host
5. Browse to the "Infobright" installation folder (by default it is located next to the FglAM installation folder)
6. Edit the "Infobright-Stop.ksh" file and add "–m fast" flag to the command line after "pg_data -s -m fast", then save the file.
7. Stop all Infobright processes by running the "infobright_stop.ksh" file * This is the recommended process to shut down the PI repository. Please give this one to two minutes to complete *
8. If there are still remaining Infobright processes, open the “postmaster.pid” file under the "pg_data" folder.
9. Identify the pid number listed in the first line of the file. This corresponds to the parent infobright process.
10. Kill the parent pid process "kill -9" pid (where pid is the parent process number from step 9)
11. Run the following command to kill the remaining processes "ps -ef | grep 'postgres\|ibengine\|bhloader' | grep -v grep | awk '{print $2}' | xargs kill -9"
    
    Please note that this step will kill and Foglight Management Server (FMS) repository processes where a PI repository is installed on the same server as an embedded Postgresql FMS repository. In these situations it is recommended to shut down the FMS and FMS repository, then run this command and then restart the FMS again.
12. Run the following command to check for remaining processes "ps -ef | grep 'postgres\|ibengine\|bhloader' "
13. This is optional only if SQL PI does not start up, customer can rename or delete postmaster.pid from infrobright/pg_data after ensuring  'postgres\|ibengine\|bhloader'  processes are all stopped. This creates a new postmaster.pid with a new PID number after restarting "infobright"Infobright-Start.ksh" from the Infobright folder. The next option is to restart the FglAM host in case there is SQL PI ghost PID captured in the cache, this is only if SQL PI does not link to the Db agents.
14. Return to the Foglight Management Server console and navigate to "Administration | Agents | Agent Status"
15. Activate SPI main agent (SPIRepository-…)
    
    
16. From the Administration panel enable the SPI extensions
    
    
17. Check the historical data for one of the agents to confirm that historical data is available.
    
    
18. Add the PI extension to the remaining databases agents
    
    

Scripted Restart

1). Get the SPIRepository agent ID

2). Run the following script via the FMS script console

def spiAgentId = "151";
println "SQL PI Repository restart started"
functionHelper.invokeFunction("system:dbwc_spi20repository_installer_apis.restartSPIRepository", spiAgentId)
println "SQL PI Repository restart completed"

3). Change the agent ID in the script and click the Run button. The restart may take a few minutes.

4). Check the result of the script in the Script Console's Log Message tab.

script_script_Restat_SPI2bdbbcde23ee3a54ebdb508ac1c745c0 - SQL PI Repository restart started 

script.system:dbwc_spi20repository_installer_apis.restartSPIRepository - Start SQL PI repository restart by SPIRepository agent Id 151 

script.system:dbwc_mssql_installer_spi.pauseAllSqlPIAgents - Start pausing SQL PI for all agents that are related to the SPIRepository agent resides on FglAM win7template#e79b7e07-9db5-4da7-afdc-0a0d5eac0a60 on host win7template 

script.system:dbwc_mssql_installer_spi.pauseAllSqlPIAgents - Disable SQL PI engine for agent 10.30.169.146 (id 155) 

script.system:dbwc_mssql_installer_spi.pauseAllSqlPIAgents - Disable SQL PI engine for agent DBSS-SPIRepository-win7template (id 154) 

script.system:dbwc_mssql_installer_spi.pauseAllSqlPIAgents - Finish pausing SQL PI for all agents that are related to the SPIRepository agent resides on FglAM win7template#e79b7e07-9db5-4da7-afdc-0a0d5eac0a60 on host win7template 

script.system:oracle_installer_apis_spi.pauseAllSqlPIAgents - Start pausing SQL PI for all agents that are related to the SPIRepository agent resides on FglAM win7template#e79b7e07-9db5-4da7-afdc-0a0d5eac0a60 on host win7template 

script.system:oracle_installer_apis_spi.pauseAllSqlPIAgents - Disable SQL PI engine for agent 10.30.152.166-orcl4test (id 152) 

script.system:oracle_installer_apis_spi.pauseAllSqlPIAgents - Disable SQL PI engine for agent DBO-SPIRepository-win7template (id 150) 

script.system:oracle_installer_apis_spi.pauseAllSqlPIAgents - Finish pausing SQL PI for all agents that are related to the SPIRepository agent resides on FglAM win7template#e79b7e07-9db5-4da7-afdc-0a0d5eac0a60 on host win7template 

script.system:dbwc_spi20repository_installer_apis.restartSPIRepository - Wait 60 seconds before SQL PI repository restart 

script.system:dbwc_spi20repository_installer_apis.restartSPIRepository - Executing callback request: 

 

script.system:dbwc_spi20repository_installer_apis.restartSPIRepository - Wait 90 seconds after SQL PI repository restart 

script.system:dbwc_mssql_installer_spi.resumeAllSqlPIAgents - Start resuming SQL PI for all agents 

script.system:dbwc_mssql_installer_spi.resumeAllSqlPIAgents - Enable SQL PI engine for agent Id 155 (type DB_SQL_Server) 

script.system:dbwc_mssql_installer_spi.resumeAllSqlPIAgents - Enable SQL PI engine for agent Id 154 (type DB_SQL_Server_SPI_Repository) 

script.system:dbwc_mssql_installer_spi.resumeAllSqlPIAgents - Finish resuming SQL PI for all agents 

script.system:oracle_installer_apis_spi.resumeAllSqlPIAgents - Start resuming SQL PI for all agents 

script.system:oracle_installer_apis_spi.resumeAllSqlPIAgents - Enable SQL PI engine for agent Id 152 

script.system:oracle_installer_apis_spi.resumeAllSqlPIAgents - Enable SQL PI engine for agent Id 150 

script.system:oracle_installer_apis_spi.resumeAllSqlPIAgents - Finish resuming SQL PI for all agents 

script.system:dbwc_spi20repository_installer_apis.restartSPIRepository - Finish SQL PI repository restart by SPIRepository agent Id 151 

script_script_Restat_SPI2bdbbcde23ee3a54ebdb508ac1c745c0 - SQL PI Repository restart completed

The infobright-stop.ksh script is the following

#!/bin/ksh

IBBASE=
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${IBBASE}/lib
${IBBASE}/bin/pg_ctl stop -D ${IBBASE}/pg_data -s -m fast

IBBASE is the installation path for the Infobright

for example  IBBASE=/opt/Foglight/infobright

If assistance is needed. Please, send the latest brighthouse.log file from Agent Manager hosting the SQL PI repository. /Quest/infobright/ib_data Also, run on SQL PI repository host if the file is too large: tail -200 brighthouse.log Please, create FMS support bundle, FGLAM support bundle for the db agents, and FGLAM support bundle with the SQL PI repository. Then submit it to support.