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.
Instance configuration and administration
Use the solutions that are provided to resolve the problems that can occur when you work with Teracloud® Streams instances.
Instance log files deleted by the system maintenance utilities
If the log files of the Teracloud® Streams instances are deleted, they are not available for troubleshooting purposes. You can change the directory in which the files are stored, or have the system administrator adjust the settings of the system maintenance utilities.

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.
      - Instance log files deleted by the system maintenance utilities
        If the log files of the Teracloud® Streams instances are deleted, they are not available for troubleshooting purposes. You can change the directory in which the files are stored, or have the system administrator adjust the settings of the system maintenance utilities.
    - 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.
    - 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.

Instance log files deleted by the system maintenance utilities

If the log files of the Teracloud® Streams instances are deleted, they are not available for troubleshooting purposes. You can change the directory in which the files are stored, or have the system administrator adjust the settings of the system maintenance utilities.

The log files for the long-running instances are deleted by the system maintenance utilities, such as tmpwatch. When these log files are deleted, you cannot use them to troubleshoot the problems that you might encounter when you work with Teracloud® Streams.

The default configuration for Linux™ system maintenance deletes the unused files and directories from the /tmp directory. If the log level of the instance is set to generate a minimal amount of information, the Teracloud® Streams log files might not be updated frequently enough to keep them from being deleted by the system maintenance processes.

To resolve the problem, you can:

Change the directory in which the instance log file is stored.
Contact the system administrator, who can adjust the settings of the system maintenance utilities by running the tmpwatch command in the daily cron.script.
For each long-running instance, exclude the following Teracloud® Streams files and directories:
```
/tmp/Streams-domain_ID/streams.instance_ID@instance_owner
/tmp/Streams-domain_ID/instance_ID@instance_owner.boot.log
```
To list the excluded files, use the -x option on the tmpwatch command.