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 service is infinitely starting

Graphite service is infinitely starting

Scheduled Pinned Locked Moved Solved Support
graphite
5 Posts 3 Posters 1.0k Views 3 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.
  • JOduMonTJ Offline
    JOduMonTJ Offline
    JOduMonT
    wrote on last edited by girish
    #1

    and this error is recurrently in the log

    Jun 08 20:48:13 08/06/2020 13:48:13 :: [console] /etc/carbon/storage-aggregation.conf not found or wrong perms, ignoring.
    Jun 08 20:49:13 08/06/2020 13:49:13 :: [console] /etc/carbon/storage-aggregation.conf not found or wrong perms, ignoring.
    

    What is graphite and how could I trouble shoot this ?

    1 Reply Last reply
    0
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #2

      I don't think that warning is causing the container to restart. Can you maybe increase the memory of that service and see if that is causing the restarts?

      JOduMonTJ 1 Reply Last reply
      1
      • nebulonN nebulon

        I don't think that warning is causing the container to restart. Can you maybe increase the memory of that service and see if that is causing the restarts?

        JOduMonTJ Offline
        JOduMonTJ Offline
        JOduMonT
        wrote on last edited by
        #3

        @nebulon wow and thank for the rapidity 😉

        I passed from 150 to 256 and it work now

        FYI

        free -m

        total        used        free      shared  buff/cache   available
        Mem:           3919        1752         788         128        1378        1740
        Swap:          3918         411        3507
        

        ps aux|grep graph

        lxd       4307  0.0  0.2 143488  8420 ?        S    13:31   0:01 uwsgi --master --workers 2 --buffer-size 16384 --no-orphans --ini /etc/uwsgi/apps-enabled/graphite-uwsgi.ini
        lxd       4639  0.0  0.9 494984 37668 ?        Sl   13:31   0:01 uwsgi --master --workers 2 --buffer-size 16384 --no-orphans --ini /etc/uwsgi/apps-enabled/graphite-uwsgi.ini
        lxd       4640  0.0  0.6 494940 24280 ?        Sl   13:31   0:00 uwsgi --master --workers 2 --buffer-size 16384 --no-orphans --ini /etc/uwsgi/apps-enabled/graphite-uwsgi.ini
        
        1 Reply Last reply
        0
        • nebulonN Offline
          nebulonN Offline
          nebulon
          Staff
          wrote on last edited by
          #4

          Not sure why you didn't receive any out-of-memory notifications for that container in such a case.

          1 Reply Last reply
          0
          • girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #5

            The permission error can be ignored.

            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