/srv/irclogs.ubuntu.com/2018/01/12/#ubuntu-server.txt

cpaelzergood morning06:16
cpaelzerrbasak: 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 ?07:04
rbasakcpaelzer: I'll try, but not sure yet. We're trying to get some things done before the end of our sprint :-/09:53
lordievaderGood morning10:08
cpaelzerrbasak: fine11:00
cpaelzerrbasak: I realized I'll not forget it11:00
cpaelzerrbasak: because as soon as one does a review I'll see the mail ping11:01
cpaelzerrbasak: go for your sprint, early next week is fine enough11:01
ahasenackcpaelzer: shall I take a look?11:22
cpaelzerahasenack: if you want sure, but not if it breaks your plan what you wanted to do today11:24
cpaelzeras I said I'm kind of ok11:24
cpaelzerif - anyone- gets to it so that it is ready monday/tuesday it will be fine11:25
cpaelzerthis morning I asked because I felt to be in a hurry, but we have time enough that next week is ok11:25
cpaelzerbut turning it around, it is not for rbasak in particular - if you can please take a look11:25
ahasenacksomehow I had a feeling it was for him in particular, I don't know why11:26
ahasenackmaybe some of the bugs, or something that was said during standups11:26
cpaelzerahasenack: thanks for the review being an improved config.ac right away :-)14:49
fricklerjamespage: 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 upstream14:58
ubottuLaunchpad bug 1715417 in Designate Dashboard "Cannot view a zone in dashboard - 404 errors" [Undecided,Fix released]14:58
coreycbfrickler: sure, will you be able to test it?15:03
fricklercoreycb: yep15:04
coreycbfrickler: ok thanks15:04
=== CodeMouse92 is now known as CodeMouse92__
=== Ussat is now known as everybody
=== everybody is now known as Ussat
axisyssudo apt-get upgrade got stuck here20:21
axisysPreparing to replace postfix 2.9.6-1~12.04.1 (using .../postfix_2.9.6-1~12.04.3_amd64.deb) ...20:21
axisysif I kill it .. it will break the pkgs, right?20:22
dpb1axisys: do you see dpkg stuck in ps output?20:22
naccaxisys: you are on 12.04? are you using ESM?20:22
axisys/usr/bin/dpkg --status-fd 65  ... yes that process is there20:22
axisysnacc: yes 12.04 .. esm?20:23
axisysdpb1: ^20:23
naccaxisys: 12.04 is eol20:23
naccaxisys: unless you're paying for support, you should upgrade20:23
dpb1https://www.ubuntu.com/support/esm20:23
axisysnacc: decomming next week.. but need to get this apt-get completed .. still in prod today20:23
dpb1sure20:24
naccaxisys: ah20:24
naccaxisys: yes, killing apt will leave your packages in an undetermined state.20:24
axisysnacc: no, not esm20:24
dpb1axisys: if it were me, I'd kill it after waiting a while20:24
naccyeah20:24
dpb1then try to upgrade it by hand with a dpkg -i20:24
dpb1sometimes depending on term settings, etc, you can miss output20:25
axisysdpb1: started it at 19:33 and now 20:25 (utc)20:25
axisysso almost an hour20:25
dpb1especially postfix could be prompting you for the mail setup thing20:25
axisysdpb1: it probably is..20:25
axisysit 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
axisysbut right now it is not..20:26
axisysso how would dpkg -i work ? I usually do that for one pkg.. but never done that instead of apt-get upgrade20:27
axisysdpb1: ^20:27
axisysstuck here .. http://dpaste.com/2ABVK52.txt20:28
rbasakI suspect it's stuck somewhere else20:29
rbasak"ps axf" may be able to hint at it. Without the grep.20:29
dpb1ya, I usually do 'ps faux | less' then search through for dpkg20:31
dpb1axisys: the package will be in /var/cache/apt... somewhere dpkg -i FILENAME20:31
axisyshttp://dpaste.com/0VCW5RK20:32
axisys/var/cache/apt/archives$ ls -1 | wc -l20:33
axisys99920:33
axisysall .deb files20:33
rbasakHung on talking to plymouth20:33
rbasakWhich seems odd.20:33
rbasakHad the machine finished booting?20:33
rbasakYou could try killing 1208420:33
axisysit is not booting.. i am not there yet20:33
axisysrbasak: ^ ok20:34
axisysas soon as I killed that .. this showed up20:34
axisys * Stopping Postfix Mail Transport Agent postfix20:34
dpb1looks good20:35
axisysah.. 14018  \_ plymouth --ping20:35
dpb1unless it tries to talk to plymouthh again :)20:35
axisyshehe.. plymouth does not want to let go20:35
axisyskill it again?20:35
rbasakSure20:36
axisys14120 \_ plymouth --ping20:36
axisyshehe..20:36
axisyshttp://dpaste.com/24B8NAK.txt20:37
axisyshttps://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/171583020:37
ubottuLaunchpad bug 1705345 in plymouth (Ubuntu) "duplicate for #1715830 Installing new kernel hangs on plymouth --ping" [Undecided,Confirmed]20:38
axisyskilled the postfix stop process http://dpaste.com/1N5818N.txt20:44
axisysbut still stuck20:44
axisysshould I kill this process?20:45
axisys/usr/bin/perl -w /usr/share/debconf/frontend20:45
axisysok that killed everything20:51
axisysbut postfix is not starting.. hmm20:51
axisysthis was the output at kill20:52
axisyshttp://dpaste.com/1MH0X3N.txt20:52
axisysmay be postfix need to be re-installed? this system relies on postfix heavily..20:52
axisyswow.. postfix start is stuck at plymouth --ping20:53
axisysend up starting postfix manually.. looks like postfix pkg install attempt added two versions of libraries20:55
axisyshttp://dpaste.com/136R1M1.txt20:55
sdezielthe x86_64 and i386 are due to multi arch21:01
sdezieland the "differ" messages are because the copies in the chroot are not up to date21:01
axisyssdeziel: ok.. I am using x86_64 bit postfix binary.. I guess then those can be ignored..21:17
sdezielaxisys: restarting postfix should refresh the stuff in the chroot21:53
sdezielthe initscript takes care of it21:54

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