Installation troubleshooting

When you log in to Task Mining Agent, you get an 404 Not Found error.

Check the URL in your browser when you log in to Task Mining Agent. Ensure that it is not https://TM_HOST.

If you are using a Linux non-containerized environment, you must uninstall Task Mining Agent and then reinstall it by using the https://<PM_HOST>/taskmining/ endpoint.

If you are using a Red Hat® OpenShift® Container Platform environment, you must uninstall Task Mining Agent, and then reinstall it by using the https://cpd-mynamespace.<CLUSTER_DOMAIN>/processmining/ endpoint.

For more information, see Installing the Task Mining Agent.

When you log in to Task Mining Agent, it results in the error message.

Check the URL in your browser when you log in to Task Mining Agent. Ensure that it is not https://www.ibm.com or another generic URL.

If you are using a Linux non-containerized environment, you must uninstall Task Mining Agent and then reinstall it by using the https://_<PM_HOST>_/taskmining endpoint.

If you are using an Red Hat® OpenShift® Container Platform (OCP) environment, you must uninstall Task Mining Agent and then reinstall it by using the https://cpd-mynamespace._<CLUSTER_DOMAIN>_/processmining/ endpoint.

For more information, see Installing the Task Mining Agent.

When you try to start the Task Mining Agent, it fails with the following error message:

Unhandled response
[https://PM_HOST/taskmining/api/userinfo]: failure with status code:
NotFound

To find the cause of the issue, you can check Apache Tomcat or NGINX logs.

To check whether the Apache Tomcat is not running or errors are present, do the following steps:

1. Check if Apache Tomcat is running with ps -ef |grep tomcat.

2. Check logs at <TM_HOME>/tomcat/logs/catalina.out.

To check whether NGINX is not correctly configured, check logs at /var/log/nginx/error.log or /var/log/nginx/access.log.

When you are using an endpoint with an untrusted or self-signed certificate, you see the following error.

Unhandled response
The SSL connection could not be established, see inner exception.

By default, the allowUntrustedCertificate attribute in the Task Mining Agent configuration JSON file is set to false to deny access to untrusted and self-signed endpoints. To allow an untrusted endpoint, set allowUntrustedCertificate to true.

When you try to log in, you encounter the following error.

comexception decoding hex
string: invalid characters
encountered in Hex string

Properties of JSON Web Token (JWT) and JSON Web Encryption (JWE) must be the same in IBM Process Mining and IBM Task Mining configuration files.

• For IBM Process Mining, check the file <PM_HOME>/etc/processmining.conf at the key authentication.jwt and authentication.jwe.

• For the IBM Task Mining, check the file <TM_HOME>/bin/environment.conf at the key jwt_secret and jwe_secret.

The following log shows an information about the wrong URL that display a Generic error.

2020-12-04 13:41:52.828 ERROR 4087 --- [nio-8090-exec-3] com.invenio.task.j: Request: http://tm-test.my-domain.com/taskbuilder-2.1.0/api/projects raised not handled exception
org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://pm-test.my-domain.com/integration/tm/processes": pm-test.my-domain.com; nested exception is java.net.UnknownHostException: pm-test.my-domain.com

Open the file <TM_HOME>/bin/environment.conf and set the value of processmining_host to the IBM Process Mining hostname.

The following log shows an information about the wrong permissions that display the 404 Not Found error.

tail -300f /var/log/nginx/error.log

2020/12/04 14:05:51 [error] 16104#0: *42 open() "/opt/taskminer/tm/index.html" failed (13: Permission denied), client: XXX.XXX.XXX.XXX,

Run the following command:

chcon -Rt httpd_sys_content_t /opt/taskminer/tm

The TM Data Processor is blocked and no evidence of errors are present in the log.

Complete the preliminary operations explained in the TM Server Setup topic.