Iotellect Server Not Responding

Sometimes, there may be situations where the server cannot be accessed, but is still running. You can see that the process is running, but when trying to access the Web UI or connect to it using Iotellect Client, the request times out.

There are several common causes of this behavior:

  • Iotellect Server has not enough memory

  • Iotellect Server is using swap memory

  • Iotellect Server causes high CPU load

  • Iotellect Server is running with errors

  • Access to Iotellect Server is blocked by the firewall

If a connection to the Iotellect Server fails, check the following:

  • Make sure that Iotellect Server is running (e.g. find the Iotellect Server tray icon in the system tray). See the Iotellect Server Startup Problems section for troubleshooting server startup.

  • Check that firewall running on the Iotellect Server machine is not preventing incoming connection attempts. The firewall should allow incoming connections to TCP port 6460 (Iotellect Clients), TCP port 8443 (Web UI secure connections), and TCP port 8080 (Web UI non-secure connections). Try completely disabling the firewall.

  • Make sure you've specified the correct address and port of Iotellect Server in server connection settings (if using Iotellect Client) or your browser address bar (for Web UI).

  • If the Server IP Address is specified in the Iotellect Server global configuration settings, make sure that you are trying to access the server using this address.

  • It is possible that Iotellect Server accepts incoming connections on non-standard ports. Check server global configuration settings to find out the current client port number and Web UI port numbers (secure and non-secure).

Iotellect Server Has Not Enough Memory

Memory shortage is the most common cause of low server performance and hanging. The server will never use more memory than specified by the -Xmx parameter located in server_*.vmoptions files. The more actual memory usage approaches this limit, the more CPU time is spent on Java garbage collection (memory cleanup). If the server tries to allocate more memory than allowed by the -Xmx parameter, it will spend all CPU time while trying to release memory, becoming effectively unresponsive.

Try increasing the value of the -Xmx parameter to 50% of server machine RAM if the server database is located on the same machine and to 75% of RAM if using a standalone database server.

See Dealing with Memory Usage for more information.

Iotellect Server Is Using Swap Memory

Iotellect Server is based on the Java platform which dynamic memory management is very sensitive to swapping. Simply speaking, if the contents of memory allocated by a Java application are transferred to a swap space by the operating system, the application's performance is dramatically decreased, making it almost unresponsive.

The maximum memory size Iotellect Server will use is defined by the -Xmx parameter located in server_*.vmoptions files. If this value is set too high, the server will allocate a lot of memory, and the underlying OS will likely move certain parts of those allocations to low-performance swap space.

Use swap usage diagnostic tools (such as smem for Linux) to make sure that Iotellect Server doesn't use swap space. If it does so, decrease the value of the -Xmx parameter (however make sure the server has enough memory for its operation) or increase the server machine RAM.

Iotellect Server Causes High CPU Load

It may happen that Iotellect Server consumes nearly 100% of CPU time. This situation is often caused by wrong settings of different system objects, most likely short polling periods or other frequent periodic actions.

To find the root cause of high CPU load, disable system resources type-by-type. If the CPU load decreases to the normal value after disabling resources of a certain type, enable them back gradually to find the one those settings cause high CPU load.

  • Suspend all devices. Synchronization settings of a device may cause frequent polling that consumes a lot of CPU time.

  • Disable all alerts. Some alert triggers may have too short check period or refer to an expensive operation (such as a query).

  • Disable all trackers. One of them may be calculated too often or refer to an expensive operation.

  • Disable all scheduled jobs. A job may have triggers that cause its too frequent execution, or the job itself may consume a lot of CPU time even if being executed only once.

  • Disable all dashboards. Despite they are running on an operator's computer, they may refer to some expensive server-side operations, causing high CPU load.

It may be hard to control the server under heavy CPU load. To avoid that, try starting Iotellect Server in safe mode. Delete or fix resources that consume CPU power and restart the server in normal mode.

Server Is Running with Errors

Check the server log file to find out the reason for the server failure. If the log file does not help to resolve the situation:

  • Shut down the server (see server shutdown for details)

  • Restart the server in console mode (use %LS_BINARY%_console executable)

  • Check console output for any errors that crop up

Connection Is Blocked By Firewall

It may happen that Iotellect Server appears to start successfully, but you cannot connect to it using Iotellect Client or a browser. No failed connection attempts are visible in the server log file. In this case, try to disable any firewalls running on the Iotellect Server machine. These firewalls may prevent the server from accepting client connections.

If Iotellect Server is running as a service, it may be necessary to manually add the following ports to the firewall exceptions list in order to allow Iotellect Server to accept connections on these ports:

Was this page helpful?