=== c74d is now known as Guest68804 === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [06:36] Hi [06:36] I replaced a fresh snappy on my BBB, updated ubuntu-core 3 to 4, installed docker and then owncloud [06:36] But owncloud is still not working on port 443! http://paste.ubuntu.com/12077510/ [06:36] Did I missed something? === chihchun_afk is now known as chihchun [06:40] Anyone knows how to use owncloud?! [06:45] When I run owncloud, docker can't find owncloud locally and it download from docker repo! http://paste.ubuntu.com/12077534/ === Rlyeh is now known as Rlyehh [06:51] No idea for owncloud? [07:05] hi [07:06] is there a way for a snap to know which other snaps are installed on the system or are the snaps completely isolated from each other? [07:07] good morning [07:08] morning, fgimenez [07:08] hey tasdomas [07:32] good morning === erkules_ is now known as erkules [10:00] are there any service discovery solutions for snappy? Both internally (snaps discovering other snaps) and externally (other wireless devices discovering services running on snappy [10:02] well, netstat is installed by default :) [10:02] (nothing hiher level yet, no) [10:03] *higher [10:06] Hi everyone, I'm not able to make a snap with snapcraft out of a python script that requires opencv, I've tried several plugins python2-project, python3-project, ubuntu, but it doesn't include the library. [10:06] has this something to do with the setup.py? === greyback__ is now known as greyback [10:25] Question - what is the preferred way to load additional kernel modules in snappy? [10:25] in normal Ubuntu i just cat them at the end of /etc/modules ... [10:27] you ship them in your devce tarball [10:27] or gadget snap later ... [10:28] no way to do this from a snap? So stuff like that always needs oem? [10:28] yes [10:28] well, kernel/device [10:28] oem is bootloader only currently [10:28] right [10:29] for now i'd just ship system/etc/modules in the device tarball [10:29] yes i can do that [10:29] i read through the webcam example [10:29] it seems to expect that the driver for the webcam gets loaded automatically [10:30] yeah [10:30] so i was wondering if there is a way for manual driver loading for other stuff [10:31] i think we'll have that via snappy-config at some point ... i.e. you can ship multiple modules and define which ones are loaded through a config hook [10:31] yes that would make sense [10:31] once we have snappified the device tarball side [10:32] yay [10:32] (RaspberryPi2)ubuntu@localhost:~$ df -h|grep oem [10:32] /dev/sda1 15G 813M 14G 6% /oem [10:32] 16G writable space :) [10:32] yah! [10:32] on USB stick [10:32] so what did you do? [10:33] moved oem to usb stick? [10:33] just format it ext4, label it writable, copy the SD writable content over and re-label the SD writable to old-writable [10:33] right, so snappy auto mounts stuff? [10:34] well, on boot [10:34] i did the above on a PC :) [10:34] and then booted with USB and SD ... [10:35] we mouont by label ... so switching the writable bts to a bi 3TB USB disk is easy [10:35] i just needed to test it (i want to blog about it) [10:35] ah ok understand [10:36] any news on getting snappy to automatically expand the partition on boot? [10:36] working on it :) [10:36] cool [10:36] i hope ot have that landed next week in the rolling channel [10:37] * ogra_ tries some fun stuff on the side with https://github.com/paimpozhil/DockerX2go/tree/master/xubuntu [10:37] :) [10:37] i guess i should switch to whatever becomes snappy 15.10 at some point [10:38] not sure there will be a snappy 15.10, currently we are backporting all backportable bits to 15.04 [10:38] ogra_: ok - well i do not care about the version really so long as i am on the latest [10:38] could well be that we directly go to 16.04 then with the next iteration of the stable channel [10:39] * ogra_ knows there are some release plans ... but i cant find them atm [10:40] ogra_: btw i ended up creating some unconfined snaps to handle some internal stuff - should i try hard to avoid unconfined stuff? [10:40] well, i would ... but i want my snaps in the store without delays :) [10:40] ogra_: things need to read all kinds of things from /proc for example [10:41] ogra_: and i am currently skipping the work to create custom profiles for this and just leave it unconfined [10:41] * longsleep wonders if that is a problem [10:41] i think the planned sub-store setup together with the oem snap will help here [10:41] in such a sub store you can break out of confinement if you want afaik [10:42] since you make the rules for it [10:42] dont quote me on that though :D [10:42] ogra_: we will try it out for sure :) [10:43] ogra_: unconfined snaps cannot go into the store at all or is it a matter of review only? [10:43] completely unconfined cant i think ... [10:43] (well, technically they can ... thats indeed a policy thing) [10:43] not that i am going to submit those at the moment but eventually it might be nice to have [10:44] as i said, with your ownb sub-store it should be possible since i guess you make the rules abouot what goes in there [10:44] right [10:45] so if adjustment to the confinement policy is needed by your oem setup that should be possible [10:46] * ogra_ hopes someone corrects him if he talks rubbish :) [10:46] well let me try to avoid unconfined for the next snap, though for this need to understand the assing block in the yaml [10:46] but first - lunch! [10:46] enjoy ! [10:46] thanks [11:03] hmm [11:03] sergiusens, we need a way to ship sysctl settings in the kernel snap ... [11:04] * ogra_ just notices that the RPi NIC exposes the typical smsc95xx where you need to adjust the vm.min_free_kbytes default to make it not drop frames [11:04] ogra_: yes - i need that - currently fusing them into initrd :/ [11:04] such an old bug ... :/ [11:04] ogra_: I did sort of mentioned that to lool [11:04] ogra_: I'm just waiting for the new snap formats to show up [11:05] cool [11:05] i guess it currentrly is possible via the device tarball [11:05] (shipping a file in system/etc/sysctl.d/ ....) [11:05] yes - that works though is too late for some settings [11:06] (thats why i currently have them all in initrd hook) [11:07] https://bugs.launchpad.net/linux-linaro/+bug/664477 [11:07] Launchpad bug 664477 in Linaro Linux "System hangs due to cascade of smsc95xx errors " [Medium,Fix released] [11:07] 2011 [11:08] oh, even reported in 2010 [11:08] and that happens on rpi2 as well? [11:08] it is a hardware thing [11:09] ah they have the same nic [11:09] well, or a kernel defaults one ... [11:09] depends which way you look at it :) [11:14] * ogra_ files bug 1484898 [11:14] bug 1484898 in Snappy "device tarball needs to allow setting sysctl defaults" [Undecided,New] https://launchpad.net/bugs/1484898 [11:15] bah [11:15] time="2015-08-14T11:12:17Z" level=fatal msg="Error response from daemon: Cannot start container 22626e0f94cf7ea90bd53faf37a8526676e2a572dc16b045a74e428e9d8d8b3b: [8] System error: exec format error" [11:15] (RaspberryPi2)ubuntu@localhost:~$ [11:15] *sniff* [11:16] dholbach: python-apt upstream now includes the verbosity fix [11:16] armf vs x86_64 [11:16] dholbach: dunno where to go from here -- resync? [11:16] dholbach: that is: it's in the debian/sid branch of debian's git thing [11:17] Chipaca, let's wait for mvo to land it in ubuntu then [11:17] he knows which branch to merge and what to upload [11:17] longsleep, yeah [11:17] dholbach: okie doke [11:18] :) === chihchun is now known as chihchun_afk [11:46] yay snappy has 'netcat-openbsd' available - is that intentional or accident? [11:48] neither :) [11:48] it is inherited from the ubuntu-core seeds [11:49] so should i use it from the system or rather have my own python netcat in each snap? [11:49] might be ripped out and become part of comfy ... dont rely on it being there [11:49] all right [11:50] its so handy to pipe stuff into sockets for testing .. [11:50] systemd, kernel and the snappy binary are the only guaranteed bits in the core :) [11:50] (and the glue necessary to make them work, but that glue can change at any time) [11:50] well i guess all the stuff from the default aa profile is pretty much solid [11:52] by the way, sideloading snaps with snappy-remote has a bug. Id does not wait for services to stop before replacing files leading to 'text file busy' issues [11:52] i thnk i have seen that with local sideloading too [11:53] might be a general race [11:53] oh? [11:53] (just exposed stronger via remote) [11:53] that sounds like a bug :) [11:53] it annoys me pretty hard at the moment :) [11:53] Chipaca, yes, i only noticed it yesterday when playin with my broken xorg stuff [11:54] "stop" waits [11:54] http://paste.ubuntu.com/12078757/ [11:54] and i'm pretty sure "remove" calls stop [11:54] (where i had syslog tailed permanently in a separate window ... sometimes it didnt stop the running process in time and fell over) [11:54] i mean, i wrote it that way :) but maybe we broke it? [11:55] if that happens one has to remote the snap two more times [11:55] first time after the error service gets not started [11:55] well, we stop the service ... but that service runs a wrapper that runs a shell script (in my case at least) which in turn runs a subcommand ... [11:55] third time everything works fine [11:56] it sounds like that is unpacking into the current directory [11:56] hmm [11:56] longsleep, thats exactly the same i have seen yesterday [11:57] Chipaca: syslog here: http://paste.ubuntu.com/12078774/ [11:57] (it does not stop the service) [11:58] lovely D: [11:59] so [12:00] sideloading is treated differently, in that the usual "is installed" check is skipped [12:00] because otherwise it slows you down (you'd have to remove the package manually before re-sideloading it) [12:00] however that does mean it's not really expecting this error [12:01] longsleep: how reproducible is this? [12:01] longsleep: if i'm understanding the error correctly, bumping the version would "fix" it [12:01] longsleep: where i'd consider that a workaround more than a fix, but [12:01] good enough to confirm that that is what's happening [12:01] i think [12:01] :) [12:02] i have seen it a lot yesterday [12:02] i would say about a third of my install attempts showed it [12:02] yeah [12:02] the unpack is done before the activate/deactivate [12:02] and in fact it's done straight to the directory it'll work from [12:03] which makes sense, as some of the checks then rely on that [12:03] the checks done before activation [12:03] the directrory is gone after the failure though [12:03] however when sideloading it's an issue [12:03] something seems to wipe it [12:03] well, yes [12:03] installation cleans up on failure [12:03] and as it's not coping with reinstallation of the same version at all [12:04] ... well, i don't need to spell it out :) [12:04] :) [12:04] so, either we block sideloading of the same version [12:04] or we cope with it properly [12:05] the current situation is a recipe for heartache [12:05] it doesnt onyl happen with the same version (i need to bump the version when changing sccomp or apparmor profiles) [12:05] ogra_: wat [12:06] ogra_: i'd love to see the error when it's a different version! [12:06] it surely can't be the same :) [12:06] (if it is, something is seriously wrong, not just a cornercase bug) [12:08] i'd give you the log, but since the broken service was starting in a loop that wont be much helpful [12:08] (over like 4h or so) [12:09] i'll write it down to you not having had lunch until i see logs :-p [12:10] Chipaca: it fails very time [12:10] longsleep: and if you bump the version? [12:10] let me try [12:10] ta [12:11] that should work i assume [12:11] it failing in a different way would be interesting [12:11] (RaspberryPi2)ubuntu@localhost:~$ sudo ls -lh /var/log/syslog [12:11] -rw-r----- 1 syslog adm 13M Aug 14 12:10 /var/log/syslog [12:11] it failing in the *same* way would be *very interesting* [12:11] hmm, dont we have logrotate in place ? [12:11] (the log starts on the 7th) [12:12] Chipaca: did not fail but now it runs twice :) [12:12] Chipaca: the old version still runs [12:12] longsleep: ok [12:12] longsleep: where it says "ok", read it in a tone of voice that implies serious non-OKness [12:12] :D [12:13] longsleep: how do you stop your service? [12:13] Chipaca: i let systemd take care of it [12:13] Chipaca: i assume it just kills it [12:13] it should [12:13] what's going on [12:13] longsleep: what does systemctl status tell you? [12:14] degraded [12:14] http://paste.ubuntu.com/12078864/ [12:15] from what i see in the logs, the old service never was stopped [12:15] and 'systemctl stop dotstar-leds_dotstar_0.0.1-1.service' just works, yes? [12:15] yes [12:16] dammit, i can't blame it on you :-) [12:16] heh [12:16] i'll file a bug, in penance [12:16] thanks :) [12:17] https://bugs.launchpad.net/snappy/+bug/1484922 [12:17] Launchpad bug 1484922 in Snappy "Sideloading a snap with a service does not stop the service of the old version" [Undecided,New] [12:18] now let's see if i can reproduce it [12:18] btw the reason my system is marged as degrated is none of my snaps but rather webdm because of bug 1466672 [12:18] bug 1466672 in Snappy 15.04 "webdm failed to start / Failed to listen 224.0.0.251:5353" [Undecided,New] https://launchpad.net/bugs/1466672 [12:20] yep [12:21] degraded means a unit failed [12:21] sergiusens: you around? [12:22] btw i find it strange that there is a poststop but no poststart in package-metadata yaml for services. [12:23] * longsleep would really like to run some things after the service started and without dash hackery [12:26] Chipaca: yeah [12:27] sergiusens: what's blocking https://code.launchpad.net/~chipaca/snappy/snappy-man/+merge/266203 do you know/remember? [12:28] longsleep: so, i can't reproduce the issue with snappy from wily edge. you're on 15.04 stable? [12:28] Chipaca: me [12:28] :-) [12:28] * Chipaca hugs sergiusens [12:28] Chipaca: yes [12:29] Chipaca: version 4 from stable channel [12:30] longsleep: 1.4? [12:30] oh, wait [12:30] this is not that [12:30] * Chipaca starts another kvm [12:30] Chipaca: ubuntu-core 2015-07-29 4 ubuntu [12:31] Chipaca: channel: ubuntu-core/15.04/stable [12:31] yep yep [12:31] the 1504 i had was something else :) [12:35] longsleep: also can't reproduce it with 15.04 rev 4 [12:35] longsleep: using the python xkcd webserver snap [12:35] Chipaca: do you have a service which is a binary file? [12:35] no [12:35] that's next [12:35] i think text files can always be replaced [12:36] but at least your service should run twice when you update to a new sideloaded version [12:36] (if that service can be run twice) [12:37] longsleep: this is with a different version, so replacing file should not be an issue [12:37] exactly, it's the running twice thing that i was trying for [12:38] ah [12:43] Chipaca: could be also related to snappy-remote - i am running 0.4-0ubuntu1build1 on trusty [12:43] is snappy-remote anything other than something that ssh's in and runns snappy with all the given args? [12:43] longsleep: Chipaca snappy-remote just uses the snappy binary on the host [12:43] exactly [12:44] i imagin it as a two-line shellscript [12:44] the problem is in snappy itself [12:44] Chipaca: dream all you want :-P [12:44] :) [12:44] sergiusens: :) [12:45] sergiusens: see, if instead of having an option for the host you took it from environ, you could've made it a oneliner :-p [12:45] ssh ${SNAPPY_REMOTE_HOST:?Set SNAPPY_REMOTE_HOST to what to ssh to} -- "$@" [12:46] done \o/ [12:46] oh, add a "snappy" before the $@ [12:46] * Chipaca does not have enough :-P to sprinkle into that [12:48] the go-example-webserver in snappy-examples is broken \o/ [12:49] ah, maybe i need to build it properly :-) [12:49] picky, pikcy [12:52] i wonder if this is something on arm only? [12:53] Chipaca: that example is also problematic as it will fail to run twice [12:53] because on amd64 i can't get it to break [12:53] (becasue of port already in use) [12:53] longsleep: ah! [12:53] * longsleep has problems with the order of letters today [12:53] maybe? [12:54] * Chipaca adds a ports section [12:54] Chipaca: well with the go service you should get the text file busy problem [12:55] longsleep: not with different versions [12:55] it's two separate issues [12:55] right [12:55] the text file busy one is due to how we (don't) handle sideloading of the same version [12:55] really? Why - if the service would stop there would be no text file busy problem [12:55] the two services of different versions of the same app is really worrying [12:56] longsleep: on install, first we unpack, then we do some checks, then we stop the old version and start the new one [12:56] Chipaca: ah ok [12:56] longsleep: :) [12:59] longsleep: so one workaround for that would be to, on sideload, stop before unpack [12:59] longsleep: because sideload install is not going to happen automatically, so the downtime is more tolerable [12:59] maybe also don't clean up on sideload install failure [13:00] slightly uncomfortable about making the two so different though [13:00] rsalveti: sergiusens: opinion about ^? [13:03] good morning. [13:04] Chipaca: I thought we wanted to kill the version on sideload installs and just create a hash [13:05] we did? i have no memory of that [13:05] but that does not mean we didn't :) [13:06] Chipaca: maybe you weren't there :-P [13:07] Chipaca: but the version is meaningless and this sort of solves people accidentally hardcoding stuff during development [13:13] longsleep: can i have a pastebin of you doing the snappy remote of an updated version that resulted in two services running, please? [13:13] Chipaca: i do not know why, but now it did stop the old service when i installed a new version [13:13] sigh [13:13] longsleep: ok [13:13] Chipaca: it might be related to the failure before [13:13] longsleep: so, how about this [13:13] let me try to reproduce [13:13] longsleep: you tried to install the same thing [13:13] longsleep: it aborted because of text file thing [13:13] longsleep: but cleaned up -- removed files [13:14] longsleep: service still running, because who cares the file was rm' [13:14] ed [13:14] let me try - should be easy to replicate [13:14] longsleep: installed, snappy did not find old thing, did not try to disable service [13:14] so that would result in two services [13:14] as a consecuence of the text file thing [13:14] most likely yes [13:14] without it being a whole separate problem [13:14] i am on it [13:14] thank you [13:15] starting from clean state now [13:15] fgimenez: yesterday I was looking at the subunit tools. With what you have in that parser branch, it should be really easy to integrate with calls to subunit-output. [13:16] Chipaca: yes it just failed to install, removed the stuff and the service is still running [13:16] os i see the process and the file is gone [13:17] that makes sense [13:17] Chipaca: yes reproduced - it only runs twice when the text file busy error happend [13:17] fgimenez: let me know when you are done with the parsing and I can start piping the subunit output to a file. [13:17] longsleep: that's a relief :) thank you! [13:17] elopio: great, only the binary encoding is missing [13:17] longsleep: it does make fixing the text file thing in stable more important [13:18] sergiusens: do we want to do the version hash thing in stable? or just workaround this there? [13:18] Chipaca: yes - for development this can result in all kind of issues [13:18] yep [13:18] elopio: there's already a file step in the pipeline, we can remove it if needed [13:19] longsleep: for the time being, can you include 'snappy-remote yadda yadda remove the thing' before a same-version install? [13:19] Chipaca: sure [13:19] snappy-remote --url=ssh://10.1.7.161 remove dotstar-leds && snappy-remote --url=ssh://10.1.7.161 install dotstar-leds_0.0.1-1_armhf.snap [13:19] or sth like that :) [13:20] yeah should do the trick [13:20] let me try [13:20] Unknown command `remove'. You should use the install command [13:20] :D [13:21] sergiusens: wat ^ [13:21] * Chipaca no habla snappy-remote [13:21] lol [13:21] its just a two linne shellscript [13:21] :P [13:21] that's my mental model of it! [13:21] and if it were, that would've worked [13:21] so my mental model needs updating :) [13:22] fgimenez: oh, so what you have in parser.go is like the subunit v1 protocol, right? [13:22] or the shellscript needs a third line :) [13:23] ogra_: tomeito, tomahto [13:23] :D [13:23] elopio: yep, that should connect with the binary encoder in its next field [13:23] snappy-remote *only* knows install [13:24] longsleep: how about: ssh ubuntu@10.1.7.161 sudo snappy remove dotstar-leds && snappy-remote --url=ssh://10.1.7.161 install dotstar-leds_0.0.1-1_armhf.snap [13:24] elopio: and the binary encoder with the file, or stdout, in the next field [13:24] * Chipaca does not know if snappy-remote keeps keys in a nonstandard place, but maybe that'll work :) [13:25] Chipaca: sure [13:26] Chipaca: that works just fine [13:27] though i found another issue with that snap .. :/ [13:27] problem is that SNAP_APP_TMPDIR=/tmp [13:27] where it should be export TMPDIR="/tmp/snaps/dotstar-leds.sideload/0.0.1-3/tmp" [13:28] longsleep: are you sure? [13:28] i thought stable already had the private tmp fix? [13:28] elopio: not sure if the binary encoding step is a must [13:28] Chipaca: yeah try hello-world.env [13:28] fgimenez: so I think that if we use subunit-output to generate the v2 stream, we can combine the parser.go and binary.go. Not sure if you'll like this idea though. [13:28] longsleep: sure, let me check [13:28] longsleep: stable already has the private /tmp fix [13:28] longsleep: all of /tmp is yours [13:29] longsleep: and /tmp will be actually a private mount of /tmp/snap.$UID_$APPID_$RANDOM [13:29] /tmp [13:29] mhm i write stuff here SOCKET=$SNAP_APP_TMPDIR/dotstar_socket into the service [13:29] longsleep: so if you look at /tmp you should see a bunch of "snap.0_somthing.sideload_Xyws/ [13:29] from the service i mean [13:29] Chipaca: yes i see them [13:29] longsleep: whereas the old tmpfile was /tmp/snaps/ [13:29] writing them from the service works fine [13:29] longsleep: so you'd see /tmp/snaps [13:30] longsleep: now [13:30] but in the binary tmp points just to /tmp [13:30] which does find nothing [13:30] longsleep: we do still set /tmp/snaps, for backwards compat, so that would be /tmp/snap.0_something.sideload_yadda/tmp/snaps/something.sideload/version/tmp [13:32] longsleep: ah, you mean SNAP_APP_TMPDIR is different in the service and in the binary? [13:33] that is entirely possible :-( [13:33] hold on i am trying clean setup [13:33] longsleep: um [13:33] longsleep: are you expecting to find the same things in tmp from both service and binary? [13:33] because it'll be a _different_ tmpdir every time [13:33] Chipaca: yes [13:34] ah [13:34] well, then i got a problem :) [13:34] longsleep: tell me more [13:34] Chipaca: service creates a unix socket file [13:35] Chipaca: i need that socket location from a binary [13:35] longsleep: $SNAP_APP_DATA_PATH ? [13:35] elopio: whatever works :), where can i read about subunit-output? [13:35] Chipaca: i would prefer if that file is not persistent [13:35] fgimenez: sudo apt-get install subunit-output [13:35] subunit-output -h [13:36] Chipaca: i thought there is a per snap temp folder [13:36] fgimenez: it even allows to attach files to the results. [13:36] longsleep: that's a very interesting use case, because i think ted was asking why we'd have SNAP_APP_DATA_PATH and SNAP_APP_USER_PATH at the same time, and that's one case where you'd want it (module persistence) [13:36] Chipaca: what is how i understood the name SNAP_APP_TMPDIR [13:36] ted: ^^^ there you go, a use case :) [13:36] * ted reads backlog for this "use case" ;-) [13:37] Yeah, for something like that you probably want something per-snap in /run [13:37] ted: yes - though that does not seem to exist [13:37]