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. Scaleway backup errors

Scaleway backup errors

Scheduled Pinned Locked Moved Solved Support
nextcloudbackupsencryptedscaleway
5 Posts 2 Posters 1.5k 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.
  • T Offline
    T Offline
    timmeh
    wrote on last edited by girish
    #1

    Hi all,

    I've been using a Scaleway storage to backup my instance on a 3-day basis but I've been getting various timeout errors since the last 5 days (each day):

    Message: write EPIPE HTTP Code: NetworkingError.
    
    Message: Your socket connection to the server was not read from or written to within the timeout period. HTTP Code: RequestTimeout.
    
    Message: Socket timed out without establishing a connection HTTP Code: TimeoutError.
    
    Message: write EPIPE HTTP Code: NetworkingError.
    

    The errors only happen after an hour or so in the backup process and files are added to my Scaleway instance. The error always pops up somewhere deep inside a gibberish directory (I think it's encrypted?) but never the same one so it seems. It's always my NextCloud instance and the directory always seems to match in some way, something like:

    snapshot/app_xxxx/....1NRyroOTEk..../....YDrvyp7W5N..../..a../..b../..c../..d..
    snapshot/app_xxxx/....1NRyroOTEk..../....YDrvyp7W5N..../..k../..l../..m../..n..

    The only thing I can think of is that I messed up my NextCloud instance a bit because I removed a file directly in the terminal, which apparently causes the instance to get confused with its database. As recommended on other NextCloud posts that I found, I ran a command to reindex my database. Something like this:

    sudo -u www-data php occ files:scan --all
    

    I ran it within the Cloudron terminal of my NextCloud instance.

    Any ideas on how to debug this problem? Is it related to the described hickup? Or is it related to Cloudron/Scaleway?

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

      Do you know if there is any network/bandwidth restrictions on your scaleway instance? And if Scaleway storage itself has any bandwidth/upload restrictions? Maybe you can ask their support if they are not immediately obvious from their pages. Looks like what is happenning is that the server is losing connectivity with the object storage. This usually happens when the network is throttled/limited somehow.

      T 1 Reply Last reply
      0
      • girishG girish

        Do you know if there is any network/bandwidth restrictions on your scaleway instance? And if Scaleway storage itself has any bandwidth/upload restrictions? Maybe you can ask their support if they are not immediately obvious from their pages. Looks like what is happenning is that the server is losing connectivity with the object storage. This usually happens when the network is throttled/limited somehow.

        T Offline
        T Offline
        timmeh
        wrote on last edited by
        #3

        Thanks for your reply @girish. I contacted customer support of Scaleway and they told me they do not throttle their object storages (which is what I backup to).

        Scanning the log files, I found that it did in fact crash on a specific series of files. I think the root cause for this was that there was a single device of mine that halted on an auto-upload via the NextCloud app. I rarely use this device and did not notice it was stuck on an upload for days. I removed the files and ran another backup, this time it did not crash.

        Is it possible that the backup script can timeout on such a partial/corrupted file?

        girishG 1 Reply Last reply
        1
        • T timmeh

          Thanks for your reply @girish. I contacted customer support of Scaleway and they told me they do not throttle their object storages (which is what I backup to).

          Scanning the log files, I found that it did in fact crash on a specific series of files. I think the root cause for this was that there was a single device of mine that halted on an auto-upload via the NextCloud app. I rarely use this device and did not notice it was stuck on an upload for days. I removed the files and ran another backup, this time it did not crash.

          Is it possible that the backup script can timeout on such a partial/corrupted file?

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

          @timmeh said in Scaleway backup errors:

          Is it possible that the backup script can timeout on such a partial/corrupted file?

          It shouldn't ideally. Are the files very large or special in some way?

          T 1 Reply Last reply
          0
          • girishG girish

            @timmeh said in Scaleway backup errors:

            Is it possible that the backup script can timeout on such a partial/corrupted file?

            It shouldn't ideally. Are the files very large or special in some way?

            T Offline
            T Offline
            timmeh
            wrote on last edited by
            #5

            @girish They are unusual I would say, yes. It's a file that is being updated on a daily basis so it has a file history of 30 different versions in NextCloud. They are .db.crypt12 files, which is a database backup of WhatsApp about 120MB in size.

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