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


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Unsolved Backup failed "crashed/stopped"

    Support
    backups
    3
    5
    220
    Loading More Posts
    • 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.
    • gobenizzle
      gobenizzle last edited by girish

      yeah I got the hint with the full disk 🙂
      Thank you for pointing me to the right FAQ section... This helped!

      Now I am running into a new Problem.
      Under the backup section of the cloudron settings I see the following error message:

      "Cloudron crashed/stopped"
      I2443126f-c1ba-48da-bcb3-813b3c7bd059-image.png

      I tried increasing memory size for graphite. Any ideas what could be the issue?

      girish 1 Reply Last reply Reply Quote 0
      • Topic has been marked as a question  nebulon nebulon 
      • nebulon
        nebulon Staff last edited by

        Have you tried to trigger a new backup? Maybe this error is just some leftover from a backup attempt while the disk was full.

        If a new attempt also does not work, do you see anything in the system or backup logs?

        gobenizzle 1 Reply Last reply Reply Quote 0
        • gobenizzle
          gobenizzle @nebulon last edited by

          @nebulon I tried backups up to 2 months back....

          nebulon 1 Reply Last reply Reply Quote 0
          • nebulon
            nebulon Staff @gobenizzle last edited by

            @gobenizzle not sure what that means in that context. Are you saying you tried to backup for 2 months already without success?

            What is your backup storage backend and do you see any backup errors which might give any hint on whats failing?

            1 Reply Last reply Reply Quote 0
            • girish
              girish Staff @gobenizzle last edited by

              @gobenizzle This only means that the backup task was "interrupted" when a backup was in progress. The code assumes that if a backup got arbitrary interrupted (i.e not via the stop button), it is because the box code crashed. That assumption is true most of the time but you probably ran out of disk space and rebooted etc which killed the backup task.

              Nothing to worry. If you trigger a new backup, it will go away.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Powered by NodeBB