Join the conversation

Sign in to join this conversation, and others like it, in the communities you care about.

Wekan

Wekan is an open-source kanban board (Trello like) which allows a card-based task and to-do management.

Wekan / Bugs

Update recently? deleting

Update recently? deleting

Wekan / Bugs · February 28, 2020 at 4:04pm (Edited 4 years ago)

was there an update last evening or the day before?

deleting archived cards do not stay deleted. Refreshing screen and they return in the list of archived things to delete

HOW do you clear out all cards from the system not using the GUI? Its suddenly happening on all three systems with no code changes.

Can we roll back to the last version. THis is broken

other issues: when updating with new cards from the api looking at the contents of the new cards put the GUI into some sort of wait mode. Until you refresh the screen several times you get this behavior that indicates its not connecting to Mongo or something

In fact the deleting the archived boards works and on screen refresh they are still there seems like its never deleting from Mongo at all

Another hint: in addition to the GUI thinking the archived card is deleted and when you refresh its not, the webhooks are not being sent out when the delete happens. So it seems that the GUI is disconnected from the mongo and webhook piece entirely.

Question: in addition to rolling back the code, using snap installed wekan, what is the correct way to get into mongo shell under snap wekan? I can at least see what is in the database then and perhaps clear it out

LMK

more hints, I can't delete archived cards but I can restore them. When I do I cannot disable or remove webhooks associated

HOw do I get into wekan under snap mongo to clear these out?

Load previous messages

February 28, 2020 at 8:23pm

the owner

    • reply
    • like

    and one user to view the cards

      • reply
      • like

      no one is changing anything

        • reply
        • like

        its all throug the GUI or the api

          • reply
          • like

          no real users we are protyping

            • reply
            • like

            Is there any errors with commands:

            sudo snap logs wekan.wekan
            sudo snap logs wekan.mongodb
              • reply
              • like

              Is there enough free disk space?

                • reply
                • like

                100 GB for Mongo

                  • reply
                  • like

                  12 GB for the file system without mongo

                    • reply
                    • like

                    Is server swapping? free -h

                      • reply
                      • like

                      looking

                        • reply
                        • like

                        nope

                          • reply
                          • like

                          not even close

                            • reply
                            • like

                            is node + mongo using high amount of CPU ? see with top

                              • reply
                              • like

                              Filesystem 1K-blocks Used Available Use% Mounted on udev 3920584 0 3920584 0% /dev tmpfs 786544 752 785792 1% /run /dev/nvme1n1p1 12131444 3802280 8312780 32% / tmpfs 3932716 0 3932716 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 3932716 0 3932716 0% /sys/fs/cgroup /dev/loop0 178048 178048 0 100% /snap/wekan/741 /dev/loop1 93568 93568 0 100% /snap/core/8592 /dev/nvme0n1 52403200 452108 51951092 1% /var/snap/wekan/common /dev/loop2 177920 177920 0 100% /snap/wekan/747 /dev/loop3 93568 93568 0 100% /snap/core/8689 /dev/loop4 18432 18432 0 100% /snap/amazon-ssm-agent/1480 tmpfs 786540 0 786540 0% /run/user/1000

                                • reply
                                • like

                                nope less than 1 %

                                  • reply
                                  • like

                                  no errors in logs for mongo at all

                                    • reply
                                    • like

                                    no real errors that I can see in wekan

                                      • reply
                                      • like

                                      mongo is obvious

                                        • reply
                                        • like

                                        mongod.27019[25214]: [conn5] received client metadata from 127.0.0.1:39612 conn5: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:26Z mongod.27019[25214]: [conn4] received client metadata from 127.0.0.1:39610 conn4: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:31Z mongod.27019[25214]: [conn5] received client metadata from 127.0.0.1:39612 conn5: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:31Z mongod.27019[25214]: [conn4] received client metadata from 127.0.0.1:39610 conn4: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:36Z mongod.27019[25214]: [conn4] received client metadata from 127.0.0.1:39610 conn4: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:36Z mongod.27019[25214]: [conn5] received client metadata from 127.0.0.1:39612 conn5: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:41Z mongod.27019[25214]: [conn4] received client metadata from 127.0.0.1:39610 conn4: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:41Z mongod.27019[25214]: [conn5] received client metadata from 127.0.0.1:39612 conn5: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:46Z mongod.27019[25214]: [conn4] received client metadata from 127.0.0.1:39610 conn4: { driver: { name: "nodejs", version: "2.2.9" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.15.0-1060-aws" }, platform: "Node.js v12.16.1, LE, mongodb-core: 2.0.11" } 2020-02-28T20:27:46Z mongod.2701

                                          • reply
                                          • like

                                          wekan logs are more confusing

                                            • reply
                                            • like

                                            I think there may be errors in wekan logs

                                              • reply
                                              • like

                                              here

                                                • reply
                                                • like

                                                that received client metadata is normal MongoDB message, it is not an error

                                                  • reply
                                                  • like