Description of problem: In this build of collectd, we cannot use the "SecurityLevel" and "AuthFile" directives in network configuration, as collectd network plugin seems to have been built without libgcrypt. If it's possible, I'd like collectd to be built with cryptographic support - it does add a dependency to libgcrypt. Version-Release number of selected component (if applicable): collectd-4.10.2-1.el5 How reproducible: Always Steps to Reproduce: 1. Setup a network block that way : <Plugin "network"> <Listen "127.0.0.1"> SecurityLevel "None" AuthFile "/etc/collectd/auth_file" </Listen> </Plugin> (Also, you should have a log file set up with at least the warning level) 2. Restart your collectd daemon. Actual results: [2011-02-08 18:59:58] [warning] network plugin: Option `SecurityLevel' is not allowed here. [2011-02-08 18:59:58] [warning] network plugin: Option `AuthFile' is not allowed here. (And, of course, the encryption support is not active) Expected results: No warning should be displayed. Encryption support should work. Additional info:
The same apply to collectd for el6.
collectd-4.10.3-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/collectd-4.10.3-1.el6
collectd-4.10.3-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/collectd-4.10.3-1.el5
Package collectd-4.10.3-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing collectd-4.10.3-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/collectd-4.10.3-1.el6 then log in and leave karma (feedback).
collectd-4.10.3-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
collectd-4.10.3-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.