Skip to main content

Alerts

The IPC Manager can show a collection of alerts for each IPC. These range from hardware errors over BIOS configuration to runtime issues.

ai.intrinsic.os:35209 SMT enabled (5209)​

This alert is raised when the IPC is running an image for realtime applications, but SMT, also known as HyperThreading, is enabled in the BIOS.

This misconfiguration can lead to performance issues or crashes.

See the BIOS configuration guidance for more information about how to disable SMT.

ai.intrinsic.os:31358 Low Memory Installed (1358)​

This alert is raised when the IPC has insufficient memory capacity. I.e. when it as less than 16GB total memory.

If this alert is shown, make sure at least 16GB of RAM is available to IntrinsicOS, for example by removing and reinserting the RAM modules.

If it persists, make sure the memory is usable, e.g. by checking the memory total displayed in the BIOS.

ai.intrinsic.os:43623 Low Memory Free (3623)​

This alert is raised when the IPC has insufficient free memory. I.e. when the running application takes up most of the memory capacity.

This isn't an error by itself, but can be an underlying issue for errors. Very low free memory results in more work for memory management, which can slow down tasks.

Possible causes include:

  • Use of unsimplified geometry in the solution.
  • Adding many pose estimators to the solution.
  • Logging large amounts of text or structured data, especially when the internet connection is slow and Operate mode is not enabled.

ai.intrinsic.os:18381 No time server configured​

IntrinsicOS uses possible 3 sources for time servers. Ensure that at least one of them is used.

  • Default time server (time.google.com): This configuration needs to be changed by an Intrinsic engineer via remote access.
  • Explicit time server configuration: This configuration needs to be changed by an Intrinsic engineer via remote access.
  • DHCP provided time server: If you have a local time server and use DHCP for network configuration, please provide the NTP server via DHCP. IntrinsicOS will automatically use it.

ai.intrinsic.os:28381 No time server could be resolved​

IntrinsicOS failed to resolve the time server from names to IP addresses. This might be a typo in the configuration (e.g. tmie.company.org) or an issue with the DNS server.

Check that the configuration actually matches the expected time server. If that's the case, make sure the DNS configuration is valid, and the server is responsive.

ai.intrinsic.os:24530 No time server can be reached​

IntrinsicOS failed to reach any of the configured time servers.

If you have not configured the time server explicitly, your network blocks outgoing connections to the default time server time.google.com. Please ensure the IPC is allowed to use NTP with time.google.com or provide a time server via DHCP.

If neither of the above options is viable, contact support so an Intrinsic engineer can set your time server in the configuration via remote access.

ai.intrinsic.os:27765 UPS is unreachable​

Ensure UPS is correctly configured and reachable.

An uninterruptible power supply (UPS) has been configured with inctl cluster ups but is not reachable, possibly because of an incorrect driver or port setting, or possibly because the UPS is turned off or not correctly connected. Double-check the connection and the values of driver and port.