Startup errors (and most debug logging, really) should go to stderr, not stdout

[wyardley]

I'm having some issues with starting Kibana 4.1.1, described here:
https://discuss.elastic.co/t/kibana-4-1-1-not-starting/40425/4
I realize this is not the place for help with resolving the error, however, in the process of debugging it, I noticed that the startup logs are split between kibana.stderr and kibana.stdout, however, the following error (incorrectly, I believe) is going to the stdout file, and to stdout when Kibana is started in the foreground.

# /opt/kibana/bin/kibana 2> /dev/null {"name":"Kibana","hostname":"xxxx","pid":18260,"level":50,"err":{"message":"unknown error","name":"Error","stack":"Error: unknown error\n at respond (/opt/kibana/src/node_modules/elasticsearch/src/lib/transport.js:237:15)\n at checkRespForFailure (/opt/kibana/src/node_modules/elasticsearch/src/lib/transport.js:203:7)\n at HttpConnector.<anonymous> (/opt/kibana/src/node_modules/elasticsearch/src/lib/connectors/http.js:156:7)\n at IncomingMessage.bound (/opt/kibana/src/node_modules/elasticsearch/node_modules/lodash-node/modern/internals/baseBind.js:56:17)\n at IncomingMessage.emit (events.js:117:20)\n at _stream_readable.js:944:16\n at process._tickCallback (node.js:442:13)"},"msg":"","time":"2016-01-29T17:54:17.793Z","v":0} {"name":"Kibana","hostname":"xxxx","pid":18260,"level":60,"err":{"message":"unknown error","name":"Error","stack":"Error: unknown error\n at respond (/opt/kibana/src/node_modules/elasticsearch/src/lib/transport.js:237:15)\n at checkRespForFailure (/opt/kibana/src/node_modules/elasticsearch/src/lib/transport.js:203:7)\n at HttpConnector.<anonymous> (/opt/kibana/src/node_modules/elasticsearch/src/lib/connectors/http.js:156:7)\n at IncomingMessage.bound (/opt/kibana/src/node_modules/elasticsearch/node_modules/lodash-node/modern/internals/baseBind.js:56:17)\n at IncomingMessage.emit (events.js:117:20)\n at _stream_readable.js:944:16\n at process._tickCallback (node.js:442:13)"},"msg":"","time":"2016-01-29T17:54:17.794Z","v":0}

[wyardley]

Not sure if it's been addressed in a newer version (though would love to see RPMs, hint, hint), but the error message is also not particularly helpful here. I can open a separate ticket or provide debugging output if that's something that someone could look at too.

[wyardley]

ps - the root cause seems to be incompatibility issue. Given that these are all tools produced by the same organization, it would be nice if there was a more useful error if there's a version incompatibility, though.

[tylersmalley]

This issue is pretty old, and we have greatly improved logging since the creation of this issue. If anyone sees current examples for areas of improvement please open a new issue. Thanks.