wohali opened a new issue #972: 2.1.1 fails to open databases after upgrade URL: https://github.com/apache/couchdb/issues/972 This is a pre-emptive bug against which we can de-duplicate issues that get filed in the future. "When starting up my CouchDB after upgrading from 2.0.0 or 2.1.0 to 2.1.1, I get either a `No DB shards could be opened.` error in couch.log, or a "This database failed to load" error in Fauxton." The fix: Edit your `etc/vm.args` file and change the line that reads `-name [email protected]` to `-name couchdb@localhost`. This is outlined in our release notes here: http://docs.couchdb.org/en/2.1.1/whatsnew/2.1.html#upgrade-notes >When upgrading from 2.x to 2.1.1, if you have not customized your node name in vm.args, be sure to retain your original vm.args file. The default node name has changed from couchdb@localhost to [email protected], which can prevent CouchDB from accessing existing databases on the system. You may also change the name option back to the old value by setting -name couchdb@localhost in etc/vm.args by hand. The default has changed to meet new guidelines and to provide additional functionality in the future. > If you recieve errors in the logfile, such as internal_server_error : No DB shards could be opened. or in Fauxton, such as This database failed to load. you need to make this change.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
