Zdenek Crha created MESOS-3229:
----------------------------------
Summary: Error logged through EXIT(1) << is missing from logs
Key: MESOS-3229
URL: https://issues.apache.org/jira/browse/MESOS-3229
Project: Mesos
Issue Type: Bug
Affects Versions: 0.22.1
Environment: debian wheezy amd64
deb mesos 0.22.1-1.0.debian78
Reporter: Zdenek Crha
Priority: Minor
When process exits using EXIT(1) << "log message" call, log message is
displayed into console, but never make it into log files in /var/log/mesos.
The message is redirected into syslog by mesos-init-wrapper and can be seen
there. But /var/log/mesos is first place to look when debugging and missing
error can lead to some heavy head scratching.
Reproduction Steps
* Have mesos slave configured to use docker as containerizer.
* Stop mesos slave
* Stop docker daemon
* Attempt to start mesos-slave through init script
* Process should stop with message: _"Failed to create a containerizer: Could
not create DockerContainerizer: Failed to execute 'docker version': exited with
status 1"_
Expected result:
* mesos-slave service is not running
* there is mesos-slave.ERROR file in /var/log/mesos with error message
Actual result:
* mesos-slave service is not running
* error message on console got swallowed by init script
* there is no mesos-slave.ERROR file in /var/log/mesos
* reason for mesos-slave service stop can't be found in any log in
/var/log/mesos
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
