• Resolved 7thcircle

    (@7thcircle)


    For the last 10 days I have been seeing the errors

    Uploading to Dropbox …
    /public_html/wp-content/plugins/backwpup/inc/class-destination-dropbox-api.php: Dropbox API: incorrect_offset/.

    WARNING: Could not look up the file session.
    /public_html/wp-content/plugins/backwpup/inc/class-destination-dropbox-api.php: Dropbox API: (55) SSL write: error -5961

    This only happens when I am trying to backup content. The DB, plugins list, and xml all work fine.

Viewing 13 replies - 1 through 13 (of 13 total)
  • I just installed this on a new site, doing the same thing for a full backup.

    I am having the same issue with: WARNING: Could not look up the file session.

    also:
    WARNING: Error while sending QUERY packet. PID=1006969

    ERROR: Job has ended with errors in 2376 seconds. You must resolve the errors for correct execution.

    It’s been some variation of these for several days now. How can it be fixed?

    Plugin Support happyAnt

    (@duongcuong96)

    Hi @bloggingknitter @canadianllama @7thcircle
    Which BackWPUp version are you using now?
    Could you please update it to the latest version then re-authentication with Dropbox again?
    Also about (55) SSL write: error -5961, please contact the hoster and ask for help since I think it caused from server-side @7thcircle
    Hope that help!

    Thread Starter 7thcircle

    (@7thcircle)

    The host shows no errors, and since this only appears when I get the file session error…

    [09-Dec-2019 00:02:13] 8659 Files with 607.50 MB in Archive.
    [09-Dec-2019 00:02:13] 1. Try to send backup file to Dropbox …
    [09-Dec-2019 00:02:14] Authenticated with Dropbox of user: xxxx
    [09-Dec-2019 00:02:14] Uploading to Dropbox …
    [09-Dec-2019 00:02:14] Beginning new file upload session
    [09-Dec-2019 00:04:50] WARNING: Could not look up the file session.
    [09-Dec-2019 00:13:26] WARNING: Could not look up the file session.
    [09-Dec-2019 00:45:06] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [09-Dec-2019 00:45:06] 2. Try to send backup file to Dropbox …
    [09-Dec-2019 00:45:07] Authenticated with Dropbox of user: xxxxxxx
    [09-Dec-2019 00:45:07] Uploading to Dropbox …
    [09-Dec-2019 01:01:01] /home1/xxxxxx/public_html/wp-content/plugins/backwpup/inc/class-destination-dropbox-api.php: Dropbox API: (55) SSL write: error -5961

    This is with the latest version, and the prior version, and it is on 3 of 40+ sites but only when I try and backup content (not db, xml by themselves)

    I updated everything, (WP Core, plugins and re authed it, also upgraded from PHP 5.4 to 7.3) It got hung up on trying to zip the file this time. I gave up and went with updraftplus.

    ME TOO! I updated everything and NO php errors! this is all of a sudden. What’s up guys?!

    Same issues here. Happened in the last week or so and hasn’t worked since. Only on some of my sites, all on the same server.

    Thread Starter 7thcircle

    (@7thcircle)

    The issue is spreading to more sites and more users yet support is nowhere to be found. Did the holidays start early? Do we need to find another solution?

    I have been having a similar issue on a number of my sites the past few weeks. Seeing the following warnings:

    WARNING: Could not look up the file session.
    WARNING: Job restarts due to inactivity for more than 5 minutes.

    The files seem to be uploading successfully to Dropbox, but always end with a failure e-mail in my inbox due to the issues in the logs.

    I have tried a number of suggestions found in the support threads here (updated the plugin, re-authenticated to dropbox, increased WP and PHP memory limit to 512MB, reduced script execution time to 25s, unchecked WordPress XML Export from my job).

    FYI, I am using HostGator re-seller shared hosting, but haven’t gone to them yet as everything appears to be in order in terms of memory limits.

    Any help or further suggestions appreciated!!!

    Here is my debug info:

    WordPress version: 5.3.2
    BackWPup version: 3.7.0
    PHP version: 7.1.14 (64bit)
    MySQL version: 5.6.41-84.1
    cURL version: 7.19.7
    cURL SSL version: NSS/3.27.1
    WP-Cron url: https://www.REMOVED.com/wp-cron.php
    Server self connect: Response Test O.K.
    Document root: /home/REMOVED/public_html
    Temp folder: /home/REMOVED/public_html/wp-content/uploads/backwpup-f71977-temp/
    Log folder: /home/REMOVED/public_html/wp-content/uploads/backwpup-f71977-logs/
    Server: Apache
    Operating System: Linux
    PHP SAPI: cgi-fcgi
    Current PHP user: polluti
    Maximum execution time: 30 seconds
    BackWPup maximum script execution time: 25 seconds
    Alternative WP Cron: Off
    Disabled WP Cron: Off
    CHMOD Dir: 0755
    Server Time: 15:40
    Blog Time: 09:40
    Blog Timezone: America/Winnipeg
    Blog Time offset: -6 hours
    Blog language: en-US
    MySQL Client encoding: utf8
    PHP Memory limit: 512M
    WP memory limit: 512M
    WP maximum memory limit: 512M
    Memory in use: 44.00 MB
    Disabled PHP Functions:: dl
    Loaded PHP Extensions:: Core, PDO, Phar, Reflection, SPL, SimpleXML, SourceGuardian, bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imap, intl, ionCube Loader, json, libxml, mbstring, mcrypt, mysqli, odbc, openssl, pcre, pdo_mysql, pdo_sqlite, posix, pspell, session, soap, sockets, sqlite3, standard, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib

    • This reply was modified 4 years, 11 months ago by pls77.
    Thread Starter 7thcircle

    (@7thcircle)

    I’m on Hostgator reseller too, with the only major difference that I am running php 7.2 and 7.3

    I may have made some progress, I managed to get a successful backup with no warnings, but I’ve changed a bunch of stuff. I need to do a few more tests and roll back a few of the changes to figure out exactly what did it and if it is sustainable. I’ll try to report back here later today.

    FYI, I spoke with Hostgator to confirm no changes were made to my server recently. The told me the server memory limit is set to 256M so I did set both my php.ini and wp-config mem limts to match.

    • This reply was modified 4 years, 11 months ago by pls77.

    False positive. Not sure why it succeeded without warnings the one time. Still fighting this.

    Thread Starter 7thcircle

    (@7thcircle)

    Turns out this was an issue with a Cyrus One network segment going into / thru a data center outside of Houston causing the issue. The equipment was replaced and the problem was resolved.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘WARNING: Could not look up the file session.’ is closed to new replies.