Skip to content

Commit 08c9cf5

Browse files
committed
Add upgrade notes for 3.x to 3.4.x
The default node name in configure.ps1 changed in #4678, from couchdb@localhost to couchdb@127.0.0.1 The same change in default node name (and resulting behaviour) also occurred in "When upgrading from 2.x to 2.1.1", so the upgrade notes for 3.4.x have been updated with the same text. https://docs.couchdb.org/en/stable/whatsnew/2.1.html#upgrade-notes
1 parent 6f42f49 commit 08c9cf5

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

src/docs/src/whatsnew/3.4.rst

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,24 @@
2020
:depth: 1
2121
:local:
2222

23+
.. _release/3.4.x/upgrade:
24+
25+
Upgrade Notes
26+
=============
27+
28+
* When upgrading from 3.x to 3.4.x, if you have not customized your
29+
node name in ``vm.args``, be sure to retain your original ``vm.args``
30+
file. The default node name has changed from ``couchdb@localhost`` to
31+
``couchdb@127.0.0.1``, which can prevent CouchDB from accessing existing
32+
databases on the system. You may also change the name option back to the
33+
old value by setting ``-name couchdb@localhost`` in ``etc/vm.args`` by
34+
hand. The default has changed to meet new guidelines and to provide
35+
additional functionality in the future.
36+
37+
If you receive errors in the logfile, such as
38+
``internal_server_error : No DB shards could be opened.`` or in Fauxton,
39+
such as ``This database failed to load.`` you need to make this change.
40+
2341
.. _release/3.4.2:
2442

2543
Version 3.4.2

0 commit comments

Comments
 (0)