Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. [Graphite] [tagdb] Error tagging collectd

[Graphite] [tagdb] Error tagging collectd

Scheduled Pinned Locked Moved Solved Support
6 Posts 3 Posters 1.2k Views 4 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • rmdesR Offline
    rmdesR Offline
    rmdes
    wrote on last edited by
    #1

    Since last cloudron upgrade I'm having two types of error in my Graphite log :

    1. python 3 error
    2. Graphite tagging error

    here is a snapshot : https://paste.armada.digital/tumovehuhu.sql
    i don't know if the two errors are related, but my graphite log is now 200MB of the same errors, over and over again

    Not sure what I can do from my side to fix this, any help ?

    nebulonN 1 Reply Last reply
    1
    • rmdesR rmdes

      Since last cloudron upgrade I'm having two types of error in my Graphite log :

      1. python 3 error
      2. Graphite tagging error

      here is a snapshot : https://paste.armada.digital/tumovehuhu.sql
      i don't know if the two errors are related, but my graphite log is now 200MB of the same errors, over and over again

      Not sure what I can do from my side to fix this, any help ?

      nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #2

      @rmdes not easy to tell from those logs, but maybe you hit a simliar issue with the graphite store as https://forum.cloudron.io/topic/4671/graphite-stuck-starting/5 if you want you could also try that workaround.

      rmdesR 1 Reply Last reply
      0
      • nebulonN nebulon

        @rmdes not easy to tell from those logs, but maybe you hit a simliar issue with the graphite store as https://forum.cloudron.io/topic/4671/graphite-stuck-starting/5 if you want you could also try that workaround.

        rmdesR Offline
        rmdesR Offline
        rmdes
        wrote on last edited by rmdes
        #3

        @nebulon I applied the suggestion but it does not change anything, errors keep being generated every few seconds, here is the log just after rebooting Graphite

        https://paste.armada.digital/azokimesux.sql

        besides, all services are running
        9db47ee5-79e6-4048-9c9e-d70fc553551d-image.png

        girishG 1 Reply Last reply
        0
        • rmdesR rmdes

          @nebulon I applied the suggestion but it does not change anything, errors keep being generated every few seconds, here is the log just after rebooting Graphite

          https://paste.armada.digital/azokimesux.sql

          besides, all services are running
          9db47ee5-79e6-4048-9c9e-d70fc553551d-image.png

          girishG Do not disturb
          girishG Do not disturb
          girish
          Staff
          wrote on last edited by
          #4

          @rmdes I am able to reproduce this. Working on a fix.

          1 Reply Last reply
          2
          • girishG Do not disturb
            girishG Do not disturb
            girish
            Staff
            wrote on last edited by
            #5

            This is fixed for the next release.

            Technical note... Recent releases of graphite/carbon (which we got automatically when we moved to the ubuntu 20 base image) have a feature to tag data. In previous releases, you have to create hierarchies of metrics. For example, cpu.datacenter1.rack1, cpu.datacenter1.rack2 and so on. These hierarchies can be unwieldy. Instead now, we can have metrics "cpu" but with a tag like dc=datacenter1,rack=rack2. And these tags can then be used in the query language. Very cool feature, might come in handy when we go multi-host. But for now, we can disable it altogether.

            rmdesR 1 Reply Last reply
            1
            • girishG girish

              This is fixed for the next release.

              Technical note... Recent releases of graphite/carbon (which we got automatically when we moved to the ubuntu 20 base image) have a feature to tag data. In previous releases, you have to create hierarchies of metrics. For example, cpu.datacenter1.rack1, cpu.datacenter1.rack2 and so on. These hierarchies can be unwieldy. Instead now, we can have metrics "cpu" but with a tag like dc=datacenter1,rack=rack2. And these tags can then be used in the query language. Very cool feature, might come in handy when we go multi-host. But for now, we can disable it altogether.

              rmdesR Offline
              rmdesR Offline
              rmdes
              wrote on last edited by
              #6

              @girish yay, thanks for the explanation !

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Bookmarks
              • Search