Kevin, Unfortunately, no. We tried a few of the tips mentioned here on the CouchDB list ( http://mail-archives.apache.org/mod_mbox/couchdb-user/201305.mbox/%3cCAL+Y1nuP=wBwXn8eM7MBzZg2v3nKChTEVmo=bntwhf5ukfi...@mail.gmail.com%3e) - for example, we didn't have an admin user set up, so we tried that and it looked like it would work...but we restarted replication with a new DB (we want this to be a repeatable process) and it failed after only 500 or so documents. We were still trying Couch 1.3 so we're gonna drop down to 1.2.1 and see how that goes.
So, no real idea what is wrong. If anyone has more tips on replicating with the public npm repo, or maybe wants to zip up their .couch file and put it on bittorrent, I'm all ears, haha. I'm really hoping StrongLoops additions to NPM work out well (see http://blog.strongloop.com/whats-new-in-strong-loop-node-beta-3-private-repositories/) and someone will create an 'enterprise' repo a la Nexus/Artifactory. andy On Thu, May 16, 2013 at 6:50 PM, Kevin Sawicki <[email protected]>wrote: > Hi Andy, > > I'm also seeing the exact same issue trying to replicate > isaacs.iriscouch.com to another iriscouch.com database, it gets stuck at > 17,286 documents (16gb) and those errors start to appear in the log. > > Have you found any more details about this issue? > > Sincerely, > Kevin > > > On Monday, May 13, 2013 8:16:51 PM UTC-7, andy wrote: >> >> Based on the awesome feedback I got from https://groups.google.** >> com/d/msg/nodejs/sX4mbsRPwls/**WtDDE-To2o4J<https://groups.google.com/d/msg/nodejs/sX4mbsRPwls/WtDDE-To2o4J>, >> we tried replicating the npm repo so we could use it in an offline >> environment. >> >> We're essentially following the instructions at http://clock.co.uk/tech-* >> *blogs/how-to-create-a-private-**npmjs-repository<http://clock.co.uk/tech-blogs/how-to-create-a-private-npmjs-repository>but >> replication fails after syncing about 17k documents. >> >> We've tried reinstalling couch (found one issue that suggested using a >> patched version of SpiderMonkey) but the same thing keeps happening, even >> after restarting replication several times. >> >> Here's our setup: >> >> CentOS 6.4 >> CouchDB 1.3 >> SpiderMonkey 1.8.5-7 >> >> Replication works fine for over 17,000 documents, then we see this error >> and can't get past it: >> >> [Sat, 11 May 2013 00:55:39 GMT] [error] [<0.12970.4>] Replicator: >> couldn't write document `bufferhelper`, revision `19-** >> d339684ee7f5eaf4cc18d84da75383**2d`, to target database `registry`. >> Error: `unauthorized`, reason: `Please log in before writing to the db`. >> >> Any ideas? >> >> Thanks, >> >> Andy >> > -- > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "nodejs" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
