http://bugzilla.suse.com/show_bug.cgi?id=1111012 http://bugzilla.suse.com/show_bug.cgi?id=1111012#c4 --- Comment #4 from Richard Brown <rbrown@suse.com> --- (In reply to Valentin Rothberg from comment #3)
Looks like, yes. The conf manpage was quite outdated, so it seems likely that this option was forgotten. Let's check if it works with --log (and setting it in crio.conf) and open a PR upstream.
--log works when set to a full filepath. It produces a fatal error if set to a directory. However, the contents of that log seems to have no relation to the contents of the logs produced by crio in /tmp. --log seems to record notices you'd typically expect in a journal, eg "error updating cni config: Missing CNI default network" with journal style timestamps The logs in /tmp have a very different format, with a header that includes "Log file created at:... Running on machine: ... Binary: Built with gc go1.10.3 for linux/amd64 Log line format: ...." and THEN log errors, which seem to be go specific error messages, eg. "hostport_manager.go:64] The binary conntrack is not installed, this can cause failures in network connection cleanup" Therefore I'm convinced that --log has no impact on the logs this bug is related to We need to find a way of getting those logs from /tmp into somewhere more sensible. log= in crio.conf seems to have zero effect if set to a full filepath or to a directory -- You are receiving this mail because: You are on the CC list for the bug.