Known problems and workarounds

Security warning error messages

When you open the Wazi Analyze UI from your browser on your local machine for the first time, you will get a security warning message. You can accept the risk to continue and configure your Wazi Analyze container with a certified security certificate. For more information, see Security considerations.

For the Firefox browser, in addition to accepting the risk on port 5000, you need to navigate to https://localhost:4680 to accept the risk on port 4680 so that you can run the Wazi Analyze API server. This is because the Firefox browser only allows accepting the risk on ports that you specifically allow.

Failing to open the Wazi Analyze UI with http protocol

When you load Wazi Analyze with http protocol, you will get the message that the site is not available. This is because the Wazi Analyze supports only https protocol. You need to change the URL to https://localhost:5000/explore.

AD authentication failure

If you see the error message that AD authentication fails, you need to perform AD authentication before you can proceed. Complete the following steps to authenticate with AD server.
  1. Select the AD authentication button from the drop-down menu under the Profile icon.
    Figure shows the drop-down menu under the Profile icon.
  2. Provide the following information for AD authentication.
    • User ID
    • Password
  3. Click the Authenticate button to process AD authentication.
  4. Click the Close button in the Application Discovery authentication dialog after you pass the authentication.

Resetting a forgotten password

If you have forgotten the password that was provided when you started the Wazi Analyze server, complete the following steps to reset the password.
  1. Run the following command to shut down the Wazi Analyze server.
    wa-shutdown.sh
  2. Run the following command to restart the server. 
    wa-startup.sh
  3. When the command line prompts for your password input, enter a password to secure access to the Wazi Analyze server. The password length should be from 5 to 15 characters long.

You can use your newly provided password to access Wazi Analyze server and view all the projects that are stored on the server.

Seeing <missing> file extension in the analysis results

When the scanner does not recognize the file extension of your source files, you will see the node in the graph with <missing> extension or the artifact with <missing> file extension in the table view. It might be because you did not use uppercase file extension. For more information, see Preparing the source files to be scanned.

Running into permission issues when you start the Wazi Analyze container with shared file system option

If you have permission issues when you start the Wazi Analyze container by using run command with shared file system option, you can set shared file setting from your Docker Desktop. For more information, see Prerequisite: Setting up Docker or Podman to deploy the Wazi Analyze container.

Common scan errors and solutions

Check the following common scan errors that you might encounter and see how you can fix them. For more information, see Understanding the scanning messages in the scan log file.
Error: EMSG_220 <file-name>
This message indicates that a file that is referenced in the source code, named <file-name>, cannot be found or cannot be opened. If it cannot be found, you can fix it by putting the mentioned file into the source directory. If it cannot be opened, it is possibly because the scanner does not know the file extension. You can consider changing the file extension to a standard extension. For more information, see Preparing the source files to be scanned.
Error: EMSG_220 <*.file-extension>
This message indicates that no files with a specific extension, the <*.file-extension> that is specified in the .dat file, are found in the source directory to be scanned. This error has no impact on the scan results. You can eliminate this message by removing the files option setting, F=<*.file-extension>, of the file extension that does not have any matching files in the project from the FILES section of the .dat configuration source file.
File: <file-name>
This message indicates that the <file-name> isn’t scanned. Check the following possible reasons and make fixes accordingly.
  • The <file-name> is not capitalized. Ensure that the file name and extension are capitalized.
  • Scanner does not understand the file extension. Consider changing the file extension to a standard extension. Check Preparing the source files to be scanned for more information. Or you can update the .dat configuration file to include the file extension in the FILES section.
rm: cannot remove ‘/home/wazi/data/fid/Output/maintab.txt’: No such file or directory
This message can be ignored. The error has no impact on the scan results.

No comment lines when previewing source content

If you cannot see comment lines when you preview the source content of a file, you might need to complete the following steps to enable scanning comment lines option in your configuration file.
  1. Open the configuration file of your project under the /home/wazi/data/<project-name> directory.
    • You can use any text editor to view or edit the file.
    • If you use the VI editor, you can run the following command to open the file. 
      vi /home/wazi/data/<project-name>/<project-name>.dat
      You can use the following keys to change the editing mode of VI editor:
      • Press i to go to edit mode.
      • Press Esc + :wq to save and exit.
      • Press Esc + :q! to exit without saving.
  2. Set OPTION_WITHCOMMENT to 1 or add the following line to the configuration file under the OPTIONS section.
    OPTION_WITHCOMMENT=1
  3. Save the changes to the file.
  4. Re-scan the project and restart the server.
For more information, see Understanding the scan options in the configuration file

Functions search in COBOL language

For the COBOL language, you can see the Functions search in the Artifact type list. The functions represent paragraphs in COBOL language. You can search for a paragraph but you will not see any associated graph or properties.

Getting information on what is running in the container

If you want to check what is running in the container, complete the following steps:
  1. Open Docker terminal.
  2. Run the following Docker command to get the information about the processes that are running in the Docker container. 
    ps
    For Wazi Analyze, after you start up the server, you can see the following running processes:
    • oatpp
    • node(2)
    • weasypro