The db part looks the same as mine. A couple of suggestions that might help:
1. On the new deployment, use the sqlite command line client to poke at the database and see if it's intact. 2. Check twistd.log in the master working directory (probably right next to sqlite.db) for any relevant error messages. In particular, does your python environment have the sqlite adapter installed? 3. It's possible the master is working fine but your web browser can't connect to the buildbot websockets. Is there a firewall in play? A reverse proxy that you need to forward through? On Sat, Jul 20, 2019, 7:33 AM Chris Mumford <cmumf...@cmumford.com> wrote: > Thanks Josh: > > Here's the whole config file: > > > https://github.com/starryexpanse/continuous-build/blob/master/buildbot/master/master.cfg > > On Sat, Jul 20, 2019 at 7:15 AM Josh Bialkowski <josh.bialkow...@gmail.com> > wrote: > >> Can you share the "db" key of your master.cfg? Perhaps you have an >> absolute path that isn't consistent across the move? >> >> For one test environment it looks like this: >> >> c['db'] = {'db_url': "sqlite:///state.sqlite"} >> >> And I was able to move it from one machine to another. >> >> On Sat, Jul 20, 2019, 7:07 AM Chris Mumford <cmumf...@cmumford.com> >> wrote: >> >>> I'm trying to move the buildbot master to a new computer. I'm using >>> SQLite as the backend and am only doing an rsync to move the master >>> directory. When I start the new buildbot everything appears to be OK, but >>> when I navigate to a build I can't see any data there (no output, change >>> info, etc.). >>> >>> What is the correct procedure to relocate a master? >>> _______________________________________________ >>> 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
