Hide Forgot
Description of problem: The netdata rpm spec seems to be based on a old version which is quite different than the upstream one here https://raw.githubusercontent.com/netdata/netdata/master/netdata.spec.in . Upstream version 1.18.1 now uses dbengine as the default memory mode, a feature which is not enabled at all in the epel package. Could this rpm spec be updated to better reflect the default functionality of the upstream packages? Version-Release number of selected component (if applicable): 1.18.1 How reproducible: install package. Edit /etc/netdata/netdata.conf and add the `memory mode = dbengine` line under `[global]` Steps to Reproduce: 1. install package. 2. Edit /etc/netdata/netdata.conf and add the `memory mode = dbengine` line under `[global]` 3. restart netdata service Actual results: Logs show `netdata FATAL : MAIN :RRD_MEMORY_MODE_DBENGINE is not supported in this platform. # : No such file or directory` Expected results: netdata is enabled with dbengine backend. Additional info: Tested using 1.18.1 currently in epel-testing
dbengine cannot be enabled in epel8 for now because of missing dependencies. Some needed packages are not yet available: libuv-devel and Judy-devel. I'm waiting (a little) before apply this modifications to all branches. If you cannot wait, I built it with dbengine enabled in my copr: https://copr.fedorainfracloud.org/coprs/tartare/netdata/build/1081316/ for all fedora releases and epel6 and 7 (where I need to add an exception for epel8, which is not wanted for stable packages).
Ah makes sense, thanks for the explanation. You're right there are a bunch of -devel packages missing among others after a quick glance. I will make use of the copr repo for now.
Blocked by: Judy-devel: https://bugzilla.redhat.com/show_bug.cgi?id=1767122 libuv-devel: https://bugzilla.redhat.com/show_bug.cgi?id=1767123
Depends on epel issues: * Judy-devel: https://pagure.io/epel/issue/92 * libuv-devel: https://pagure.io/epel/issue/64
FEDORA-2020-aeb3b29305 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-aeb3b29305
FEDORA-2020-4d87a62071 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4d87a62071
FEDORA-2020-c807d02b1f has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c807d02b1f
FEDORA-EPEL-2020-c3fca161ee has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c3fca161ee
FEDORA-EPEL-2020-ff11142989 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ff11142989
FEDORA-2020-aeb3b29305 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-aeb3b29305` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-aeb3b29305 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-c807d02b1f has been pushed to the Fedora 30 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c807d02b1f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c807d02b1f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-4d87a62071 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-4d87a62071` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4d87a62071 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-c3fca161ee has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-c3fca161ee See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-ff11142989 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ff11142989 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-aeb3b29305 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-c807d02b1f has been pushed to the Fedora 30 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-4d87a62071 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-c3fca161ee has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-ff11142989 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.