From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <32a656c205050918431fd640da@mail.gmail.com>
Date: Tue, 10 May 2005 10:43:28 +0900
From: Vester Thacker <vester.thacker@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Subject: [9fans] Plan 9 server controls impaired and steps taken before
	failure.
Topicbox-Message-UUID: 48d898f4-ead0-11e9-9d60-3106f5b1d025

I am running a fossil+venti on an AMD64 machine. After about 20 to 30
minutes the machine ceases to receive text or chording input but the
mouse cursor still moves and the stats display continues to run. Also,
I am unable to cpu to it.

Any suggestions for a fix?

Btw, I have rebooted the machine numerous times for troubleshooting. I
disabled cron once while troubleshooting but that didn't appear to be
the culprit.

If anyone has successfully installed Plan 9 with the fossil+venti
option please state an overview of the procedures that allowed for a
hassle free installation.

Here the standard steps taken:
1) started with the default fossil+venti option
2) modified fossil.conf (e.g, added -AWP)
3) reviewed plan9.ini to ensure a line was a venti line added.
4) reboot
5) login as glenda
6) modified /lib/ndb/local (i.e., added dns, dnsdomain, ip address,
name, netmask, cpu, fs, auth, ect...)
7) modified /rc/bin/cpurc (e.g. added devices, set IP address,
factotum, secstored, keyfs, /ndb/dns -r,  ect...)
8) added user...a new hostowner
9) modified /lib/ndb/auth=20
10) reboot=20
11) login as hostowner
12) replica/pull -v /dist/replica/network
13) stopped to fix this annoying problem that occurs every 20 to 30 minutes=
 ;)

If I am forgetting something or doing something out of order, I'd like
to know. I've tried variations on my steps and even minimize the steps
but the results all lead to the same conclusion.

What really gets my goat is that this is my third machine that I've
attempted to get fossil+venti working correctly. All machines have the
same problem. I'm really thinking that it isn't an issue with hardware
but rather a missed step. If it turns out to be a hardware issue in
all 3 cases, then I am an unlucky guy.

-vester