Static support troubleshooting

This topic provides troubleshooting information for static devices.

Troubleshooting directories and files

The following table lists directories and files that are relevant for troubleshooting static devices, depending on the scenario.

 

Device Definition

Analysis
Working folder

/home/afa/algosec/work/ collect_gen-<PID>

For example:

/home/afa/algosec/work/ collect_gen-62123

/home/afa/algosec/firewalls/afa-<###>

For example:

/home/afa/algosec/firewalls/afa-88
Configuration file

gen_data.txt

<device name>.<device brand suffix>

For example:

10_20_74_1.secui

Note: This file is compressed and contained in the raw_files.zip file at the end of the analysis. This is not done yet when the partner parser is launched.
Log file

/home/afa/.fa-history

/home/afa/algosec/firewalls/afa-<###>/fwa.history

Problem: Analysis failed

Probable cause: The JSON configuration is invalid. The required data is missing and/or the file structure is wrong.

Confirm the issue: Confirm the problem by searching the failed analysis's error log file for the following errors:

  • "Invalid JSON format in file: …"
  • "Invalid format in file: …"
  • "…..at /usr/share/fa/bin/config_parser_json2out line … Error: hash creation failed."

Solution: Identify the problem in the JSON file and fix it.

Do the following:

  1. Open an SSH connection to AFA and run:

    su - afa

  2. Run:

    curl –si ‘127.0.0.1:8080/afa/configParser/validate?path=<full path to JSON file>’

  3. View the validation results and error messages in the file ValidationLogs.txt file. This file will be in the same directory as the JSON file.
  4. Fix the error identified in the error message.

Example

After the analysis failed, search the failed analysis's error logs for the following:

Info: running config_parser_json2out -i "gen-algosec_generic_device.algosec" -o "config_parser.out" malformed JSON string, neither array, object, number, string or atom, at character offset 163088 (before "a_ext_10.10.110.88"\n...") at /usr/share/fa/bin/config_parser_json2out line 33. 
Error: hash creation failed.

You validate the JSON file (as described in the solution above). The following error message appears in the ValidationLogs.txt file:

ERROR: [Validator] [2015-10-25 13:23:54,884] [ConfigParserValidatorService.java{1}::validate{1}:41] Invalid JSON format in file =/home/afa/algosec_generic_device.algosec
        Line: 6847
        Field: policies -> src
        Error message: Unexpected character ('a' (code 97)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
 at [Source: java.io.FileInputStream@86daca; line: 6847, column: 14

With this information, you recognize that on line 6847 there is a missing quotation mark:

"src" : [
               a_ext_10.10.110.88"
            ],

Back to top