[Buildbot-commits] buildbot/docs slave.xhtml,1.1,1.2

[Brian Warner]

Update of /cvsroot/buildbot/buildbot/docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv26287

Modified Files:
	slave.xhtml 
Log Message:
more notes


Index: slave.xhtml
===================================================================
RCS file: /cvsroot/buildbot/buildbot/docs/slave.xhtml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- slave.xhtml	6 Dec 2004 03:09:24 -0000	1.1
+++ slave.xhtml	6 Dec 2004 03:31:46 -0000	1.2
@@ -186,7 +186,21 @@
 respond to this by shutting down normally.</p>
 
 
-<p>Troubleshooting</p>
+<h2>Maintenance</h2>
+
+<p>It is a good idea to check the buildmaster's status page every once in a
+while, to see if your buildslave is still online. Eventually the buildbot
+will probably be enhanced to send you email (via the <q>info/admin</q> email
+address) when the slave has been offline for more than a few hours.</p>
+
+<p>If you find you can no longer provide a buildslave to the project, please
+let the project admins know, so they can put out a call for a
+replacement.</p>
+
+
+<h2>Troubleshooting</h2>
+
+<h3>Starting the buildslave</h3>
 
 <p>Cron jobs are typically run with a minimal shell (/bin/sh, not /bin/bash),
 and tilde expansion is not always performed in such commands. You may want to
@@ -205,6 +219,26 @@
 stop the buildslave with nothing but the cries of sorrowful developers to
 remind you that it has gone away.</p>
 
+
+<h3>Connecting to the buildmaster</h3>
+
+<p>If the buildslave cannot connect to the buildmaster, the reason should be
+described in the <code>twistd.log</code> logfile. Some common problems are an
+incorrect master hostname or port number, or a mistyped bot name or password.
+If the buildslave loses the connection to the master, it is supposed to
+attempt to reconnect with an exponentially-increasing backoff. Each attempt
+(and the time of the next attempt) will be logged. If you get impatient, just
+manually stop and re-start the buildslave.</p>
+
+<p>When the buildmaster is restarted, all slaves will be disconnected, and
+will attempt to reconnect as usual. The reconnect time will depend upon how
+long the buildmaster is offline (i.e. how far up the exponential backoff
+curve the slaves have travelled). Again, <code>buildbot stop BASEDIR;
+buildbot start BASEDIR</code> will speed up the process.</p>
+
+
+<h3>Running builds</h3>
+
 <p>From the buildmaster's main status web page, you can force a build to be
 run on your build slave. Figure out which column is for a builder that runs
 on your slave, click on that builder's name, and the page that comes up will
@@ -215,5 +249,4 @@
 the same web page should also show the <q>admin</q> and <q>host</q>
 information files that you configured earlier.</p>
 
-
 </body> </html>