-
-
Notifications
You must be signed in to change notification settings - Fork 237
GridFS: 5593bfe857f397093508f1c5 does not exist #731
Comments
I believe I'm experiencing the same issue, but with a different string.
Which occurs fairly rarely on upload of an image, and crashes the meteor server. |
This seems to be a duplicate of #408 |
Getting the same thing here.
|
Hi, looks I have something similar: I just started running my app on Galaxy and I am seeing the error below when uploading an image. I am using Collections FS with S3
My app currently runs OK on on AWS Opsworks/Docker... so this is just happening on Galaxy. |
I've got a similar error for my app:
|
Having the same error, whole server crashes: [server-crash] 56324147e575535820228f38 does not exist |
Having the same error here (local Mac dev): |
Same thing in here
It restarts the server, which is a big pain, I've searched all of the collections and couldn't find this id. I wonder where is it coming from ? |
That's kind of a big problem since it restarts the server anyone ? |
@tagrudev Clear all temp collections of CollectionFS |
@dnish you mean all temp mongo collections ? If so I've already tried that, it's not working |
Yeah all ones that are related to CollectionFS like chunks or the temp ones. |
I've already tried cleaning the collectons, but that doesn't solve the issue (as I said I've tried finding the id that the collectionFS is trying to access and it's nowhere to be found), which is kind of strange - I think the problem comes from CollectionFS trying to access unfinished / failed upload file that's been chunked |
Have the same problem! |
This fix works : Eliga@86939dc |
@louis49 Your suggested fix and your own fix do not appear to be related, care to explain? |
Neither, after using some time I realize that this does not work 100% of the time in very specific conditions: After applying other unpublished corrections there are some bug (but not crash) We base our tests on a bulk of 1000 files < 6 MB |
Thanks for the speedy reply, it would appear the temp store doesn't handle multiple application servers accessing it particularly well. In our implementation we are using CollectionFS to store things on the local server filesystem and manage the access. We have been hitting this heavily with tens of thousands of files 10-100MB. The problem doesn't seem to occur when the app and db are on the same server and we only run one app server. I haven't tested it yet but I'm hoping the welelay fix could prevent additional application server from causing the tempstore to crash collectionFS. |
OK, i found it! |
@jackkav If "The problem doesn't seem to occur when the app and db are on the same server and we only run one app server." sounds like a race condition. |
Hi all - Just a quick FYI; I just had this problem as well and clearing the
|
In our case it was actually the upload and storing of huge images that caused this problem. An image of 2.5M and roughly 4000x3000px was too much. |
@hwillson Yeah, we did this too, but the error occured just a few days later again. |
This was working fine in my Meteor app until I adopted the new project structure in the Meteor guide and I started getting this error - 59c7a6c4ed1108551a335157 does not exist. |
I've hacked together some code that uploads GIFs, decomposes them into frames and eventually inserts all of them into GridFS. It works.
But there is one specific GIF for which it fails:
Please notice that the
5593bfe857f397093508f1c5
is the exact same on my development machine and the meteor test server, referenced above.Upload code:
The
frame
in the callback is a stream.Or see the entire source code.
The text was updated successfully, but these errors were encountered: