Menu

Reboot Workaround for Manager 8.7.3 & 8.4.4 OnPremise

Overview

In Manager 8.7.3 & 8.4.4 OnPremise, there is a Known Issue where some lock files will get stuck on the system, which prevents Manager from restarting properly after a system reboot. The qTest service will report "Running" in the Service Manager, but you will not be able to access Manager on your web browser after the system reboot.

This is being fixed with the Manager 9.0 OnPremise release, which will be available February 26, 2018.

Workaround

You will need to manually clean up the lock files to restart your qTest service. This will need to be done everytime a system reboot is performed.

Windows Instructions

To restart your qTest service manually on Windows:

  1. Open the Command Prompt (cmd) as Administrator.
  2. Change the working directory in your qtestctl/ folder.
  3. Navigate to the Services application for your Windows Server and right-click to Stop the "qTest" service.
  4. Go back to your Command prompt and List(search) the lock file(s) in the current folder. Use the following command:
    dir *.pid.lock /s /p
  5. Delete the lock files. Use the following command:
    del *.pid.lock /s /p
    IMPORTANT: Only delete files with the .pid.lock extension.
  6. List(search) the lock file(s) again to ensure they were deleted properly. Use the following command:
    dir *.pid.lock /s /p
  7. Navigate back to your Command prompt and Start qTest as a normal (foreground) process. Use the following command:
    qtestctl.bat --offline start
  8. Wait for the application to start. This may take a few minutes. You will receive the following message:
    "qTest has successfully started!
  9. Press CTRL+C in this terminal or run the following command to terminate the service.
    qtestctl stop
  10. Confirm the availability of the web application(s) by logging in to your Manager instance.
  11. Once you confirm that qTest can be started, return to the Command prompt and terminate the running process using Ctrl + C.
  12. In your Command prompt Restart your "qtest" Windows Service. Use the following command:
    net start qtest

Linux Instructions

To restart your qTest service manually on Linux:

  1. Remote into the server as "root."
  2. Change the working directory into your qtestctl folder.
  3. Stop "qtest" service
    service qtest stop
    Note: Ignore the error if the service is not started.
  4. Make sure there are no running processes originated from the current directory.
    ps aux | grep -v grep | grep $(pwd)
  5. If there are any, proceed to kill them.
    kill $PID1 $PID2 ... $PIDn
    Note: Where $PID* displays, these should be replaced with the actual PID of the processes that are listed from the `ps` command above.
  6. Once you confirm that there are no running processes originated from the current directory, start looking for any lock files from the same place.
    find . -name "*.pid.lock"
  7. If there are any lock files that still remain on the system, proceed to delete them. There should be a prompt for each delete. Make sure you only delete the file with ".pid.lock" extension before confirming.
    find . -type f -name "*.pid.lock" -exec rm -i {} +
  8. List all of the lock files again to make sure none of them are left on the system.
    find . -name "*.pid.lock"
  9. Try starting qTest as a normal (foreground) process.
    ./qtestctl --offline start
  10. Wait for everything to finish starting up, which will be indicated by:
    "qTest has successfully started!"
  11. Press CTRL+C in this terminal or run the following command to terminate the service.
     qtestctl stop
  12. Proceed to confirm the availability of the web application(s) via your web browser.
  13. Once confirmed that everything can be started, go back to the terminal and terminate the running process using Ctrl + C.
  14. Restart "qtest" service.
    service qtest start

 

Powered by Zendesk