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. Backup Task Crashing - Signal SIGABRT Error

Backup Task Crashing - Signal SIGABRT Error

Scheduled Pinned Locked Moved Solved Support
3 Posts 2 Posters 311 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.
    • F Offline
      F Offline
      Felipe.rubilar
      wrote on last edited by Felipe.rubilar
      #1

      Dear Cloudron Support Team,

      I am experiencing a recurring issue with the backup tasks on my Cloudron instance. The backup task for the mail application is consistently crashing, and I am unable to determine the cause or find a solution.

      Details:

      • Error Log Excerpt:
        2024-07-23T09:11:39.794Z box:shell backup-snapshot/mail: /usr/bin/sudo -S -E --close-from=4 /home/yellowtent/box/src/scripts/backupupload.js snapshot/mail tgz {"localRoot":"/home/yellowtent/boxdata/mail","layout":[]} errored BoxError: backup-snapshot/mail exited with code null signal SIGABRT
        2024-07-23T09:11:40.020Z box:taskworker Task took 11497.389 seconds
        2024-07-23T09:11:40.032Z box:tasks setCompleted - 11410: {"result":null,"error":{"stack":"BoxError: Backuptask crashed\n    at runBackupUpload (/home/yellowtent/box/src/backuptask.js:163:15)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async uploadMailSnapshot (/home/yellowtent/box/src/backuptask.js:404:5)\n    at async backupMailWithTag (/home/yellowtent/box/src/backuptask.js:452:5)\n    at async fullBackup (/home/yellowtent/box/src/backuptask.js:510:26)","name":"BoxError","reason":"Internal Error","details":{},"message":"Backuptask crashed"}}
        

      Current Configuration:

      • Memory Limit: 2 GiB
      • Upload Part Size: 128 MiB

      Issue:

      I have not made any changes to the default configuration settings. The backup process crashes with a SIGABRT signal, indicating a critical error that the process could not handle.

      Request:

      Could you please assist me in diagnosing and resolving this issue? I would like to know the specific changes or configurations I should apply to prevent this problem from recurring and to ensure the stability of my Cloudron instance.

      Thank you for your support.

      Best regards

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

        Can you check the system logs for around the time-frame when a backup crashes for indications if the system ran out of memory? There was another issue when SIGABRT was triggered https://forum.cloudron.io/topic/1720/backup-fails-task-475-crashed-with-code-null-and-signal-sigabrt which was also memory related.

        1 Reply Last reply
        0
        • F Offline
          F Offline
          Felipe.rubilar
          wrote on last edited by Felipe.rubilar
          #3

          Hi Nebulon,
          Thank you for your assistance regarding the backup issue for the mail application. Based on your suggestion and the error logs, I have decided to increase the memory limit for the backup process to 4.5 GiB.

          Here is the updated configuration:

          Memory Limit: 4.5 GiB
          Upload Part Size: 128 MiB

          I will monitor the backup process after this change to see if it resolves the issue. I have attached a screenshot of the updated settings for your reference.

          If the problem persists, I will provide additional logs and system metrics for further analysis.

          Thank you for your support.

          Best regards,
          Felipe Rubilar

          1 Reply Last reply
          0
          • J joseph marked this topic as a question on
          • J joseph has marked this topic as solved on
          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