FS.Tempstore.createWriteStream cannot access temporary filesystem

[nkraich]

Hey guys,

I updated to the latest version (coming from 0.4.0 I think...) I noticed that the new version was using new collection names in the db, so I took a chance and renamed what I had:

wallPosts.files -> cfs.wallPosts.filerecord
wallPostFileData.files -> cfs_gridfs.wallPostFileData.files
wallPostFileData.chunks -> cfs_gridfs.wallPostFileData.chunks

This seemed to work just fine locally, however, I am getting an error in production on meteor.com. When I try to upload a file:

[Error] Error: "Queue" failed [503] Error in method "/cfs/files/:value/:value/", Error: Error: FS.Tempstore.createWriteStream cannot access temporary filesystem     at EventEmitter.FS.TempStore.cr... [undefined], undefined
    runTaskDone (9bc6a0731d5f57ec00821361ef45fa2e5496f346.js, line 13)
    (anonymous function) (9bc6a0731d5f57ec00821361ef45fa2e5496f346.js, line 13)
    (anonymous function) (9bc6a0731d5f57ec00821361ef45fa2e5496f346.js, line 13)
    (anonymous function) (9bc6a0731d5f57ec00821361ef45fa2e5496f346.js, line 13)
    (anonymous function) (9bc6a0731d5f57ec00821361ef45fa2e5496f346.js, line 1)
    onreadystatechange (9bc6a0731d5f57ec00821361ef45fa2e5496f346.js, line 13)

Is there anything I missed when updating the database? Thanks!

[nkraich]

Actually, this might be due to having used --force and then forgotten. I'm getting the same conflict as a few others:

#211

[nkraich]

It sounds like it's OK to use --force for now, so I think I'm having some other kind of issue here.

I tried deploying to a clean site/db and still got the same error, so I don't think the issue is my database.

[raix]

I'll see if I can replicate

[nkraich]

Great, thanks!

[raix]

Closing this, its tracked in new issue