Start a conversation

LGP Reboot Procedure (RHEL)

Overview

You may need to reset an LGP node; for example, after running a Health Check and finding it has been up and running for a long time (e.g., more than a year), which is not recommended. This article details the steps to create a backup and reboot an LGP node.

 

Requirements

  • VPN Access to the end-user system.
  • Release 12.4.1

 

Hardware Check

Before any reboot, the hardware needs to be checked to make sure no hardware issue might affect the reboot. To do so, run the following commands as root (the command could also be hpssacli):

# hpacucli ctrl all show config
# hpacucli ctrl all show config detail

For any failure found, inform the end-user about it so that they can check it before planning a reboot.

You can access the iLO GUI to check the status of all the hardware and any alarm in iLO and IML logs. If you cannot access the iLO GUI or SSH to the iLO IP, it will need to be verified with the hardware support and network teams. The iLO access will be required in case there are any issues with the reboot because the server can still be accessed via console.


 

Process

LGP Backup and Reboot

  1. Copy important files to another server or external PC.

  2. As a TextPass user, copy the content of the directories below. There are hidden files, so please use the a option in the ls command to see the content.

    • /usr/TextPass/etc/
    • /usr/TextPass/.store/
  3. As root user, copy the route and ifcfg files in /etc/sysconfig/network-scripts/.

  4. As TextPass user, save the output of the commands below.

    1. $ netstat -rn
    2. $ ifconfig -a
    3. $ cat /etc/fstab
    4. $ cat /etc/mtab
  5. As TextPass user, stop the NMM process and make sure that no pending logfiles are being processed before stopping LGP.

    1. $ tp_status
    2. $ tp_walk -l lgpstatus
    3. $ tp_stop
    4. $ tp_status
    5. $ stv_poller --status
    6. $ stv_poller --stop
  6. As root user, reboot server.

    # init 6
  7. After the reboot, check the status of the LGP node.

  8. As root user, check if MySQL is running.

    1. # service mysql status
    2. # ps -ef | grep -I sql
  9. As TextPass user, run the following commands:

    1. $ tp_status
    2. $ tp_walk -l lgpstatus
    3. $ stv_poller --status
  10. Check the system logs for any persistent error and check if the LGP node is running the collector.

    # tail -f /var/log/messages
  11. Check the output of the commands in step 4.

  12. Check if the LGP node can process new logfiles and insert it into the DB.

  13. As TextPass user, run this command:

    $ tp_walk -l lgpstatus
  14. Usually, the collection is done every 15 minutes (00, 15, 30, 45). Check again and see if the lgpDbFiles and lgpDbSize files are increasing.


 

Confirmation

  1. Check the system logs for any persistent error.

  2. As root, check if the LGP node is running the collector.

    # tail -f /var/log/messages
  3. Check the MySQL process as a root user.

    1. # service mysql status
    2. # ps -ef | grep -i sql

Back to top

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted

Comments