On Thu, Jan 17, 2008 at 09:59:27PM +0100, Bernhard Leiner wrote: > > Björn Ketelaars <[EMAIL PROTECTED]> wrote: > > > I'm trying to run rtorrent-0.7.9 on snapshot. Unfortunately rtorrent > > > crashes after sometime taking down the complete system. > > > > > > It is still possible to ping the machine. It is not possible to reach > > > it by means of a serial console or by means of SSH. > > I'm facing the same problems here. Right after upgrading to 4.2 > (and to libtorrent-0.11.4, rtorrent-0.7.4p0). > > On 05/01/2008, viq <[EMAIL PROTECTED]> wrote: > > I'm trying to track down the same thing too. Two questions: did you try > > forcing the box to drop to ddb to see what's happening? I was advised > > that ddb(4) and crash(8) man pages may be useful to get some > > information out of it. Another, I was advised to try running "dd > > if=/dev/rwd0c of=/dev/null bs=64k" (or something similar) to read the > > whole disk, and look in syslog for any disk errors. My disks show some > > errors, so my bug hunting session is postponed until I rule out disk > > problems (ie get a new disk...) > > My disk looks ok.
How did you check it? Either all my disks are bad, or I am checking in wrong way... > I have a serial connection to the crashed box right now (a soekris > net4801) but unfortunately all I can see is the frozen rtorrent > client. No reactions on any key strokes. No traceback and I can't > switch to ddb. An existing ssh connection accepted three more key > strokes before freezing. Try setting ddb.console=1 in /etc/sysctl.conf and sending BREAK over serial (in cu that would be ~#) > I can still ping the machine, and NAT also still works (otherwise I > couldn't write this mail ;-)) > No daemon running (sshd, dhcpd, smbd) accepts a new connection. > > Sorry for this rather useless bug report... I will keep trying to get > a traceback. > > best regards, > bernhard -- viq
