Comment 5 for bug 467179

Funny that it doesn't happen again. Perhaps there was some other process running that confused openttd in some way, or something else was different in your environment? If you manage to reproduce it again, let us know. If not, I'll probably close this report soon.

The debug output generated by openttd -d 4 is generated on stderr (not stdout), so use 2> log.txt to redirect.