Join the conversation

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

Wekan

Bugs

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

More active conversations

Wekan / Bugs

Update recently? deleting

Update recently? deleting

Wekan/Bugs · February 28, 2020 at 4:04pm

Paul Verdone

@pvcon13
rep
1.5k

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:25pm
Paul Verdone@pvcon13
8:25pm

nope

    • reply
    • like
    8:25pm

    not even close

      • reply
      • like
      Lauri Ojansivu@xet7
      Team
      8:25pm

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

        • reply
        • like
        Paul Verdone@pvcon13
        8:26pm

        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
          8:26pm

          nope less than 1 %

            • reply
            • like
            8:28pm

            no errors in logs for mongo at all

              • reply
              • like
              8:28pm

              no real errors that I can see in wekan

                • reply
                • like
                8:29pm

                mongo is obvious

                  • reply
                  • like
                  8:29pm

                  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
                    8:29pm

                    wekan logs are more confusing

                      • reply
                      • like
                      8:30pm

                      I think there may be errors in wekan logs

                        • reply
                        • like
                        8:30pm

                        here

                          • reply
                          • like
                          Lauri Ojansivu@xet7
                          Team
                          8:30pm

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

                            • reply
                            • like
                            Paul Verdone@pvcon13
                            8:30pm

                            root@ip-172-31-35-186:/snap/wekan/747/programs/server/packages# sudo snap logs wekan.wekan 2020-02-28T20:11:33Z wekan.wekan[23840]: at ns.Collection.remove (packages/mongo/collection.js:620:31) 2020-02-28T20:11:33Z wekan.wekan[23840]: at models/boards.js:1190:15 2020-02-28T20:11:33Z wekan.wekan[23840]: at Array.forEach (<anonymous>) 2020-02-28T20:11:33Z wekan.wekan[23840]: at boardRemover (models/boards.js:1188:62) 2020-02-28T20:11:33Z wekan.wekan[23840]: at Object.<anonymous> (models/boards.js:1394:5) 2020-02-28T20:11:33Z wekan.wekan[23840]: at packages/matb33collection-hooks.js:598:28 2020-02-28T20:11:33Z wekan.wekan[23840]: at Array.forEach (<anonymous>) 2020-02-28T20:11:33Z wekan.wekan[23840]: at Function..each._.forEach (packages/underscore.js:139:11) 2020-02-28T20:11:33Z wekan.wekan[23840]: at packages/matb33_collection-hooks.js:597:11 2020-02-28T20:11:33Z wekan.wekan[23840]: at Array.forEach (<anonymous>)

                              • reply
                              • like
                              8:31pm

                              yeah that is

                                • reply
                                • like
                                8:31pm

                                sudo snap logs wekan.wekan sudo snap logs wekan.mongodb

                                  • reply
                                  • like
                                  8:31pm

                                  as you requested

                                    • reply
                                    • like
                                    8:31pm

                                    I believe there is a breaking between mongo from wekan node.js

                                      • reply
                                      • like
                                      Lauri Ojansivu@xet7
                                      Team
                                      8:32pm

                                      Hmm, why it would try to remove Collection?

                                        • reply
                                        • like
                                        8:32pm

                                        That is strange

                                          • reply
                                          • like
                                          Paul Verdone@pvcon13
                                          8:32pm

                                          yeah

                                            • reply
                                            • like
                                            Lauri Ojansivu@xet7
                                            Team
                                            8:32pm

                                            It would be like removing table from database. That does not make sense.

                                              • reply
                                              • like
                                              8:33pm

                                              I'll look at what is at those lines of code

                                                • reply
                                                • like
                                                Paul Verdone@pvcon13
                                                8:33pm

                                                I use api to create cards with members with webhook with list with cards

                                                  • reply
                                                  • like
                                                  8:33pm

                                                  then I move the cards around in wekan and capture the web hooks

                                                    • reply
                                                    • like