Task #905
Updated by Aaron Marcuse-Kubitza about 10 years ago
_see #887, #902_ try each of the following, in order: h3(. alternate OS approach # fix @`make install`@, install`@ which sets up the entire BIEN installation and dependencies # test the import on Mac (eg. the local testing machine (a Mac), machine, which already has most of the dependencies dependencies) # if that doesn't work, try the clean VM approach below h3(. clean VM approach # fix @`make install`@, install`@ which sets up the entire BIEN installation and dependencies # install the database from scratch on a clean VM (VirtualBox) ** this would involve adding any missing dependencies to our install scripts # test the import in the clean VM with a sample datasource to see if that reproduces the problem ** if it does, we know it's a bug in Postgres/Ubuntu and can troubleshoot using VM images with different Postgres/Ubuntu versions ** if it doesn't, it's a problem specific to just the vegbiendev VM and we would reset the vegbiendev VM to a clean Ubuntu install and reinstall our dependencies h3(. Postgres rollback approach # roll back Postgres to the version it was at in the last successful import ** this may require building Postgres from source, because past _revisions_ of the same numeric version might only be available in version control, not in binary form via apt-get (which numbers packages by numeric version) ** if this isn't possible, it may be necessary to downgrade to Postgres 9.2 (which will unfortunately be missing some features that we now use) # see if this fixes the problem h3(. VM rollback approach # restore vegbiendev to last working configuration # upgrade Postgres # see if this reproduces the problem