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. SSHFS backup on windows not working after upgrading to Cloudron 8.0.1

SSHFS backup on windows not working after upgrading to Cloudron 8.0.1

Scheduled Pinned Locked Moved Solved Support
backupssshfs
4 Posts 3 Posters 506 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.
  • G Offline
    G Offline
    ganyuss
    wrote on last edited by joseph
    #1

    Hello people!

    I have been updating my Cloudron install to migrate to another machine using Ubuntu 24, but After the upgrade it looks like I am not able to do backups like I used to. I do backups using SSHFS, on a remote server running Windows, and I did not change any of the backup settings before upgrading.

    When I try to manually back up, I get this error from the logs:

    [no timestamp]  at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
    [no timestamp]  at ChildProcess.emit (node:events:518:28)
    [no timestamp]  at ChildProcess.exithandler (node:child_process:422:12)
    [no timestamp]  at Object.copy (/home/yellowtent/box/src/storage/filesystem.js:189:30)
    [no timestamp]  at genericNodeError (node:internal/errors:984:15)
    [no timestamp]  at maybeClose (node:internal/child_process:1105:16)
    [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    [no timestamp]  at wrappedFn (node:internal/errors:538:14)
    [no timestamp]  cmd: 'ssh -o "StrictHostKeyChecking no" -i /home/yellowtent/platformdata/sshfs/id_rsa_[Backup IP] -p 22 [Backup User]@[Backup IP] cp -al snapshot/app_0f9d09df-539e-4f8b-bedf-91597c6ff778.tar.gz 2024-07-19-152601-428/app_music.ganyuss.com_v1.17.0.tar.gz'
    [no timestamp]  code: 1,
    [no timestamp]  killed: false,
    [no timestamp]  signal: null,
    [no timestamp]  copy errored with code 1 message Command failed: ssh -o "StrictHostKeyChecking no" -i /home/yellowtent/platformdata/sshfs/id_rsa_[Backup IP] -p 22 [Backup User]@[Backup IP] cp -al snapshot/app_0f9d09df-539e-4f8b-bedf-91597c6ff778.tar.gz 2024-07-19-152601-428/app_music.ganyuss.com_v1.17.0.tar.gz
    [no timestamp]  n'est pas reconnu en tant que commande interne, externe, un programme ex�cutable ou un fichier de commandes. 
    

    Only those lines have "no timestamp", the rest of the logs look fine

    Error message translation: 'cp' is not recognized as an internal or external command.

    Here are my configuration details for backing up:
    b5cc03a1-5d19-4f65-8214-3a459e660060-image.png

    Let me know if I missed something, of it is an actual regression.

    Thank you for your time,
    ganyuss

    girishG 1 Reply Last reply
    2
    • G ganyuss

      Hello people!

      I have been updating my Cloudron install to migrate to another machine using Ubuntu 24, but After the upgrade it looks like I am not able to do backups like I used to. I do backups using SSHFS, on a remote server running Windows, and I did not change any of the backup settings before upgrading.

      When I try to manually back up, I get this error from the logs:

      [no timestamp]  at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
      [no timestamp]  at ChildProcess.emit (node:events:518:28)
      [no timestamp]  at ChildProcess.exithandler (node:child_process:422:12)
      [no timestamp]  at Object.copy (/home/yellowtent/box/src/storage/filesystem.js:189:30)
      [no timestamp]  at genericNodeError (node:internal/errors:984:15)
      [no timestamp]  at maybeClose (node:internal/child_process:1105:16)
      [no timestamp]  at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      [no timestamp]  at wrappedFn (node:internal/errors:538:14)
      [no timestamp]  cmd: 'ssh -o "StrictHostKeyChecking no" -i /home/yellowtent/platformdata/sshfs/id_rsa_[Backup IP] -p 22 [Backup User]@[Backup IP] cp -al snapshot/app_0f9d09df-539e-4f8b-bedf-91597c6ff778.tar.gz 2024-07-19-152601-428/app_music.ganyuss.com_v1.17.0.tar.gz'
      [no timestamp]  code: 1,
      [no timestamp]  killed: false,
      [no timestamp]  signal: null,
      [no timestamp]  copy errored with code 1 message Command failed: ssh -o "StrictHostKeyChecking no" -i /home/yellowtent/platformdata/sshfs/id_rsa_[Backup IP] -p 22 [Backup User]@[Backup IP] cp -al snapshot/app_0f9d09df-539e-4f8b-bedf-91597c6ff778.tar.gz 2024-07-19-152601-428/app_music.ganyuss.com_v1.17.0.tar.gz
      [no timestamp]  n'est pas reconnu en tant que commande interne, externe, un programme ex�cutable ou un fichier de commandes. 
      

      Only those lines have "no timestamp", the rest of the logs look fine

      Error message translation: 'cp' is not recognized as an internal or external command.

      Here are my configuration details for backing up:
      b5cc03a1-5d19-4f65-8214-3a459e660060-image.png

      Let me know if I missed something, of it is an actual regression.

      Thank you for your time,
      ganyuss

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      @ganyuss said in SSHFS backup on windows not working after upgrading to Cloudron 8.0.1:

      Let me know if I missed something, of it is an actual regression.

      It is a regression. The code was written assuming the cp tool will be available in the remote .

      As a workaround:

      • Edit /home/yellowtent/box/src/storage/filesystem.js .
      • In the copy function, there is a line if (apiConfig.provider === PROVIDER_SSHFS) { . Just disable this.. You can do it like this:
          if (false && apiConfig.provider === PROVIDER_SSHFS) {
      

      We will make a proper fix. cc @nebulon

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

        Indeed, I wasn't even aware Windows can act as an SSH server! Have to see what can be done here. For a start does windows have any shell tool which supports hardlinks? If so maybe we can try to figure out which endpoint this is and run another tool for windows?

        1 Reply Last reply
        0
        • G Offline
          G Offline
          ganyuss
          wrote on last edited by
          #4

          Hey @girish, @nebulon, thanks for coming back to me so quickly!

          Happy to report that the fix worked wonders, and the backup completed successfully.

          As for our setup, we set up the backup server a while ago now, my memories are not the freshest. But IIRC we are using OpenSSH Server for Windows Server.
          And from what I can see Windows shell uses mklink to create hard links. But I have never used it.

          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