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
  • Brite
  • 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. Backups exiting with code 70

Backups exiting with code 70

Scheduled Pinned Locked Moved Solved Support
backups
5 Posts 2 Posters 44 Views 2 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.
  • LanhildL Online
    LanhildL Online
    Lanhild
    App Dev
    wrote last edited by girish
    #1

    I am using the s3-v4-compat (rsync) backup target, with OVH S3's product. All my system backups exit with a code 70. It seems like backups roll on for a bit, and then exit with said code.

    The same happens with app backups, making their updates impossible unless skipping the backup for them.

    This issue happened since the upgrade from 8.3.2 to 9.0.10

    Logs

    Nov 18 23:02:06 box:taskworker Terminated
    Nov 18 23:02:06 Exiting with code 70
    

    13e3656b-35ff-45a1-b908-4b2f0bf827d6-image.png

    We can see here with the "Upload finished" lines that the backup seemingly works for a while, but then exits.

    Troubleshooting Already Performed

    None, I can't control the backup process.

    System Details

    Cloudron version
    9.0.10

    Ubuntu version
    Ubuntu 22.04.4 LTS Linux 5.15.0-161-generic

    Vendor
    DigitalOcean

    CPU
    8 Core "DO-Premium-AMD"

    Memory
    33.65 GB RAM & 1.03 GB Swap

    1 Reply Last reply
    1
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote last edited by
      #2

      @Lanhild code 70 means the task worker received a SIGTERM . This code is only sent when you click 'Stop Backup' (or stop task in general) from the UI.

      Could it be that the task runs out of memory and the OS is sending SIGTERM? (usually it gets a SIGKILL). Can you try by bumping the memory of the backup task?

      LanhildL 3 Replies Last reply
      0
      • girishG girish

        @Lanhild code 70 means the task worker received a SIGTERM . This code is only sent when you click 'Stop Backup' (or stop task in general) from the UI.

        Could it be that the task runs out of memory and the OS is sending SIGTERM? (usually it gets a SIGKILL). Can you try by bumping the memory of the backup task?

        LanhildL Online
        LanhildL Online
        Lanhild
        App Dev
        wrote last edited by Lanhild
        #3

        @girish There are no memory usage spikes coinciding with the timestamp of the error. Also, I have the same issue on another Cloudron.

        Where should I bump the memory of backup task? Trying it out.

        1 Reply Last reply
        1
        • girishG girish

          @Lanhild code 70 means the task worker received a SIGTERM . This code is only sent when you click 'Stop Backup' (or stop task in general) from the UI.

          Could it be that the task runs out of memory and the OS is sending SIGTERM? (usually it gets a SIGKILL). Can you try by bumping the memory of the backup task?

          LanhildL Online
          LanhildL Online
          Lanhild
          App Dev
          wrote last edited by
          #4

          @girish Bumped the memory from the default (?) 1GB to 4GB. Right now, it seems like an app backup worked correctly. My Cloudron has quite a lot of stuff, so an global backup takes longer. I'll report back.

          1 Reply Last reply
          1
          • girishG girish

            @Lanhild code 70 means the task worker received a SIGTERM . This code is only sent when you click 'Stop Backup' (or stop task in general) from the UI.

            Could it be that the task runs out of memory and the OS is sending SIGTERM? (usually it gets a SIGKILL). Can you try by bumping the memory of the backup task?

            LanhildL Online
            LanhildL Online
            Lanhild
            App Dev
            wrote last edited by
            #5

            @girish Increasing the task memory did it. Issue solved.

            1 Reply Last reply
            1
            • jamesJ james has marked this topic as solved
            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