This comes up after a few lines have been sent to the log file, after logstash starts up and events start flowing in.
Pretty sure this was fixed before the 1.2.0 release (I was able to use --log)