Predix Edge Release Notes 2.6.0
These are the new features, enhancements, and known and resolved issues for the 2.6.0 release of Predix Edge.
Upgrade Path
Predix Edge OS must be installed incrementally; you cannot skip a minor release (i.e., if you are running version 2.4.0, you must first install 2.5.0 and then 2.6.0). You do not have to install every patch release (indicated by a change to the third digit in the release number).
New Features and Enhancements
This release contains the following new features and enhancements:
- Netdata Device Monitoring
- Netdata is a real-time monitoring utility that has been incorporated into Predix Edge Technician Console for monitoring your devices. See Device Monitoring.
- Troubleshooting Commands
- The following commands are available through SSH access for troubleshooting
networking and system operation:
- curl(1)
- dig(1)
- ip(8)
- ss(8)
- ping(8)
- tcpdump(8)
- openssl(1)
- jq(1)
- ssh(1)
- scp(1)
- gzip(1)
- nc(1)
- traceroute(1)
Known Issues
This release has the following known issues:
- Successful Factory Reset Returns Failure Message
- After performing a factory reset via PETC, an error message may pop up indicating the operation Failed to reset device; however, the factory reset will have been successful.
- Docker Apps Flooding Logs
- A Docker application that floods the logs can cause system performance to degrade, resulting in the Docker applications restarting.
- Serial Port Bootlog
- A qemu- or vmware-based OS will output the bootlog out of the serial ports. This can cause problems if they are connected to physical hardware.
- Device Clock Modifications
- If a device’s clock is modified to a time prior to when it was first initialized, all deployed applications will be stopped and all system applications will run after the device reboots.
- Application Configurations
- Applications will not be able to read application configuration files created without read permissions. Ensure that configuration files have read permissions prior to zipping them in preparation for uploading them to Edge Manager or PETC.
- Invalid Log Level
- A cloud gateway with an invalid log level will not forward data to the cloud and will not generate any log messages.
- Data Not Forwarding When OPC-UA Adapter Fails to Connect to Broker
- In some instances, when the client id is not specified in the application configurations, two separate applications may have identical mqtt client IDs, resulting in the applications failing to connect to the broker and data not being forwarded.