Home
Troubleshooting
Resolve problems with Teracloud® Streams using the troubleshooting tools provided with the product as well as the resources offered by Teracloud Support.
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.
Managing log and trace data
Teracloud® Streams generates log and trace data that can help you to identify, diagnose, and resolve problems with the Teracloud Streams product and applications.
Customizing logging and tracing
Teracloud® Streams provides domain and instance properties that you can use to customize logging and tracing.
Logging events and messages in the Linux™ system log
By default, Teracloud® Streams logs events and messages in rolling log files on each resource. You can use this procedure to configure Teracloud Streams to log events and messages in the Linux™ system log.
Log file formats and examples
There are differences in the file format of the rolling log file on each Teracloud® Streams resource and the Linux™ system log.

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.
- 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.
  - Log and trace services
    The default log and trace service for Teracloud® Streams logs events and messages in rolling log files on each resource. Because the logs are distributed across the cluster, use the streamtool getlog command to collect the logs from each resource for easy examination.
  - Managing log and trace data
    Teracloud® Streams generates log and trace data that can help you to identify, diagnose, and resolve problems with the Teracloud Streams product and applications.
    - Log and trace files
      By default, Teracloud® Streams generates log and trace files for the domain and instance services and applications. Administrators, instance owners, application developers, and Teracloud Support can use this data to correct problems with Teracloud Streams.
    - Customizing logging and tracing
      Teracloud® Streams provides domain and instance properties that you can use to customize logging and tracing.
      - Log and trace properties
        Teracloud® Streams provides log and trace properties for domains and instances that apply to all or specific Teracloud Streams services.
      - Modifying log and trace properties
        You can use the streamtool command-line interface or the Teracloud® Streams graphical user interfaces to modify settings for Teracloud Streams log and trace properties.
      - Changing the default location of log and trace files
        The default root directory for the log and trace files that are generated by Teracloud® Streams is the /tmp directory. To configure a different root directory, update the domainLog.path domain property by using the streamtool setdomainproperty command.
      - Logging events and messages in the Linux™ system log
        By default, Teracloud® Streams logs events and messages in rolling log files on each resource. You can use this procedure to configure Teracloud Streams to log events and messages in the Linux™ system log.
        Log file formats and examples
        There are differences in the file format of the rolling log file on each Teracloud® Streams resource and the Linux™ system log.
  - Diagnostic tools
    Teracloud® Streams provides a set of diagnostic tools that can help you troubleshoot problems.
- 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.

Log file formats and examples for Teracloud® Streams and Linux™

There are differences in the file format of the rolling log file on each Teracloud® Streams resource and the Linux™ system log.

Teracloud® Streams rolling log file

In the rolling log file, the following format is used:

[Timestamp] [Host IP address] [Aspect] Message ID and text

For example:

[2016-06-09T12:49:51.211-0400] [192.0.2.0] [domain=domain1,host=host1.ibm.com] 
CDISA3046W The host1.ibm.com resource in the domain1 domain experienced a zookeeper disconnect 
on 2016-06-09T12:49:43.-0400. Zookeeper reconnected at 2016-06-09T12:49:43.-0400.

Linux™ system log file

In the Linux™ system log file, the following format is used:

[Timestamp in syslog format] [Host] [Product] [Host IP address] [Aspect] Message ID and text


Jul 27 14:16:07 host1 : [Teracloud Streams][192.0.2.0] [domain=domain1,host=host1.teracloud.com] CDISA0021I Starting the following domain: domain1.
Jul 27 14:16:07 host1 : [Teracloud Streams][192.0.2.0] [domain=domain1,host=host1.teracloud.com] CDISA0034I Waiting for all services to start.
Jul 27 14:16:07 host1 : [Teracloud Streams][192.0.2.0] [domain=domain1,host=host1.teracloud.com] CDISA0038I The aas service started on the following resource: host1.ibm.com. The service has the following process id: 10380.
Jul 27 14:16:07 host1 : [Teracloud Streams][192.0.2.0] [domain=domain1,host=host1.teracloud.com] CDISA0038I The auditlog service started on the following resource: host1.ibm.com. The service has the following process id: 10380.
Jul 27 14:16:13 host1 : [Teracloud Streams][192.0.2.0] [domain=domain1,host=host1.teracloud.com] CDISA0039I The jmx service started on the following resource: host1.ibm.com. The service has the following process id: 10539. The service uses the following port: 9975.
Jul 27 14:17:02 host1 : [Teracloud Streams][192.0.2.0] [domain=domain1,host=host1.teracloud.com] CDISA0039I The sws service started on the following resource: host1.ibm.com. The service has the following process id: 10827. The service uses the following port: 8443.
Jul 27 14:17:02 host1 : [Teracloud Streams][192.0.2.0] [domain=domain1,host=host1.teracloud.com] CDISA0022I The following domain started successfully: domain1.