Installation on REE

[que]

Hi,
Is where a way to install WebROaR on REE?
I'm getting the following error:
Checking for libruby.so.1.8.7........not found.

[Aditya Babbar]

We have never tried it with REE. Sorry, can't be of more help on this as of now.

Aditya

[que]

Solved by reinstalling REE with --enable-shared flag

[Aditya Babbar]

Great! Please do let us know (if you can) how WebROaR goes with REE. We would be very interested to hear about it.

Aditya

[Oleh Khomey]

Well.. it simply doesn't work :)

webroar.log looks good, but I'm getting 404 for all requests.

Regards,
 Oleh Khomey

[Aditya Babbar]

1. Are you able to access the Admin Panel? http://localhost:[port]/admin-panel
2. If not, could you please check out the details in the admin panel log in /var/log/webroar.

Aditya

[Oleh Khomey]

1. no - 404

2. see attachments

Regards,
 Oleh Khomey

[Chris Heald]

Given that compiling with --enable-shared slows down the REE
interpreter by ~20%, I'm not sure it's a viable solution, even if it
could be made to work.

WebROaR with REE would be best-case, since otherwise each fork of the
process results in a full copy of the master process's memory space.
Running a prefork server with a non-COW-friendly VM seems like a
really bad idea, even if it does serve requests 5% faster. If I have
to choose between 30% more active instances running 5% slower (due to
COW memory savings) or 30% fewer instances with 5% more throughput on
each, the former is a no-brainer.

[Aditya Babbar]

Some points about WebROaR Design:

1. It always has a 'minimum' number of workers running for a particular deployed application. As the request load increases, more workers are created by forking 'webroar-head' process and then calling execl() for 'webroar-worker'. The new worker then loads up interpreter/VM and the application code. Till the time the new worker comes up, the existing workers keep serving requests for that application. 

2. As you rightly pointed out, forking a process that has non-COW-friendly interpreter loaded is not efficient, and in my personal opinion it *could* be prone to issues. (Ruby 1.8.x has a lot of dark alleys where i would not prefer to go .. unless really required.) And since we want to support non-COW-friendly interpreter as well, we made a choice for forking head as mentioned above. 

WebROaR + REE (that I have heard is fantastic as is most of Phusion's work) could very well be a good choice for reducing memory consumption of the deployed application. We would try it out sometime in the future to see how it goes.

Aditya

[Aditya Babbar]

Just to add to the points below, the newly created worker sticks around and keeps serving out more requests. When the request load starts coming down, the worker that is occupying the maximum memory is killed. This takes care of the worker processes that keep growing due to interpreter memory leaks etc, and tries to keep the memory usage for the server to the minimum.

Aditya

[Aditya Babbar]

Oleh,

It seems none of the spawned workers are able to connect back to the head process.

1. Could you please give the details of your system? (OS/gcc)

2. If possible, could you please run a debug build of the server. It would give more verbose logs, and hopefully help us in figuring out the issue. You can use the following commands:

*sudo webroar uninstall*

*sudo webroar install --debug-build*

Aditya

[Oleh Khomey]

Hi,

I'm using up to date Ubuntu 9.10 x64

gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.1-4ubuntu8' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8)

Debug log attached

Regards,
 Oleh Khomey

[Aditya Babbar]

Oleh,

We have fixed one issue seen for WebROaR with REE + tcmalloc installation. Could you please pull the latest code from Github repository and let us know how it goes for your application?

You can refer the details of the issue here:

http://webroar.lighthouseapp.com/projects/36429/tickets/9-malfunctional-webroar-installed-in-optruby

Aditya

[pavel...@gmail.com]

I made it works on ubuntu 9.04 x64, REE 2010.01
First I made rake rails:freeze:gems for admin_panel application and
admin panel start working.
It was very difficult to make applications work because if it run with
error, error writes in log and application just says 404.
webroar-analyzer does not working for me, starling crashes for with
and showing just 404:

> Sun Jan 24 02:19:57 2010-14300-Error: /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/memcache-client-1.7.7/lib/memcache.rb:646:in `stats'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/starling-0.10.1/lib/starling.rb:83:in `sizeof'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/webroar-0.2.7/src/ruby_lib/analyzer/message_reader.rb:40:in `read'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/webroar-0.2.7/src/ruby_lib/analyzer/message_analyzer.rb:63:in `process_messages'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/webroar-0.2.7/src/ruby_lib/analyzer/webroar_analyzer_script_runner.rb:82:in `start'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/webroar-0.2.7/src/ruby_lib/analyzer/webroar_analyzer_script_runner.rb:79:in `initialize'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/webroar-0.2.7/src/ruby_lib/analyzer/webroar_analyzer_script_runner.rb:79:in `new'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/webroar-0.2.7/src/ruby_lib/analyzer/webroar_analyzer_script_runner.rb:79:in `start'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/webroar-0.2.7/src/ruby_lib/analyzer/webroar_analyzer_script_runner.rb:48:in `initialize'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/webroar-0.2.7/src/ruby_lib/analyzer/webroar_analyzer_script_runner.rb:26:in `new'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/webroar-0.2.7/src/ruby_lib/analyzer/webroar_analyzer_script_runner.rb:26:in `run'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/webroar-0.2.7/src/ruby_lib/analyzer/webroar_analyzer.rb:28
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
> /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8/gems/webroar-0.2.7/bin/webroar-analyzer:23
> /usr/local/bin/webroar-analyzer:19:in `load'
> /usr/local/bin/webroar-analyzer:19

One more annoying error in that it does not works with different
versions of rails

Is the way to show startup errors in admin panel and show what
application starts with errors instead of "404" ?
I think it'll be very useful (for example like it made in passenger)

Good luck

On Nov 26 2009, 9:40 pm, Aditya Babbar <aditya.bab...@webroar.in>
wrote:
> 1. Are you able to access the Admin Panel?http://localhost:

> [port]/admin-panel
> 2. If not, could you please check out the details in the admin panel log in
> /var/log/webroar.
>
> Aditya
>
>
>
> On Fri, Nov 27, 2009 at 12:03 AM, Oleh Khomey <varyf...@gmail.com> wrote:
> > Well.. it simply doesn't work :)
> > webroar.log looks good, but I'm getting 404 for all requests.
>
> > Regards,
> >  Oleh Khomey
>

> > On Thu, Nov 26, 2009 at 7:54 PM, Aditya Babbar <aditya.bab...@webroar.in>wrote:
>
> >> Great! Please do let us know (if you can) how WebROaR goes with REE. We
> >> would be very interested to hear about it.
>
> >> Aditya
>

[pavel...@gmail.com]

Oh, webroar installed from github
git clone git://github.com/webroar/webroar.git
cd webroar
sudo rake install
as you recommended

[Aditya Babbar]

Thank you for trying out WebROaR and sending out this email. I'll try to address the points raised by you:

1. "First I made rake rails:freeze:gems for admin_panel application and

admin panel start working."

Could you please provide us the log messages from the Admin Panel log file when it was not working? We would like to understand the exact issue seen on your system.

2. "webroar-analyzer does not working for me, starling crashes"

Thank you for reporting this issue. We have raised a ticket on Lighthouse for it. It looks like occasionally some of the workers are unable to connect to Starling server. In that case their analytics & exceptions data would not be logged to the DB and hence would not be available on the Admin Panel as well.

A 404 error should not be seen in this case.

3. "One more annoying error in that it does not works with different

versions of rails"

Could you give more details about this issue?

4. "Is the way to show startup errors in admin panel and show what

application starts with errors instead of "404" ?"

Yes we are working on also showing the startup errors on admin panel/console apart from the log files as well. This feature should be available in the coming releases of WebROaR.

Aditya

[Dharmarth Shah]

For issue #2 (webroar-analyzer not working) a fix has been checked in
to github. Please refer this resolved ticket for more details:

http://webroar.lighthouseapp.com/projects/36429/tickets/14-sometime-workers-not-connecting-to-starling-server

#4 - “"show startup errors in admin panel"”

In case there is an error during starting of an application, the
details are now also displayed on the admin panel/command line along
with them being saved in to the logs.

You call pull the latest code from github to look at this changes.

Dharmarth

On Jan 25, 7:37 pm, Aditya Babbar <aditya.bab...@webroar.in> wrote:
> Thank you for trying out WebROaR and sending out this email. I'll try to
> address the points raised by you:
>
> 1. "First I made rake rails:freeze:gems for admin_panel application and
> admin panel start working."
>
> Could you please provide us the log messages from the Admin Panel log file
> when it was not working? We would like to understand the exact issue seen on
> your system.
>
> 2. "webroar-analyzer does not working for me, starling crashes"
>
> Thank you for reporting this issue. We have raised a ticket on Lighthouse
> for it. It looks like occasionally some of the workers are unable to connect
> to Starling server. In that case their analytics & exceptions data would not
> be logged to the DB and hence would not be available on the Admin Panel as
> well.
>
> A 404 error should not be seen in this case.
>
> 3. "One more annoying error in that it does not works with different
> versions of rails"
>
> Could you give more details about this issue?
>
> 4. "Is the way to show startup errors in admin panel and show what
> application starts with errors instead of "404" ?"
>
> Yes we are working on also showing the startup errors on admin panel/console
> apart from the log files as well. This feature should be available in the
> coming releases of WebROaR.
>
> Aditya
>

> On Sun, Jan 24, 2010 at 6:00 AM, Pavel.e...@gmail.com
> <pavel.e...@gmail.com>wrote: