Hello,
This is possibly a bug: I discovered that logstash.err log file starts with an array of zero bytes, which makes it hard (but not impossible) to read by text viewers. I use LogStash 2.2.2.
> file logstash.err
logstash.err: data
> hexdump -C logstash.err
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00006650 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4d 61 |..............Ma|
00006660 72 20 30 37 2c 20 32 30 31 36 20 31 32 3a 31 37 |r 07, 2016 12:17|
00006670 3a 32 37 20 41 4d 20 6f 72 67 2e 61 70 61 63 68 |:27 AM org.apach|
00006680 65 2e 68 74 74 70 2e 69 6d 70 6c 2e 65 78 65 63 |e.http.impl.exec|
00006690 63 68 61 69 6e 2e 52 65 74 72 79 45 78 65 63 20 |chain.RetryExec |
000066a0 65 78 65 63 75 74 65 0a 49 4e 46 4f 3a 20 49 2f |execute.INFO: I/|
000066b0 4f 20 65 78 63 65 70 74 69 6f 6e 20 28 6a 61 76 |O exception (jav|
000066c0 61 2e 6e 65 74 2e 53 6f 63 6b 65 74 45 78 63 65 |a.net.SocketExce|
000066d0 70 74 69 6f 6e 29 20 63 61 75 67 68 74 20 77 68 |ption) caught wh|
000066e0 65 6e 20 70 72 6f 63 65 73 73 69 6e 67 20 72 65 |en processing re|
000066f0 71 75 65 73 74 20 74 6f 20 7b 7d 2d 3e 68 74 74 |quest to {}->htt|
...
MG