[Paraview] WebSocket Connection lost in ParaviewWeb
Arya Mazaheri
aryanet at gmail.com
Sun Jan 26 02:54:39 EST 2014
OK, I managed to solve the problem. The logs in /tmp/pw-logs/ helped me a
lot.
I had compiled the Paraview from source and in the log I saw that the
pvpython throws the following exception:
Traceback (most recent call last):
File
"/root/paraview/build/lib/site-packages/paraview/web/pv_web_data_prober.py",
line 37, in <module>
from vtk.web import server
File "/usr/local/lib/paraview-4.1/site-packages/vtk/web/server.py", line
27, in <module>
from . import testing
File "/usr/local/lib/paraview-4.1/site-packages/vtk/web/testing.py", line
71
TestModuleBrowsers = type("Enum", (), {k: i for i, k in
enumerate(test_module_browsers)})
^
SyntaxError: invalid syntax
So, I decided to use the binary version instead of the compiled one. Now,
It works properly.
Does the source have any bug you think?
Thanks for your help.
On Sat, Jan 25, 2014 at 5:39 PM, Arya Mazaheri <aryanet at gmail.com> wrote:
> I tried that.
> I switched to 'daemon' user as the apache is set to work with. I could cat
> the mapping.txt file without any problem.
> I'm suspicious on mod_rewrite module. I think it may now working properly.
> Do you have any idea that I could check it's functionality?
> Do you have any clue that what would be the cause of this problem?
>
> Thanks for your helps,
>
>
> On Thu, Jan 23, 2014 at 5:31 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> Does the apache "user" can read that file?
>> Are all the directories above that file "executable" for that user?
>>
>> Try by switching to that user and check if you can "cat" that file.
>>
>> Seb
>>
>>
>> On Thu, Jan 23, 2014 at 4:36 AM, Arya Mazaheri <aryanet at gmail.com> wrote:
>>
>>> Yes, I checked that. There are some entries with the following pattern:
>>> 97b94394-7edb-4b9b-b26a-4d76aee49925 pvwserver:9099
>>>
>>> Just to let you know, I didn’t create the special group like mentioned
>>> in Amazon EC2 tutorial. I made this file’s permission to 777. I hope this
>>> wouldn’t be the cause of the problem.
>>>
>>> On Wednesday ۲ November ۱۳۹۲ BC at ۷:۱۶ بعدازظهر, Sebastien Jourdain
>>> wrote:
>>>
>>> That patch was integrated into the master branch of Apache a while ago,
>>> but I was not aware that it made it to the 2.4.7 release.
>>> So, if you have Apache 2.4.7, you SHOULD NOT patch it.
>>>
>>> The version that you had was correct and should have worked.
>>> The remaining question is regarding the
>>> file: /opt/apache-2.4.7/pv-mapping-file/mapping.txt
>>>
>>> Is that file properly created? Does the content reflect the session id,
>>> host and port as expected?
>>>
>>> Seb
>>>
>>>
>>> On Wed, Jan 22, 2014 at 1:36 AM, Arya Mazaheri <aryanet at gmail.com>wrote:
>>>
>>> Thanks for mentioning that. I've got stuck in running PW, trying every
>>> solution and wondering why it doesn't work!!
>>>
>>> Anyway, since I didn't have any other choice I decided to patch my
>>> Apache 2.4.7 source and then recompile it. Now, when I try to run the
>>> 'make' it throws the following error:
>>> mod_rewrite.c: In function ‘is_absolute_uri’:
>>> mod_rewrite.c:600: error: duplicate case value
>>> mod_rewrite.c:589: error: previously used here
>>> mod_rewrite.c:601: error: duplicate case value
>>> mod_rewrite.c:590: error: previously used here
>>> make[4]: *** [mod_rewrite.slo] Error 1
>>> make[4]: Leaving directory
>>> `/root/apacheInstall/apache-src/httpd-2.4.7/modules/mappers'
>>> make[3]: *** [shared-build-recursive] Error 1
>>> make[3]: Leaving directory
>>> `/root/apacheInstall/apache-src/httpd-2.4.7/modules/mappers'
>>> make[2]: *** [shared-build-recursive] Error 1
>>> make[2]: Leaving directory
>>> `/root/apacheInstall/apache-src/httpd-2.4.7/modules'
>>> make[1]: *** [shared-build-recursive] Error 1
>>> make[1]: Leaving directory `/root/apacheInstall/apache-src/httpd-2.4.7'
>>> make: *** [all-recursive] Error 1
>>>
>>>
>>> Shouldn't I patch my source??
>>>
>>>
>>> On Tue, Jan 21, 2014 at 8:12 PM, Scott Wittenburg <
>>> scott.wittenburg at kitware.com> wrote:
>>>
>>> Just wanted to jump in here. The patch instructions are, strangely,
>>> missing from that Amazon EC2 setup documentation. That's my fault, since I
>>> wrote it. I'll update the documenation with the steps below, which should
>>> have been in there all along. However, I just checked, and the version
>>> you're using (2.4.7) already has the patch included, so these steps really
>>> only apply to versions 2.4.6 and earlier. Sorry for the oversight.
>>>
>>> 1) Download the patch:
>>>
>>> wget -O patch.txt
>>> https://issues.apache.org/bugzilla/attachment.cgi?id=30886&action=diff&context=patch&collapsed=&headers=1&format=raw
>>>
>>> 2) Change to the root of the httpd source tree and patch the source:
>>>
>>> patch -u -p1 < path-to-patch/patch.txt
>>>
>>>
>>>
>>>
>>> On Tue, Jan 21, 2014 at 4:24 AM, Arya Mazaheri <aryanet at gmail.com>wrote:
>>>
>>> Thanks for your reply.
>>> Previously, I was following the old model approach using apache 2.2.
>>> Now, I upgraded to Apache 2.4.7. And followed the Amazon EC2 tutorial.
>>> However, now I get the following message in the firebug which the
>>> rickshaw.min.js file generated that:
>>> Firefox can't establish a connection to the server at
>>> ws://pvwserver/proxy?sessionId=9521c7c5-d2c6-4e9d-980e-5c7ea9f7dfd4.
>>>
>>> Is it related to the rewriting module? Maybe it's not working! Any idea?
>>> I've attached my 'pw-config.properties' and 'httpd-vhosts.conf' files
>>> to this thread.
>>>
>>> Regards,
>>>
>>>
>>> On Mon, Jan 20, 2014 at 10:26 PM, Sebastien Jourdain <
>>> sebastien.jourdain at kitware.com> wrote:
>>>
>>> The web socket forwarding should be handle by Apache at that point and
>>> it seems to be done by Jetty?
>>> In your jetty configuration, the session URL might not be valid when
>>> using Apache as a front-end.
>>>
>>> Moreover, which Apache setup did you used? 2.4+ like for the EC2 Amazon
>>> documentation or the old one with the Python module?
>>>
>>> Seb
>>>
>>>
>>> On Mon, Jan 20, 2014 at 9:24 AM, Arya Mazaheri <aryanet at gmail.com>wrote:
>>>
>>> Hi there,
>>> I've installed ParaviewWeb from source and configured apache to work
>>> with jetty. I think I've done every configuration according to the
>>> tutorials. But everytime I try to open DataProber application I face with
>>> the following error in Jetty console output:
>>>
>>> Jan 20, 2014 7:50:18 PM com.kitware.paraview
>>> web.websocket.WebSocketForwarder onOpen
>>> INFO: null
>>> java.util.concurrent.ExecutionException: java.net.ConnectException:
>>> Connection refused
>>> at
>>> org.eclipse.jetty.websocket.WebSocketClient$WebSocketFuture.get(WebSocketClient.java:569)
>>> at
>>> org.eclipse.jetty.websocket.WebSocketClient$WebSocketFuture.get(WebSocketClient.java:372)
>>> at com.kitware.paraviewweb.websocket.WebSocketForwarder.onOpen
>>> (WebSocketForwarder.java:54)
>>> at
>>> org.eclipse.jetty.websocket.WebSocketConnectionRFC6455.onWebSocketOpen(WebSocketConnectionRFC6455.java:425)
>>> at
>>> org.eclipse.jetty.websocket.WebSocketServletConnectionRFC6455.handshake(WebSocketServletConnectionRFC6455.java:60)
>>> at
>>> org.eclipse.jetty.websocket.WebSocketFactory.upgrade(WebSocketFactory.java:309)
>>> at
>>> org.eclipse.jetty.websocket.WebSocketFactory.acceptWebSocket(WebSocketFactory.java:382)
>>> at
>>> org.eclipse.jetty.websocket.WebSocketHandler.handle(WebSocketHandler.java:43)
>>> at
>>> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
>>> at org.eclipse.jetty.server.Server.handle(Server.java:365)
>>> at
>>> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:485)
>>> at
>>> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:926)
>>> at
>>> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:988)
>>> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:635)
>>> at
>>> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
>>> at
>>> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
>>> at
>>> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:628)
>>> at
>>> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
>>> at
>>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
>>> at
>>> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
>>> at java.lang.Thread.run(Thread.java:701)
>>> Caused by: java.net.ConnectException: Connection refused
>>> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>>> at
>>> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:597)
>>> at
>>> org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:628)
>>> at
>>> org.eclipse.jetty.io.nio.SelectorManager$1.run(SelectorManager.java:290)
>>> ... 3 more
>>>
>>>
>>> In the firebug, I see the following error:
>>> Connection lost - retrying (1) ..
>>>
>>> Any ideas?
>>>
>>> _______________________________________________
>>> 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://www.paraview.org/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://www.paraview.org/mailman/listinfo/paraview
>>>
>>>
>>>
>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20140126/5560587c/attachment.html>
More information about the ParaView
mailing list