MongoDB GridFS“非法块格式"异常 [英] MongoDB GridFS "illegal chunk format' exception
问题描述
我一直在用Node.js编写一个应用程序，该应用程序将图像存储在MongoDB的GridFS文件系统中.
I've been writing an app in Node.js that stores images in MongoDB's GridFS file system.
我已经通过该应用上传了图片，并且这些图片似乎存储正确:
I've uploaded images through the app, and the images appear to be stored correctly:
$ mongofiles -v -d speaker-karaoke get howard-basement-100x115.jpg
Tue Jul 17 12:14:16 creating new connection to:127.0.0.1
Tue Jul 17 12:14:16 BackgroundJob starting: ConnectBG
Tue Jul 17 12:14:16 connected connection!
connected to: 127.0.0.1
done write to: howard-basement-100x115.jpg
这从MongoDB中抓取了.jpg，我可以打开它，没问题，所以看来我上传的内容已正确存储.
This grabbed the .jpg out of MongoDB and I was able to open it no problem, so it looks like what I'm uploading is being stored correctly.
但是，在运行的应用程序中，当我尝试读取相同的文件时，会得到:
However, in my running application, when I attempt to read the same file, I get:
12:15:44 web.1 | started with pid 89621
12:15:45 web.1 | Connecting to mongodb://localhost/speaker-karaoke
12:15:45 web.1 | Speaker Karaoke express app started on 5000
12:15:48 web.1 | DEBUG: Get review thumbnail for 5005b7550333650000000001
12:15:48 web.1 |
12:15:48 web.1 | node.js:201
12:15:48 web.1 | throw e; // process.nextTick error, or 'error' event on first tick
12:15:48 web.1 | ^
12:15:48 web.1 | Error: Illegal chunk format
12:15:48 web.1 | at Error (unknown source)
12:15:48 web.1 | at new <anonymous> (/Users/hlship/workspaces/github/speaker-karaoke/node_modules/mongodb/lib/mongodb/gridfs/chunk.js:43:11)
12:15:48 web.1 | at /Users/hlship/workspaces/github/speaker-karaoke/node_modules/mongodb/lib/mongodb/gridfs/gridstore.js:488:24
12:15:48 web.1 | at Cursor.nextObject (/Users/hlship/workspaces/github/speaker-karaoke/node_modules/mongoose/node_modules/mongodb/lib/mongodb/cursor.js:462:5)
12:15:48 web.1 | at [object Object].<anonymous> (/Users/hlship/workspaces/github/speaker-karaoke/node_modules/mongoose/node_modules/mongodb/lib/mongodb/cursor.js:456:12)
12:15:48 web.1 | at [object Object].g (events.js:156:14)
12:15:48 web.1 | at [object Object].emit (events.js:88:20)
12:15:48 web.1 | at Db._callHandler (/Users/hlship/workspaces/github/speaker-karaoke/node_modules/mongoose/node_modules/mongodb/lib/mongodb/db.js:1290:25)
12:15:48 web.1 | at /Users/hlship/workspaces/github/speaker-karaoke/node_modules/mongoose/node_modules/mongodb/lib/mongodb/connection/server.js:329:30
12:15:48 web.1 | at [object Object].parseBody (/Users/hlship/workspaces/github/speaker-karaoke/node_modules/mongoose/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:118:5)
12:15:48 web.1 | process terminated
12:15:48 system | sending SIGTERM to all processes
使用此代码(CoffeeScript，用于Express):
Using this code (CoffeeScript, for Express):
app.get "/images/review-thumbnail/:id", (req, res) ->
id = req.params.id
util.debug "Get review thumbnail for #{id}"
store = new GridStore mongoose.connection.db, new ObjectID(id), null, "r"
store.open (err, file) ->
throw err if err
util.debug "Store open for #{id}, type = #{file.contentType}"
# TODO: Scale the image before sending it!
res.header "Content-Type", file.contentType
store.stream(true).pipe res
因此，它似乎甚至没有传递到传递给store.open()的回调中.
So it doesn't seem to be even making it to the callback passed to store.open().
当您知道ID而不是文件名时，打开GridFS文件是否有问题?
Is there a problem opening a GridFS file when you know the id, but not the file name?
顺便说一句:
$ npm ls
speaker-karaoki@0.0.1 /Users/hlship/workspaces/github/speaker-karaoke
├─┬ blueimp-file-upload-node@1.0.2 extraneous
│ ├── formidable@1.0.11
│ ├── imagemagick@0.1.2
│ └── node-static@0.6.0
├── coffee-script@1.3.3
├─┬ connect-assets@2.1.9
│ ├── connect-file-cache@0.2.4
│ ├── mime@1.2.2
│ ├─┬ snockets@1.3.4
│ │ ├── coffee-script@1.3.3
│ │ ├── dep-graph@1.0.1
│ │ └── uglify-js@1.0.7
│ └── underscore@1.1.7
├─┬ express@2.5.9
│ ├─┬ connect@1.9.1
│ │ └── formidable@1.0.11
│ ├── mime@1.2.4
│ ├── mkdirp@0.3.0
│ └── qs@0.4.2
├─┬ jade@0.26.0
│ ├── commander@0.5.2
│ └── mkdirp@0.3.0
├─┬ mongodb@1.0.2
│ └── bson@0.0.6
├─┬ mongoose@2.7.0
│ ├── hooks@0.2.1
│ └─┬ mongodb@1.0.2
│ └── bson@0.0.6
├─┬ passport@0.1.10
│ └── pkginfo@0.2.3
├─┬ passport-twitter@0.1.3
│ ├─┬ passport-oauth@0.1.9
│ │ ├── oauth@0.9.7
│ │ └── passport@0.1.11
│ └── pkginfo@0.2.3
├── sass@0.5.0
└── underscore@1.3.3
这是失败的函数:
var Chunk = exports.Chunk = function(file, mongoObject) {
if(!(this instanceof Chunk)) return new Chunk(file, mongoObject);
this.file = file;
var self = this;
var mongoObjectFinal = mongoObject == null ? {} : mongoObject;
this.objectId = mongoObjectFinal._id == null ? new ObjectID() : mongoObjectFinal._id;
this.chunkNumber = mongoObjectFinal.n == null ? 0 : mongoObjectFinal.n;
this.data = new Binary();
if(mongoObjectFinal.data == null) {
} else if(typeof mongoObjectFinal.data == "string") {
var buffer = new Buffer(mongoObjectFinal.data.length);
buffer.write(mongoObjectFinal.data, 'binary', 0);
this.data = new Binary(buffer);
} else if(Array.isArray(mongoObjectFinal.data)) {
var buffer = new Buffer(mongoObjectFinal.data.length);
buffer.write(mongoObjectFinal.data.join(''), 'binary', 0);
this.data = new Binary(buffer);
} else if(mongoObjectFinal.data instanceof Binary || Object.prototype.toString.call(mongoObjectFinal.data) == "[object Binary]") {
this.data = mongoObjectFinal.data;
} else if(Buffer.isBuffer(mongoObjectFinal.data)) {
} else {
throw Error("Illegal chunk format");
}
// Update position
this.internalPosition = 0;
};
解决方案
在此处更新解决方案，因为它在下面的注释中无法正确显示.
Updating the solution here as it does not render correctly in the comments below.
问题是重复.拥有mongodb和bson的两个副本(即使版本相同).
The problem was the duplication; having two copies, even with the same version, of mongodb and bson.
幸运的是，猫鼬将其所需的mongodb导出为mongo属性，因此我能够从我的package.json中删除显式mongodb并进行了更改:
Fortunately, mongoose exports the mongodb it requires as property mongo, so I was able to remove the explicit mongodb from my package.json and changed:
mongo = require "mongodb"
mongoose = require "mongoose"
收件人:
mongoose = require "mongoose"
mongo = mongoose.mongo
现在情况看起来不错；我仍然认为模块系统需要一种批准的方式来访问依赖项依赖项(对于dep不够周全以暴露其dep的情况).
Things are now looking nice; I still think the module system needs a sanctioned way to access a dependencies dependencies (for the case where a dep is not thoughtful enough to expose its deps).
推荐答案
可以肯定它是mongodb模块的重复副本(相同版本)；删除node_modules并进行nmp安装似乎已解决了该问题.
Pretty sure it was duplicate copies (same version) of mongodb module; removing node_modules and nmp install seems to have fixed it.
这篇关于MongoDB GridFS“非法块格式"异常的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
