-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging not working #108
Comments
I found the problem. When the default service_file is used, the log4j.properties file is used (as it should do). When I set this parameter in my hiera yaml:
The service file is managed by this module and all king of parameters are added as a startup parameter which are also in log4j.properties. But then is does work. I still think the log location should be properly set in log4j.properties. Why else use that file if you're going to override the |
Thanks for the report. It should be fixed in v0.7.5 release. |
The logfile of Zookeeper is not being written.
In my /var/log/messages i get this:
In the log4j.properties, the
zookeeper.log.dir
is set to.
So
./zookeeper.log
is legit.In
/etc/zookeeper/java.env
this is set as the logdir:ZOO_LOG_DIR=/var/log/zookeeper
but zookeeper seems to ignore this.When I change the log4j template on my puppetmaster from this:
to this
It works fine.
I use a Satellite with zookeeper 3.4.10 compiled from source using this spec file: spec-file
The text was updated successfully, but these errors were encountered: