Each weekend a server reboot is done on the system where the Infobright SQL PI repository is located.
How can the Infobright and Postgresql processes be gracefully (cleanly) shut down and restarted to limit any corruption to the posgresql PI repository database caused by a hard shutdown of the OS?
Can the Infobright / Postgresql PI processes shutdown and restart be scheduled?
The Infobright and Postgresql processes are called by the SPI-Repository agent but runs as a separate process. Shutting down the Foglight Management Server (FMS), Foglight Agent Manager (FglAM), or SQL PI agents does not shut down or kill the Infobright, brighthouse, and postgresql processes used by the PI repository.
SQL PI Inforbright DB will be started by PI Repository Manager Agent automatically. To avoid the Infobright DB corrupted by Server hard restart, Dev recommends the following start/stop order:
Please refer to KB 304050 for the recommended stop and start (restart) order for SQL PI components.
The Infobright based version of SQL Performance Investigator (SQL PI) is out of support and has been replaced with a SQL Server based version of the PI repository in the 5.9.5.20 and higher releases of the database cartridges. Please upgrade the database cartridges to the most current release for continued full support of the product.
Details on how to restart the PI repository on Linux is detailed in KB article 232387.
Details on how to restart the PI repository on Windows is detailed in KB article 232383.
The following steps are based on a modification of these two restart processes.
These steps were created for a basic Foglight environment where the FMS and PI repository are located on the same system. This could be modified to use a fglcmd utility installed and running remotely from the PI repository server.
1). Navigate in the FMS console to Administration | Agents | Agent Status
2). Type "SPI" (without quotes) in the search panel
3). Record/note the names of all of the agents of the types SPRepository, DB_SQL_Server_SPI_Repository, DB_Oracle_SPI_Repository running on the PI repository's FglAM server.
4). Use the steps in KB article 267419 to find the AgentID values for each of the SPI repository agents running on the PI repository's FglAM server.
5). Connect with a SSH or Windows desktop (RDP) connection to open a OS prompt and navigate to the location of the fglcmd script (this is in under the main \bin folder on the Foglight Management Server (FMS)).
6). Run fglcmd commands to deactivate the SPI agents using the Agent IDs found in Step 3 (above).
\fglcmd -usr foglight -pwd foglight -srv localhost -port 8080 -cmd agent:deactivate -agentid #
7). Run the infobright-bat (in Windows as Administrator) or .\infobright.sh (in Linux or Windows as the process owner) to shut down the Infobright processes.
8). Restart the OS
9). After the Foglight Agent Manager has restarted, the SPI agents will be in a deactivated state. Run fglcmd commands to reactivate the SPI agents.
\fglcmd -usr foglight -pwd foglight -srv localhost -port 8080 -cmd agent:activate -agentid #
Additional notes
© ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center