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. "socket hang up" when trying to display Memory Graph in Dashboard, no graphs displayed

"socket hang up" when trying to display Memory Graph in Dashboard, no graphs displayed

Scheduled Pinned Locked Moved Solved Support
8 Posts 3 Posters 1.2k 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.
    • scookeS Offline
      scookeS Offline
      scooke
      wrote on last edited by
      #1

      Why would this happen? I have a VPS with 16 GB of RAM!

      Is it because ssdnodes uses the XFS file system, and not ext4? Remember, the only way I could get Cloudron to install was to comment out the check for ext4 in the install script.

      This is just one of a few issues that really bug me, and I wish I knew if it was something to do with XFS or something entirely different. I mean, 16 GB.... why would there be any problems running cloudron????

      Thank you for looking into this.

      ![alt text](Screenshot 2019-03-19 20.55.21.png image url)

      A life lived in fear is a life half-lived

      1 Reply Last reply
      0
      • subvenS Offline
        subvenS Offline
        subven
        wrote on last edited by subven
        #2

        Take a look at docker stats graphite

        CONTAINER ID        NAME                CPU %               MEM USAGE / LIMIT   MEM %            NET I/O             BLOCK I/O           PIDS
        c83fb2b97d77        graphite            0.09%               83.45MiB / 512MiB   16.30%              28.3MB / 821kB      0B / 0B             6
        

        I gave the container more RAM and the problem never occurred for me again. Standard setting is 75MiB with is not enough.

        Note to @girish and @nebulon: It would be cool if we could change RAM for box, graphite and especially redis from the UI. 🙂

        scookeS 1 Reply Last reply
        0
        • subvenS subven

          Take a look at docker stats graphite

          CONTAINER ID        NAME                CPU %               MEM USAGE / LIMIT   MEM %            NET I/O             BLOCK I/O           PIDS
          c83fb2b97d77        graphite            0.09%               83.45MiB / 512MiB   16.30%              28.3MB / 821kB      0B / 0B             6
          

          I gave the container more RAM and the problem never occurred for me again. Standard setting is 75MiB with is not enough.

          Note to @girish and @nebulon: It would be cool if we could change RAM for box, graphite and especially redis from the UI. 🙂

          scookeS Offline
          scookeS Offline
          scooke
          wrote on last edited by scooke
          #3

          @subven said in "socket hang up" when trying to display Memory Graph in Dashboard, no graphs displayed:

          docker stats graphite

          Thank you for sharing this info. I see that my MEM USAGE was 72.6 / 75 MB limit, so that would indicate why it crashes. How do I increase the limit then?

          A life lived in fear is a life half-lived

          subvenS 1 Reply Last reply
          0
          • scookeS scooke

            @subven said in "socket hang up" when trying to display Memory Graph in Dashboard, no graphs displayed:

            docker stats graphite

            Thank you for sharing this info. I see that my MEM USAGE was 72.6 / 75 MB limit, so that would indicate why it crashes. How do I increase the limit then?

            subvenS Offline
            subvenS Offline
            subven
            wrote on last edited by
            #4

            @scooke I did it with:

            docker update --memory "256mb" --memory-swap "1g" graphite
            

            but thats the very dirty way.

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

              Whoops, didn't realize that graphite is actually not listed under services. Will add that for the next release.

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

                This is now added for 3.6

                1 Reply Last reply
                1
                • subvenS subven

                  @scooke I did it with:

                  docker update --memory "256mb" --memory-swap "1g" graphite
                  

                  but thats the very dirty way.

                  scookeS Offline
                  scookeS Offline
                  scooke
                  wrote on last edited by
                  #7

                  @subven said in "socket hang up" when trying to display Memory Graph in Dashboard, no graphs displayed:

                  docker update --memory "256mb" --memory-swap "1g" graphite

                  There is no need to restart anything after that?
                  Thank you so much to the help!

                  A life lived in fear is a life half-lived

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

                    Yes, there is no need to restart after that.

                    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