Troubleshooting application configuration

You can troubleshoot the issues or exceptions that you come across while configuring IBM Process Mining. You can see the troubleshooting methods for the following categories in this topic:

Installation troubleshooting

Error 404 on port 80

When you install IBM Process Mining on the RedHat Linux 8 operating system, you get 404 error on Port 80.

Troubleshooting

Check in the NGINX file (/etc/nginx/nginx.conf) of the RedHat Linux 8 operating system for the following command lines for server on port 80:

location / {
}

If you see the above mentioned command lines in the nginx.conf file, then it is an issue caused by the undefined redirection to Port 443.

Workaround

When you see the 404 error on Port 80, you must edit the nginx configuration file of the RedHat Linux 8 operating system (/etc/nginx/nginx.conf). You must define the redirection to Port 443 by doing the following steps:

  1. Remove the following command line

    location / {
}

  2. Add the following command line for the redirection

    return 301 https://$host$request_uri;

After making the changes, restart the NGINX server.

Application did not start

Application not started - Effect

Troubleshooting

Possible cause: database not correctly configured.

Check the log file:

<PM_HOME>/jetty-web/logs/yyyy_MM_dd.jetty.log

Application not started - Troubleshooting

Process app fail during launch

./pm-accelerators.sh start
Using tmp: /opt/processmining/repository/temp
Starting accelerator server...
output to [/opt/processmining/repository/logs/pm-accelerator-sap-p2p.log] started.
Using tmp: /opt/processmining/repository/temp
Starting custom accelerator service...
output to [/opt/processmining/repository/logs/pm-accelerator-custom-std.log]
initiating python venv..
    first time running....
'Python3.9' is WAS NOT found as specified in 'environment.conf'
    '/usr/bin/python3.9'
    custom accelerator requires python3.9 installed.
    please check python3.9 is installed and available.

Troubleshooting

  • If you already have a custom deployment of Python 3.9 or later and you want to use it instead of a standard Python 3.9, then ensure that your configuration is available in the <PM_HOME>/bin/environment.conf file.

    CMD_PYTHON=/usr/bin/python3.9

    In addition, on ubuntu you must commit a override check

    ACF_CUSTOM_UBUNTU_CHECK=1

  • If you have an existing deployment of standard Python 3.9, then in the <PM_HOME>/bin/environment.conf file run the following command:

    CMD_PYTHON=/usr/bin/python3.9

    You must also confirm if your original deployment matches with the details that are listed in <PM_HOME>/bin/environment.conf

    which python3.9
/usr/bin/python3.9

For more information about installing Python 3.9 for process app, see Installing Python for Custom process app.

Upgradation troubleshooting

Error while running update.sh

  • When you attempt to upgrade to IBM Process Mining version 1.14.2 from version 1.13.1 or earlier, the system throws the following error after running ./update shell script:

    ./update.sh
current deployment is older than version '1.13.1'
this upgrade is ONLY available for upgrading from '1.14.1' to '1.14.2'
please follow documentation on how to upgrade to '1.14.1' before attempting this upgrade

  • When you attempt to upgrade to IBM Process Mining version 1.14.2 from any version other than 1.14.1, the system throws the following error after running ./update shell script: :

    ./update.sh
current deployment is not applicable for this upgrade.
current release: [<current release>]
current version: [<current version>]
this upgrade is ONLY available for upgrading from '1.14.1' to '1.14.2'
please follow documentation on how to upgrade to '1.14.1' before attempting this upgrade

  • If you do not set the environment variable when you upgrade to IBM Process Mining version 1.14.2, the update.sh throws the following error message:

    ./update.sh
Error: PM_HOME environment variable is not set. Set it to the processmining home.

Application service startup might fail on SELinux

Starting the application service on Red Hat with Security-Enhanced Linux (SELinux) might fail with the 203/exec error because it is necessary to allow the application script to be run by the Linux service.

Troubleshooting

  1. Run the following command to check whether SELinux is enabled. For more information, see Changing SELinux states and modes.

    getenforce

The getenforce command must display an output Enforcing.

  1. To allow the script to run, issue the following command:

    chcon -t bin_t /opt/processmining/bin/<SCRIPT NAME>

  2. The previous command is a temporary option that you can use for testing. Nevertheless, you can use the following commands to make the configuration permanent (to retain the configuration even after a system restart).

    semanage fcontext -a -t bin_t '/opt/processmining/bin/<SCRIPT NAME>'
restorecon -Fv /opt/processmining/bin/<SCRIPT NAME>

<SCRIPT NAME>: You must configure the following scripts: pm-accelerators.sh, pm-analytics.sh pm-engine.sh, pm-eureka.sh, pm-monitoring.sh and pm-web.sh. You can find them in the directory /opt/processmining/bin/.

  1. Optionally, you can also assign the execute rights to shell scripts (for example: chmod +x /opt/taskminer/tomcat/bin/*.sh, chmod +x /opt/taskminer/bin/*.sh, chmod +x /opt/processmining/bin/*.sh).