Home
Troubleshooting
Resolve problems with Teracloud® Streams using the troubleshooting tools provided with the product as well as the resources offered by Teracloud Support.
Known problems and solutions
Use the solutions that are provided to resolve known problems that you might encounter when you work with different components of the product.
Teracloud® Streams problems and solutions
Use the solutions that are provided to resolve the problems that you can encounter when you work with Teracloud® Streams.
Stream applications
Use these solutions to resolve the problems that you might encounter when you develop stream applications.
Conflicts requesting ports from the local port range
An error is generated when the TCPSink, TCPSource, UDPSource, or UDPSink operator of an application specifies the port that Teracloud® Streams is already using, and the application is launched.

Welcome
Learn about the core capabilities of Teracloud® Streams, its architecture, and key concepts.
Installing
Use this information to install, upgrade, and uninstall the Teracloud® Streams product.
Configuring
Create a basic or an enterprise domain which is a single point for configuring and managing common resources, security, and instances.
Administering
Administer the product by using the Teracloud® Streams graphical user interface, APIs, or the streamtool command-line interface.
Developing
Develop stream applications with the Streams Processing Language (SPL), Java, and Python.
Troubleshooting
Resolve problems with Teracloud® Streams using the troubleshooting tools provided with the product as well as the resources offered by Teracloud Support.
- Before contacting Teracloud® Support
  Review this information before you contact Teracloud® Support. These resources might help you to find possible solutions for your issue, or make your support experience more efficient if you need to contact Teracloud Support.
- Troubleshooting techniques
  Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as you expect it to work, and then decide how to resolve the problem.
- Known problems and solutions
  Use the solutions that are provided to resolve known problems that you might encounter when you work with different components of the product.
  - Teracloud® Streams problems and solutions
    Use the solutions that are provided to resolve the problems that you can encounter when you work with Teracloud® Streams.
    - Authentication
      Use the solutions that are provided to resolve problems with Teracloud® Streams authentication.
    - Connectivity
      Use the solutions that are provided to resolve connectivity problems with the product.
    - Domain configuration and administration
      Use the solutions that are provided to resolve the problems that can occur when you work with Teracloud® Streams domains.
    - Installation
      Use the solutions that are provided to resolve the problems that you can encounter when you install Teracloud® Streams.
    - Instance configuration and administration
      Use the solutions that are provided to resolve the problems that can occur when you work with Teracloud® Streams instances.
    - Streams Console
      Use the solutions that are provided to resolve the problems that you might encounter when you work with Streams Console.
    - Stream applications
      Use these solutions to resolve the problems that you might encounter when you develop stream applications.
      - Processing element problems when the maximum number of file descriptors or the maximum number of user processes is exceeded
        When the number of processing elements (PEs) or the number of external connections for a PE exceeds the maximum number of open file descriptors or the maximum number of user processes, the PEs might fail to start or to connect correctly.
      - Processing element startup problems
        If the processing elements fail to start after you submit an application job, you might have to increase the value of the hc.pecStartTimeout property for the domain controller service.
      - Getting rid of the Uncrustify source code formatter warning message
        To ensure that your C++ code is indented and formatted correctly when you generate code by using the sc command, you can optionally install and use the Uncrustify source code formatter. If you do not install this formatter, a warning message is displayed when you compile your code and use the code beautification option.
      - Conflicts requesting ports from the local port range
        An error is generated when the TCPSink, TCPSource, UDPSource, or UDPSink operator of an application specifies the port that Teracloud® Streams is already using, and the application is launched.
    - Teracloud® Streams runtime
      Use the solutions that are provided to resolve the problems encountered during the Teracloud® Streams runtime processes.
  - Toolkit problems and solutions
    Use the solutions that are provided to resolve the problems that you can encounter when you work with toolkits in Teracloud® Streams.
  - ZooKeeper problems and solutions
    Use these solutions to resolve the problems that you might encounter with Apache ZooKeeper.
- Troubleshooting services and diagnostic tools
  Teracloud® Streams provides log and trace services and troubleshooting tools that can help you resolve the issues that you encounter when you work with the product.
- Teracloud® Streams messages
  The Teracloud® Streams messages describe the errors and solutions, warnings of potentially problematic conditions, and helpful information that you can use to troubleshoot the problems that can occur when you work with the product. These messages are displayed in the user interfaces and log files.
Reference
Find details on the SPL language, toolkits, APIs, commands, and more.
Glossary
Use this glossary to find terms and definitions for Teracloud® Streams.

Conflicts requesting ports from the local port range

An error is generated when the TCPSink, TCPSource, UDPSource, or UDPSink operator of an application specifies the port that Teracloud® Streams is already using, and the application is launched.

The symptoms can best be described in an example. A port can be assigned to Teracloud® Streams at any time. In this example, assume that port number 8303 was unused and assigned to Teracloud® Streams. Then, when an application that explicitly uses port 8303 is launched, the following error message is issued:

22 Aug 2012 12:24:51.050 [41774] ERROR spl_operator M[OperatorThread.cpp:run:76]  
- Received exception during execution of operator 'calc_profile_tcp_sink': 
'Unable to bind to port '8303': Address already in use.'.

The application can also exhibit any of the following symptoms:

Fails to launch
Launches sometimes and fails to launch at other times
Launches and then fails when a PE is restarted manually
Launches and then fails after a PE is restarted or relocated by the system

Use the following diagnostic commands, but replace port number 8303 in the first command with the port number that is causing the error in your system:

To show which process is using the port:

> netstat -lnp | grep '8303'
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address    Foreign Address        State       PID/Program name   
tcp        0      0 0.0.0.0:8303     0.0.0.0:*              LISTEN      30523/streams-pec

To show the range of IP ports from which the operating system provides port numbers to Teracloud® Streams:

> cat /proc/sys/net/ipv4/ip_local_port_range
8000 61000

Use one of the following solutions:

Change the Linux™ ip_local_port_range parameters to keep the operating system from allocating certain ports to any process that requests an unspecified port. The following example for the local port range ensures that only the unused ports in the 32768 to 61000 range are assigned.
```
ip_local_port_range 32768   61000
```
In the application source code, edit the invocations of the TCPSink, TCPSource, UDPSource, and UDPSink operators to keep them from using port numbers that are within the local port range.