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.kit
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 on
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 connect
Looking quickly at your files, everything seems fine.
But did you patch Apache, like the documentation explain? Or did you just
used the binaries?
I guess the "pvwserver" host name is known by your web client?
Did you check if the pvpython process was running and if the proper mapping
information
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
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_rew
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/a
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
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 wrote:
> Yes, I checked that. There are some entries with the
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 wo
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_pr
Hi Arya,
That looks like a problem with the version of Python you were trying to
use. I don't think ParaViewWeb supports Python versions lower than 2.7, so
you could check the version you were using before you switched to the
binary. Maybe you were trying to use Python 2.6 or lower? At any r
12 matches
Mail list logo
