=== xymox_ is now known as xymox
=== xymox is now known as xymox_
=== xymox_ is now known as xymox
=== alexlist` is now known as alexlist
* adie huggles TingPing 00:56
adiehi #ubuntu dev people, I have a problem in unity launcher API stuff, and I was wondering if you can help me out :O00:58
adieI am trying to set a msg count number in hexchat with python launcher.set_property ('count', count), and it works the first time, but if I reload the script is breaks like this: http://pastebin.com/raw.php?i=eudXgAcG00:59
adieI was wondering if there was something I can do to clear out whatever is preventing the script from working upon second launch01:00
sarnoldadie: you didn't miss any responses while gone..01:09
adieokay, ty :|01:09
sarnoldadie: still nothing while you were gone. perhaps try in twelve-sixteen hours, more people will be around01:25
adie:D maybe01:26
adiesorry for quit/join01:26
adiehave to restart the client to make the script work :D01:26
sarnoldah :) hehe01:26
TingPingadie, if only it were possible to have two clients open at the same time.. hmm01:26
adieTingPing, I wouldn't be surprised if this script would interfere with two client instances01:31
adietargeting the same external resource01:33
TingPingadie, well you would be wrong01:33
adieIsn't that the rule?01:33
adie"Adie is always wrong"01:33
TingPingthe error has something to do with loading the glib library from the the same python library twice i guess01:34
micahgadie: #ubuntu-unity might be of some help02:12
=== Nisstyre-laptop is now known as Nisstyre
=== Kk2 is now known as kk2
pittiSnow-Man: yes, unfortunately there is no way to ship a logrotate file which works on both < 3.8 and >= 3.8, so during package build we have to create a file for a particular version05:07
pittiSnow-Man: FYI, unstable will switch to 9.3 as soon as it gets released (beta2 just came out)05:07
pittiGood morning05:07
=== jamesh_ is now known as jamesh
mwhudsonapache2-mpm-worker-dbgsym seems to be uninstallable07:42
dholbachgood morning07:43
ubottuLaunchpad bug 1196440 in apache2 (Ubuntu) "apache2-mpm-worker-dbgsym is uninstallable" [Undecided,New]08:10
=== doko_ is now known as doko
=== tkamppeter__ is now known as tkamppeter
=== oSoMoN__ is now known as oSoMoN
=== MacSlow is now known as MacSlow|lunch
maxoiaojuncjwatson: ping11:23
cjwatsonmaxoiaojun: just leave your message directly, please11:24
maxoiaojuncjwatson: I believe pad.lv/1035136 is not fixed even on saucy, please try "/usr/lib/lsb/install_initd" if you have saucy box11:25
=== oSoMoN_ is now known as oSoMoN
xnoxbug #103513611:36
ubottubug 1035136 in lsb (Ubuntu Raring) "install_initd crashed with SyntaxError in __main__: invalid syntax" [Medium,Triaged] https://launchpad.net/bugs/103513611:36
cjwatsonmaxoiaojun: I've followed up in the bug.11:38
maxoiaojunthanks, i'm firing a saucy vm11:41
cjwatsonmaxoiaojun: A chroot should be enough.11:42
=== sraue_ is now known as sraue
jibelhallyn, stgraber with kernel 3.10 I get the following error when I create an LXC container12:08
jibel      lxc-start 1372673552.852 ERROR    lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/saucy-i386-20130701-1012/devices.deny : Invalid argument12:08
jibelhallyn, stgraber does this kernel requires a config change of the containers?12:09
jibelI don't see this error with 3.9.0-712:10
maxoiaojuna bit confused now12:10
maxoiaojunhttps://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/lsb/saucy/files and what installed on saucy box is different?12:10
xnoxmaxoiaojun: the new lsb is not in release pocket yet, above imports from release pocket with a propagation delay.12:12
hallynjibel: no, nothing like that should have changed.12:13
maxoiaojunxnox: but the bzr branch is behind what is actually installed12:14
jibelhallyn, okay, I'll report a bug12:14
cjwatsonI ignored the branch12:15
cjwatsonAlso, in any case, the files you're probably talking about are modified in debian/rules12:15
cjwatson(Looks like the branch is up to date otherwise)12:15
cjwatsonmaxoiaojun: https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/lsb/saucy/view/head:/debian/rules12:16
cjwatson$(twotothree) -n -w debian/lsb-core/usr/lib/lsb/*12:16
maxoiaojuni see12:17
cjwatsonNot the way I prefer to do things myself, but whatever12:18
maxoiaojunhow about raring and quantal then, I propose that we just change rules so that /usr/lib/usb will continue to use python 212:20
cjwatsonI'd rather we backported the fixes12:21
maxoiaojunbecause it's all rules magic12:23
maxoiaojuni guess just remove the python => python3 magic for /usr/lib/lsb/ is enough12:24
cjwatsonWell, whatever.  I'm not going to do the work here.  But I think it'd be wiser to bring quantal/raring more into line with saucy rather than going backwards, as a general principle of SRUing12:25
cjwatsonIt's already running 2to3 over things there so it's not that big a change to expand that12:26
cjwatsonAnd it would be a more direct backport12:26
cjwatsonSee bug 79819212:26
ubottubug 798192 in lsb (Ubuntu) "install_initd fails" [Undecided,Fix released] https://launchpad.net/bugs/79819212:26
cjwatsonIn fact this bug is a dup of that one, I think12:27
maxoiaojunindeed, but 2to3 is not enough for the scripts in quantal and raring I guess12:30
=== MacSlow|lunch is now known as MacSlow
maxoiaojunas someone mentioned "sudo sed -i "s/python3/python/" /usr/lib/lsb/install_initd"  as a workaround12:32
cjwatsonmaxoiaojun: The bug fixed in 4.1+Debian9ubuntu1 was that 2to3 wasn't run over the proper files.  Backport that12:32
maxoiaojuni see using tested python 2 code better than using untested 2to3 generated python 3 code12:32
cjwatsonI'm concerned about pulling python (2) back into environments where it wasn't needed before; and in general I prefer straight backports of what's in the development release for SRUs, where at all possible12:34
ogra_also testing happens in saucy anyway, if there are bugs, fices can be backported easily12:35
jibelhallyn, I filed bug 119651812:35
cjwatsonBut, as I say, I'm not the one who's going to be doing the work here, so you don't have to persuade me12:35
ubottubug 1196518 in lxc (Ubuntu) "lxc-start failed with lxc_cgroup - Invalid argument - write /sys/fs/cgroup/devices/lxc/<NAME>/devices.deny : Invalid argument with kernel 3.10" [Undecided,New] https://launchpad.net/bugs/119651812:35
jibelapw, ^12:35
xnoxdiverging further increases maintenance cost as the next fix will have to be written twice....12:35
ogra_xnox, ++12:36
maxoiaojunbut the python 2 code is well tested by debian i guess12:37
=== maxoiaojun is now known as maxiaojun
apwjibel, oh goodie12:37
ogra_maxiaojun, that doesnt make maintaining two patchesets less work12:38
maxiaojunbut the lsb package is already in different versions anyway12:39
maxiaojunyou can check the rules file, saucy one is very different from quantal/raring one12:39
maxiaojunyou know, saucy contains lsb4.1-blah while older releases all lsb4.012:40
hallynjibel: thanks12:42
ScottKbarry: I see that socket.error is now deprecated: http://www.python.org/dev/peps/pep-3151/ - Is it deprecated, but won't be dropped for a long time because it's widely used or deprecated and I better make sure I don't use it because it's going away soon?12:44
barryScottK: the former, most likely.  i wouldn't expect it to go away before 3.5 at the earliest, if ever12:45
ScottKbarry: Thanks.12:48
stgraberjibel: LXC appears to work fine here, can you pastebin your container config?12:55
=== _salem is now known as salem_
=== oSoMoN_ is now known as oSoMoN
=== Sweetsha1k is now known as Sweetshark
stgraberjibel: nevermind, just saw the bug report now13:22
barryxnox: ping13:32
xnoxbarry: hola =)13:32
barryxnox: hi!  there's a comment in emacs24 24.3+1-1ubuntu1: - debian/emacsVER.desktop: Also set StartupWMClass for bamf and gnome-shell.  have you by any chance seen the icon break for tab completion after this?13:33
barry 13:33
maxiaojunhttps://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1035136 branches linked13:35
ubottuLaunchpad bug 1035136 in lsb (Ubuntu Raring) "install_initd crashed with SyntaxError in __main__: invalid syntax" [Medium,Triaged]13:35
xnoxbarry: define break? after this patch the icon has become a beautiful svg emacs bubble with a fountain pen; before this patch it was an ugly pixalated xmp icon instead.13:35
xnoxbarry: what DE do you use?13:35
barryxnox: unity13:35
barryxnox: i get a nice big question mark on a beautiful gray background13:36
jibelstgraber, sorry was otp. The setup is a bit special because it uses 2 loop-mounted devices + an overlay13:36
xnoxbarry: i can quickly test in a clean / new environment.13:36
barryxnox: great, thanks.  i see it on two saucy desktops now13:36
jibelstgraber, but downgrading to 3.9.0-7 clearly fixed the problem and we could dozens of test without any issue.13:37
xnoxbarry: all works correctly in a saucy VM. Do you have custom .desktop files? are you launching emac24 or emacs which happens to be update-alternatives launching emacs24? are you starting emacs via upstart or some-such?13:50
ogra_hallyn, i need to link a dir across from the containers /dev to the hosts /dev (there are sockets the binary android blobs create) ... i used to use a link from /dev/socket into /proc/$lxc_pid/root/dev/socket but seems a normal user cant access that, any idea how to do that more elegant and with permission for normal users ?13:50
barryxnox: launching emacs via gnome do.  i wonder if that would matter13:51
barryxnox: nope13:51
xnoxbarry: emacs (symlink) or emacs24 ? can you type "emacs24" in gnome-do?13:52
barryxnox: so i see the right icon in both the hud when i use the launcher to start it, and in gnome do when i use that to start it13:52
barryxnox: but either of those, and starting from the shell, all give me broken icons13:52
xnoxweird. no idea.13:53
barrynot that it's a huge deal of course13:53
=== wedgwood_away is now known as wedgwood
jibelxnox, jodh there is a regression in upstart 1.8-0ubuntu1.1 in Raring and bug exists in Saucy (bug 1124384 and bug 1195955)14:02
ubottubug 1124384 in cloud-init (Ubuntu Saucy) "Configuration reload clears event that others jobs may be waiting on" [High,Confirmed] https://launchpad.net/bugs/112438414:02
ubottubug 1195955 in upstart (Ubuntu) "Setting up upstart (1.8-0ubuntu1.1) ... dpkg: error: unknown option --compare-version" [Undecided,Confirmed] https://launchpad.net/bugs/119595514:02
hallynogra_: well you should be able to get around the permission issue by doing a bind mount instead of a link14:03
hallynogra_: probably the more robust way would be to use mounts propagation to cause the contaienr's / or /dev to be mounted someplace where the host can see it14:03
hallynogra_: is the container's /dev a static dir, or a tmpfs?14:04
jodhjibel: yeah, looks like a typo from the last uploader14:05
ogra_hallyn, android uses a tmpfs for /dev14:05
ogra_and we hold our boot until thats propagated14:05
hallynogra_: what do you mean by propagated?14:06
hallynpopulated, or are you actually propagating the mount already?14:06
stgraberhallyn: IIRC you can't bind-mount /proc/<pid>/root/<something> (or at least it wouldn't let me do that the last time I tried)14:06
xnoxjibel: that's mine.14:07
ogra_hallyn, like ubuntu has udev, android uses ueventd to propagate the tmpfs /dev14:07
ogra_stgraber, right, i had the samme issue, thus the link14:07
ogra_which worked fine until rsalveti came around :P14:08
ogra_(trying to access it as normal user)14:08
stgraberogra_: btw, you mean "populate" not "propagate" :)14:08
ogra_errr, yeah14:08
hallynogra_: ok, i think you should make the container's rootfs --make-rshared14:09
ogra_what does that chare and how ?14:09
=== a16g_ is now known as ypwong
hallynset lxc.rootfs.mount to /container/rootfs in the container config,14:09
stgraberhallyn: won't help much as the final setup (once we're fully flipped and loop-mounted) uses a tmpfs rootfs mounted from the container ns14:10
ogra_we want the container to stay haf way safe ...14:10
hallynand on the host do mount --bind /container/rootfs /container/rootfs; mount --make-rshared /container/rootfs14:10
stgraberhallyn: so the rootfs isn't visible outside of the container mountns14:10
hallynstgraber: I think I might need a pic :)14:10
stgraberhallyn: basically /var/lib/lxc/android/rootfs is empty (or in ogra's case doesn't even exist), at boot time we have a pre-start which mounts a tmpfs on top, then unpack a cpio initrd, then does a bunch of stuff and finally boots that as rootfs14:11
hallynstgraber: that shouldn't matter14:11
hallynstgraber: so long as you make lxc.rootfs.mount = /container/rootfs, then the actualy rootfs that you pivot-root into will be /container/rootfs14:12
stgraberhallyn: but as all of this happens in pre-start, we're already in the container mountns so the rootfs isn't visible from the host, which means that if we were to use rshared, we still wouldn't be able to see it14:12
hallynand if you make that rshared, then the mounts from the child container should be reflected on the host14:12
hallynstgraber: the rootfs you're building isn't visibile in the host,14:12
hallynbut when you mount that onto /container/rootfs to pivot-root to it, you should see that on the host14:12
* ogra_ thinks he slowly gets it14:13
hallyni coudl be wrong, as this is being held together by duct tape, but that's what I"d expect :)14:13
stgraberah, let me try that14:13
hallyn(duct tape == bind mounts :)14:13
hallyncool.  meanwhile i've got someone telling me they can't provide apport info bc the bug is happening on fedora.14:13
=== oSoMoN_ is now known as oSoMoN
ogra_hallyn, so adding "lxc.rootfs.mount = /var/lib/lxc/android/rootfs" .... makes the container sigsev14:21
ogra_nothing further in the logs14:22
ogra_(or did you mmean literally /container/rootfs ?)14:25
hallynogra_: yeah :)14:25
ogra_doesnt work either14:25
hallyndoes that directory exist?14:25
ogra_do i need to create /container soemwhere ?14:26
ogra_heh, snap :)14:26
hallynmind you i wouldn't expect /var/lib/lxc/android/rootfs to segv...  it should just bind mount that onto itself then pivot to it.14:26
hallynogra_: and after you create /container/rootfs, remember to make it rshared14:26
hallynso mkdir -p /container/rootfs; mount --bind /container/rootfs /container/rootfs; mount --make-rshared /container/rootfs14:27
apacheloggerheya, any kernel guys around?14:27
ogra_hallyn, well, the container doesnt start14:28
hallyni can't reproduce quite your setup, but let me try a simpler case here14:30
hallynogra_: which release is this on, and which lxc package?14:30
ogra_apt-get source lxc-android-config ...14:30
* stgraber fights with make-rshared being a bit stupid14:31
ogra_hallyn, saucy latest lxc package indeed14:31
ogra_stgraber, does your container start at all ?14:31
stgraberogra_: yes, mine is fine because I'm using my loop-mounted images which have a saner lxc setup14:32
ogra_why didnt you pull  that into the non loop one :P14:32
* ogra_ wants sanity too !14:32
stgraberno point we'll get rid of those eventually and I have no way of testing them :)14:32
ogra_phablet-flash --flipped14:32
ogra_easy to test14:33
hallynjibel: so just to be clear, you created that container completely by hand, writing your own config?  If not, can you add steps including lxc-create command to the bug?14:34
ogra_stgraber, point is that we need a fix for flipped atm, it doesnt help if it works for you in the loop case14:35
ogra_(we want to swtich to flipped by default today, that one is a blocker)14:35
stgraberogra_: well, my container works with a lxc.rootfs set, rshared still doesn't so getting you past the lxc.rootfs won't help much14:36
bjfbug 119636314:36
ubottubug 1196363 in network-manager (Ubuntu) "network-manager is breaking my wireless during "Stage 5 of 5 (IPv6 Configure Timeout)"" [Undecided,New] https://launchpad.net/bugs/119636314:36
bjf^ this is saucy, 100% reproduceable14:37
ogra_stgraber, hmm, k14:37
* ogra_ would at least like to know what keeps his container from starting at all :(14:37
hallynogra_: can you do lxc-start -l info -o outout and pastebinit outout?14:38
hallyni'm still waiting for my testbed to install saucy...14:38
ogra_root@ubuntu-phablet:/# cat outout14:39
ogra_      lxc-start  947224102.538 INFO     lxc_start_ui - using rcfile /var/lib/lxc/android/config14:39
hallyndat not good14:40
hallynogra_: in that case can you strace it?  (strace -f -ooutout2 lxc-star ...)14:40
ogra_we start from an upstart job btw ...14:40
ogra_(on which other boot bits depend)14:40
ogra_bah, sigh, cant install strace without NM running14:41
stgraberogra_: wget http://ports.ubuntu.com/ubuntu-ports/pool/main/s/strace/strace_4.5.20-2.3ubuntu2_armhf.deb + adb push strace_4.5.20-2.3ubuntu2_armhf.deb /tmp/ + dpkg -i /tmp/strace_4.5.20-2.3ubuntu2_armhf.deb14:42
ogra_stgraber, :P i know, i'm lazy14:42
* ogra_ just rebooted with reverted container config14:43
stgraberhallyn: ok, finally got /var/lib/lxc/android/rootfs mounted rshared here, pivot_root fails14:43
ogra_hallyn, http://paste.ubuntu.com/5816923/14:44
ogra_not really informative, it seems to die when reading the fist line of the config14:45
stgraberslangasek: hey, with all the /run talks a while back, do you ever remember someone mentioning /etc/mtab? just noticed that one being an obvious candidate for /run and pretty annoying when /etc is read-only14:46
ogra_stgraber, didnt we always follow the "link to /proc/mounts" directive for readonly rootfs ?14:47
hallynstgraber: no, /var/lib/lxc/android/rotofs is not to be rshared,14:48
hallynstgraber: /container/rootfs is14:48
hallynstgraber: in other words, /var/l/ib/lxc/android/rootfs is the *source* of the mount, but you want the target to be rshared - the dir you end up pivot_rooting into14:48
stgraberogra_: yeah and that's what I'm doing here, though /run may make more sense (so that things like mount -n work)14:49
ogra_yeah. /proc/moounts definiely isnt 100% equal14:50
stgraberhallyn: hmm, right, that'll be even trickier because of mount's silly restriction of having the target be in /etc/mtab...14:50
jibelhallyn, I don't use the ubuntu template but scripts from https://code.launchpad.net/otto if that's what you mean by "by hand". The default config is a modified version of an install on Saucy months ago.14:50
jibelhallyn, the major difference being the hooks, and lxc.cgroup.devices.allow on snd, dri, input and tty14:51
jibeland the memory limits14:52
hallynholy schnickities14:52
jibelhallyn, I also noticed +lxc.hook.mount = /usr/share/lxc/hooks/mountcgroups which is not there with latest template14:52
jibelI'll add steps to reproduce14:52
hallynjibel: thanks14:53
hallynstgraber: holy schnickities, bug in saucy's lxc with lxc.rootfs.mount set.  oh!  i think i knew about that one14:54
stgraberhallyn: so I added:14:54
stgrabermount --bind $LXC_ROOTFS_PATH $LXC_ROOTFS_PATH > /tmp/debug 2>&114:54
stgrabermount --make-rshared $LXC_ROOTFS_PATH > /tmp/debug 2>&114:54
stgraberhallyn: to the pre-start, was that what you were saying?14:54
hallynstgraber: yeah14:54
stgraberhallyn: because if it's, then pivot_root still fails14:54
hallynright, kernel won't allow that will it14:55
stgraberyeah, same thing we had with UFA I think, kernel won't let us do it14:55
hallynok, new plan :)14:56
hallynmkdir /junk;  mount --bind /junk /junk;  mount --make-rshared /junk14:56
hallynstart the container as per usual14:56
hallynoh no, I guess bind-mount /junk into the container with lxc.mount.entry14:56
hallynthen, mkdir /junk/console; lxc-attach $container mount /dev/console /junk/console14:57
stgraberhallyn: we're on old kernels, can't rely on lxc-attach :)14:57
stgraberhallyn: but I have an idea for our specific case14:57
stgraberogra_: how about we create /dev/sockets on the host (ubuntu), then bind-mount that to /sockets in the container and then have init.rc mount --move it to /dev/sockets right after /dev is mounted in android?14:58
hallynstgraber: then just ssh $container mount /dev/console /junk/cnosole :)14:58
stgraberhallyn: no ssh or getty either :)14:58
ogra_stgraber, not sure how the blobs will cope with that ...14:58
ogra_we try to not change anything on the android side that could affect the binary blob functionallity (we already have way to many intrusive changes in the android setup)14:59
hallynstgraber: club it over the head and shout?14:59
* hallyn will wait to hear what stgraber is trying and whether it worked :)14:59
stgraberogra_: they won't have to, it's just an extra line in the init.rc to make /dev/sockets a mount instead of a standard dir15:00
stgraberogra_: unless the blobs start checksuming /proc/mounts or something, they won't notice and if they're looking at /proc/mounts, they'd already fail today :)15:00
ogra_stgraber, ok, lets try it15:01
stgraberogra_: ok. I'm stuck in meetings for the next 2 hours at least but will try to do some tests in parallel15:02
* ogra_ is in a call now as well15:02
xnoxjibel: uploaded a fix into raring-proposed unapproved queue and pinged about it on #ubuntu-release. Also committed a fix for the next upstart upload into saucy.15:05
evmpt: I don't think using the rate of errors is going to work for determining whether the architecture is significant.15:07
evAs an example, if we have 1,000 errors from 1,000 am64 machines in a day, the error rate is 1. If we have 1 error from 1 machine in that same day, the error rate is also 1.15:07
xnoxev: but if on adm64 for a particular crash error rate is 0.98, whilst i386 error rate is 0. it does imply an arch specific bug. And a single error from a single i386 machine instantly makes the bug report "not arch specific, yet triggered easier on amd64"15:10
evxnox: the error rate would be 1 on both cases15:10
evor am I missing something?15:12
xnoxev: i see what you mean, as we only collect crashes.15:12
xnoxev: i guess what matters is proportion of architectures within a given crash report, and whether it's statistically significant disproportion.15:12
evxnox: as opposed to machines that were out there running a particular version, package, and architecture?15:12
xnoxthat's overly specific, but yeah =)15:13
evxnox: yeah, proportion seems to be more helpful at least for architecture differences15:14
xnoxif foo is 50/50 amd64-i386 yet one crash of foo is 90/10 amd64-i386 it does hint arch-specific bug or "... easier to trigger on amd64"15:14
evI've been using >= 75% in my tests15:15
xnoxev: but even comparing with overall architecture split of all machines reporting any errors would be fine. As anything within 20% of a split can be accounted to random.15:15
xnoxev: 75 sounds good, but what's the current split between amd64/i386 reporters? 50/50? 60/40? 70/30?15:16
xnox(across all crashes ever uploaded)15:16
evthat's a good question, and an interesting thing to start monitoring15:16
xnoxit's not true indication of install base, but for the purpose of hinting arch-specific bugs that's the only baseline we can go by.15:17
xnoxev: don't forget about multi-arch though, just because my machine is :amd64 a crash in :i386 package should still count towards i386.....15:17
evoh ew.15:18
evI had not considered that.15:18
evI've been going off the Architecture field in the report.15:18
xnoxev: all skype crashes are i386 binaries & libraries & dependancies. As there is no amd64 skype.15:18
xnoxev: if the Architecture field from the report comes from the dpkg Architecture filed, all is fine. If it comes from machine/kernel then it's not so useful for this exercise.15:20
xnoxev: of course there are kernel bugs that only matching i386 kernel + i386 userspace binary will trigger, but those are rare.15:20
xnoxand given enough reporters should still generate significant arch bias.15:20
mptev, if we have 1000 errors from 1000 amd64 machines in a day, that would be a fluke unless the error is clock-based. Nonetheless, the calculated error rate wouldn't be 1000/1000, it would be 1000/(weighted count of AMD64 machines).15:21
mptWhich, at the moment, is 1000/(number of AMD64 machines that reported any error in the past 90 days).15:22
mptBut would become more sophisticated once bug 1077122 is fixed.15:23
ubottubug 1077122 in Errors "Machine weighted at 100% 89 days after last report, 0% 90 days after" [High,Confirmed] https://launchpad.net/bugs/107712215:23
evwhy would 1,000 errors from 1,000 amd64 machines be a fluke?15:23
mptIt would be a fluke that every single machine that had the error had it only once in that 24 hours -- that none of them had it twice or thrice.15:24
mpt(And thank you for giving me an opportunity to use the word "thrice". I was beginning to lose hope of using it at all in 2013.)15:25
evyou could start listening to the band. That would give you plenty of opportunity15:25
evI'm not convinced this solves the problem though. The frequency an error occurs at is not what makes the architecture interesting. The percentage of instances that occurred on said architecture is though.15:27
evmpt: You may have an error that, on average, happens twice a day for i386 and twice a day for amd64, but is significantly more prevalent on amd64.15:28
stgraberogra_: early-init is pretty much the first thing to be called right?15:28
eveven when factoring in the population of systems seen in the past 90 days15:28
stgraberogra_: (talking of init.rc targets)15:28
ogra_stgraber, hmm, yeah, i think so15:29
stgraberogra_: ok, I'll try to dump my extra mount line as the first thing it does, that seems to be the easiest to do with sed and should avoid any potential race15:29
slangasekstgraber: current util-linux supports /run/mount/utab; however, the implementation is only half-finished despite having been rolled out in Debian, Debian bug #70293515:34
ubottuDebian bug 702935 in mount "'mount -f' does not update /run/mount/utab" [Serious,Open] http://bugs.debian.org/70293515:34
stgraberslangasek: ok, good to hear someone's working on that. I indeed noticed /run/mount/utab in the strace output but the file ended up empty so wasn't of much use (which appears to be exactly the bug you mentioned)15:37
mptev, if you're controlling for the proportion of machines that have that architecture, you'll end up with exactly the same result starting from the proportion of errors coming from an architecture as if you start from the error rate for the architecture. They're just two routes to the same formula: (errors(amd64)*count(all arches))/(count(amd64)*errors(all arches)).15:38
slangasekstgraber: right; it's meant to be supplemental to /proc/mounts, so it's assumed that /etc/mtab is a symlink there first of all - but it still fails in various scenarios15:41
=== kk2 is now known as Kk2
dokoDaviey, zul: can I pass you the  system-config-cluster merge?15:55
Davieydoko: I think that one is better handled by either roaksoax or ivoks TBH15:56
dokoroaksoax, ivoks: ^^^. thanks for the pointer15:56
ivoksthat thing is still alive?15:58
evmpt: so we don't actually keep a count of the number of unique machines over a 90 day period per architecture, yet.15:58
evmpt: we never did return to the denominator question. Is this "count of machines (eventually weighted)" for the bucket in question, or for all problems seen that day?15:59
mptev, remember it's not just per-architecture: That's just one of the most interesting variables.15:59
mptPackage versions being another, locale settings, upgrade vs. fresh install, etc.15:59
evsure, I was just doing architecture first as it seemed easiest16:00
ev"c(amd64)" implies an architecture-specific count of machines16:00
mptOkay, just as long as you don't fix that problem in a way that works for architecture and nothing else16:00
evI can't envision a way in which I would, but I'll keep that in the back of my mind16:01
mptev, re. denominator: Neither. It's the count of machines that are using Ubuntu.16:01
roaksoaxdoko: i can take care of it16:01
dokoroaksoax, thanks16:05
=== Claudinux_ is now known as Claudinux
evmpt: yeah, we don't keep a count of the number of unique systems in the past 90 days for a given architecture. I'll work on a branch to add this to both the current approach and the weighting code16:09
stgraberogra_: ok, I have an updated pre-start.sh that fixes /dev/socket (triple testing it now)16:45
stgraberogra_: had to read android's init source code to figure out exactly how those commands work... they look like shell but they're not at all...16:46
ogra_heh, no, its its own language16:47
stgraberafter reading builtins.c it's much clearer what's allowed and what's not :)16:47
stgraberogra_: I guess I should probably fix cpuctl too while I'am at it?16:49
ogra_i'm not even sure we access it16:49
ogra_but yeah, all subdirs in /dev should eb available in the hosts /dev preferably16:50
ogra_we can drop them still if we find we dont need them16:50
=== fabo_ is now known as fabo
stgraberogra_: ok. I'll do the right thing for it which is to bind-mount /sys/fs/cgroup/cpu to /dev/cpuact (we already have it in the host, just not at the same place as Android)16:50
ogra_stgraber, err, with the same permissions ?16:51
stgraberor rather, have it symlinked when booting the current flipped images and have it bind-mounted when booting the loop-mounted images (much simpler to implement)16:51
ogra_i took the /dev nodes because i know everything is already processed there and listening processes are in place proper16:52
stgraberogra_: yep, the permissions are identical as the cgroupfs isn't namespace aware and so any change from android or from ubuntu will show up on the other side16:52
ogra_ah, good16:53
=== sabdfl_ is now known as sabdfl
ogra_cjwatson, just FYI, maguro and grouper images work fine from the new build16:59
stgraberogra_: please test http://paste.ubuntu.com/5817323/17:03
stgraberogra_: tested here and I get /dev/socket and /dev/cpuctl working as expected (and no more /proc/<pid> black magic)17:04
ogra_stgraber, i think the cpuctl stuff should become a udev rule instead17:07
* ogra_ reboots with the changes17:08
stgraberogra_: that'd trigger on what? you need to wait until cgroup-lite is started before it can be bind-mounted so it can't be a reaction to a uevent17:10
cjwatsonogra_: Brilliant17:10
ogra_stgraber, hmm, i was thinking to just match on sysfs node creation ... but that might indeed not work then17:12
ogra_stgraber, the change doesnt work17:12
ogra_Jul  1 17:12:07 ubuntu-phablet ofonod[868]: Excluding AT modem driver17:12
ogra_Jul  1 17:12:07 ubuntu-phablet ofonod[868]: create_ril: can't connect to RILD: Connection refused (111)17:12
ogra_Jul  1 17:12:07 ubuntu-phablet ofonod[868]: Exiting...17:12
stgraberogra_: what do you have in /dev/socket on Ubuntu?17:13
ogra_the right files17:13
ogra_but apparently the connnection between rild and the socket on the android side isnt working17:14
stgraberJul  1 17:03:35 ubuntu-phablet ofonod[1253]: [UNSOL]< UNSOL_RIL_CONNECTED17:14
stgraberJul  1 17:03:35 ubuntu-phablet ofonod[1253]: No SIM card present.17:14
stgraberI have that on mine17:14
ogra_i have ofono just adly respawning on maguro17:14
ogra_stgraber, out of ten reboots one worked17:16
ogra_stgraber, so the race got a lot worse than without the change17:16
ogra_(it was one out of 20 or so that failed before)17:17
ogra_and the boot seems to have gotten slower17:17
ogra_but thats a subjective feeling17:17
ogra_(at with an 1.5min boot probably even not a real issue :P)17:17
stgraberogra_: not sure what would make boot slower, we're doing less stuff now :)17:18
stgraberogra_: can you get: lsof -n -p <pid of rild> 2>/dev/null17:18
stgraberogra_: to avoid a respawn loop we could have a start on starting upstart-file-bridge job create /dev/socket, then have ofono.override use FILE=/dev/socket/rild17:23
ogra_doesnt work17:24
* ogra_ spent days on that bit already ... just to find that inotify doesnt seem to operate on sockets 17:24
ogra_so the file bridge doesnt work17:24
ogra_stgraber, i think having it respawn properly is the solution... just add that upstart fix so ofono doesnt die on respawns :)17:25
stgraberogra_: well, upstart as a respawn limit, so on fast phones we may hit it, then ofono won't start...17:26
ogra_oh, we actually want the limit being used17:26
ogra_but we dont want it to die on the second one already :)17:26
stgraberactually we should just have a wait loop in pre-start, that'd be much simpler :)17:27
stgraberoh, just like we do, nevermind17:27
stgraberoh, 8s sleep is a bit excessive isn't it? it's basically the time the phone takes to do a full reboot here17:28
ogra_yeah, mako isnt our target arch17:29
ogra_a reboot on maguro takes  about 2-3min17:29
ogra_the boot lies between 50sec and 1.5min alone17:29
* ogra_ would really like to get rid of the shutdown process ... having the shell thell the apps to save the UI realted data, calling sync and reboot -f would be so much more effective)17:30
stgraberogra_: anyway, got that lsof output?17:30
ogra_stgraber, the 8s was already in ... i think telepathy required it in unflipped17:31
ogra_stgraber, stop sending me copy paste lines with 2>/dev/null ... then i can easier find out that lsof isnt installed :P17:32
stgraberogra_: ah yeah, should have told you you'd need to install it first ;)17:33
ogra_heh, i thought it was in -minimal17:33
stgraberogra_: the 2>/dev/null will be useful once you have it though (otherwise it spits out errors about unknown uids)17:33
ogra_looks ok17:34
ogra_this boot also has found the socket in time17:34
ogra_stgraber, so your idea is to loop over lsof until it connected ?17:35
stgraberogra_: can you get me the same thing from a boot where the socket doesn't work?17:39
=== kirkland_ is now known as kirkland
stgraberogra_: well, I'm not sure why it doesn't connect... to me it seems like if the socket exists it should work, so I'd like to see exactly what rild is listening on when it doesn't work17:40
ogra_if i only could get one now17:40
ogra_the first ten were all broken ... the next ten werent17:40
stgraberI first thought it was a race in my init.rc change but I triple-checked and early-init runs before everything else including ueventd so there's no way that rild can be spawned before that and listen to the wrong /dev/socket (the one under my bind mount)17:41
slangasekstgraber: race between the bind() and listen() calls?17:41
slangasekwell, not a race /between/ those calls; but a race because bind+listen is not atomic17:41
ogra_stgraber, http://paste.ubuntu.com/5817423/17:41
ogra_stgraber, nah, the race is oldm nothing you caused ... but the timing of the startup indeed changed a bit17:42
ogra_ofono used to come up later before17:42
ogra_slangasek, well, likely something inside rild ...17:43
ogra_not much we can do about it17:43
cjwatsonCan anyone unpick https://jenkins.qa.ubuntu.com/job/saucy-adt-apt-clone/7/ARCH=amd64,label=adt/artifact/results/log ?  It doesn't happen for me locally, and I don't think acpi-support has changed.  Although I suppose it relies on archive state so maybe it's inherently chancy ...17:43
stgraberogra_: that second lsof shows that it's listening twice17:43
slangasekogra_: yes, bind+listen are the calls made by rild17:44
ogra_stgraber, hw do you see that ?17:44
ogra_i only see one entry17:44
slangaseklisten-before-bind would be race-free, but I'm not sure if that's actually allowed... it's not the conventional order17:45
ogra_stgraber, you mean the first one shows it is listening twice, right ?17:45
ogra_oh, how did my browser tabs flip their places17:46
cjwatsonWe can't have rild fork/daemonise/whatever after it listens?17:46
ogra_stgraber, ignore me ...17:46
cjwatsonAh, I guess it isn't supervised by upstart17:46
ogra_cjwatson, rild is a highly confidential binary blob17:46
cjwatsoni.e. broken :)17:46
ogra_living in android ... and each vendor seemss to have its pown rild implementation17:47
cjwatsonCan we ptrace it?17:47
slangasekcurrently it's launched by android init17:47
ogra_they are not even 100% protocol compatible17:47
cjwatsoni.e. ptrace until it calls listen, detach, emit upstart event17:47
slangasekwe could unpick all of that, but currently we're trying to avoid having to make deep changes there17:48
slangasekI suppose a ptracing wrapper could work17:48
slangasekcjwatson: do you know ptrace well enough to cook something like that up quickly?17:48
ogra_for kernels where we have ptrace :)17:48
cjwatsonDo we not have ptrace on the relevant kernels?17:49
stgraberthat should be all of them, otherwise upstart would have some difficulties17:49
* ogra_ doesnt think it is enabled on ports 17:49
slangasekogra_: er, that seems unlikely17:49
ogra_cjwatson, in our nexus kernels it definitely is17:49
slangasekthe ports kernels need to have ptrace enabled, period17:49
cjwatsonslangasek: It'd be ab initio, but I can read docs quickly :)  However I'm at EOD for today17:50
slangasekif they aren't currently enabling it, that's a bug that they'll need to fix17:50
slangasekcjwatson: mmk, never mind then :)17:50
ogra_slangasek, yeah, its a one line change to the porting docs17:50
ogra_just saying i dont think they have it now17:50
cjwatsonIf they don't, as stgraber says, Ubuntu won't work17:50
stgraberogra_: so, just to confirm the theory, what happens if you add let's say a 5s sleep after you find the socket and before starting ofono?17:50
ogra_oh, k17:50
ogra_stgraber, to the existing 8s sleep you mean ?17:51
stgraberogra_: if we indeed have a race between bind/listen, that should be way enough to get it past that point and so it should be reliable (wouldn't recommend it as a solution, but good enough to test)17:51
stgraberogra_: right, the current loop won't be executed (no sleep) if the socket is found, the 8s is only if it's not there17:52
stgraberogra_: so just add a "sleep 5" after the while loop17:52
ogra_oh, right, let me add 5s above the while17:52
stgraberbelow please17:52
ogra_bah, to late ...17:52
stgraberotherwise we may still get the race17:52
ogra_even tough ... heh ... another hanging reboot17:53
stgraber(if the socket happens to show up right after the sleep 5, we'll skip the loop and start running ofono before the bind/listen is done)17:53
stgraberogra_: can you retry with the sleep after the while loop, as the last thing in pre-start?17:53
ogra_yes, waiting for the boot ro finish17:54
ogra_(as i said, takes minutes)17:54
ogra_this one worked, let me do a few more17:54
ogra_stgraber, still there ... but more like it was before the shole change17:58
ogra_1 out of 10 fails17:58
stgrabernot very reassuring17:59
ogra_well, as long as the respawn works all is fine17:59
stgraberright and I gave a workaround to rsalveti for that earlier18:00
ogra_adding the 5s sleep and having respawn work should get us going until we can do something proper18:00
ogra_so its just that upstart fix :)18:00
ogra_stgraber, ok with you if i add all the chnages to lxc-android-config now ?18:01
ogra_or do you have a package branch ready18:01
stgraberogra_: I'll upload in a couple of minutes18:01
ogra_rsalveti, readable /dev/socket for you ^^^18:02
stgraberogra_: I won't push the ugly while loop (instead of respawn) though as I just thought of a couple of problems that'd cause (pid tracking), so I'll just try to fix the upstart bug asap (once I'm done with lunch, uploading that stuff and a couple of meetings)18:02
ogra_stgraber, right, the 5s sleep should be fine for now18:03
ogra_as long as we arent more broken than before i'm fine for now18:03
ogra_the respawning usually works at least once ... its the subsequent ones that fail18:04
rsalvetiogra_: thanks, patch seems fine18:04
rsalvetistgraber: thanks :-)18:04
ogra_stgraber, so i used the UI for the first time with the change in place ... *something* changed ... it is a lot less choppy !18:07
ogra_i can scroll through G+ without it stuttering now ... never worked on the flipped images18:08
stgraberogra_: uploaded18:10
ogra_stgraber, ugh, copying the two files over to the grouper breaks completely :(18:37
stgraberogra_: hmm, that's weird, can't think of why the change wouldn't work on grouper... let me update mine quickly (for some 30min definition of quickly... that's why I don't use it)18:40
ogra_stgraber, lxc_conf - File exists - failed to symlink '/dev/pts/ptmx'->'/dev/ptmx'18:41
stgraberogra_: weird indeed, can't remember changing anything that'd affect that...18:41
ogra_they are also the exact same image both installed at the same time18:43
ogra_the only thing that differs is that there is indeed no rild on the N718:43
ogra_stgraber, aha, the init.rc mangling doesnt happen18:45
stgraberogra_: ah? missing early-init target?18:45
ogra_nope, it is there18:46
ogra_but the mount line isnt18:46
stgraberogra_: what mount line? my new sed only requires "on early-init" to be present, then it adds a mkdir and a mount line below it18:46
ogra_right, these two arent there on grouper18:46
ogra_i see them on maguro18:47
ogra_hmm, no red herring18:48
ogra_seems it didnt even unpack the initrd18:48
ogra_stgraber, so it looks like we dont get into pre-start.sh at sll18:52
stgraberogra_: container started fine here (using loop mount)19:13
ogra_very weird19:14
stgraberogra_: ah, wait a sec, I'm not on the new lxc-android-config ;)19:14
ogra_i really only replaced the upstart job and pre-start.sh with the ones from maguro19:14
ogra_on a brandnew image19:14
stgraberogra_: ok, rebooted with the new version of lxc-android-config and the container still starts /dev/socket and /dev/cpuctl look good and init.rc contains the two extra lines19:17
ogra_hmm weird, i'll wait for the package19:18
=== pgraner is now known as pgraner-afk
tedgogra_, So when /sbin/initctrl is move to /sbin/initctrl.REAL is /sbin/init moved as well?20:02
tedgogra_, Thanks20:03
ogra_tedg, debian-installer-utils has a good reference script (chroot-setup.sh), similar code is used all over the place when chroots are used and daemon startups need to be prevented20:05
tedgogra_, Wow, that's a very evil script :-)20:06
ogra_well, thats what you need to do in an image build chroot or if you want to avouid to taint a fresh install while putting stuff into place20:07
tedgSure, but that's usually a little bit lower than where I play.20:09
ogra_yeah, plumbing ...20:10
=== james_ is now known as Guest20092
=== racarr is now known as racarr|lunch
luistanyone familiar with multistrap?20:30
ogra_stgraber, lol ... so i transferred pre-start.sh via adb from one devices to the other ... guess what my issue was :) .... adb removes the executable bits from files20:36
ogra_stgraber, so flase alarm, all is fine with the scripts ...20:37
stgraberogra_: oh, that'd explain it ;)20:37
ogra_and even the nx7 all of a sudden feels snappier20:39
luistcan anyone help me with multistrap? I'm trying to add my custom repository/package , but its not working. This is the config file: http://pastie.org/810113020:42
=== racarr|lunch is now known as racarr
roaksoaxdoko: makes sense? http://paste.ubuntu.com/5834245/20:49
dokoroaksoax, did the fix for the desktop file exist before? if yes, then maybe write in the changelog "resync ..., remaining changes"- but that's a minor nit.  and use -v to include the changes from the debian updates in the changes file21:00
roaksoaxdoko: cool thanks121:06
hallynjibel: ok, sorry this took so long - had some other issues.  but all i'm seeing is that memsw.limit_in_bytes appears to be misbehaving21:12
bdmurraydobey: are you working with software-center now?21:20
dobeybdmurray: it's in maintenance mode, so sort of. my team owns it now though, yes.21:21
bdmurraydobey: there is a reference in aptd.py to ERROR_PACKAGE_MANAGER_FAILED errors (from aptdaemon) and those being reported by dpkg and this isn't really happening and trying to sort out why21:24
bdmurrayaptdcon creates package install failure crash files and so does apt itself, so I think software-center is stopping them some how21:26
dobeybdmurray: unfortunately i don't really know much about the core of the code. maybe send an e-mail to glatzor/mvo about it?21:27
bdmurraydobey: okay, thanks21:27
=== halfie is now known as halfie|afk
hallynjibel: when i remove that line from the config, i can start the otto container - no complaints about devices cgroup21:56
hallynoh, d'oh.  but that wasn't kernel 3.10.  sigh.21:57
=== Guest86750 is now known as zumbi
=== wedgwood is now known as wedgwood_away
=== emma is now known as em
=== salem_ is now known as _salem

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!