9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: [9fans] venti
Date: Wed,  3 Oct 2007 21:51:00 -0400	[thread overview]
Message-ID: <20071004014849.69A641E8C4D@holo.morphisms.net> (raw)

I have fixed the sync livelock bug that anothy and others reported.

To make it easier to debug problems in the future (and to inspect
your venti servers from other machines), I suggest changing your
plan9.ini from reading

	venti=/dev/sdC0/arenas

to

	venti=/dev/sdC0/arenas tcp!127.1!17034 tcp!*!8000

The two additional addresses are where venti listens for venti
and http traffic, respectively.  The defaults are tcp!127.1!17034
and tcp!127.1!8000.  Using * instead of 127.1 in the latter will
make it so the http server is accessible from other machines.
(If you want to make your venti server accessible too, change
the first address to tcp!*!17034.) The default is 127.1 for
security reasons.

Having done this, you will be able to load pages like

	http://venti:8000/proc/threads

to get a list of threads and what code they are blocked in.  And

	http://venti:8000/proc/stacks

will give the stack for each thread, much like running stacks()
in an "acid -l thread" session.

If you do encounter problems where venti appears to be
hung in some form, I would appreciate if you could save
the output of 

	http://venti:8000/proc/all

and mail it to me when reporting the problem. 

Note that although there are new venti binaries on sources,
the kernels do not yet use the new venti.  If you boot from 
a combined venti+fossil server, you will need to rebuild 
9pccpuf/9pcf yourself in order to get it.

Thanks.
Russ



             reply	other threads:[~2007-10-04  1:51 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04  1:51 Russ Cox [this message]
2007-10-07 20:51 ` Steve Simon
2007-10-08  7:02   ` [9fans] here document arisawa
2007-10-08  7:46     ` sqweek
2007-10-08 11:59       ` arisawa
2007-10-08 12:12         ` erik quanstrom
2007-10-08 12:47           ` roger peppe
2007-10-08 13:09             ` erik quanstrom
2007-10-08 14:02               ` roger peppe
2007-10-08 15:14                 ` erik quanstrom
2007-10-08 16:34                   ` [9fans] International Workshop on Plan 9 Sape Mullender
2007-10-10  0:37         ` [9fans] here document Scott Schwartz
2007-10-10  0:46           ` erik quanstrom
2007-10-19  6:20             ` arisawa
2007-10-19 10:59               ` erik quanstrom
2007-10-19 12:44                 ` Martin Neubauer
2007-10-19 13:25                   ` erik quanstrom
2007-10-19 13:56                     ` Martin Neubauer
  -- strict thread matches above, loose matches on Subject: below --
2009-01-09  8:20 [9fans] venti Tharaneedharan Vilwanathan
2009-01-09  9:44 ` Sape Mullender
2009-01-09 12:18   ` Richard Miller
2009-01-09 12:38     ` Sape Mullender
2009-01-09 13:39     ` erik quanstrom
2009-01-09 20:11   ` Dave Eckhardt
2009-01-09 20:27     ` erik quanstrom
2009-01-09 22:18       ` Dave Eckhardt
2009-01-09 22:27         ` erik quanstrom
2009-01-09 20:34     ` Steve Simon
2009-01-09 21:08     ` Roman V. Shaposhnik
2007-07-03  4:58 [9fans] Venti Lucio De Re
2007-03-30 16:32 [9fans] venti Steve Simon
2003-02-06  1:11 Kenji Arisawa
2003-02-06  1:21 ` Russ Cox
2002-11-29 18:59 Russ Cox
2002-11-29 18:27 Russ Cox
2002-06-13 20:58 [9fans] bug or a feature? Dan Cross
2002-06-13 21:34 ` Tharaneedharan Vilwanathan
2002-06-13 22:51   ` [9fans] venti Tharaneedharan Vilwanathan
2002-06-14  2:19     ` Sean Quinlan
2002-06-14  5:05       ` Tharaneedharan Vilwanathan
2002-01-30 20:35 George Michaelson
     [not found] <rob@plan9.bell-labs.com>
2002-01-30  5:52 ` rob pike
2002-01-30  6:23   ` George Michaelson
2002-01-30  8:07   ` paurea
2002-01-30 11:17   ` Boyd Roberts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071004014849.69A641E8C4D@holo.morphisms.net \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).