{"id":5567,"date":"2018-02-22T18:21:32","date_gmt":"2018-02-22T16:21:32","guid":{"rendered":"http:\/\/mummila.net\/kommentit\/?p=5567"},"modified":"2018-02-22T18:21:32","modified_gmt":"2018-02-22T16:21:32","slug":"i-have-two-systems-affected-with-the-following-specifics","status":"publish","type":"post","link":"https:\/\/mummila.net\/kommentit\/2018\/02\/22\/i-have-two-systems-affected-with-the-following-specifics\/","title":{"rendered":"I have two systems affected with the following specifics"},"content":{"rendered":"

@kubiko<\/a>\u00a0Thanks for taking a look!<\/p>\n

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:<\/p>\n

Server (though with Ubuntu desktop installed)<\/h3>\n

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\u00a0January 15th refresh<\/a>. I’ve since removed the snap along with the settings so the attempts on this system should in theory be clean installs.<\/p>\n

17.33 jani@battra:~$ uname -a\r\nLinux 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\r\n17.33 jani@battra:~$ snap version\r\nsnap    2.31\r\nsnapd   2.31\r\nseries  16\r\nubuntu  16.04\r\nkernel  4.4.0-112-generic\r\n17.33 jani@battra:~$ snap info core\r\nname:      core\r\nsummary:   snapd runtime environment\r\npublisher: canonical\r\ncontact:   snappy-canonical-storeaccount@canonical.com\r\nlicense:   unknown\r\ndescription: |\r\n  The core runtime environment for snapd\r\ntype:        core\r\nsnap-id:     99T7MUlRhtI3U0QFgl5mXXESAiSwt776\r\ntracking:    stable\r\ninstalled:   16-2.31 (4017) 85MB core\r\nrefreshed:   2018-02-06 17:18:04 +0200 EET\r\nchannels:                                  \r\n  stable:    16-2.31                (4017) 85MB -\r\n  candidate: 16-2.31.1              (4110) 85MB -\r\n  beta:      16-2.31.1              (4110) 85MB -\r\n  edge:      16-2.31+git586.d89ba3c (4127) 85MB -\r\n17.34 jani@battra:~$ snap list\r\nName  Version  Rev   Developer  Notes\r\ncore  16-2.31  4017  canonical  core\r\n<\/code><\/pre>\n
Main desktop<\/h2>\n
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).<\/p>\n
17.08 jani@saegusa:~$ uname -a\r\nLinux 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\r\n17.11 jani@saegusa:~$ snap version\r\nsnap    2.31.1\r\nsnapd   2.31.1\r\nseries  16\r\nubuntu  16.04\r\nkernel  4.13.0-36-generic\r\n17.11 jani@saegusa:~$ snap info core\r\nname:      core\r\nsummary:   snapd runtime environment\r\npublisher: canonical\r\ncontact:   snappy-canonical-storeaccount@canonical.com\r\nlicense:   unknown\r\ndescription: |\r\n  The core runtime environment for snapd\r\ntype:        core\r\nsnap-id:     99T7MUlRhtI3U0QFgl5mXXESAiSwt776\r\ntracking:    stable\r\ninstalled:   16-2.31 (4017) 85MB core\r\nrefreshed:   2018-02-06 17:18:04 +0200 EET\r\nchannels:                                  \r\n  stable:    16-2.31                (4017) 85MB -\r\n  candidate: 16-2.31.1              (4110) 85MB -\r\n  beta:      16-2.31.1              (4110) 85MB -\r\n  edge:      16-2.31+git586.d89ba3c (4127) 85MB -\r\n17.12 jani@saegusa:~$ snap list\r\nName  Version  Rev   Developer  Notes\r\ncore  16-2.31  4017  canonical  core\r\n<\/code><\/pre>\n
Since the issue with Wekan occurred, I’ve tried installing other snaps (on both systems) and they all work just fine.<\/p>\n
If there’s anything else you need or something I missed, please let me know and I’ll be happy to provide.<\/p>\n
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.<\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
I’m sure it’s a matter of configuration on these systems, and the issue is mainly just that of it not failing gracefully under the circumstances.<\/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":[14051,14042],"class_list":["post-5567","post","type-post","status-publish","format-standard","hentry","category-vianhallintajarjestelmat","tag-snap","tag-wekan","sijainti-github"],"_links":{"self":[{"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/posts\/5567","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=5567"}],"version-history":[{"count":3,"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/posts\/5567\/revisions"}],"predecessor-version":[{"id":5570,"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/posts\/5567\/revisions\/5570"}],"wp:attachment":[{"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/media?parent=5567"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/categories?post=5567"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mummila.net\/kommentit\/wp-json\/wp\/v2\/tags?post=5567"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}