"stopping server" logs not always visible #663
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
when invoking
/etc/init.d/influxdb stop
, all messages from https://github.com/influxdb/influxdb/blob/ffbe9be48a00e3e8361af0180b9237f05bb5d0a1/src/server/server.go#L212-242should appear in the log, but this doesn't seem the case.
i suspect this is a race, the
log.Info()
's are probably called correctly but the server exits before the records get written to the log.I made sure to edit influxdb-daemon and to redirect all stderr/stdout to a file, so that if it panics, i would see it there (see #650), but the daemon records no stdout/stderr, implying a clean exit.
all the snippets below are the tail of a log, after calling
/etc/init.d/influxdb stop
and confirming the process is no longer running. It seems pretty arbitrary how much of the log messages make it into the log.