Troubleshooting

This document will help you troubleshoot common issues with your Fluvio cluster.

Troubleshooting a Local Cluster

To troubleshoot a local Fluvio cluster, you can check the logs of the SC and SPUs processes.

• Run cat ~/.fluvio/log/flv_sc.log for SC logs
• Run cat ~/.fluvio/log/spu_log_XXXX.log for each SPU
  • E.g. when running 1 SPU, there will be spu_log_5001.log

You can also use tail -n 100 ~/.fluvio/log/flv_sc.log to just print the last 100 lines of the log file.

Getting help

You can ask for help from the Fluvio Discord group,

The logging information needed for diagnostics can be packaged up with the command fluvio cluster diagnostics. The compressed archive can be shared in the Discord group or sent via PM to Infinyon admins

Upgrading the Cluster

If you receive an error Check Versions match failed Check Versions match failed: cannot resume a x.y.z cluster with fluvio version a.b.c. This is an error that may be shown when upgrading Fluvio version of a locally deployed cluster. The fluvio cluster may need to be upgraded to the new version: see the fluvio cluster upgrade command for more information.

Log directory

By default, Fluvio logs are stored in the ~/.fluvio/log directory. But if you have the FLUVIO_DIR environment variable set, the logs will be stored in the directory specified by the variable.

Setting log level

You can set various log levels as filtering tracing log.

For example, to start cluster using log level info using cluster start

$ fluvio cluster start --rust-log=info

For individual binaries, you can use RUST_LOG env variable:

$ RUST_LOG=info fluvio run sc --local

The log level can be set to trace, debug, info, warn, error.

Producer

Max Record Size Exceeded

if you are having issues with the producer, like the error record size (35707200 bytes), exceeded maximum request size (33554432 bytes) you can increase the maximum record size by setting the max_record_size parameter in the producer command.

fluvio produce hello-node --max-request-size 37748736