From user-return-19707-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Tue Jan 31 23:39:30 2012 Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 759879F19 for ; Tue, 31 Jan 2012 23:39:30 +0000 (UTC) Received: (qmail 14942 invoked by uid 500); 31 Jan 2012 23:39:28 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 14866 invoked by uid 500); 31 Jan 2012 23:39:28 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 14858 invoked by uid 99); 31 Jan 2012 23:39:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2012 23:39:27 +0000 X-ASF-Spam-Status: No, hits=2.6 required=5.0 tests=FROM_LOCAL_NOVOWEL,HK_RANDOM_ENVFROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cgsmcmlxxv@gmail.com designates 209.85.216.52 as permitted sender) Received: from [209.85.216.52] (HELO mail-qw0-f52.google.com) (209.85.216.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2012 23:39:22 +0000 Received: by qafi31 with SMTP id i31so529367qaf.11 for ; Tue, 31 Jan 2012 15:39:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=2OijpAT6P4EyLoGpC1Ap3eteD/zVw2+eOFVsow9m6Ag=; b=F8MZX8jHbtTjMN4TRiYQ2IAVRaQPmulQ75tG9xVFB4cX5VWP0b7x7ncP9xYMZQd02r MWkXAgIsnWiePIJKiDxx58ujdlSVulsl/JIcAeC0OLYhLHaUWpNOl6Hv247xfe7LuAYQ yl3+PQl76WTRk9zfvdrqRs8wX39wxxWjSrAm8= MIME-Version: 1.0 Received: by 10.224.117.1 with SMTP id o1mr13155774qaq.4.1328053141373; Tue, 31 Jan 2012 15:39:01 -0800 (PST) Received: by 10.229.83.197 with HTTP; Tue, 31 Jan 2012 15:39:01 -0800 (PST) In-Reply-To: References: Date: Wed, 1 Feb 2012 00:39:01 +0100 Message-ID: Subject: Re: new ReferenceError(options is not defined) From: CGS To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=20cf3074d7f6bc02ee04b7db7703 --20cf3074d7f6bc02ee04b7db7703 Content-Type: text/plain; charset=ISO-8859-1 I don't know what you did there, but it seems there is an interaction in between node and couch in which couch catches 'new ReferenceError(options is not defined)' (it may be that node returns this error to couch via JS, but really no idea because I don't know what you did there). From the error, Erlang catches a JS engine error which is reported that way. How and where, I don't know without more info. The first part of the error: [error] [<0.7533.1>] OS Process Error <0.7546.1> :: {<<"unnamed_error">>, suggested the error caught by Erlang from JS engine, while the second part: <<"(new ReferenceError(\"options is not defined\", \"\"))">>} is the JS engine report for that error (which is translated like: "the 'options' variable/element... is not defined", meaning, either something happened within that variable which provoked the crash, or the variable is not recognized by the environment). From what you gave us, the only place containing "options" variable is line 6 from your node code. That's why I made that connection. If you have somewhere else "options", there are chances that there could be the problem. But, as I said, more than interpreting the error, I cannot say for sure it's like that because I have no idea what you did there and, more than that, I don't know node. Sorry, but more than that I am not able to help you with my knowledge in this moment. If that is not enough info, please, accept my apologies for interfering. CGS On Tue, Jan 31, 2012 at 11:57 PM, Mark Hahn wrote: > How did the couch error message know the word "options"? My use of the > word options is for the specific node call http.request. > > BTW: thanks for the help. I'm sure I'm doing something stupid. > > On Tue, Jan 31, 2012 at 2:48 PM, CGS wrote: > > > At line 6 from your node code snippet you defined variable "options": > > > > options = {host: 'localhost', port: mh.dbPort, method: 'PUT', headers, > > path: dbPath} > > > > My toss of dices would go in the definition of the headers, but that's > just > > a wild guess. > > > > CGS > > > > > > > > On Tue, Jan 31, 2012 at 11:30 PM, Mark Hahn wrote: > > > > > I'm not familiar with the options you are talking about. Are these > some > > > kind of http options or couchdb options in the json body? > > > > > > On Tue, Jan 31, 2012 at 2:16 PM, CGS wrote: > > > > > > > Hi Mark, > > > > > > > > It looks very much like an JS engine error and it seems there is a > > > problem > > > > in setting up the "options" parameter. From the error, either > "options" > > > > parameter doesn't exist, or it is not well formatted (no idea about > > > > node.js). Another option is an incompatibility with JS engine version > > > which > > > > doesn't accept your "options" in that format. > > > > > > > > I would suggest to ask about what's wrong with your "options" setup > > (and > > > JS > > > > engine compatibility if nothing is wrong) in node.js mailing > list/forum > > > or > > > > wait here for someone who knows node.js enough to see where you went > > > wrong > > > > there. Definitely the error is there, but I cannot tell you what as I > > > have > > > > no idea about node.js (as I said it before). > > > > > > > > I hope this post will help you at least as a starting point in > > debugging. > > > > > > > > CGS > > > > > > > > > > > > > > > > > > > > On Tue, Jan 31, 2012 at 10:00 PM, Mark Hahn wrote: > > > > > > > > > I'm bumping this because it is killing me. I can't get past this > > > > problem. > > > > > It is happening several places in my code. > > > > > > > > > > What can cause an "OS Process Error"? > > > > > > > > > > On Mon, Jan 30, 2012 at 2:29 PM, Mark Hahn > wrote: > > > > > > > > > > > I'm getting this error on a put request for an attachment. > > > > > > > > > > > > [error] [<0.7533.1>] OS Process Error <0.7546.1> :: > > > > > > {<<"unnamed_error">>, > > > > > > <<"(new ReferenceError(\"options is not defined\", \"\"))">>} > > > > > > > > > > > > This is my node code ... > > > > > > > > > > > > headers = {} > > > > > > headers.Authorization = mh.dbAuthHdr > > > > > > headers['content-type'] = contentType > > > > > > headers['content-length'] = contentLength > > > > > > dbPath = '/ri/' + compDoc._id + '/' + attachmentName + '?rev=' + > > > > > > compDoc._rev > > > > > > options = {host: 'localhost', port: mh.dbPort, method: 'PUT', > > > headers, > > > > > > path: dbPath} > > > > > > > > > > > > respStr = '' > > > > > > resp = null > > > > > > readStream = fs.createReadStream filePath > > > > > > readStream.on 'error', (e) -> > > > > > > vh.err req, res, 'um: uploadAttachment read error ' + compDoc._id > > + ' > > > > ' + > > > > > > e.message, 500 > > > > > > readStream.pipe http.request options, (resProx) -> > > > > > > if +resProx.statusCode isnt 201 > > > > > > vh.err req, res, > > > > > > 'um: uploadAttachment db request err ' + compDoc._id + ' ' + > > > > > > resProx.statusCode, 500 > > > > > > return > > > > > > resProx.on 'data', (chunk) -> respStr += chunk.toString() > > > > > > resProx.on 'end', (chunk) -> > > > > > > if chunk then respStr += chunk.toString() > > > > > > resp = JSON.parse respStr > > > > > > docUpdate = procThumbnails: compDoc.procThumbnails > > > > > > if lastUpdate then docUpdate.needsNotification = yes > > > > > > db.updateDoc compDoc._id, docUpdate, (err, doc) -> > > > > > > if err > > > > > > log 'dba: uploadAttachment compDoc update err ' + compDoc._id > > > > > > cb false > > > > > > return > > > > > > compDoc = doc > > > > > > callback true > > > > > > > > > > > > This is the value of my options ... > > > > > > > > > > > > host: localhost > > > > > > path: > > > > > > > > > > > > > > > > > > > > > /ri/04b7c4eb50d1d01dbb1a0f097bb80/thumbnail-72x48c.jpg?rev=27-3d44ae708d6fe9c835577d71f5e70359 > > > > > > method: PUT > > > > > > headers: > > > > > > content-length: 3511 > > > > > > content-type: image/jpeg > > > > > > Authorization: Basic ... snipped ... > > > > > > port: 5984 > > > > > > > > > > > > Does anyone have an idea of what I'm doing wrong? > > > > > > > > > > > > > > > > > > > > > > > > > > > --20cf3074d7f6bc02ee04b7db7703--