Troubleshooting Steps for iScrape

Troubleshooting steps for iScrape, a component used for searching, extracting, and downloading scripts for automation. Covers issues with service startup, missing Python packages, incorrect paths and ports, and service not running.

iScrape is the component responsible to search, extract, and download scripts from open sources to create runbooks which are not available within BigFix Runbook AI repository for automation. It is a component developed using python and is hosted on Apache Web Server as a service under the name HCL.iAutomate.iScript.

HCL.iAutomate.iScript service is not starting

Table 1. Table 92- iScrape: Scenario 1
Issue Description HCL.iAutomate.iScript service is not starting
Modules Impacted iScript
Probable Root Cause Invalid “iScript.conf” file content

Steps to resolve

  1. Check for existence of the file iScript.conf at location <Apache_Root_Folder_Path>/conf.
For e.g. - “C:/Apache24/conf” has <Apache_Root_Folder_Path> as “C:/Apache24”
  1. Verify the contents of file iScript.conf by checking the snippet with paths to << iScript_Directory>>. Verify and change the <VirtualHost *> tag with correct path entries to << iScript_Directory>> as shown below. Where << iScript_Directory>> is “C:/iAutomate/Comp/HCL.iAutomate.iScript” in the snippet from iScript.conf

<VirtualHost *>

WSGIScriptAlias /iAutomate C:/iAutomate/Comp/HCL.iAutomate.iScript/iScript/app.wsgi

SSLVerifyClient require

SSLVerifyDepth 10

<Directory C:/iAutomate/Comp/HCL.iAutomate.iScript/ iScript>

WSGIApplicationGroup %{GLOBAL}

Require all granted

</Directory>

</VirtualHost>

  1. Ensure that service was created through Service Account and not through Local Account. Refer to below figure to check the status.
Figure 1. Figure 139 - HCL.iAutomate.iScript service is not starting
1
  1. If not, open Windows Command Prompt in Administrator mode and run the below command:

sc config HCL.iAutomate.iScript obj= “ID” password= “PSWD”

where ID is the [Domain\SA ID] and PSWD is the [Password of SA] and SA is

[Service Account].

Log On As’ field corresponding to the service HCL.iAutomate.iScript should be changed to ‘Service Account’. Click Start to start the service.

Service returns Internal Server Error - status code 500

Table 2. Table 93 - iScrape: Scenario 2
Issue Description Service is reachable but returns Internal Server Error with status code 500.
Modules Impacted iScript
Probable Root Cause Python package not available

Steps to resolve

  1. Check the Apache error log at <Apache_Root_Folder_Path>/logs/error.log.

If the error is because of the missing package, perform the following steps:

  1. Open Windows Command Prompt in Administrative mode in Apache_Root_Folder_Path:
  1. If open internet access is available, run the below command:

pip install package_name

  1. If open internet access is not available, download wheel file for the package from where user has internet connectivity and move onto the server at same location where it needs to be installed. E.g. https://pypi.org has a repository of most used wheel files, else other sources are available as well. Subsequently, run the below command:

pip install package_name.whl

‘404 Resource Not Found’

Table 3. Table 94 - iScrape: Scenario 3
Issue Description Error message ‘404 Resource Not Found’ when iScript is hit
Modules Impacted iScript
Probable Root Cause
  • Paths are not correct in iScript.conf
  • Port is not correct

Steps to resolve

  1. If the issue is due to the incorrect paths, refer to resolution steps mentioned for issue in Table 92- iScrape: Scenario 1 .
  1. Also, check if correct port is being used. To identify the correct port, perform the following steps:
  • Open iScript.conf
  • Search for Listen xxxx

e.g. – Here the image below shows the port set for iScript component is 9000.

#

Listen 9000

# ports, instead of the default. See also the <VirtualHost>

# directive

  1. The set port is one where iScript is deployed.

‘Could not get any response’

Table 4. Table 95 - iScrape: Scenario 4
Issue Description Error message ‘Could not get any response’ appears when iScript is being hit.
Modules Impacted iScript
Probable Root Cause HCL.iAutomate.iScript service is not running

Steps to resolve

  1. Press Win+R, type services.msc and press Enter to open Windows Services.
Figure 2. Figure 140 - HCL.iAutomate.iScript
  1. Find service HCL.iAutomate.iScript and select it.
  2. Click Start to start the service, if it’s not running already.
Figure 3. Figure 141 - HCL.iAutomate.iScript (cont.)