{"id":5528,"date":"2018-01-22T15:58:06","date_gmt":"2018-01-22T13:58:06","guid":{"rendered":"http:\/\/mummila.net\/kommentit\/?p=5528"},"modified":"2018-01-22T15:59:05","modified_gmt":"2018-01-22T13:59:05","slug":"install-refresh-stuck-at-configure-hook-wekan","status":"publish","type":"post","link":"https:\/\/mummila.net\/kommentit\/2018\/01\/22\/install-refresh-stuck-at-configure-hook-wekan\/","title":{"rendered":"Install\/refresh stuck at configure hook (Wekan)"},"content":{"rendered":"

Since some time over the holidays I’ve had problems refreshing\/installing the Wekan snap [1] on my home server and also my desktop. The installation stalls at the configuration phase, which on the surface looks a bit like bug #1674193<\/a> [2], but here core gets installed just fine, and the hang occurs just alike if I first install just core, then the `wekan` snap separately.<\/p>\n

14.52 jani@saegusa:~$ sudo snap install wekan
\n[sudo] salasana henkil\u00f6lle jani:
\nerror: cannot perform the following tasks:
\n– Run configure hook of ”wekan” snap if present (run hook ”configure”: <exceeded maximum runtime of 5m0s>)<\/p><\/blockquote>\n

Installing other snaps works (the couple that I tried just to be able to say this did anyway).<\/p>\n

I’ve reported this on the Wekan snap Github page [3], but there’s been no confirmation from anyone else affected so far. Also, I’m unable to reproduce this myself in a VM and on at least one other (physical) desktop I have access to.<\/p>\n

So naturally I’ve looked for differences between these systems, but so far the only correlating one I’m pretty sure of is an Apparmor denial:<\/p>\n

apparmor=”DENIED” operation=”open” profile=”snap.wekan.mongodb” name=”\/sys\/block\/” pid=9478 comm=”mongod” requested_mask=”r” denied_mask=”r” fsuid=0 ouid=0<\/p><\/blockquote>\n

The two systems where Apparmor denies mongodb’s access to \/sys\/block get stuck at the configure hook, whereas systems that don’t deny access finish the configuration (and installation) successfully.<\/p>\n

I have not tweaked any Apparmor configuration on any of these systems prior to this issue cropping up (not that I can remember anyway). I’ve also not touched anything snap-related, as Wekan was one of the first snaps I’ve ever tried and is (or would be) the only one (besides core) currently installed on these systems.<\/p>\n

All systems are running Ubuntu 16.04, with my (affected) desktop having both HWE and -proposed enabled, my (affected) server running a 4.4-series kernel (no HWE or -proposed) and the other (unaffected) desktop having HWE but no -proposed. The (unaffected) VM starts with kernel 4.4 and remains unaffected if I upgrade it with HWE.<\/p>\n

I’m submitting this from the (HWE+proposed-enabled) desktop, so any logs attached here are from one of the two affected systems. I’ll of course provide other logs too if requested.<\/p>\n

* [1] https:\/\/snapcraft.io\/wekan\/<\/a>
\n* [2] https:\/\/bugs.launchpad.net\/snappy\/+bug\/1674193<\/a>
\n* [3] https:\/\/github.com\/wekan\/wekan-snap\/issues\/25<\/a><\/p>\n

ProblemType: Bug
\nDistroRelease: Ubuntu 16.04
\nPackage: snapd 2.29.4.2
\nProcVersionSignature: Ubuntu 4.13.0-30.33~16.04.1-generic 4.13.13
\nUname: Linux 4.13.0-30-generic x86_64
\nApportVersion: 2.20.1-0ubuntu2.15
\nArchitecture: amd64
\nCurrentDesktop: Unity
\nDate: Mon Jan 22 15:44:20 2018
\nInstallationDate: Installed on 2016-10-13 (466 days ago)
\nInstallationMedia: Ubuntu-Server 16.04.1 LTS ”Xenial Xerus” – Release amd64 (20160719)
\nSourcePackage: snapd
\nUpgradeStatus: No upgrade log present (probably fresh install)
\nmtime.conffile..etc.X11.Xsession.d.65snappy: 2018-01-19T18:18:12.001969
\nmtime.conffile..etc.apparmor.d.usr.lib.snapd.snap-confine.real: 2018-01-22T15:46:34.793893<\/p>\n","protected":false},"excerpt":{"rendered":"

The installation stalls at the configuration phase. The only hint I’ve found so far is an Apparmor denial of \/sys\/block access for snap.wekan.mongodb.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8860],"tags":[14065,14051,14042],"class_list":["post-5528","post","type-post","status-publish","format-standard","hentry","category-vianhallintajarjestelmat","tag-apparmor","tag-snap","tag-wekan","sijainti-launchpad"],"_links":{"self":[{"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/posts\/5528","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/comments?post=5528"}],"version-history":[{"count":7,"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/posts\/5528\/revisions"}],"predecessor-version":[{"id":5536,"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/posts\/5528\/revisions\/5536"}],"wp:attachment":[{"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/media?parent=5528"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/categories?post=5528"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/tags?post=5528"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}