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. Bug in app-backup > app-import > Cloudron SSHFS backup connection: LOST!

Bug in app-backup > app-import > Cloudron SSHFS backup connection: LOST!

Scheduled Pinned Locked Moved Unsolved Support
8 Posts 2 Posters 93 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.
  • imc67I Offline
    imc67I Offline
    imc67
    translator
    wrote last edited by imc67
    #1

    Description

    In this issue (https://forum.cloudron.io/post/114808) I noticed that after I back upped an app (export json) and imported it on another domain (import json), the SSHFS backup location lost its connection (red dot and errors when trying to backup)

    Logs

    App log when trying to make an app-backup after app-backup>app-import. At this point the Backups Location had a RED dot đź”´

    "success": false,
      "errorMessage": "SSH connection error: ssh exited with code 255 signal null",
      "backupId": null
    

    Troubleshooting Already Performed

    Only way to make it work again is to enter the private key again in the backup location config and save it.

    Cloudron Version

    8.3.2
    

    Ubuntu Version

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

      Since this is a linux mountpoint, do you see anything around that timestamp in the journalctl --system logs on the server?

      Also did the "Remount Storage" button on the backups page not work?

      1 Reply Last reply
      0
      • imc67I Offline
        imc67I Offline
        imc67
        translator
        wrote last edited by
        #3

        somehow I can't find the right moment in the that log list, it seems only to be a few hours old

        No, the "Remount Storage" button did not work, was the first thing I tried. Only adding the private key and save it worked.

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

          Are you able to reproduce this somehow? Otherwise without further logs from the system/kernel itself, I don't think we can do much, but keep this logged for the future here.

          1 Reply Last reply
          0
          • imc67I Offline
            imc67I Offline
            imc67
            translator
            wrote last edited by
            #5

            It was easy to reproduce, but again journalctl is grrrr.

            this was I guess around the backup import:

            Nov 04 08:31:37 **REDACTED** systemd[1]: Mounting appimport-5d7106db-a620-42ee-b9b0-fa045c371815...
            Nov 04 08:31:37 **REDACTED** systemd[1]: Starting Daily apt download activities...
            Nov 04 08:31:37 **REDACTED** systemd-udevd[495]: Network interface NamePolicy= disabled on kernel command line, ignoring.
            Nov 04 08:31:37 **REDACTED** systemd[1]: Mounted appimport-5d7106db-a620-42ee-b9b0-fa045c371815.
            Nov 04 08:31:37 **REDACTED** sudo[569371]: pam_unix(sudo:session): session closed for user root
            ---
            Nov 04 08:31:47 **REDACTED** systemd[1]: Unmounting appimport-5d7106db-a620-42ee-b9b0-fa045c371815...
            Nov 04 08:31:47 **REDACTED** syslog.js[747]: 2025-11-04T08:31:47.564Z syslog:server Unable to parse: <30>1 2025-11-04T08:31:47Z **REDACTED** mongodb 963 mongodb - {"t":{"$d…:1762245107,"t
            Nov 04 08:31:47 **REDACTED** syslog.js[747]: 2025-11-04T08:31:47.578Z syslog:server Unable to parse: <30>1 2025-11-04T08:31:47Z **REDACTED** mongodb 963 mongodb - {"t":{"$d…duration":60}}
            Nov 04 08:31:47 **REDACTED** systemd[1]: mnt-appimport\x2d5d7106db\x2da620\x2d42ee\x2db9b0\x2dfa045c371815.mount: Deactivated successfully.
            Nov 04 08:31:47 **REDACTED** systemd[1]: Unmounted appimport-5d7106db-a620-42ee-b9b0-fa045c371815.
            
            

            And this around the error when trying to backup the app

            Nov 04 08:32:00 **REDACTED** containerd[758]: time="2025-11-04T08:32:00.104454346Z" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.cont…inerd.event.v1
            Nov 04 08:32:00 **REDACTED** containerd[758]: time="2025-11-04T08:32:00.104545753Z" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.co…rd.internal.v1
            Nov 04 08:32:00 **REDACTED** containerd[758]: time="2025-11-04T08:32:00.104564047Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.container…inerd.ttrpc.v1
            Nov 04 08:32:00 **REDACTED** containerd[758]: time="2025-11-04T08:32:00.104739185Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.pause\"..." runtime=io.containe…inerd.ttrpc.v1
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.110Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 013c8bbf-aad9-4dca-9c9f-1171bd7…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.131Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 1cdb3baa-2e40-4534-8359-f352d18…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.146Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** aa0b978a-6f43-4f9a-a729-6ad7143…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.153Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 8f6214da-37b9-4ccc-8c79-c4f1ebc…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.155Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 8d9e6d16-8ce0-49b5-a999-321e463…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.155Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 34504d40-cc51-4eba-a872-7e0d5fb…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.157Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** ffc9deab-bf4e-46db-b522-a582b99…TTP/1.1" 302 -
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.162Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 5d7106db-a620-42ee-b9b0-fa045c3…TTP/1.1" 302 -
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.170Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 3028ad69-1c5f-44c7-ae4c-f61a3f1…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.176Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** c9549dd5-75f0-489e-a713-aa394a6…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.181Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 941004d9-1b1b-4a4d-9e77-1db6f05…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.188Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** cbf1e7d7-288d-4f99-863f-55f50e4…ET /" 200 46ms
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.191Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** cbf1e7d7-288d-4f99-863f-55f50e4…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.191Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 72a8f512-45c2-4410-ae6f-8affc84…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.196Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 5d7106db-a620-42ee-b9b0-fa045c371815 963 5d71…
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.207Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 460bd50a-e043-4a78-9555-14e29f4…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.211Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** a80f822d-5c39-4148-bbcc-4d4801d…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.215Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 77d6c795-349b-435e-8306-ac08bcf…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.226Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** e34e6f37-ea96-4883-8176-0410b56…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.264Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.269Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** dc938853-f3ca-47b8-b3ea-2661825…oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: <30>1 2025-11-04T08:32:00Z **REDACTED** dc938853-f3ca-47b8-b3ea-2661825b7932 963 dc938853-f3ca-47b8-b3ea-2661825b7932 - - - - […oudronHealth)"
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.372Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 5d7106db-a620-42ee-b9b0-fa045c371815 963 5d71…
            Nov 04 08:32:00 **REDACTED** kernel: Packet dropped: IN=eth0 OUT= MAC=4a:ba:07:45:61:f0:bc:0f:fe:37:fb:a3:08:00 SRC=207.90.244.18 DST=**REDACTED** LEN=44 TOS=0x00 PREC=0x00…x00 SYN URGP=0 
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.432Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 54269279-19e5-4865-9b38-59dc8c6…278.807 ms - -
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.458Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.734Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 1cdb3baa-2e40-4534-8359-f352d18…> Run cron job
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.906Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** mongodb 963 mongodb - {"t":{"$date":"2025-11-…
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.910Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 013c8bbf-aad9-4dca-9c9f-1171bd798d7d 963 013c…
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.937Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** 5d7106db-a620-42ee-b9b0-fa045c371815 963 5d71…
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.955Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:00 **REDACTED** syslog.js[747]: 2025-11-04T08:32:00.996Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:00Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.197Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** 5d7106db-a620-42ee-b9b0-fa045c3… check failed:
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.509Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.530Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** 013c8bbf-aad9-4dca-9c9f-1171bd7…ue' in 0.073s.
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.546Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** 013c8bbf-aad9-4dca-9c9f-1171bd7…ss' in 0.016s.
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.559Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** 013c8bbf-aad9-4dca-9c9f-1171bd7…nt' in 0.013s.
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.567Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** 013c8bbf-aad9-4dca-9c9f-1171bd7…bs' in 0.008s.
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.576Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** 013c8bbf-aad9-4dca-9c9f-1171bd7…bs' in 0.008s.
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.584Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** 013c8bbf-aad9-4dca-9c9f-1171bd7…bs' in 0.008s.
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.584Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** 013c8bbf-aad9-4dca-9c9f-1171bd7…6 cron events.
            Nov 04 08:32:01 **REDACTED** containerd[758]: time="2025-11-04T08:32:01.641567090Z" level=info msg="shim disconnected" id=b52408820757e3e0f565fbbd84057696a7b3bb945ab4f8f04…namespace=moby
            Nov 04 08:32:01 **REDACTED** dockerd[963]: time="2025-11-04T08:32:01.641767446Z" level=info msg="ignoring event" container=b52408820757e3e0f565fbbd84057696a7b3bb945ab4f8f0…ts.TaskDelete"
            Nov 04 08:32:01 **REDACTED** containerd[758]: time="2025-11-04T08:32:01.642285424Z" level=warning msg="cleaning up after shim disconnected" id=b52408820757e3e0f565fbbd8405…namespace=moby
            Nov 04 08:32:01 **REDACTED** containerd[758]: time="2025-11-04T08:32:01.642309762Z" level=info msg="cleaning up dead shim" namespace=moby
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.668Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** ffc9deab-bf4e-46db-b522-a582b9995387 963 ffc9…
            Nov 04 08:32:01 **REDACTED** systemd[1]: var-lib-docker-overlay2-88c6ae1b7c9a2ac01e56a6e0b8a0d54b74bb77141e91bbf8cb20e4dc7136a9cb-merged.mount: Deactivated successfully.
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.670Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** ffc9deab-bf4e-46db-b522-a582b99…hild processes
            Nov 04 08:32:01 **REDACTED** syslog.js[747]: 2025-11-04T08:32:01.906Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:01Z **REDACTED** mongodb 963 mongodb - {"t":{"$date":"2025-11-…
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.007Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.048Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.058Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** 1cdb3baa-2e40-4534-8359-f352d18…ss' in 0.019s.
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.072Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** 1cdb3baa-2e40-4534-8359-f352d18…ng' in 0.014s.
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.124Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** 1cdb3baa-2e40-4534-8359-f352d18…ue' in 0.052s.
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.130Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** 1cdb3baa-2e40-4534-8359-f352d18…ts' in 0.006s.
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.131Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** 1cdb3baa-2e40-4534-8359-f352d18…4 cron events.
            Nov 04 08:32:02 **REDACTED** containerd[758]: time="2025-11-04T08:32:02.185130326Z" level=info msg="shim disconnected" id=70cae9f52fe9f378a587add7dc3735cc2aae0d136166d0a77…namespace=moby
            Nov 04 08:32:02 **REDACTED** containerd[758]: time="2025-11-04T08:32:02.185202365Z" level=warning msg="cleaning up after shim disconnected" id=70cae9f52fe9f378a587add7dc37…namespace=moby
            Nov 04 08:32:02 **REDACTED** containerd[758]: time="2025-11-04T08:32:02.185211833Z" level=info msg="cleaning up dead shim" namespace=moby
            Nov 04 08:32:02 **REDACTED** dockerd[963]: time="2025-11-04T08:32:02.185466674Z" level=info msg="ignoring event" container=70cae9f52fe9f378a587add7dc3735cc2aae0d136166d0a7…ts.TaskDelete"
            Nov 04 08:32:02 **REDACTED** systemd[1]: var-lib-docker-overlay2-9de841d3869113d2e6c135a74df84cb9af939b4e4f344952f2a88461bc65642c-merged.mount: Deactivated successfully.
            Nov 04 08:32:02 **REDACTED** sudo[572510]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=998)
            Nov 04 08:32:02 **REDACTED** systemd[1]: Started /home/yellowtent/box/src/scripts/../taskworker.js 25283 /home/yellowtent/platformdata/logs/5d7106db-a620-42ee-b9b0-fa045c3…5/apptask.log.
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.560Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.738Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** 5d7106db-a620-42ee-b9b0-fa045c3…ight console: 
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: <30>1 2025-11-04T08:32:02Z **REDACTED** 5d7106db-a620-42ee-b9b0-fa045c371815 963 5d7106db-a620-42ee-b9b0-fa045c371815 - 2025-11… warning: The 
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.739Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** 5d7106db-a620-42ee-b9b0-fa045c3…ight console: 
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.865Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** 013c8bbf-aad9-4dca-9c9f-1171bd798d7d 963 013c…
            Nov 04 08:32:02 **REDACTED** syslog.js[747]: 2025-11-04T08:32:02.906Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:02Z **REDACTED** mongodb 963 mongodb - {"t":{"$date":"2025-11-…
            Nov 04 08:32:02 **REDACTED** sudo[572529]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=998)
            Nov 04 08:32:03 **REDACTED** syslog.js[747]: 2025-11-04T08:32:03.058Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:03Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:03 **REDACTED** syslog.js[747]: 2025-11-04T08:32:03.099Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:03Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:03 **REDACTED** syslog.js[747]: 2025-11-04T08:32:03.611Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:03Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:03 **REDACTED** syslog.js[747]: 2025-11-04T08:32:03.906Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:03Z **REDACTED** mongodb 963 mongodb - {"t":{"$date":"2025-11-…
            Nov 04 08:32:04 **REDACTED** syslog.js[747]: 2025-11-04T08:32:04.109Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:04Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:04 **REDACTED** syslog.js[747]: 2025-11-04T08:32:04.150Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:04Z **REDACTED** ed04407a-e8d6-4274-a9f3-b990e21…s to be queued
            Nov 04 08:32:04 **REDACTED** syslog.js[747]: 2025-11-04T08:32:04.198Z syslog:server Unable to parse: <30>1 2025-11-04T08:32:04Z **REDACTED** 5d7106db-a620-42ee-b9b0-fa045c371815 963 5d71…
            
            1 Reply Last reply
            0
            • nebulonN Offline
              nebulonN Offline
              nebulon
              Staff
              wrote last edited by
              #6

              Hm there is really not much about the actual backup mountpoint in the logs. So when this happens, and your backup mointpoint is at /mnt/cloudronbackup what happens if you run mount /mnt/cloudronbackup or systemctl status mnt-cloudronbackup.mount manually via SSH? any further information on why that wouldn't work?

              From the limited info we have, somehow it seems unmounting an sshfs (the app import) somehow unmounts other sshfs mounts on your server?

              imc67I 1 Reply Last reply
              0
              • nebulonN nebulon

                Hm there is really not much about the actual backup mountpoint in the logs. So when this happens, and your backup mointpoint is at /mnt/cloudronbackup what happens if you run mount /mnt/cloudronbackup or systemctl status mnt-cloudronbackup.mount manually via SSH? any further information on why that wouldn't work?

                From the limited info we have, somehow it seems unmounting an sshfs (the app import) somehow unmounts other sshfs mounts on your server?

                imc67I Offline
                imc67I Offline
                imc67
                translator
                wrote last edited by
                #7

                @nebulon it looks like that, but all mounts are via the GUI.

                Isn’t it easier to give you access to my server, you’re asking a little too much technical things?

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

                  That might help indeed then. Please enable remote ssh support for us then and send a mail with details to support@cloudron.io Also please mention the steps to reproduce with which to not risk breaking anything in production use on that server.

                  1 Reply Last reply
                  2
                  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