Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

 

 

 

 


 

Searches that appear "stuck" in Queued or Searching mode

During the normal course of operation, you may execute a search that remains in a "queued",  "searching" or "collecting" state. Endpoints will naturally transition into sleep mode, are shut down by the end-user, or may be off network for whatever reason. When you select endpoint groups within Interrogate, some offline endpoints may be called upon to search or collect but will not be available to perform the task or perhaps shut down during the task. This is completely normal and the more endpoints that you have, the greater the chance that the state of the system will remain in queued, searching or collecting.

The best method for checking the status of your endpoints is to look at the configuration > endpoints page and view the "Last Checked-in" column. This will give you a good indications as-to whether your endpoint is actively communicating with Interrogate. You may find that an endpoint has been offline for some amount of time. If the owner of the endpoint is on vacation or perhaps traveling for work, it may be normal to be offline for days. If, however an endpoint should be checking-in with Interrogate you may want to dive a bit deeper into why the endpoint may not be communicating with Interrogate. See the Verifying Communications second below for more details.

Image showing Last Checked-in column

 

 


 

Verifying Endpoint-to-Interrogate Communication

One of the first items to troubleshoot involves the actual communication between the installed endpoint and the Interrogate Command Center interface. There are several log files and/or console windows you can use in order to verify that the proper communication is occurring between endpoint and Interrogate. See below.

Windows

Test 1: Navigate to C:\Program Files (x86)\HeurekaAgent\log. Open the newest log file with a text editor and you should see connections between your endpoint and Interrogate. (See image to the right)

Restarting the Windows endpoint service

Should it become necessary to stop and restart the PC endpoint service, open the endpoint task manager and browse to the "Services" tab. Locate the HeurekaAgent service, right-click and select "Restart Service". The endpoint service will cycle itself back to a running state.

Macintosh

As a first step you need to determine whether or not the endpoint service is running and communicating with Interrogate. Follow the steps below:

Endpoint Service Verification

  1. Open a terminal window and type: sudo launchctl list | grep heureka
  2. Enter your password
  3. "com.heurekasoftware.agent" should be returned in your terminal window.

Viewing communication

  1. Open a console window using the Mac search tool.
  2. Locate the com.heurekasoftware.agent.log 

You should see information streaming into the console window showing connections back to Interrogate. (See image to the right)

Restarting the Macintosh endpoint service

Should it become necessary to stop and restart the Mac endpoint service, open a terminal window on the endpoint computer and type the following commands:

Stop Service

sudo launchctl unload /Library/LaunchDaemons/com.heurekasoftware.agent.plist

Start Service

sudo launchctl load /Library/LaunchDaemons/com.heurekasoftware.agent.plist

It may be necessary to type your password in the terminal window!

 

 

 

 

Image showing successful handshake between endpoint and Interrogate

 

 

 

 

Image showing PC Task manager for endpoint service restart





 


 

Manual Re-index (Forced Reindex)

Windows

Windows endpoints require a program to force a "PUT" request to a localhost URL. Heureka recommends a Firefox plugin called "HttpRequester" which can be found here. Once installed in the endpoint's Firefox browser, please follow the instructions below:

  1. Type http://localhost:30000/api/task/index in the Request URL line
  2. Click the "PUT" button

The endpoint will now re-index from the configured start point.

(See image to the right)

 

 

 

 

 

 

 

Macintosh

Open a terminal window on the Mac

  1. Type: curl -XPUT http://localhost:30000/api/task/index <Return>

  The endpoint will now re-index from the configured start point.

(See image to the right)





Image showing HttpRequester plug-in for Firefox with PUT command






Image showing Mac terminal window with curl command for forced re-index


 

  • No labels