General Troubleshooting

When you are not able to either collector data from your source or distribute data to your destination, follow the following steps to troubleshoot StreamWeaver.

Enable Debug Logging via User Interface

Configuration User Interface

Screen Shot 2021-05-05 at 2.50.03 PM.png

Select Configuration on the Menu Bar to set the log levels.
Update the com.j9tech packages.
Set the logging level of any of the software packages to DEBUG

View Logs

Linux OS

tail -f /opt/streamweaver/logs/swpallinone.log

Enable Debug Logging via SWP configuration

vi /opt/streamweaver/conf/swp.conf
Change FROM:

logging {
# Reduces log output for some kinds of log messages
# quiet = false

     # Flush log records to file immediately upon receipt. When this is turned
     # on, log results are immediately apparent in the log file, but throughput
     # is reduced by frequent IOPS.When this is false, throughput is enhanced,
     # but the last megabyte or so of the log won't be immediately apparent
     # because it is being cached in memory until it grows large enough to flush.
    # immediate-flush = false

# The default log level for logging components if not specified in levels
#default-level = info

     # Specific logging levels for specific prefixes in logger names
     levels {
          # All J9 code is in the com.j9tech package. We set its logging level to
          # INFO by default.
          #com.j9tech = info

# Akka is the actor, cluster and persistence framework we use.
# akka = warn

          # Kamon is the measurements reporting framework we use.
          # kamon = warn
     }
}

3. Change TO:

# Control of logging
logging {
# Reduces log output for some kinds of log messages
# quiet = false

# The default log level for logging components if not specified in levels
default-level = info

     # Specific logging levels for specific prefixes in logger names
     levels {
          # All J9 code is in the com.j9tech package. We set its logging level to
          # INFO by default.
          com.j9tech = debug

# Akka is the actor, cluster and persistence framework we use.
# akka = warn

          # Kamon is the measurements reporting framework we use.
          # kamon = warn
     }
}

4. Save changes

5. Restart StreamWeaver (service streamweaver restart)

Stopping/Restarting StreamWeaver

To restart StreamWeaver, run the following command: "service streamweaver restart"
To stop StreamWeaver, run the following command: "service streamweaver stop"
To verify that StreamWeaver is started, run "service streamweaver status"
To verify that all StreamWeaver are running, run "/opt/streamweaver/bin/swp status -w 3

Service                            State        Elapsed time   PID    Message
---------------------------------------------------------------------------------------
zookeeper                       Running   59.12 s            95271 healthy
kafka                               Running   48.89 s            95290 healthy
kafka-schema-registry    Running   43.67 s            95309 healthy
cassandra                       Running   38.45 s            95313 healthy
swpallinone                     Running   37.22 s            95375 healthy

You may also want to use visual panels to communicate related information, tips or things users need to be aware of.

Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.