Wekan export internal server error

[ashgoodman]

When I try to export a board I get an internal server error and a file with a size of 0 bytes

Tested in Firefox and Chrome

Running on an Ubuntu 18.04 Server

[xet7]

@Angtrim is currently looking into fixing this.

[fsainovich]

Same here - 2.90

[xet7]

What Wekan platform (Snap/Docker/Sandstorm) ? For me, export works on Wekan v2.90 Snap.
Please try doing this:

sudo snap set wekan with-api='true'

[teutat3s]

Just happened here, too. This is on wekan docker, self-built the Dockerfile, docker-compose setup. Imported database from backup using mongorestore, other than that all standard. Wekan Version v3.11.0

Logs show:

2019-08-08T22:12:03.781366794Z wekan-app 8495 MongoError: file with id 5d4c9e33fb96e2212f8dbbbe not opened for writing
2019-08-08T22:12:03.781405722Z wekan-app 8495     at Function.MongoError.create (/build/programs/server/npm/node_modules/meteor/cfs_gridfs/node_modules/mongodb/node_modules/mongodb-core/lib/error.js:31:11)
2019-08-08T22:12:03.781417435Z wekan-app 8495     at /build/programs/server/npm/node_modules/meteor/cfs_gridfs/node_modules/mongodb/lib/gridfs/grid_store.js:979:33
2019-08-08T22:12:03.781427592Z wekan-app 8495     at handleCallback (/build/programs/server/npm/node_modules/meteor/cfs_gridfs/node_modules/mongodb/lib/utils.js:96:12)
2019-08-08T22:12:03.781435629Z wekan-app 8495     at /build/programs/server/npm/node_modules/meteor/cfs_gridfs/node_modules/mongodb/lib/collection.js:1401:5
2019-08-08T22:12:03.781444945Z wekan-app 8495     at handleCallback (/build/programs/server/npm/node_modules/meteor/cfs_gridfs/node_modules/mongodb/lib/utils.js:96:12)
2019-08-08T22:12:03.781452132Z wekan-app 8495     at /build/programs/server/npm/node_modules/meteor/cfs_gridfs/node_modules/mongodb/lib/cursor.js:675:5
2019-08-08T22:12:03.781459019Z wekan-app 8495     at handleCallback (/build/programs/server/npm/node_modules/meteor/cfs_gridfs/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:172:5)
2019-08-08T22:12:03.781465496Z wekan-app 8495     at setCursorNotified (/build/programs/server/npm/node_modules/meteor/cfs_gridfs/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:517:3)
2019-08-08T22:12:03.781473132Z wekan-app 8495     at /build/programs/server/npm/node_modules/meteor/cfs_gridfs/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:590:16
2019-08-08T22:12:03.781482717Z wekan-app 8495     at queryCallback (/build/programs/server/npm/node_modules/meteor/cfs_gridfs/node_modules/mongodb/node_modules/mongodb-core/lib/cursor.js:233:18)
2019-08-08T22:12:03.781494114Z wekan-app 8495     at /build/programs/server/npm/node_modules/meteor/cfs_gridfs/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:436:18
2019-08-08T22:12:03.781501236Z wekan-app 8495     at _combinedTickCallback (internal/process/next_tick.js:132:7)
2019-08-08T22:12:03.781508675Z wekan-app 8495     at process._tickDomainCallback (internal/process/next_tick.js:219:9)

[xet7]

@teutone

What MongoDB version you have?

[teutat3s]

MongoDB shell version v4.0.11

[xet7]

#2533 (comment)

[xet7]

@teutone

Please add your docker commands and settings you used, without your own domains and credentials included.

[xet7]

@teutone

What Docker image are you using?

[xet7]

I'm just thinking, if you use latest tag, without version tag, I don't know would this #2603 by @whowillcare have any effects on this.

[xet7]

Did you use newest docker-compose.yml from https://github.com/wekan/wekan ?

[teutat3s]

Built the docker image myself using the Dockerfile from master 9ed0c30

Yes, used docker-compose.yml from master

[xet7]

Do you have old data at /data/db ? #2585 (comment)

[teutat3s]

No, it's a fresh mongo:4.0 docker image without data.

• first stopped wekan-app
• then imported with mongorestore --drop --noIndexRestore --db wekan /data/dump/wekan/
• then started wekan-app

[xet7]

I did test building Docker image. I did uncomment these lines https://github.com/wekan/wekan/blob/master/docker-compose.yml#L132-L142 and then did:

docker-compose up -d --build

And Wekan is available at port 80 just fine. I don't know how you did build your Docker image.

[teutat3s]

And does board export work for you?

[xet7]

You need to import with:

mongorestore --drop --noIndexRestore

[xet7]

Yes, export board works for me, on that container I just built above.

[teutat3s]

Yes I used that command from https://github.com/wekan/wekan/wiki/Export-Docker-Mongo-Data
Sorry, should have been more detailed

[teutat3s]

Just tested with another board - and it seems it's just one board that makes problems. I can export other boards just fine.
If I remember correctly I was not admin from the start for that board where export fails. Maybe that's causing some problem?

[xet7]

Hmm, I have not tested is export enabled for normal users.

[teutat3s]

I could not export a board where I was not admin - the button was not available. So I kindly asked the creator of the board to make me admin. Now export doesn't work with just that board - maybe it's a permission problem.

[xet7]

With only one board? You can try to build Wekan container again, I just fixed one permission problem:
9f6d615

[xet7]

Correction: other Wekan contributor fixed it.

[teutat3s]

Just tried it, but didn't fix the buggy board. Can't export only a few boards, trying to find out why

[tesfithagos]

I have the same problem, is there a solution now?
I use Apache2 as a web server, i can see these messages in the logs:

[proxy_http:error]
(20014)Internal error (specific information not available):
AH01102: error reading status line from remote server wekan..:3001
AH00898: Error reading from remote server returned by /api/boards/********/export

On some boards it works and on some it does not work.

[xet7]

@tesfithagos

Are you BoardAdmin on those boards you are trying to export?

[tesfithagos]

@xet7 Yes i am BoradAdmin

https://wekan.telekom.de/api/boards/6Cz5KP9Tsb7MuYazk/export?authToken=lde79D0jVpRl7aAKho9cAo4aYG2sr3GNTi12Wu9EbTx

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /api/boards/6Cz5KP9Tsb7MuYazk/export.
Reason: Error reading from remote server

it could be a timeout problem???

[c-9u11]

present on one of my boards running wekan v3.29, ubuntu 16.04, mongo 3.2.22.

[xarinatan]

I presume I'm also getting this issue inside Sandstorm, Version 2.97.0~2019-07-01, I don't see any errors pop up though, neither in the Networking tab of the webbrowser console, nor in the sandstorm debug log.. but I'm getting a 0 bytes file every time I try export any of the boards from an older grain that's been around for a while, in fresh grains it works fine (exporting a board there generates a 14.2kb file), but in that specific grain none of the boards can be exported, even fresh boards.

[c-9u11]

poked around the log a bit. I have the same error as teutat3s:

MongoError: file with id 5cae8de230a374304a5f7152 not opened for writing

edit: i found the file (which won't open), and deleted it in the card. now i've progressed to this error:
Exception in removed observe/observeChanges callback: Error: Removed nonexistent document dqrXncesyGkvteR49

[xet7]

Moved to here from https://community.vanila.io/home?t=28ccfe48-0f4c-435e-a822-d8d22dafa94c

@whowillcare

Currently exporting board does not work, when there is attachments on boards like images. I don't know are these related to your changes to save attachments to disk instead of MongoDB. There are some errors related to cfs-upload. Do you have time to look at this?

[whowillcare]

Will talk a look when I have time

…

On Sunday, October 6, 2019, Lauri Ojansivu ***@***.***> wrote: Moved to here from https://community.vanila.io/home?t=28ccfe48-0f4c-435e- a822-d8d22dafa94c @whowillcare <https://github.com/whowillcare> Currently exporting board does not work, when there is attachments on boards like images. I don't know are these related to your changes to save attachments to disk instead of MongoDB. There are some errors related to cfs-upload. Do you have time to look at this? [image: export-bug-2] <https://user-images.githubusercontent.com/15545/66277435-4d905d80-e8a7-11e9-84a8-f73480dff94c.png> [image: export-bug-1] <https://user-images.githubusercontent.com/15545/66277441-58e38900-e8a7-11e9-93c2-b0b987980a11.png> [image: export-bug-3] <https://user-images.githubusercontent.com/15545/66277444-626cf100-e8a7-11e9-8694-df1f07b46681.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2093?email_source=notifications&email_token=ABUL3KFO4H6M7FDGEKRAOBLQNJV3DA5CNFSM4GOJSNZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAOWM6Q#issuecomment-538797690>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABUL3KATAHGSSM4TNPGWIEDQNJV3DANCNFSM4GOJSNZQ> .