On Thu, 19 Sep 2019 05:25:25 +0000 René Romijn Rene.Romijn@tabsholland.nl wrote:
Also i changed the /etc/carbon/carbon.conf. i changed the value ENABLE_TAGS to False. I am not realy sure what the function is doing, but the 'tagging' resulted in a lot of logging in the /var/log/carbon/tagdb.log
Graphite 1.1 introduced tagging support (which I have not used thus far). The TagDB is an SQL database managed by graphite-web, so it seems carbon-cache needs to know graphite-web's URL to send tag information to it.
I don't think the virtual appliance configures this URL, so carbon-cache will try to post tag data to a non-existent location.
So, everything seems to be working fine now 😊 running on the latest.
Glad to hear it! Please do consider bumping the Debian issue, though; anything that prods the package maintainer to make a more permanent solution would be helpful :)