Oddly, that outputs nothing at all. Not even an error message. On Mon, Dec 21, 2015 at 4:31 PM, Francesco Di Mizio < francescodimi...@gmail.com> wrote:
> Hi, > > try twistd --nodaemon --no_save -y buildbot.tac, see what you get. > > On Mon, Dec 21, 2015 at 9:57 PM, Chris Spencer <chriss...@gmail.com> > wrote: > >> I ran through the steps in the tutorial ( >> http://docs.buildbot.net/current/tutorial/firstrun.html) >> and was able to get Buildbot running. >> >> However, when I rebuilt the virtualenv on an Ubuntu VM and rsynced up my >> custom configuration folder, buildbot appears unable to start. >> >> If I activate my virtualenv and then run `buildbot start master` all I >> get is: >> >> Following twistd.log until startup finished.. >> >> The buildmaster took more than 10 seconds to start, so we were unable >> to >> confirm that it started correctly. Please 'tail twistd.log' and look >> for a >> line that says 'BuildMaster is Running' to verify correct startup. >> >> A twistd.log file is generated, but nothing is ever written to it and `ps >> aux|grep -i twist` shows nothing running. >> >> How do I diagnose this problem? How do I run buildbot in non-daemon mode >> so I can see whatever error it's running into? >> >> _______________________________________________ >> users mailing list >> users@buildbot.net >> https://lists.buildbot.net/mailman/listinfo/users >> > >
_______________________________________________ users mailing list users@buildbot.net https://lists.buildbot.net/mailman/listinfo/users
