Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't access one board anymore #13

Closed
boospy opened this issue Jun 4, 2020 · 6 comments
Closed

Can't access one board anymore #13

boospy opened this issue Jun 4, 2020 · 6 comments

Comments

@boospy
Copy link

boospy commented Jun 4, 2020

Hello All,

using here Wekan 4.01.0 on UCS 4.4.x. One board that is an Overview of some other board cards, so they are linked with. So for about 2 weeks, i can't load the board anymore. I can see the board, an i can click the board, but it is loading for ever. A reboot did not help.

So what you need that you can help me to give me access again to this one board?

Very thanks :) :)

@xet7
Copy link
Member

xet7 commented Jun 4, 2020

wekan/wekan#1885

sudo su
docker exec -it wekan-db bash
mongo
use wekan
show collections
db.cards.find()

Etc.

And look at MongoDB 3.2.x docs, for mongo cli commands.

https://github.com/wekan/wekan/wiki/Backup

These are some tips, that I had a little time to write now.

@edgarvenom
Copy link

i don't use docker, i install white snap

@xet7
Copy link
Member

xet7 commented Jun 4, 2020

@edgarvenom

Then you can use nosqlbooster GUI to connect through SSH to server localhost port 27019 and edit

@boospy
Copy link
Author

boospy commented Jun 23, 2020

This is exactly this Bug: https://gitmemory.com/issue/wekan/wekan/2492/504653688 but what can i do? Some lists are not accessable anymore. Not even in the mobile interface. We started also to repair the database. But it seems everything ok.

@xet7
Copy link
Member

xet7 commented Jun 23, 2020

@boospy

Why do you link to gitmemory and not to actual issue?

@boospy
Copy link
Author

boospy commented Jun 23, 2020

@boospy

Why do you link to gitmemory and not to actual issue?

This is that what we find. And it look likes the same on this board we have. If you find out the same bug report here. It would be nice.

Very Thanks.

@xet7 xet7 closed this as completed Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants