Comment 1 for bug 871596

I also tried starting a Librarian manually, with “bin/start_librarian.” That starts up happily, without any weirdness in the blog. I suppose things only start getting weird at the time of first use. It's not technically impossible though that those null bytes are just sitting in a buffer somewhere waiting to be flushed by the first error message.