Sage server upgrade (6.5 to 7.2) introduces Bad Gateway error

53 views
Skip to first unread message

Keir Lockridge

unread,
Jun 23, 2016, 11:34:54 AM6/23/16
to sage-support
Hi all,

I have a working installation of the Sage notebook server on a machine running RHEL, with ssl enabled (I can connect via https and I'm running the notebook with secure=True). I just built 7.2 (with ssl support, per the installation instructions, as I did with 6.5) and now I'm getting the error (when I try to connect via https):

Bad Gateway

The proxy server received an invalid response from an upstream server.


Is there something that has changed since version 6.5 that would require me to make some change to the ssl configuration in apache?


Here is a possibly relevant bit from the httpd error log.


[Thu Jun 23 11:18:09 2016] [info] Initial (No.1) HTTPS request received for child 2 (server sage.xxx.org:443)

[Thu Jun 23 11:18:09 2016] [debug] mod_proxy_http.c(56): proxy: HTTP: canonicalising URL //127.0.0.1:8888/

[Thu Jun 23 11:18:09 2016] [debug] proxy_util.c(1524): [client 69.255.143.168] proxy: https: found worker https://127.0.0.1:8888/ for https://127.0.0.1:8888/

[Thu Jun 23 11:18:09 2016] [debug] mod_proxy.c(1026): Running scheme https handler (attempt 0)

[Thu Jun 23 11:18:09 2016] [debug] mod_proxy_http.c(1982): proxy: HTTP: serving URL https://127.0.0.1:8888/

[Thu Jun 23 11:18:09 2016] [debug] proxy_util.c(2094): proxy: HTTPS: has acquired connection for (127.0.0.1)

[Thu Jun 23 11:18:09 2016] [debug] proxy_util.c(2150): proxy: connecting https://127.0.0.1:8888/ to 127.0.0.1:8888

[Thu Jun 23 11:18:09 2016] [debug] proxy_util.c(2277): proxy: connected / to 127.0.0.1:8888

[Thu Jun 23 11:18:09 2016] [debug] proxy_util.c(2528): proxy: HTTPS: fam 2 socket created to connect to 127.0.0.1

[Thu Jun 23 11:18:09 2016] [debug] proxy_util.c(2660): proxy: HTTPS: connection complete to 127.0.0.1:8888 (127.0.0.1)

[Thu Jun 23 11:18:09 2016] [info] [client 127.0.0.1] Connection to child 0 established (server sage.xxx.org:443)

[Thu Jun 23 11:18:09 2016] [info] Seeding PRNG with 144 bytes of entropy

[Thu Jun 23 11:18:09 2016] [debug] ssl_engine_kernel.c(1845): OpenSSL: Handshake: start

[Thu Jun 23 11:18:09 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: before/connect initialization

[Thu Jun 23 11:18:09 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv2/v3 write client hello A

[Thu Jun 23 11:18:09 2016] [debug] ssl_engine_io.c(1940): OpenSSL: I/O error, 7 bytes expected to read on BIO#7f063c7dec40 [mem: 7f063c7e1790]

[Thu Jun 23 11:18:09 2016] [debug] ssl_engine_kernel.c(1882): OpenSSL: Exit: error in SSLv2/v3 read server hello A

[Thu Jun 23 11:18:09 2016] [info] [client 127.0.0.1] SSL Proxy connect failed

[Thu Jun 23 11:18:09 2016] [info] [client 127.0.0.1] Connection closed to child 0 with abortive shutdown (server sage.xxx.org:443)

[Thu Jun 23 11:18:09 2016] [error] (502)Unknown error 502: proxy: pass request body failed to 127.0.0.1:8888 (127.0.0.1)

[Thu Jun 23 11:18:09 2016] [error] proxy: pass request body failed to 127.0.0.1:8888 (127.0.0.1) from 69.255.143.168 ()

[Thu Jun 23 11:18:09 2016] [debug] proxy_util.c(2112): proxy: HTTPS: has released connection for (127.0.0.1)

[Thu Jun 23 11:18:09 2016] [debug] ssl_engine_kernel.c(1863): OpenSSL: Write: SSL negotiation finished successfully

[Thu Jun 23 11:18:09 2016] [info] [client 69.255.143.168] Connection closed to child 2 with standard shutdown (server sage.xxx.org:443)


This may not be a Sage issue at all, but since it worked in one version but not the other I'm hoping someone can point me in the right direction. I admit I don't really understand what I'm doing. Thanks in advance ...

Reply all
Reply to author
Forward
0 new messages