Could you reply with your launcher configuration file as well as the relevant virtual hosts file? That information could help isolate what's going on.
Thanks, Scott On Tue, Jun 17, 2014 at 12:21 PM, CLSA Mcmaster <clsamcmas...@gmail.com> wrote: > Hello > > I feel I am very close to getting this but I need some help. > > I am using Paraview with Python and an Apache front end with proxying. My > logs show as follows: > > [Tue Jun 17 14:18:34.353847 2014] [proxy:debug] [pid 5840] > proxy_util.c(2035): AH00943: http: has released connection for ( > dragonfly.domain.ca) > [Tue Jun 17 14:18:34.353905 2014] [deflate:debug] [pid 5840] > mod_deflate.c(764): [client 192.168.1.9:45352] AH01384: Zlib: Compressed > 246 to 151 : URL /paraview/, referer: > http://paraview.domain.ca/apps/FileViewer/ > [Tue Jun 17 14:18:34.366482 2014] [authz_core:debug] [pid 5843] > mod_authz_core.c(828): [client 192.168.1.9:45354] AH01628: authorization > result: granted (no directives) > [Tue Jun 17 14:18:34.366557 2014] [proxy:debug] [pid 5843] > mod_proxy.c(1104): [client 192.168.1.9:45354] AH01143: Running scheme ws > handler (attempt 0) > [Tue Jun 17 14:18:34.366566 2014] [proxy_ajp:debug] [pid 5843] > mod_proxy_ajp.c(708): [client 192.168.1.9:45354] AH00894: declining URL > ws://192.168.1.110:9103/ws?sessionId=c83abd36-f64b-11e3-b1d5-14feb5ee4ae2 > [Tue Jun 17 14:18:34.366577 2014] [proxy_http:debug] [pid 5843] > mod_proxy_http.c(1892): [client 192.168.1.9:45354] AH01113: HTTP: > declining URL ws:// > 192.168.1.110:9103/ws?sessionId=c83abd36-f64b-11e3-b1d5-14feb5ee4ae2 > [Tue Jun 17 14:18:34.366583 2014] [proxy_wstunnel:debug] [pid 5843] > mod_proxy_wstunnel.c(331): [client 192.168.1.9:45354] AH02451: serving > URL ws:// > 192.168.1.110:9103/ws?sessionId=c83abd36-f64b-11e3-b1d5-14feb5ee4ae2 > [Tue Jun 17 14:18:34.366590 2014] [proxy:debug] [pid 5843] > proxy_util.c(2020): AH00942: WS: has acquired connection for (*) > [Tue Jun 17 14:18:34.366596 2014] [proxy:debug] [pid 5843] > proxy_util.c(2072): [client 192.168.1.9:45354] AH00944: connecting ws:// > 192.168.1.110:9103/ws?sessionId=c83abd36-f64b-11e3-b1d5-14feb5ee4ae2 to > 192.168.1.110:9103 > [Tue Jun 17 14:18:34.366665 2014] [proxy:debug] [pid 5843] > proxy_util.c(2206): [client 192.168.1.9:45354] AH00947: connected > /ws?sessionId=c83abd36-f64b-11e3-b1d5-14feb5ee4ae2 to 192.168.1.110:9103 > [Tue Jun 17 14:18:34.366800 2014] [proxy:debug] [pid 5843] > proxy_util.c(2610): AH00962: WS: connection complete to 192.168.1.110:9103 > (192.168.1.110) > [Tue Jun 17 14:18:34.574643 2014] [proxy_wstunnel:debug] [pid 5843] > mod_proxy_wstunnel.c(253): [client 192.168.1.9:45354] AH02445: woke from > poll(), i=1 > [Tue Jun 17 14:18:34.574681 2014] [proxy_wstunnel:debug] [pid 5843] > mod_proxy_wstunnel.c(262): [client 192.168.1.9:45354] AH02446: sock was > readable > [Tue Jun 17 14:18:34.574725 2014] [proxy_wstunnel:debug] [pid 5843] > mod_proxy_wstunnel.c(129): (104)Connection reset by peer: [client > 192.168.1.9:45354] AH02442: error on sock - ap_get_brigade > [Tue Jun 17 14:18:34.574751 2014] [proxy:debug] [pid 5843] > proxy_util.c(2035): AH00943: WS: has released connection for (*) > > As you can see, I am getting a reset by peer but I'm not sure of the > cause. Any help or clues would be greatly appreciated. > > > _______________________________________________ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the ParaView Wiki at: > http://paraview.org/Wiki/ParaView > > Follow this link to subscribe/unsubscribe: > http://public.kitware.com/mailman/listinfo/paraview > >
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
