Avainsanana Snap

Checklist item gets overwritten by previous item when selecting another item with mouse

20. toukokuuta 2019 klo 17.28
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Chrome, Firefox, Snap, Wekan

When a checklist item is in edit mode (through the specific steps below), selecting another item for editing does not take the previous item out of edit mode, and upon selecting a third item (or pressing enter) causes the second item to be overwritten by whatever content is in the first selected item.

Server Setup Information:

  • Wekan version: 2.74
  • Operating System: Ubuntu 16.04
  • Deployment Method: snap (stable)
  • Http frontend if any: Apache 2.4
  • ROOT_URL environment variable: https://my-domain.com/kan

Problem description:

Steps to reproduce

  1. Have a card with a checklist with 4 (or more) items with contents A, B, C, D (and so on):
  2. Select item A with LBM
  3. Select item B with LBM
  4. Select item C with LBM
  5. Select item D with LBM

What happens
At step 4, when C opens for editing, B remains in edit mode. At step 5, contents of C are overwritten by contents of B (that is, ”C” becomes a ”B”).

What I expect to happen
At step 4, for B to leave edit mode, and at step 5, the contents of C to remain as they are.

Other notes

  • Reproducible in both Chrome and Firefox.
  • Curiously, this does not seem to affect the firstly selected item: in step 3 above, A leaves edit mode correctly and thus B doesn’t get overwritten by the contents of item A in step 4.
  • At step 5, instead of selecting item D, pressing enter has the same effect.

Browser console output
empty

snap logs wekan.wekan
nothing related

Vastaa viestiin sen kontekstissa (Github)

Wekan’s mongodb.log grows pretty large (unlimited?)

4. toukokuuta 2019 klo 21.35
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: MongoDB, Snap, Wekan

I noticed my mongodb.log has grown pretty large:

root@battra:~# ls -lh /var/snap/wekan/common/mongodb.log
-rw-r--r-- 1 root root 3,1G touko  4 21:14 /var/snap/wekan/common/mongodb.log

The first lines in the log are timestamped 2018-03-02T16:39:44.754+0200.

Should the log rotate automatically, but doesn’t for some reason? Alternatively, should I truncate it manually (and if so, how)? I have no use for the logs apart from the occasional bug reports here, so even losing all of it is fine.

There are no related mongodb settings keys AFAICS. (And sorry if this is unrelated to snap packaging, it was just a guess on my part.)

Server Setup Information:

  • Wekan version: 2.65
  • Operating System: Ubuntu 16.04
  • Deployment Method: snap
  • Http frontend if any: Apache 2.4

Vastaa viestiin sen kontekstissa (Github)

As a workaround, copying the logos and manifest to the root seems to work

16. joulukuuta 2018 klo 9.16
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Apache, Snap, Wekan

As a workaround, copying the icons and manifest from public to domain root seems to work (with Wekan snap running behind Apache here). As the files have a wekan- prefix, collisions shouldn’t be an issue. Naturally, this solution does require write access to the domain root directory.

Vastaa viestiin sen kontekstissa (Github)

That gives me confidence in running the snap on my main server again

2. maaliskuuta 2018 klo 19.09
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Snap, Wekan

@kubiko That’s good to hear, gives me confidence in running the snap on my main server again (instead of the VM). Thanks again guys!

Vastaa viestiin sen kontekstissa (Github)

Here’s hoping those fixes hit the spot!

2. maaliskuuta 2018 klo 17.06
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Snap, Wekan

@xet7 Alright, here’s hoping those fixes hit the spot! Thanks a lot.

Vastaa viestiin sen kontekstissa (Github)

And now, suddenly, it just works

2. maaliskuuta 2018 klo 16.57
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Snap, Wekan

And now, suddenly, it just works again.

root@saegusa:~# snap install wekan
wekan 0.77-29-g9e62584 from 'xet7' installed

root@battra:~# snap install wekan
2018/03/02 16:39:13.986937 cmd.go:212: DEBUG: restarting into "/snap/core/current/usr/bin/snap"
wekan 0.77-29-g9e62584 from 'xet7' installed

Darn it, I was hoping to catch the exact cause. Unless you guys already found and fixed it?

What’s changed on my end since I posted the last comment a week ago is the core snap updating from 4017 to 4110.

Vastaa viestiin sen kontekstissa (Github)

Output from snap changes and snap change below, syslog output attached

23. helmikuuta 2018 klo 8.59
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Snap, Wekan

@kubiko Output from snap changes and snap change below, syslog output (with snapd debugging enabled) attached here.

root@battra:~# snap changes
ID   Status  Spawn                 Ready                 Summary
30   Error   2018-02-22T09:55:45Z  2018-02-22T10:02:02Z  Install "wekan" snap from "edge" channel
31   Error   2018-02-22T10:27:51Z  2018-02-22T10:33:04Z  Install "wekan" snap from file "wekan_0.76-22-g31f25bc_amd64.snap"
32   Error   2018-02-22T12:05:21Z  2018-02-22T12:10:33Z  Install "wekan" snap from file "wekan_0.76-22-g31f25bc-dirty_amd64.snap"
33   Error   2018-02-22T12:12:20Z  2018-02-22T12:17:32Z  Install "wekan" snap from file "wekan_0.76-22-g31f25bc-dirty_amd64.snap"
34   Error   2018-02-22T12:25:15Z  2018-02-22T12:30:28Z  Install "wekan" snap from file "wekan_0.76-22-g31f25bc-dirty_amd64.snap"
35   Error   2018-02-22T15:28:37Z  2018-02-22T15:33:54Z  Install "wekan" snap
36   Error   2018-02-23T06:24:32Z  2018-02-23T06:31:05Z  Install "wekan" snap

root@battra:~# snap change 36
Status  Spawn                 Ready                 Summary
Done    2018-02-23T06:24:32Z  2018-02-23T06:31:05Z  Ensure prerequisites for "wekan" are available
Undone  2018-02-23T06:24:32Z  2018-02-23T06:31:05Z  Download snap "wekan" (128) from channel "stable"
Done    2018-02-23T06:24:32Z  2018-02-23T06:31:04Z  Fetch and check assertions for snap "wekan" (128)
Undone  2018-02-23T06:24:32Z  2018-02-23T06:31:04Z  Mount snap "wekan" (128)
Undone  2018-02-23T06:24:32Z  2018-02-23T06:31:03Z  Copy snap "wekan" data
Undone  2018-02-23T06:24:32Z  2018-02-23T06:31:03Z  Setup snap "wekan" (128) security profiles
Undone  2018-02-23T06:24:32Z  2018-02-23T06:31:02Z  Make snap "wekan" (128) available to the system
Undone  2018-02-23T06:24:32Z  2018-02-23T06:31:01Z  Set automatic aliases for snap "wekan"
Undone  2018-02-23T06:24:32Z  2018-02-23T06:31:01Z  Setup snap "wekan" aliases
Done    2018-02-23T06:24:32Z  2018-02-23T06:31:01Z  Run install hook of "wekan" snap if present
Undone  2018-02-23T06:24:32Z  2018-02-23T06:31:01Z  Start snap "wekan" (128) services
Error   2018-02-23T06:24:32Z  2018-02-23T06:31:00Z  Run configure hook of "wekan" snap if present

......................................................................
Run configure hook of "wekan" snap if present

2018-02-23T08:31:00+02:00 ERROR run hook "configure": <exceeded maximum runtime of 5m0s>

Vastaa viestiin sen kontekstissa (Github)

I have two systems affected with the following specifics

22. helmikuuta 2018 klo 18.21
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Snap, Wekan

@kubiko Thanks for taking a look!

I have two systems affected by this, both running Ubuntu 16.04[.3] LTS desktop and both tracking the core snap, with the following specifics:

Server (though with Ubuntu desktop installed)

This system is running stock 16.04 (no -proposed or HW) and Apache doing proxying. I had previously installed the snap on this system, set my root-url and changed the port to 3333 (IIRC), and it was running fine when the issue occurred sometime around the January 15th refresh. I’ve since removed the snap along with the settings so the attempts on this system should in theory be clean installs.

17.33 jani@battra:~$ uname -a
Linux battra 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
17.33 jani@battra:~$ snap version
snap    2.31
snapd   2.31
series  16
ubuntu  16.04
kernel  4.4.0-112-generic
17.33 jani@battra:~$ snap info core
name:      core
summary:   snapd runtime environment
publisher: canonical
contact:   snappy-canonical-storeaccount@canonical.com
license:   unknown
description: |
  The core runtime environment for snapd
type:        core
snap-id:     99T7MUlRhtI3U0QFgl5mXXESAiSwt776
tracking:    stable
installed:   16-2.31 (4017) 85MB core
refreshed:   2018-02-06 17:18:04 +0200 EET
channels:                                  
  stable:    16-2.31                (4017) 85MB -
  candidate: 16-2.31.1              (4110) 85MB -
  beta:      16-2.31.1              (4110) 85MB -
  edge:      16-2.31+git586.d89ba3c (4127) 85MB -
17.34 jani@battra:~$ snap list
Name  Version  Rev   Developer  Notes
core  16-2.31  4017  canonical  core

Main desktop

This system has the -proposed repository enabled and the HWE stack installed, no proxy. I’ve only ever attempted to install Wekan on this system after the issue occurred on the other system, and it has never succeeded (so in that sense it’s a clean install… attempt anyway).

17.08 jani@saegusa:~$ uname -a
Linux saegusa 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
17.11 jani@saegusa:~$ snap version
snap    2.31.1
snapd   2.31.1
series  16
ubuntu  16.04
kernel  4.13.0-36-generic
17.11 jani@saegusa:~$ snap info core
name:      core
summary:   snapd runtime environment
publisher: canonical
contact:   snappy-canonical-storeaccount@canonical.com
license:   unknown
description: |
  The core runtime environment for snapd
type:        core
snap-id:     99T7MUlRhtI3U0QFgl5mXXESAiSwt776
tracking:    stable
installed:   16-2.31 (4017) 85MB core
refreshed:   2018-02-06 17:18:04 +0200 EET
channels:                                  
  stable:    16-2.31                (4017) 85MB -
  candidate: 16-2.31.1              (4110) 85MB -
  beta:      16-2.31.1              (4110) 85MB -
  edge:      16-2.31+git586.d89ba3c (4127) 85MB -
17.12 jani@saegusa:~$ snap list
Name  Version  Rev   Developer  Notes
core  16-2.31  4017  canonical  core

Since the issue with Wekan occurred, I’ve tried installing other snaps (on both systems) and they all work just fine.

If there’s anything else you need or something I missed, please let me know and I’ll be happy to provide.

I’m fairly sure it’s a matter of some configuration these two systems happen to have, and the Wekan snap issue is mainly just that of it not failing gracefully under the circumstances and leaving me in the dark about the exact cause.

 

Vastaa viestiin sen kontekstissa (Github)

Still not fixed I’m afraid

22. helmikuuta 2018 klo 14.30
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Snap, Wekan

Still no fix I’m afraid, but watching /var/snap/wekan/common/hook.log did provide a clue. The hook appears to get stuck at snapctl get caddy-enabled, after that there are no more entries.

I tried tweaking the hook by replacing value=$(snapctl get caddy-enabled) with value="", but installing the resulting snap then just gets stuck at the next snapctl call:

+ '[' '' = true ']'
+ snapctl stop --disable wekan.caddy

There’s also an ’error running snapctl: unknown service: ”caddy-service”’ line in syslog, but this seems to occur just alike on systems where the installation does not get stuck, so I’m not sure if it’s relevant.

 

Vastaa viestiin sen kontekstissa (Github)

Over at Launchpad, Jamie Strandboge had this to say

21. helmikuuta 2018 klo 19.32
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Jamie Strandboge, Launchpad, Snap, Wekan

Over at Launchpad, Jamie Strandboge had this to say:

”As for install/refresh getting stuck, it seems that the wekan hooks aren’t exiting so snapd has no choice but to wait a while then timeout.

At this point, this seems like the issues are in the wekan snap: it needs to plug hardware-observe and needs to handle error conditions better in the hooks so the exit.”

Vastaa viestiin sen kontekstissa (Github)

Vanhempia »