sklassen commented on issue #27: vm.args is now editable -- enabling clusters; snap set works for name and cookie URL: https://github.com/apache/couchdb-pkg/pull/27#issuecomment-435890423 Actually, the mounts need to be explicitly permissioned. sudo snap connect couchdb:mount-observe sudo snap connect couchdb:process-control However, once doing this, and stressing a database, I didn't see the compactor run automatically. It did, however, work when I ran it manually. The actual data directory is under /var/snap/couchdb/common, this read/writeable; the application sits under /snap/couchdb/current and is read only. Erlang should be monitoring the data directory not the base directory, I'll add a PR with the new README.md to make clear what's needed for permissions. I'll raise an issue about the erroneous error in the logs I'd like to see a 2.2 in the ubuntu snap store, if only so that the next 2.3 can be added as a candidate version first before promoting to stable. This is a useful feature of the snap eco system and would be a useful test. On Sun, Nov 4, 2018 at 4:01 AM Joan Touzet <notificati...@github.com> wrote: > Eek. I'd rather you not force disable the compactor on snap packaging, > let's focus instead on getting CouchDB fixed. > > Am I correct in assuming that the actual data directory for CouchDB is not > under /snap? > > Can you please open a new issue at > https://github.com/apache/couchdb/issues that says that the compactor is > getting confused when any mountpoint is read only? > > Let's get that fixed, then we will publish the snap when v2.3.0 of CouchDB > is released, not before. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/couchdb-pkg/pull/27#issuecomment-435616697>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AGrF5UM2qnlx5AlRsNQ2hbTxFVfIdi1Oks5urfYigaJpZM4WEZWm> > . >
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
