[06:16] <cpaelzer> good morning
[07:04] <cpaelzer> rbasak: I'd like to get that completed before leaving to the sprint, do you think you have a bit of time to look at https://code.launchpad.net/~paelzer/ubuntu/+source/collectd/+git/collectd/+merge/335985 ?
[09:53] <rbasak> cpaelzer: I'll try, but not sure yet. We're trying to get some things done before the end of our sprint :-/
[10:08] <lordievader> Good morning
[11:00] <cpaelzer> rbasak: fine
[11:00] <cpaelzer> rbasak: I realized I'll not forget it
[11:01] <cpaelzer> rbasak: because as soon as one does a review I'll see the mail ping
[11:01] <cpaelzer> rbasak: go for your sprint, early next week is fine enough
[11:22] <ahasenack> cpaelzer: shall I take a look?
[11:24] <cpaelzer> ahasenack: if you want sure, but not if it breaks your plan what you wanted to do today
[11:24] <cpaelzer> as I said I'm kind of ok
[11:25] <cpaelzer> if - anyone- gets to it so that it is ready monday/tuesday it will be fine
[11:25] <cpaelzer> this morning I asked because I felt to be in a hurry, but we have time enough that next week is ok
[11:25] <cpaelzer> but turning it around, it is not for rbasak in particular - if you can please take a look
[11:26] <ahasenack> somehow I had a feeling it was for him in particular, I don't know why
[11:26] <ahasenack> maybe some of the bugs, or something that was said during standups
[14:49] <cpaelzer> ahasenack: thanks for the review being an improved config.ac right away :-)
[14:58] <frickler> jamespage: coreycb: could one of you take a look at this bug and update the pkg, please? https://bugs.launchpad.net/bugs/1715417 version 5.0.1 of designate-dashboard has been released upstream
[15:03] <coreycb> frickler: sure, will you be able to test it?
[15:04] <frickler> coreycb: yep
[15:04] <coreycb> frickler: ok thanks
[20:21] <axisys> sudo apt-get upgrade got stuck here
[20:21] <axisys> Preparing to replace postfix 2.9.6-1~12.04.1 (using .../postfix_2.9.6-1~12.04.3_amd64.deb) ...
[20:22] <axisys> if I kill it .. it will break the pkgs, right?
[20:22] <dpb1> axisys: do you see dpkg stuck in ps output?
[20:22] <nacc> axisys: you are on 12.04? are you using ESM?
[20:22] <axisys> /usr/bin/dpkg --status-fd 65  ... yes that process is there
[20:23] <axisys> nacc: yes 12.04 .. esm?
[20:23] <axisys> dpb1: ^
[20:23] <nacc> axisys: 12.04 is eol
[20:23] <nacc> axisys: unless you're paying for support, you should upgrade
[20:23] <dpb1> https://www.ubuntu.com/support/esm
[20:23] <axisys> nacc: decomming next week.. but need to get this apt-get completed .. still in prod today
[20:24] <dpb1> sure
[20:24] <nacc> axisys: ah
[20:24] <nacc> axisys: yes, killing apt will leave your packages in an undetermined state.
[20:24] <axisys> nacc: no, not esm
[20:24] <dpb1> axisys: if it were me, I'd kill it after waiting a while
[20:24] <nacc> yeah
[20:24] <dpb1> then try to upgrade it by hand with a dpkg -i
[20:25] <dpb1> sometimes depending on term settings, etc, you can miss output
[20:25] <axisys> dpb1: started it at 19:33 and now 20:25 (utc)
[20:25] <axisys> so almost an hour
[20:25] <dpb1> especially postfix could be prompting you for the mail setup thing
[20:25] <axisys> dpb1: it probably is..
[20:26] <axisys> it is a server and I have done this type of upgrade million times and config change comes up with yes current and no default..
[20:26] <axisys> but right now it is not..
[20:27] <axisys> so how would dpkg -i work ? I usually do that for one pkg.. but never done that instead of apt-get upgrade
[20:27] <axisys> dpb1: ^
[20:28] <axisys> stuck here .. http://dpaste.com/2ABVK52.txt
[20:29] <rbasak> I suspect it's stuck somewhere else
[20:29] <rbasak> "ps axf" may be able to hint at it. Without the grep.
[20:31] <dpb1> ya, I usually do 'ps faux | less' then search through for dpkg
[20:31] <dpb1> axisys: the package will be in /var/cache/apt... somewhere dpkg -i FILENAME
[20:32] <axisys> http://dpaste.com/0VCW5RK
[20:33] <axisys> /var/cache/apt/archives$ ls -1 | wc -l
[20:33] <axisys> 999
[20:33] <axisys> all .deb files
[20:33] <rbasak> Hung on talking to plymouth
[20:33] <rbasak> Which seems odd.
[20:33] <rbasak> Had the machine finished booting?
[20:33] <rbasak> You could try killing 12084
[20:33] <axisys> it is not booting.. i am not there yet
[20:34] <axisys> rbasak: ^ ok
[20:34] <axisys> as soon as I killed that .. this showed up
[20:34] <axisys>  * Stopping Postfix Mail Transport Agent postfix
[20:35] <dpb1> looks good
[20:35] <axisys> ah.. 14018  \_ plymouth --ping
[20:35] <dpb1> unless it tries to talk to plymouthh again :)
[20:35] <axisys> hehe.. plymouth does not want to let go
[20:35] <axisys> kill it again?
[20:36] <rbasak> Sure
[20:36] <axisys> 14120 \_ plymouth --ping
[20:36] <axisys> hehe..
[20:37] <axisys> http://dpaste.com/24B8NAK.txt
[20:37] <axisys> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1715830
[20:44] <axisys> killed the postfix stop process http://dpaste.com/1N5818N.txt
[20:44] <axisys> but still stuck
[20:45] <axisys> should I kill this process?
[20:45] <axisys> /usr/bin/perl -w /usr/share/debconf/frontend
[20:51] <axisys> ok that killed everything
[20:51] <axisys> but postfix is not starting.. hmm
[20:52] <axisys> this was the output at kill
[20:52] <axisys> http://dpaste.com/1MH0X3N.txt
[20:52] <axisys> may be postfix need to be re-installed? this system relies on postfix heavily..
[20:53] <axisys> wow.. postfix start is stuck at plymouth --ping
[20:55] <axisys> end up starting postfix manually.. looks like postfix pkg install attempt added two versions of libraries
[20:55] <axisys> http://dpaste.com/136R1M1.txt
[21:01] <sdeziel> the x86_64 and i386 are due to multi arch
[21:01] <sdeziel> and the "differ" messages are because the copies in the chroot are not up to date
[21:17] <axisys> sdeziel: ok.. I am using x86_64 bit postfix binary.. I guess then those can be ignored..
[21:53] <sdeziel> axisys: restarting postfix should refresh the stuff in the chroot
[21:54] <sdeziel> the initscript takes care of it