Known Issues¶
The following are the known issues as of 06/24:
| Issue | Troubleshooting |
|---|---|
| Large RSA keys in certificate chains can cause a client to expend significant CPU time verifying signatures. | In case you experience this behavior when using the IE State Service, it is recommended to reduce the size of the RSA key in your certificate chain. |
| When you change the user in the Management UI of the IEM, it is possible that you still see the Edge Devices from the previous user. | Clear the cache of your Internet browser and refresh the IEM. |
| It is possible that the error "Out of memory" occurs in the VM with the issue that the IEM is not accessible anymore. | Reboot the VM. |
| When you take a snapshot of the Industrial Edge Management OS (IEM‑OS) in the VM while the VM is running and you restore the snapshot, you will be signed out from the Industrial Edge Management when you open an app in the "Catalog" menu item in the Management UI. Also, when you restore the snapshot in this case, the time of the VM is not aligned with the current time. | To realign the time of the VM, reboot the VM or restart NTP services. When you take a snapshot of the Industrial Edge Management OS (IEM OS) in the VM while the VM is powered off, this issue will not occur and you do not have to reboot the VM or restart NTP services. |
| Deleting a configuration of the IE Databus and the SIMATIC S7 Connector by clicking the "Delete Configuration" button under the "My Installed Apps" menu item starts a task on the according Edge Device but fails immediately. | - |
| Connecting an Edge Device to the IEM fails and the "Nginx configuration test failed" error message is displayed during activating the Edge Device phase. | Check the DNS server configuration since the error message is DNS server related. The DNS server must be configured properly and reachable for the IEM. |
| After you have updated the Industrial Edge Management App to a newer version, the IEM does not work properly anymore, and IE services cannot be installed. | To successfully update the Industrial Edge Management App version 1.2.5 or older, you must perform the following steps:
|
| After you have updated the IEM OS to a newer version (V1.3), the already onboarded Edge Devices will go offline in the IEM and new Edge Device cannot be onboarded. | Reboot the IEM OS or update the Industrial Edge Management App to the latest available version. |
| If you enter an invalid character for the storage size or if you enter too much storage size for the IE State Service (IESS) during its installation, the IESS app will be indeed installed in the Maintenance UI of the IEM. But when navigating to the "Backups" section in the Management UI of the IEM, the "IE State Service unavailable" message is displayed. In this case, the IESS is not working. | In the Maintenance UI of the IEM, download and check the logs of the IESS. If one of the described errors is included in the logs, uninstall and reinstall the IESS in the Maintenance UI of the IEM. Ensure that a valid value (only numbers) is entered for the storage size and that the entered value fits to the available hard disk size of the whole IEM system. |
| If an user creates an "Admin Group" and adds devices to it these devices will not only show up under "My Edge Devices" but also under "Authorized Edge Devices". | The user automatically gets the role for the created "Admin Group" assigned. You could remove the role for the group in IAM. |
| Field mac_address in apps docker compose is ignored. | This is a bug of Docker Engine resolved with devices that use Docker Engine greater than 24.0. |
IEDK version effects on the app developer mode¶
The following table shows the IEDK version effects on the app developer mode after soft resetting the IED:
| IEDK version | App Developer Mode Setting | App Developer Mode Behaviour |
|---|---|---|
| 1.3 |
|
All installed apps are listed in the app developer mode. |
| 1.5 |
|
All installed apps are listed in the app developer mode. |
| 1.7 |
|
Apps which are created under `App Projects` in the IEMA and installed on the IED are listed in the app developer mode. Imported apps on the IEMA created by another user and installed on the IED are not listed in the app developer mode. Imported apps from the IE Hub to the catalog of the IEMA and installed on the IED are not listed in the app developer mode. |
| >=1.8 |
|
The session will be invalidated and cookies will be deleted due to cookie management after a reset, hard reset and firmware update. |
| The function "Transfer Ownership" is removed from the Admin Management of the IEM offerings except IEM OS. | Recommendation is to use DeviceOwner role to access devices as owner. Recommendation is to always share a project app with others as project.apps.co-owner. If the project app is not shared and the owner is no longer available, the project app will need to be recreated. | |
| The IEM will not be accessible, if it is setup with a hostname in capital letter (e.g., “IEM.MYURL.COM”). | Setup the IEM again with a hostname in small letter. | |
| If the user does not have access rights to the "Identity & Access Management", the error message when clicking on "Identity & Access Management" is "Network response was not OK". | The error code means that the user does not have permissions to work with the "Identity & Access Management". If you want to enable this for the user, you can follow the description in the "Assign Role" chapter and add the "realm-management - realm-admin" role to the user. | |
| If the email address of the original IEM user is deleted, the installation of IEM applications such as Flow Creator Configurator fails with the following error message "Something went wrong...cannot perform requested operation." | Add an email address to the initial IEM user. | |
| If an OTP is required for a user either by 'required action' or 'browser login flow', the login will fail with an error message: "We are sorry... An internal server error has occurred." | If multi-factor authentication is required, use an external identity provider or switch to the "keycloak" login theme (Realm Settings -> Themes -> Login Theme). | |
| If an Edge Device with a created/active firmware update job is deleted from the IEM, the Edge Device itself may become unstable. | Before deleting a Device from the IEM, make sure there is no scheduled/active firmware update job on the device. | |
| The user who onboarded a Device is not supposed to be deleted. If the user is deleted, no apps can be downloaded to the device because the device cannot authenticate to the IEM's docker registry. | - |
The following table shows the IEDK version effects on login of Device¶
| IEDK version | Behaviour difference |
|---|---|
| 1.3 | Same session will be running |
| 1.5 | Same session will be running. |
| >=1.7 | Same session will be running. |
| =1.8 | The session will be invalidated, and cookies will be deleted due to cookie management after a reset, hard reset and firmware update. |
Note If the device updates from 1.8 to 1.9, the session will not be invalidated after a soft reset, Hard reset and firmware update. The same session will be running if the device updates from 1.8.0-6 to 1.8.0-7. These changes affect only the 1.8 version, so if the device updates to 1.8, the user must log in again.
Industrial Edge Management Virtual¶
| Issue | Troubleshooting |
|---|---|
| UPDATE: For some IEM Virtual instances the update stalls if only limited bandwidth is available | If an IEMV update stalls due to restricted network bandwidth, access the Service and Maintenance applet using the Recovery key through port 4443. You'll see the update in progress; cancel it to revert to the previous version for continued operation. Enhance bandwidth before attempting the update again. We're developing a solution to facilitate updates with limited bandwidth. |
| DHCP: When using DHCP, make sure to always assign the same IP address to the IEM-V. Not doing so will result in an unreachable and unstable system. | Assign a fixed IP Address to the IEM-V instance. Ensure the DHCP does not change it dynamically. |
| Custom Certificates: When using custom certificates, they are not checked for their format. | Provide X509 PEM Formatted keys and certificates only that match to each other. |
| Custom Certificates: Custom Certificates cannot be changed or renewed | Keep the IEM-V instance "up to date". Functionality will be available in upcoming versions |
| Self Signed Certificates: Self Signed Certificates cannot be changed | Self Signed Certificates are valid for 10 Years by default. Keep the IEM-V instance "up to date". Functionality will be available in upcoming versions |
| Network Limitations: Network & Proxy Settings cannot be changed after onboarding | Keep the IEM-V instance "up to date". Functionality will be available in upcoming versions. |
| If an FQDN is provided, the IEM-APP cannot be reached via IP address anymore, only via the hostname. | Ensure that the DNS server is available and working before providing a FQDN name. |