You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
currently, any error that happens in influxdb ( daemon) that goes into stdout or stderr, gets lost because scripts/influxdb-daemon.sh, wraps it and sends all stdout and stderr to /dev/null.
there was probably a reason for this, see d40ed03 I wonder why this change was made ( @jvshahid ?)
but i'm thinking we should probably track those streams into a logfile.
Some things can't be logged by the process and appear on stdout/stderr, such as panics.
The text was updated successfully, but these errors were encountered:
+1 on this one. I just had to troubleshoot something that would have taken me seconds to track down if we were capturing process panics that kill things.
Hi,
currently, any error that happens in
influxdb
(daemon
) that goes into stdout or stderr, gets lost becausescripts/influxdb-daemon.sh
, wraps it and sends all stdout and stderr to /dev/null.there was probably a reason for this, see d40ed03 I wonder why this change was made ( @jvshahid ?)
but i'm thinking we should probably track those streams into a logfile.
Some things can't be logged by the process and appear on stdout/stderr, such as panics.
The text was updated successfully, but these errors were encountered: