Introduction
This Troubleshooting Guide is intended for operators, supervisors, administrators, and other users of Plant Applications.
This guide helps the user to troubleshoot the issues related to Plant Applications Installation, Plant Applications Web Client, and Plant Applications Administrator. It includes the information on how to diagnose and troubleshoot various common issues the user may encounter in Plant Applications.
This guide has the following sections:
- Troubleshooting Install Issues (on page 3)
- Troubleshooting Web Client Applications (on page 6)
Prerequisites
Refer to Plant Applications Server and Client Requirements before you attempt to troubleshoot an issue.
Troubleshooting Install Issues
Issue: SSL Certificate not updated
An SSL certificate allows you to access Enterprise Edition Web Client using HTTPS. You can either use a self-signed certificate or get a trusted certificate from a Certificate Authority (CA).
You must use utility.sh located at plantapps-enterprise-webclient-<buildno> folder to apply the certificate. If the certificate is not updated correctly, navigate to <Install file path>/plantapps-enterprise-webclient<buildno>/log/ansible.log to see the log files.
Refer to the below table, for issues related to certificates and corresponding resolutions.
| Issue | Reason | Resolution |
|---|---|---|
| If utility fails | Not a valid path |
Note: If the Certificate is signed by Enterprise CA, then it should contain all certificate levels: the Root CA, the Intermediate Enterprise Certificate, and the Server Certificate.
|
| Certificate not reflecting in the Web Client | Self-signed certificate is not updated, or the certificate is expired |
This issue is fixed in PA2022. The PApamymachinesservice stack was not removed which prevented the certificates to be configured properly. You must remove the PApamymachinesservice stack by running the command:
|
| Un-authorization error | Proficy server certificate failed |
For more information, refer to: Replace the Public Keys of Remote Services and Replace the SSL Certificate of Enterprise Edition Web Client. Access the access control service and check for the PKIX errors, if found:
|
| HAProxy error | Web Client application not accessible |
To verify the logs, run the command:
and check for the HAProxy error: [ALERT] (8) : config : parsing [/usr/local/etc/haproxy/haproxy.cfg:34] : 'bind *:5059': No Private Key found in '/usr/local/etc/haproxy/haserver.pem.key' To troubleshoot the HAProxy error:
Note: You should not provide the path of the entire chain of the certificate. You must only provide the server certificate and server key path.
|
Issue: Unable to access the Enterprise Edition Web Client
Plant Applications Enterprise Edition Web Client is installed only on a Linux machine. After successful installation, application is not accessible and Haproxy service logs display the following errors:
[NOTICE] (6) : haproxy version is 2.5.1-86b093a
[NOTICE] (6) : path to executable is /usr/local/sbin/haproxy
[ALERT] (6) : [haproxy.main()] Cannot raise FD limit to 8251, limit is 1024
Follow the below steps to troubleshoot the issue:
- Modify the following parameter at: /etc/sysconfig/docker
- Restart the docker.
OPTIONS="--default-ulimit nofile=1024:4096"
Replace with
OPTIONS="--default-ulimit nofile=10000:15000"
Troubleshooting Web Client Applications
Issue: History of Work Order Manager Stops Working
In the Standard Plant Applications Web Client, if the History section does not display the events associated with the work order, or if the work order history stops working, you must verify Tomcat Web Application Manager to check the running state of Kafka dependent services. If the Kafka dependent services are down (indicated by false in the Running column of Tomcat Web Application Manager), it implies that there is an issue with Kafka log message, or that the message broker is down and stopped:
The issue with the Kafka broker may be due to the following reasons:
- PA web client Master control did not start GE PlantApps Zookeeper and GE PlantApps Kafka in a specific order or, there was a delay in starting Kafka after Zookeeper started.
- Kafka\Kafka-logs is in crash state.
To troubleshoot the issue, follow the below steps:
- Open the Services window from the search box.
- Stop GE PlantApps Zookeeper and GE PlantApps Kafka services.
- Delete Kafka log messages from:
- C:\Kafka\kafka-logs
- C:\Kafka\logs
- Restart GE PlantApps Zookeeper and then GE PlantApps Kafka services.
Verify Tomcat Web Application Manager to ensure that the below mentioned Kafka dependent services are up and in running state:
- approval-cockpit-service
- comment-app-service
- erp-export-service
- labor-service
- operator-app-service
- plant-execution-service
- supervisor-app-service
- work-order-history-service
Result: The Kafka dependent services that were down, will restart now (indicated by true in the Running column of Tomcat Web Application Manager). This indicates the Kafka broker is working as expected.
Issue: Time Booking records cannot be modified
In the Security application, the Moderate time booking records role enables you to edit the time booking records of other users using the Time Booking application, and this permission is only applicable at a Site/Plant level resource.
As a supervisor or an operator, if you are not able to modify labor records in Time Booking even if you have the required permissions, it means that the role assignment is not done at Site/Plant level resource.
Follow the below steps to troubleshoot the issue:
- Navigate to the Security application.
- Select the Roles tab and select [edit icon] against the required role (the role that was assigned to the user who is not able to modify time records).
- Select the Time Booking tab from ROLE CATEGORY and ensure that the Moderate time booking records toggle is enabled.
- Select Assignments tab and select the assignment you want to edit (the assignment that includes the user who is not able to modify time booking records).
- From the Resources tab, add the required Site/Plant level resource to that assignment.
Result: In the Time Booking application, you will be able to modify the user capabilities, when you select Change User located below your username.
Issue: Cannot create raw material lots in PA2022
After upgrading to PA2022 from 8.1 or 8.2 version, user may have issues in creating raw material lots. This is because, in 8.1 or 8.2 version the lowest resource level that should be added to the assignment was the unit at which the produced material was executing. In PA2022, the lowest resource level that should be added to the assignment is the unit at which the raw material is stored.
To troubleshoot this issue, the assignment for the user (for creating raw material lots) must be changed from the unit at which the produced material was executing to the unit at which the raw material is stored. For more information on how to modify an assignment, refer to Modify an Assignment topic in Plant Applications Help.
Issue: Cannot find the serial/lot no. or work order or operation added to Work Queue
In the earlier versions of Plant Applications, when you added a new serial/lot no. or work order or operation to Work Queue application, it was added to the first row of the grid.
In PA2022, the content of the grid is sorted based on the ascending alphabetical order of the WORK ORDER column. Hence, you can locate the newly added serial/lot no. or work order or operation based on the alphabetical order of the WORK ORDER column.
