Ok, here are debug packages linked against glibc: http://www.hypertable.com/debug/hypertable-0.9.6.0.95b0abc-linux-i386-debug.tar.bz2 http://www.hypertable.com/debug/hypertable-0.9.6.0.95b0abc-linux-i386-debug.deb
Please give it another try and report back and let us know if the RangeServer crashed and if so, whether or not it generated any more useful error messages. Thanks for your help! - Doug On Thu, Aug 9, 2012 at 7:42 AM, Kenny F. <[email protected]> wrote: > I add "Virtual Memory Size" and "Resident Memory Size" graphs to attached > file. > Crash is on the right-end of data, sure. > > Kenny F. > > > On Tuesday, August 7, 2012 9:57:52 PM UTC+3, Doug Judd wrote: >> >> Great! We're getting close. One thing I'd like to know is what the >> virtual memory size and resident set size of the RangeServer process was >> immediately before the failure. If you haven't blown away your database >> yet, you should be able to get the monitoring system up and running and >> inspect the stats page for rs1. To do that, do the following: >> >> # install ruby and rubygems >> apt-get install ruby rubygems >> >> # make sure you have ruby >= 1.8.7 >> $ ruby -version >> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] >> >> # install gems required for monitoring system: >> gem install capistrano sinatra rack thin json titleize >> >> # start monitoring system >> /opt/hypertable/current/bin/**start-monitoring.sh >> >> # pull up the monitoring system in your web brower: >> http://178.162.111.111:38090 >> >> You should see a table with one row in it. The first column is the >> "Server" column and should have a link "rs1" in it. Click on that link and >> it should pull up a page of graphs for that server. Set the "Start Time" >> and "End Time" to cover the period leading up to and including the time of >> the failure. The click the "show" button. Now scroll down to the graphs >> "Virtual Memory Size" and "Resident Memory Size" and screen capture those >> two graphs and post the screen capture to this list so that we can take a >> look. >> >> If you have trouble getting the monitoring graphs up, let us know and we >> can help you get it up and running. >> >> - Doug >> >> -- > You received this message because you are subscribed to the Google Groups > "Hypertable Development" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/hypertable-dev/-/EGDFaREGYS4J. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/hypertable-dev?hl=en. > -- Doug Judd CEO, Hypertable Inc. -- You received this message because you are subscribed to the Google Groups "Hypertable Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hypertable-dev?hl=en.
