** Description changed: + == SRU Justifcation == + + === Impact === + This bug can cause juju's local provider to fill up the local disk very rapidly after a reboot. + + === Test Case === + 1. Create a local environment in ~/.juju/environments.yaml, something like this: + + environments: + local: + type: local + data-dir: /home/myuser/.juju/data + default-series: precise + + 2. juju bootstrap + 3. reboot the machine + 4. check /home/myuser/.juju/data/myuser-local/machine-agent.log .. if it is streaming errors, the system is affected. + 5. juju destroy-environment + 6. update the package + 7. repeat steps 1 - 4. If the logs are no longer streaming, the bug is fixed. + + === Dev Fix === + + This is fixed in upstream commit 533 by suppressing the logs from + libzookeeper. + + === Regression Potential === + Very low, this simply suppresses the logs that come streaming out of libzookeeper, and they are not useful in most cases. This does mean that in the rare cases where client error logs would be useful, they are suppressed. + + == Original Bug Description == + The verbosity and frequency of the zookeeper log is considerable, use a pipe and filter on level and rate. Lacking this its possible for the log - to fill up the disks on the machine for a disconnected agent, happened + to fill up the disks on the machine for a disconnected agent, happeneRd to me on local provider, ugh. Just to be clear this on the client connection logging, not the server.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/958312 Title: Change zk logging configuration To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/958312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
