Running the -c on the command to start couch is a nice tip. Gives me confidence whenever I start it up.
I re-installed couch. This time my config edits worked without all the weirdness. I guess I'll chalk all this up to some unknown pilot error. It does bother me that couch is capable of getting so screwed up. It makes me nervous. I apologize for my posting so much. I was freaked out last night. P.S. I have always gotten two identical couch processes and a beam in my ps listing. Is this normal? If so, why are there two identical running? This happens even when everything is working right. On Sat, Dec 17, 2011 at 2:36 AM, Dave Cottlehuber <[email protected]> wrote: > On 17 December 2011 11:17, Dave Cottlehuber <[email protected]> wrote: > > On 17 December 2011 06:13, Mark Hahn <[email protected]> wrote: > >>> (a) another couchdb still running, or (b) not starting couchdb with > the > >> user who is part of the admin/sudo group. > >> > >> Thanks for the tips. I know there is only one instance running and > >> everything is being done under root so I'm still confused. > > > > Hi Mark, > > > > I'm not within reach of a build-couchdb, however the couchdb > > shell script I think it should work like this: > > Lesson learned to read again before sending… > d'oh I'm 80% wrong; the couchdb script doesn't remember anything between > runs. So your couchdb -c needs to be issued on the same command used prior: > > couchdb -n \ > -a /ria/etc/db/default.ini \ > -a /ria/etc/db/local.ini \ > -p /mnt/db/couch.pid \ > -o /mnt/db/couch.stdout \ > -e /mnt/db/couch.stderr \ > -R -b -r 0 \ > -c > > which shows correctly on my system: > /ria/etc/db/default.ini > /ria/etc/db/local.ini > > what does couchdb -k -s show when running under the same user? > does pgrep beam show up anything? > > A+ > Dave > > ref: https://github.com/apache/couchdb/blob/master/bin/couchdb.tpl.in >
