Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-4068

Proxy Error when backup Confluence or export a space

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Support Request
    • Icon: Medium Medium
    • None
    • 1.4.3
    • None

      Running standalone version of Confluence and behind Apache ( with ProxyReverse ), we are having problem to export space or entire confluence.

      Proxy Error
      The proxy server received an invalid response from an upstream server.
      The proxy server could not handle the request GET /admin/dobackup.action.

      Reason: Error reading from remote server

            [CONFSERVER-4068] Proxy Error when backup Confluence or export a space

            Matt Ryall added a comment -

            Hi Kalle, Barrow,

            This issue is caused by mod_proxy losing the connection to Confluence before the export is complete.

            I'd suggest two changes to your Apache configuration:

            1. Increase the ProxyTimeout value from the default of 300 seconds [1].
            2. If using Apache 2.1 or newer, enable the 'keepalive' parameter in your mod_proxy configuration [2] to ensure that any intervening firewall does not interrupt the connection.

            If your backups still take too long, you have two options: either connect directly to the application server to perform the backup/export, or backup the database and confluence-home separately. The latter is our recommended backup method for large instances until the major backup & restore improvements that are planned for a future release.

            Please let me know if you're still having problems.

            Regards,
            Matt

            [1] http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxytimeout
            [2] http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypass

            Matt Ryall added a comment - Hi Kalle, Barrow, This issue is caused by mod_proxy losing the connection to Confluence before the export is complete. I'd suggest two changes to your Apache configuration: 1. Increase the ProxyTimeout value from the default of 300 seconds [1] . 2. If using Apache 2.1 or newer, enable the 'keepalive' parameter in your mod_proxy configuration [2] to ensure that any intervening firewall does not interrupt the connection. If your backups still take too long, you have two options: either connect directly to the application server to perform the backup/export, or backup the database and confluence-home separately. The latter is our recommended backup method for large instances until the major backup & restore improvements that are planned for a future release. Please let me know if you're still having problems. Regards, Matt [1] http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxytimeout [2] http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypass

            Kalle Hallivuori added a comment -

            Hi.

            I have this issue with CFL 2.1.5a, although it is only used for testing upgrade from 2.1.3 to 2.2 series, where we can return from using ProxyPass to using Jakarta.

            (It is not a problem for us since 2.1.3 in production still nicely produces nightly backups, just blocks the way of upgrading to 2.1.5a and then to 2.2.x (yet to find a properly functioning one) with data transported via backups.)

            Nothing gets printed into logs. The export takes a while to produce an entities.xml with a size of zero, and the results never end up in a zip file.

            –

            /home/confluence/intra21/data/temp/export_06192006_160249:
            total 4
            rw-rr- 1 intra21 intra21 0 Jun 19 16:05 entities.xml
            rw-rr- 1 intra21 intra21 86 Jun 19 16:02 exportDescriptor.properties

            –

            Cheers,

            Kalle Hallivuori / Sulake IT Support

            Kalle Hallivuori added a comment - Hi. I have this issue with CFL 2.1.5a, although it is only used for testing upgrade from 2.1.3 to 2.2 series, where we can return from using ProxyPass to using Jakarta. (It is not a problem for us since 2.1.3 in production still nicely produces nightly backups, just blocks the way of upgrading to 2.1.5a and then to 2.2.x (yet to find a properly functioning one) with data transported via backups.) Nothing gets printed into logs. The export takes a while to produce an entities.xml with a size of zero, and the results never end up in a zip file. – /home/confluence/intra21/data/temp/export_06192006_160249: total 4 rw-r r - 1 intra21 intra21 0 Jun 19 16:05 entities.xml rw-r r - 1 intra21 intra21 86 Jun 19 16:02 exportDescriptor.properties – Cheers, Kalle Hallivuori / Sulake IT Support

            jens added a comment -

            Is it possible that the proxy times out when waiting for the response, because the export takes a while to be created. I will have to look deeper into that issue in order to verify that explanation.

            In order to be able to analyze the issue better, it would be helpful if you could attach more details of your configuration and your log files to the issue. I would suggest you to create a support request on our support Jira instance on http://support.atlassian.com which is completely private.

            Cheers,
            Jens

            jens added a comment - Is it possible that the proxy times out when waiting for the response, because the export takes a while to be created. I will have to look deeper into that issue in order to verify that explanation. In order to be able to analyze the issue better, it would be helpful if you could attach more details of your configuration and your log files to the issue. I would suggest you to create a support request on our support Jira instance on http://support.atlassian.com which is completely private. Cheers, Jens

              Unassigned Unassigned
              457b589fa799 Barrow Kwan
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: