Closed rmoff closed 6 years ago
Currently start_service
writes stdout
and stderr
to separate files:
${start_command} "${service_dir}/${service}.properties" \
2> "${service_dir}/${service}.stderr" \
1> "${service_dir}/${service}.stdout" &
But confluent log
only exposes the stdout
file
local service_log="${service_dir}/${service}.stdout"
[...]
less "$service_log"
So either the stderr
should be exposed another way (back to the user who invoked the confluent
command), or stderr and stdout should be routed to the same log file.
Consolidation of stderr with stdout to a single logfile was merged and backported.
Connect fails to start, but with
confluent log connect
the stacktrace & error is missed, making it appear that it's just hung.With Confluent CLI:
Run directly