sync errors at random times

[iamkevinv]

Just been having some problems during sync - i was getting this after updating a successfully previously synced database, right after it hit 100. I removed the module and the db, and reinstalled. But still get the issue, this time earlier on in the sync. See below:

---

65.55 65.56

events.js:72 throw er; // Unhandled 'error' event ^ SyntaxError: Unexpected token U at Object.parse (native) at Object.exports.parse (/usr/local/share/npm/lib/node_modules/npmd/node_modules/multilevel/node_modules/mux-demux/node_modules/json-buffer/index.js:40:15) at parse (/usr/local/share/npm/lib/node_modules/npmd/node_modules/multilevel/node_modules/mux-demux/node_modules/stream-serializer/index.js:21:18) at Stream.onData as write at write (_stream_readable.js:573:24) at flow (_stream_readable.js:582:7) at Socket.pipeOnReadable (_streamreadable.js:614:5) at Socket.EventEmitter.emit (events.js:92:17) at emitReadable (_stream_readable.js:408:10) at emitReadable (_stream_readable.js:404:5)

---

Ideas?

[dominictarr]

hmm, yes this is an encoding error. levelup is trying to JSON.parse(undefined)

attempting to reproduce...

[dominictarr]

what npmd version are you on? hmm, I just did a full sync, and it looks like it worked. can you update and try again?

[iamkevinv]

Updated.

$ npm view npmd version 0.8.0

$ npm version { http_parser: '1.0', node: '0.10.15', v8: '3.14.5.9', ares: '1.9.0-DEV', uv: '0.10.13', zlib: '1.2.3', modules: '11', openssl: '1.0.1e', npm: '1.3.5' }

Each time i run npmd --sync it gets a little further.. eg: $ npmd --sync 72.36 72.4 72.41 ... etc etc.... 87.83 87.84 87.85 87.86

events.js:72 throw er; // Unhandled 'error' event ^ SyntaxError: Unexpected token U at Object.parse (native) at Object.exports.parse (/usr/local/share/npm/lib/node_modules/npmd/node_modules/multilevel/node_modules/mux-demux/node_modules/json-buffer/index.js:40:15) at parse (/usr/local/share/npm/lib/node_modules/npmd/node_modules/multilevel/node_modules/mux-demux/node_modules/stream-serializer/index.js:21:18) at Stream.onData as write at write (_stream_readable.js:573:24) at flow (_stream_readable.js:582:7) at Socket.pipeOnReadable (_streamreadable.js:614:5) at Socket.EventEmitter.emit (events.js:92:17) at emitReadable (_stream_readable.js:408:10) at emitReadable (_stream_readable.js:404:5)

[iamkevinv]

By repeating that i'm able to get it up to 100. But it will sit there forever on 100 and not return.

[dominictarr]

sitting there at 100 and not returning is correct, it's pulling data on new modules as they are published. npmd --sync --verbose to see them, idea is to run this in the background or another tab.

are you running more than once instance of npmd? I don't think you should be seeing that stacktrace if you are just running sync...

okay, I've added logging, can you try npmd@0.8.1 ?

[iamkevinv]

Cold boot, nothing run yet. I updated to 0.8.2,

Ran npmd --sync --verbose

... 99.66 generator-ultimate pilwon 2013-08-15T23:28:19.334Z grunt-vtex-deploy gadr90 2013-08-15T23:33:41.813Z html.js nbubna 2013-08-15T23:35:18.307Z zepto-browserify jiyinyiyong 2013-08-15T23:37:36.265Z command_input jseip 2013-08-15T23:38:16.784Z mongo-db-populator bitliner 2013-08-15T23:42:33.706Z redis-first segmentio 2013-08-15T23:44:29.248Z icycupcake chamrc 2013-08-15T23:44:41.925Z thinky neumino 2013-08-15T23:45:45.653Z

events.js:72 throw er; // Unhandled 'error' event ^ SyntaxError: Unexpected token U at Object.parse (native) at Object.exports.parse (/usr/local/share/npm/lib/node_modules/npmd/node_modules/multilevel/node_modules/mux-demux/node_modules/json-buffer/index.js:40:15) at parse (/usr/local/share/npm/lib/node_modules/npmd/node_modules/multilevel/node_modules/mux-demux/node_modules/stream-serializer/index.js:21:18) at Stream.onData as write at write (_stream_readable.js:573:24) at flow (_stream_readable.js:582:7) at Socket.pipeOnReadable (_streamreadable.js:614:5) at Socket.EventEmitter.emit (events.js:92:17) at emitReadable (_stream_readable.js:408:10) at emitReadable (_stream_readable.js:404:5)

[garthk]

I'm getting this quite often. err.message is always connect ECONNREFUSED at the failing point in level-couch-sync.

[dominictarr]

@garthk can you post the stacktrace?