[00:03] <thumper> menn0: are you getting time to finish off https://github.com/juju/juju/pull/2724?
[00:03] <menn0> thumper: working on that right now
[00:03] <menn0> thumper: not far
[00:03] <thumper> cool
[00:11] <menn0> thumper: done, about to merge
[01:26] <perrito666> mehh I was reviewing a pr and when I got to the end it got discarded
[01:27] <anastasiamac> perrito666: :(
[01:27] <anastasiamac> perrito666: what time is it for u?
[01:30] <thumper> wallyworld: I don't suppose someone on your team can fix the intermittent failure in uniter worker?
[01:30] <thumper> FAIL: uniter_test.go:892: UniterSuite.TestUniterUpgradeConflicts
[01:30] <thumper> happens relatively regularly
[01:31] <perrito666> anastasiamac: 22:30
[02:13] <wwitzel3> axw: ping
[02:15] <wallyworld> thumper: sorry, missed ping about failing test. will take a look. currently full with WIP fixes for 1.25 release and soon a critical customer issue which is more a feature thana bug
[02:15] <wallyworld> i suspect will be end of week or early next
[02:15] <wallyworld> also working on arm issue for 1.24.3
[03:07] <menn0> wallyworld, thumper: the mongodb timeout PR has landed in 1.24
[03:07] <wallyworld> great
[03:08] <wallyworld> do we know who to prod to see if it helps with anything?
[03:09] <menn0> wallyworld: ahasenack reported the bug that lead to me doing this work (i'm not sure if it will help or not)}
[03:10] <wallyworld> ok
[03:10] <menn0> thumper also thinks it might help with a problem env he was looking at
[03:10] <wallyworld> time will tell i guess
[03:27] <menn0> wallyworld: so what is the github.com/juju/juju/juju package all about?
[03:30] <menn0> seems like stuff that I would have expected to be in the state package
[03:41] <wallyworld> menn0: that package is sort of an attempt to get stuff out of state as far as i understand
[03:42] <wallyworld> it is horribly named
[03:44] <menn0> wallyworld: so state helpers then?
[03:45] <cherylj_> wwitzel3: ping?
[03:45] <wallyworld> menn0: more like juju core business logic
[03:45] <wallyworld> that is not persistence related
[03:45] <menn0> hmm ok
[03:45] <wallyworld> i didn't add it :-)
[03:46] <thumper> menn0: cool
[03:48] <menn0> wallyworld: I didn't think you did
[03:48] <wallyworld> i can't defend it too hard :-)
[03:53] <menn0> wallyworld: review done
[03:54] <wallyworld> ty menn0
[04:02] <wallyworld> thumper: have you picked up much about juju and arm via osmosis?
[04:02] <thumper> nope
[04:02] <wallyworld> and dave is away this week :-(
[04:08] <thumper> aye
[05:25] <anastasiamac> thumper: u got a fish trophy!
[05:56] <wallyworld> jam: hi
[05:57] <jam> hey wallyworld
[05:57] <wallyworld> jam: network related question if you have a moment
[05:57] <wallyworld> bug 1472014
[05:57] <mup> Bug #1472014: juju 1.24.0: wget cert issues causing failure to create containers on 14.04.2 with lxc 1.07 <openstack-installer> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1472014>
[05:57] <wallyworld> see the last couple of comments
[05:58] <wallyworld> it seems we don't store / report all the cloud local addresses for a machine
[05:58] <wallyworld> so a machine's AddressWatcher doesn't get told about all possible addresses an https request can arrive on
[05:59] <wallyworld> do you know why we throw away some cloud local addresses?
[05:59] <wallyworld> i'm not looked at the code in detail, just going by jame's comment
[05:59] <wallyworld> but i'm wary about changing network related code
[06:00] <wallyworld> as it has the habit of breaking things
[06:02] <jam> wallyworld: so offhand I'd say we don't actually cope with having multiple addresses where things could arrive
[06:02] <jam> wallyworld: consider charms, they can only really report 1 private address to eachother
[06:02] <wallyworld> hmmm, so which one to pick then
[06:02] <jam> wallyworld: so the issue is probably that we are thinking 10.0.6.* is the right address, when really the correct cloud-local address is the 10.0.3* one
[06:02] <wallyworld> as we are picking the wrong one
[06:03] <wallyworld> hmmm, so how to pick the right one
[06:04] <jam> wallyworld: so that machine has 3 addresses that I would consider "cloud-local" sort of addresess, a 10.0.3 a 10.0.6 and a 192.168
[06:04] <wallyworld> for this purpose we should just stick everything in the SAN
[06:04] <jam> wallyworld: Surprisingly (for me) 10.0.3 is usually the LXC bridge (I thought)
[06:05] <wallyworld> jam: what about this line : setting API hostPorts
[06:05] <jam> wallyworld: I think in the  idealized model Juju would be aware of all the subnets and have labled names for them (spaces), in which case it would know that machine X is supposed to talk to machine Y on a given address.
[06:05] <wallyworld> it seems there we pass in everything
[06:05] <jam> wallyworld: internally it feels like we should be aware and save all the addresses
[06:05] <wallyworld> yes, save them all internally sounds good to me too, but if we do that now stuff would break i would tink
[06:06] <jam> wallyworld: short term, I think just adding all addresses to the SAN is fine.
[06:06] <wallyworld> but
[06:06] <wallyworld> that relies on AddressWatcher :(
[06:06] <wallyworld> so i'll need to change how it all works
[06:06] <wallyworld> bollocks
[06:06] <wallyworld> i'll go read the code and see what can be done
[06:06] <jam> wallyworld: well, I think you can certainly get help from Sapphire on this one.
[06:07] <wallyworld> jam: i asked but none were 100% sure about why only one address was saved etc
[06:07] <wallyworld> so maybe there's not the level of knowledge there to dive right in
[06:07] <jam> wallyworld: well, dimitern is away and the others probably not quite as familiar
[06:08] <jam> gophercon being this week.
[06:08] <wallyworld> yeah, that's what i figured, hence asking you :-)
[06:08] <wallyworld> i'll see if it's possible to tinker with the cert updater
[06:08] <wallyworld> i could re-read all machine addresses
[06:08] <wallyworld> but may not be triggered
[08:09] <dooferlad> wallyworld, jam: just read the backlog. Yell if you want a networking hand.
[08:10] <dooferlad> wallyworld: also with ARM, I am an ex-ARM employee so if I can help with that please call on me
[08:41] <wallyworld> dooferlad: oh, i might take you up on that arm offer. i might ping you after dinner
[09:02] <dooferlad> jam, fwereade: hangout?
[09:30] <voidspace> fwereade: git blame -L302,302 provider/ec2/config_test.go
[09:30] <voidspace> fwereade: that's the test that fails for me on master
[09:31] <voidspace> fwereade: git blame may be deceived of course...
[11:15] <mattyw> fwereade, quick ping?
[11:15] <fwereade> mattyw, heyhey
[11:16] <mattyw> fwereade, is there any doc or something about the uniter operation/ callbacks arch? I'm finding myself getting in to it and was hoping I could make some decisions about my stuff without having to hassle you
[11:16] <fwereade> mattyw, only what's inline, I'm afraid
[11:17] <mattyw> fwereade, I probably only want to call a certain function when a certain hook has finished
[11:17] <fwereade> mattyw, that sounds like the responsibility of the CommitHook bit to me?
[11:18] <fwereade> mattyw, but the callbacks themselves are basically evil
[11:18] <mattyw> fwereade, time for a 5 minute hangout?
[11:18] <fwereade> mattyw, it's basically just a cut-down uniter facade/adapter for the use of the ops
[11:18] <mattyw> fwereade, I'll try to timebox it at that
[11:18] <fwereade> mattyw, sure, start one please?
[12:36] <wwitzel3> ericsnow: ping
[12:52] <mup> Bug #1472596 opened: bootstrap failed yet retry says it succeeded <juju-core:New> <https://launchpad.net/bugs/1472596>
[13:42] <mgz> bogdanteleaga: is rr 2107 live or not atm?
[13:49] <bogdanteleaga> mgz: no it's not
[13:49] <bogdanteleaga> mgz: it's more of a weird interaction, 2109 is the same but should show a better diff
[13:49] <bogdanteleaga> mgz: any ideas if I can delete that one?
[13:52] <mgz> bogdanteleaga: it is marked as discarded, so that's probably fine, is just getting updated still I guess as it's the same github branch
[13:53] <bogdanteleaga> mgz: yeah, that was the one submitted to github, but the diff would be a bit funky since it contains another branch
[13:56] <mgz> bogdanteleaga: do you need anything else on those branches, or are you good to go?
[13:56] <mgz> bogdanteleaga: I think we'll want to backport to 1.24 after master has blessed the change
[13:59] <bogdanteleaga> mgz: no, I was doing some final tests a couple of hours ago, but everything seems fine
[13:59] <bogdanteleaga> mgz: got caught up with something else
[14:00] <mgz> bogdanteleaga: no problem
[14:01] <bogdanteleaga> mgz: squashing now and I'll start merging
[14:01]  * bogdanteleaga grabs popcorn
[14:01] <mgz> :)
[14:19] <wwitzel3> ericsnow: ping
[14:20] <ericsnow> wwitzel3: hey hey hey
[14:24] <wwitzel3> ericsnow: trying to work through an issue and I've run in to some code that I could use some help deubgging
[14:24] <ericsnow> wwitzel3: sure
[14:25] <ericsnow> wwitzel3: moonstone?
[14:25] <wwitzel3> ericsnow: we can go to a query, conference wifi probably won't work so well with a hangout
[14:25] <ericsnow> wwitzel3: right :)
[14:35] <bogdanteleaga> mgz: you said they ought to be backported?
[14:35] <mgz> bogdanteleaga: I think we do need it on 1.24, yeah
[14:35] <mgz> want to see it work on master first of course
[14:39] <bogdanteleaga> mgz: Build failed: Does not match ['fixes-1472632']
[14:39] <bogdanteleaga> can't find a bug with that number
[14:40] <mgz> abentley: ^did you mean to make that bug a blocker and private?
[14:40] <abentley> mgz: Yes.
[14:40] <mgz> it does not really strike me as either
[14:40] <abentley> mgz: Regressions are blockers.
[14:40] <abentley> mgz: It has debug logs from SSH.
[14:42] <mgz> I am reading the debug ssh log and apart from containing your name and some of juju-ci's ips addresses it seems to have nothing personal
[14:42] <mgz> and I don't see how this bug prevents us releasing, which is the point of blockers
[14:43] <mgz> we've been releasing fine with this for three 1.24-s
[14:43] <abentley> mgz: Well, I was erring on the side of caution with the SSH.  If you're willing to take responsibility for making it public, I'm fine with that.
[14:44] <abentley> mgz: I don't know why we've continued to make releases after it was discovered.  I assumed sinzui had filed a regression bug, since he knew about it.
[14:44] <sinzui> abentley: I didn't know about it
[14:44] <mgz> abentley: okay. I can confirm this does not contain your private ssh keys. :)
[14:45] <abentley> sinzui: Oh? Didn't you say you'd had to rename your ssh key to id_rsa to deal with this issue?
[14:45] <mgz> abentley: the issue with the ssh stuff is it depends somewhat on your personal setup, so I knew that the combo of my local ssh config + juju ci scripts borked ssh for juju
[14:46] <sinzui> abentley: yes, for just bootstrapping ec2 and openstack providers. I haven't seen any issue with other providers or ssh in general
[14:46] <mgz> I agree this is a regression, but given it has an annoying but somewhat trivial workaround (don't use your personal ssh config) I don't see how it's critical
[14:47] <sinzui> abentley: nd this behaviour matches the windows setup from 18 months ago
[14:50] <abentley> mgz: I don't think the existence or lack of workarounds is a factor in whether an issue should block.  We don't want to break users' existing workflows, and this does break users' existing workflows.
[14:51] <sinzui> abentley: I don't disagree
[15:11] <mup> Bug #1472632 opened: regression: juju ssh dies with (publickey) <blocker> <regression> <ssh> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1472632>
[15:17] <alexisb> abentley, do we know what commit caused the regression?
[15:17] <alexisb> I would like to see bogdanteleaga be able to land his fix, it is a critical fix for 1.24.3
[15:17] <abentley> alexisb: No, we don't know which commit.  We found it by hand, not with automated tests, so we don't have logs that would show it.
[15:18] <alexisb> abentley, ok
[15:21] <alexisb> sinzui, abentley, mgz there will not be anyone from core looking at that bug until NZ/AUS comes online
[15:22] <mgz> I don't see how blocking is productive for this issue, nor how it's justified by our procedure
[15:22] <sinzui> alexisb: it doesn't blocl
[15:22] <sinzui> not tag blocker
[15:22] <mgz> sinzui: it has that tag currently, I was planning on raising in standup in 5 mins
[15:23] <alexisb> sinzui, ok, I must have miss read the back scroll
[15:23] <alexisb> I thought bogdanteleaga was blocked
[15:24] <mgz> sinzui: `./check_blockers.py check master`
[15:24] <sinzui> alexisb: if he is, he can add __JFDI__  to $$merge$$ to make it mege and test <- bogdanteleaga
[15:24] <mgz> noo..
[15:24] <mgz> either the bug blocks or it doesn't, we shouldn't be bypassing
[15:25] <mgz> I don't think it should block.
[15:25] <bogdanteleaga> it is blocked currently, but this is just the fix for master, the one for 1.24 is coming up
[15:26] <bogdanteleaga> not sure how long it takes for the upgrade ci job to test the fix though
[15:26] <sinzui> mgz: as we don't have a test for it and the regression is in the wild, we don't need to block. I think this is like the expressions closing the stable door after the horse has bolted
[15:29] <abentley> sinzui: That assumes that the number of people who have not upgraded to 1.24 is not significant.  I think that it is significant.  I think every time we put out a release, especially if we release 1.25, we encourage people who are using 1.23 and earlier to upgrade.
[15:53] <sinzui> bogdanteleaga: use "$$merge$$ fixes-1471332" to the pull requet comment to ensure CI will test and merge
[15:55] <bogdanteleaga> sinzui: I did try it with __JFDI__ but I fluked a test
[15:55] <bogdanteleaga> sinzui: should be fine on the next try; should I use jfdi or fixes?
[15:56] <sinzui> either bogdanteleaga
[15:56] <bogdanteleaga> cool
[16:10] <voidspace> dooferlad: TheMue: if you have a chance I'd appreciate a review http://reviews.vapour.ws/r/2116/
[16:11] <TheMue> voidspace: one moment, hunting a test failure, but will start in a few seconds
[16:11] <voidspace> cool, thanks
[16:11] <voidspace> good luck with the hunt :-)
[16:15] <TheMue> ah, kewl, panic is gone. now I can jump into your review
[16:18] <TheMue> voidspace: seeing your new ReleaseAddress() signature. could it be that the passed address doesn't match to the passed MAC address? IMHO they always should be a kind of pair with 1:N (one MAC, multiple IP)
[16:18] <voidspace> TheMue: no they're always 1:1
[16:18] <voidspace> TheMue: the MAC comes from state.IPAddress
[16:19] <voidspace> instance id is stored there too
[16:19] <TheMue> voidspace: ok, but technologically one MAC could have o´multiple IP, we only don't model it so right now
[16:19] <voidspace> ah
[16:19] <voidspace> our model does allow that, sorry
[16:19] <voidspace> although we don't use that capability
[16:20] <TheMue> ok
[16:20] <voidspace> so yes, one mac address could have multiple ip addresses - and we handle that
[16:20] <voidspace> we only delete the device if the IP address is the last one
[16:20] <voidspace> otherwise we just release the address normally
[16:20] <voidspace> biab, grabbing coffee whilst you read
[16:31] <TheMue> voidspace: you've got a review
[16:34]  * TheMue is afk for a moment, continue later
[17:15] <voidspace> TheMue: thanks
[17:32] <mup> Bug #1472711 opened: MAAS node has "failed deployment", juju just says "pending" <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1472711>
[18:20] <mup> Bug #1472729 opened: juju stuck in "upgrade in progress " for 20min <juju-core:New> <https://launchpad.net/bugs/1472729>
[18:23] <mup> Bug #1472729 changed: juju stuck in "upgrade in progress " for 20min <juju-core:New> <https://launchpad.net/bugs/1472729>
[18:32] <mup> Bug #1472729 opened: juju stuck in "upgrade in progress " for 20min <juju-core:New> <https://launchpad.net/bugs/1472729>
[19:47] <mup> Bug #1472749 opened: github.com/juju/utils has contradictory licences <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1472749>
[21:49] <marcoceppi> hello world
[21:49] <marcoceppi> maas 1.8.0 juju 1.24.2 deploying to LXC containers seems stuck, it's trying to wget the image from the bootstrap node/api server and it's been doing that for like 15 mins
[21:53] <marcoceppi> jk, it's moving on now
[22:00] <alexisb> hey marcoceppi welcome back from vacation
[22:01] <marcoceppi> alexisb: hey, thanks!
[22:37] <thumper> holy shit balls
[22:37] <thumper> these worker tests are taking ages to run...
[22:39] <thumper> FAIL	github.com/juju/juju/state/leadership	1200.021s
[22:39] <thumper> hmm
[22:39] <thumper> timeout kill
[22:40] <marcoceppi> nbd, 20 min tests
[22:41] <thumper> nbd?
[22:42] <marcoceppi> no big deal
[22:44] <thumper> nah man, it is a big deal
[22:44] <thumper> this is broke
[22:54] <menn0> thumper: shall I pick up the juju ssh blocker?
[22:54] <thumper> bug?
[22:55] <menn0> thumper: bug 1472632
[22:55] <mup> Bug #1472632: regression: juju ssh dies with (publickey) <blocker> <regression> <ssh> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1472632>
[22:55] <menn0> it's blocking master and 1.24
[22:58] <alexisb> sinzui, ^^ I thought we had decieded that bug was not a blocker
[22:58] <alexisb> menn0, we discussed that one earlier today
[23:00] <thumper> menn0: I think abentley's analysis is wrong
[23:00] <thumper> menn0: if you look at the logs, it was his personal id_rsa that worked
[23:00] <thumper> but 1.24 and master did not appear to be trying
[23:02] <menn0> thumper: i haven't looked at it in any detail
[23:03] <alexisb> so menn0, thumper, my understanding from this morning is that bug should not be a blocker and the tag was going to be removed
[23:04]  * thumper removes blocker tag
[23:04] <alexisb> unfortunately I don't see any of the release dudes online atm
[23:04] <alexisb> sweet
[23:04] <menn0> thumper, alexisb: cool. that unblocks master
[23:04] <menn0> 1.24 is still blocked due to the window upgrade issue
[23:04] <menn0> i've just been talking to bogdanteleaga
[23:05] <menn0> he's waiting to see the problem is fixed on master before pushing the fixes to 1.24
[23:05] <thumper> that shouldn't block 1.24 then
[23:05] <menn0> the PR to fix 1.24 is ready to go though
[23:06] <menn0> thumper: no?
[23:06]  * thumper thinks
[23:06] <thumper> it will block us doing a release
[23:06] <thumper> but I don't think it should block us landing other fixes on 1.24
[23:07] <menn0> thumper: remove the blocker tag then?
[23:08] <thumper> menn0: do we know if it fixed the issue on master?
[23:08] <menn0> thumper: no we don't. CI hasn't gotten to running it yet
[23:09] <menn0> thumper: bogdanteleaga just noticed that his fix broke the unit tests under windows so he's going to do a fix for that now
[23:11] <wallyworld> waigani_: can you take a look at 1.24 bug 1472711? it claims bug 1376246 may not quite be fixed
[23:11] <mup> Bug #1472711: MAAS node has "failed deployment", juju just says "pending" <maas-provider> <juju-core:Triaged> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1472711>
[23:11] <mup> Bug #1376246: MAAS provider doesn't know about "Failed deployment" instance status <landscape> <maas-provider> <juju-core:Fix Released by waigani> <juju-core 1.24:Fix Released by waigani> <https://launchpad.net/bugs/1376246>
[23:37] <thumper> rick_h_: hey there
[23:59] <menn0> thumper: so the windows upgrade still isn't working in CI


[01:40] <Zx33> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[01:40] <Zx33> I thought you guys might be interested in this blog by freenode staff member Bryan 'kloeri' Ostergaard https://bryanostergaard.com/
[01:40] <Zx33> Read what IRC investigative journalists have uncovered on the freenode pedophilia scandal https://encyclopediadramatica.rs/Freenodegate
[01:41] <Patrick21> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[01:45] <myth0d15> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[01:49] <thevdude0> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[02:05] <pendo32413> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/
[02:11] <fford> With our IRC ad service you can reach a global audience of entrepreneurs and fentanyl addicts with extraordinary engagement rates! https://williampitcock.com/


[02:37] <twb> I am looking at /etc/event.d/ on an Ubuntu Server 8.04 system.
[02:38] <twb> Can someone explain why tty1 and tty2 differ in their start/stop parameters?
[02:42] <twb> It looks like tty2 through 6 are only active for runlevels 2 and 3.
[07:24] <JamesB192> twb: tty1 should also come up for single console mode. j/k I dunno.
[07:27] <JamesB192> I don't have any *buntu boxes or boxes w/ upstart, so I'm actually guessing wildly.
[07:29] <twb> JamesB192: out of curiosity, what are you running upstart on, then?
[07:30] <JamesB192> nothing atm, I haven't gotten around to (re)installing it on my ??ntoo box.
[07:30] <twb> Righto.
[07:32] <JamesB192> I think I remember though that some linux boxes have a single console mode for non live coaster rescue type stuff.
[07:32] <twb> They do; this is traditionally runlevel 1.
[07:33] <JamesB192> and no doubt in 30 minutes someone who know what they're talking about will explain what I'm missing.
[07:33] <JamesB192> but I answered first.
[07:33] <twb> I imagine that is very important to you.
[07:38] <JamesB192> I think I have a tarball with jobs similar to those, but I can't seem to find them atm.
[07:39] <twb> JamesB192: upstart's source contains some examples along those lines.
[09:55] <Keybuk> twb: actually, it's exactly as JamesB192 says
[09:56] <Keybuk> in Ubuntu, we don't start getty on tty2-6 unless in runlevel 2 or 3
[09:56] <Keybuk> just a hold-over from sysvinit
[09:57] <twb> Keybuk: it's not a holdover from sysvinit, because Debian's inittab starts all six in all those runlevels (2 through 5).
[09:57] <twb> Unless you're referring to an intermediary instance of inittab, or RH's inittab ;-)
[09:57] <Keybuk> I'm pretty sure ours didn;t
[09:57] <twb> Oh well.
[09:58] <twb> At least the differences make sense.
[09:59]  * Keybuk grabs a copy of sysvinit's source to check
[09:59] <Keybuk> 1:2345:respawn:/sbin/getty 38400 tty1
[09:59] <Keybuk> 2:23:respawn:/sbin/getty 38400 tty2
[09:59] <Keybuk> 3:23:respawn:/sbin/getty 38400 tty3
[09:59] <Keybuk> 4:23:respawn:/sbin/getty 38400 tty4
[09:59] <Keybuk> 5:23:respawn:/sbin/getty 38400 tty5
[09:59] <Keybuk> 6:23:respawn:/sbin/getty 38400 tty6
[10:00] <twb> What version is that from?  6.04?
[10:00] <Keybuk> current (karmic)
[10:00] <twb> Huh?  But most of inittab is completely ignored, at least in 8.04.
[10:00] <Keybuk> sure, we still have the source in the archive though
[10:00] <twb> Ah, OK.
[10:01] <Keybuk> err
[10:01] <Keybuk> I just grabbed the Debian source
[10:01] <Keybuk> it has the same
[10:01] <twb> Wow.
[10:01] <twb> What is Debian doing, changing behind my back?
[10:01] <Keybuk> how do you mean?
[10:01] <Keybuk> it looks like it's always been like this
[10:02] <twb> Maybe I misunderstood it, then.
[10:02] <Keybuk> can you paste the getty lines from yours?
[10:02] <twb> I could've sworn that at some time, probably around Sarge, it defaulted to :2345:
[10:02] <twb> Keybuk: eh, my instances are modified ;-)
[10:03] <Keybuk> doesn't look like it
[10:03] <twb> Oh well.
[10:04] <Keybuk> no idea why Debian is like this, of course
[11:52] <soren> Keybuk: Have you had a chance to look at https://bugs.edge.launchpad.net/ubuntu/+source/upstart/+bug/372864 ?
[11:53] <Keybuk> if I haven't commented on it, I missed it
[11:53] <soren> You haven't :)


[02:35] <Guest37518> hello?
[02:36] <Guest37518> hi
[02:36] <Guest37518> hi
[02:36] <Guest37518> hi
[03:04] <nit-wit> Guest37518, talking to yourself.:)
[04:03] <Guest83939> !nick
[04:03] <newnick> !register
[04:05] <IdleOne> if you plan on using Ubuntu channels I suggest not using that nick
[04:06] <IdleOne> onetonturd: Please change your nick to something more family friendly.
[04:17] <juk> hey guys volume control on the panel is gone
[04:21] <sagaci> which to install from, alpha 1 or the latest daily
[04:21] <nit-wit> sagaci, daily
[04:22] <sagaci> oh, separate amd64+mac isos
[04:22] <nit-wit> sagaci, ??
[04:23] <sagaci> http://cdimage.ubuntu.com/daily-live/20101222/
[04:24] <juk> hi is volume control on the panel is gone recently
[04:24] <nit-wit> sagaci, I tried to get that build to work not to well but todays upgrades from the US servers got the installed Natty purring you might go alpha or wait for the next daily your choice really
[04:25] <nit-wit> juk, how about the envelope they are separate in natty correct.
[04:28] <nit-wit> juk, run in the terminal gnome-volume-control-applet and see if one shows. If it does just put that in a command for startup applications in  preferences. the one generated in the terminal will disappear at closing the terminal. also the fn key held down and the up down arrows on the keyboard control volume.
[04:33] <juk> nit-wit: yeah, got old gnome volume control, thanks, fn - yes i know, it's on my laptop, on pc i use ctrl+]/[ since no fn key
[04:34] <nit-wit> juk, most people know about the fn control but it doesn't hurt to mention it. you just going to put that command in startup applications.
[04:37] <juk> nit-wit: agree, yes i did
[04:40] <nit-wit> juk, early on in Natty I was not able to get the gnome volume to work glad to hear it does now.
[04:44] <juk> nit-wit: thank you
[09:39] <H4F> Hi all, After one of the update my system brokes
[09:39] <H4F> now I am working from livecd trying to restore
[09:40] <H4F> I chrooted the installation system
[09:40] <H4F> when doing apt-get upgrade or dpkg -configure -a I have the many errors
[09:41] <H4F> first error is "Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory"
[09:42] <H4F> may be I didnt mount something before chrooting ? any one have an idea ?
[09:43] <weside> hi
[09:47] <H4F> ok guys I think I fixed the issue with Dbus. I exited chroot and mounted "mount --bind /var/run/dbus/ chroot/var/run/dbus/" then chrooted back
[09:53] <H4F> I still have one error "Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files"
[12:25] <nperry> All you virtualbox box users
[12:25] <nperry> Install virtualbox 4
[12:25] <nperry> http://www.virtualbox.org/wiki/Changelog
[12:25] <nperry> 3D support: fixed Unity/Compiz crashes on natty
[12:26] <nperry> Enjoy
[12:46] <htorque> nperry, yeah, that's good news for vbox testers :-)
[13:12] <coz_> hey all
[13:39] <Ian_Corne> yeah jrib gdm broke :(
[13:41] <yofel> well, the only gtk related thing that's broken here is that I can't copy & paste from firefox and thunderbird anymore :(
[13:43] <coz_> mm let me try the firefox copy / paste...  yofel   what were you trying to copy paste?
[13:43] <Ian_Corne> yofel: I couldn't copy paste from anywhere anymore
[13:44] <yofel> *anything* - even xclipboard doesn't work anymore
[13:44] <coz_> yofel,  I just highlighted and middle clicked in gedit from firefox.... seems to work
[13:44] <yofel> well, any kde app works fine, but every gtk app is broken here
[13:46] <coz_> yofel,   mm  when I copy paste from firefox it works here...and I have bot kde and gnome stuff onboard unless I am not understanding :(
[13:46] <yofel> maybe it's just minefield, I'll look into it later
[13:46] <coz_> yofel,  it could be  and actually I am using swiftfox  here  ,, i dont like firefox 4
[14:14] <coz_> ok breakfast time  ,, be back in a bit
[14:44] <dnivra> i was looking at https://bugs.launchpad.net/ubuntu/+bug/682852. it says [Needs Packaging]. what exactly is to be done?
[14:45] <jrib> !packaging
[14:45] <jrib> dnivra: is the NewPackages link what you want?
[14:47] <dnivra> jrib, reading it now
[14:48] <dnivra> suppose a package is built in ubuntu, is it edubuntu compatible?
[14:49] <jrib> dnivra: yep
[14:49] <jrib> dnivra: edubuntu uses the same repositories, it just has a different set of default packages installed by default
[14:50] <dnivra> jrib, oh! it's like that for all official OS of ubuntu family-ubuntu, kubuntu, xubuntu etc? shared repositories?
[14:51] <dnivra> i read https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages-it links to packaging guide but what do I do after creating the deb file. what do I have to upload? if i fix a but, i upload a debdiff. in case of packaging?
[14:51] <jrib> dnivra: yep
[14:52] <dnivra> bug* not but :)
[14:53] <jrib> dnivra: read the "Going through motu" part.  #ubuntu-motu is a good place for help with this.  Also, eventually you should get the package into debian too (if it gets into debian it automatically gets into ubuntu, so you help more people)
[14:54] <dnivra> jrib, sure i'll check out the links and #ubuntu-motu for more on this.
[14:55] <dnivra> jrib, if i get it into debian, don't i have to be the package maintainer? in ubuntu, it is always 'Ubuntu Developers' right? works the same in debian too?
[14:57] <jrib> dnivra: not sure
[14:57] <dnivra> jrib, okay then. i'll check it out in debian. will go ask their IRC. thanks a lot for the links!
[14:58] <jrib> dnivra: yep, they have a packaging channel too but I don't know it offhand
[14:58] <dnivra> jrib, no problem. i'll find it out. google :) thanks a lot!
[14:59] <jrib> dnivra: yeah, there should be a link somewhere on the wiki about contributing to debian too
[15:00] <dnivra> jrib, #debian-newmaint on OFTC i think.
[15:00] <jrib> sounds about right
[15:01] <dnivra> topics asks me to head to #debian-mentors
[15:01] <dnivra> :)
[15:01] <dnivra> topic*
[15:03] <dnivra> jrib, would building the package on ubuntu make it compatible with debian? and would debian accept it? or would they ask me to build it on debian again?
[15:05] <jrib> dnivra: in most cases, yes.  But you should setup some sort of debian build environment to do it.  They can probably advise you better than me in that debian channel
[15:05] <dnivra> jrib, no response there so just thought i'd get a basic idea. i'll figure it out there. thanks!
[15:07] <jrib> dnivra: if you build for natty, packages will likely be similar to debian unstable, so you should be okay
[15:08] <wzssyqa> bug #693737
[15:08] <dnivra> jrib, fair enough then. i'll keep pinging debian channel too.
[15:09] <wzssyqa> OMG, just recovery
[15:09] <jrib> wzssyqa: eh?
[15:10] <wzssyqa> jrib: topic
[15:10] <jrib> wzssyqa: did that affect you too?
[15:11] <wzssyqa> jrib: y, thanks to btrfs
[15:49] <AlanBell> hi all
[15:50] <AlanBell> just tried booting todays alternate CD, works in virtualbox but not on real hardware
[15:51] <AlanBell> doesn't get to the point of asking languages, just get an unthemed grub menu and all of the options hang on a blank screen with a small white cursor top left
[16:21] <hggdh> nice. I now have nothing in gnome-panel -- indicator-applet, nm-applet, everything vanished
[16:39] <jMCg> I'm a terrible tester. I've gotten used to all of these things.
[16:42] <charlie-tca> heh, at least in Xubuntu we get to watch them shrink and disappear
[16:45] <hggdh> I thjink it is the gtk2.23... I will wait for an update, easier than downgrading
[16:47] <Amaranth> hggdh: hrm, most of the desktop team is gone for about a week
[16:48] <Amaranth> hggdh: From what I've been able to tell, anyway
[16:48] <hggdh> Amaranth: yes, Canonical will be off next week
[16:48] <Amaranth> hggdh: So you'll be a week without indicators :)
[16:49] <hggdh> Amaranth: heh. Perhaps I should downgrade, then :-)
[16:49] <charlie-tca> hggdh: did you see VBox 4.0 is out with 3d support?
[16:49] <Amaranth> charlie-tca: they specifically mentioned fixing compiz/unity on natty in the changelog :)
[16:50] <hggdh> charlie-tca: no, I had not. Interesting, now we can play with unity on a VM :-)
[16:50] <Amaranth> I can't, palm tools don't support 4.0 yet
[16:50] <Amaranth> Well, I think I can get away with two installs, actually...
[16:50] <charlie-tca> but it works, too.
[16:50] <Amaranth> oh well, I'm already using natty on my main machine
[16:51] <charlie-tca> Of course, now you also need the extension pack to get usb2
[16:52] <hggdh> ah well.
[16:52]  * hggdh goes checking upstream VBox
[16:52] <charlie-tca> but at least I can test in VBox again
[17:02] <vish> Amaranth: whoa! unity is possible in VB4?
[17:02] <vish> has anyone tried it?
[17:04] <rumpel> Visual Basic?
[17:04] <vish> VirtualBox
[17:05] <vish> charlie-tca might have tested it i guess "<charlie-tca> but it works, too."
[17:05] <rumpel> ah... k
[17:05] <charlie-tca> No, I didn't test unity
[17:05] <charlie-tca> I haven't been able to VBox to do any installs
[17:05] <vish> yea, i was not sure :)
[17:06] <charlie-tca> Let me try it
[17:07] <charlie-tca> starting the live cd in VBox, let's find out
[17:12] <charlie-tca> hm, fails here with my Nvidia video card, maybe I got the settings wrong
[17:20] <charlie-tca> vish: how to install guest additions on the live environment that won't start without 3d?
[17:21] <vish> hmm, i dont think we can do it for a live cd..
[17:21] <vish> charlie-tca: it needs a reboot once we install the guest additions
[17:21] <charlie-tca> so much for unity in VBox 4 live then
[17:22] <charlie-tca> Maybe it will work for an installed image, but not for the live image?
[17:22] <vish> i think we could install a virtual machine and then try to use is..
[17:22] <vish> charlie-tca: yea..
[17:23] <charlie-tca> But, hey, there are several changes in version 4, I might have to just play with it to get it right, too
[17:29] <mongy> login to the 'fallback' gnome, install additions, logout/login to unity
[17:33] <charlie-tca> that is a nice plan. Boot the desktop cd, pick Try Ubuntu, and do that?
[17:33] <coz_> hey guys.. real quick before I reboot... anyone having issues with gnome-panel broken ?
[17:34] <coz_> today's updates seem to have broken gnome-panel in classic gnome
[17:34] <Amaranth> coz_: yeah, everyone seems to be getting that
[17:35]  * Amaranth was just about to pull the trigger on an apt-get upgrade before people started talking about it
[17:35] <coz_> Amaranth,  oh ok thanks :)
[17:36] <coz_> well at least I can reboot  and killall gnome panel :)
[18:11] <charlie-tca> Well, to be sure, Unity does run in virtualbox 4.0 now with guest additions installed!
[18:42] <Pici> jadd: The bug linked in the topic is likely relevant to your issue.
[18:43] <jadd> Pici: can i do a downgrade to that one before ?
[18:44] <IdleOne> jadd: see the comments in the bug
[18:48] <jadd> k thanks
[19:21] <alfa> ciao
[19:21] <alfa> qualcuno?
[19:26] <[lan3y]> Hi, i am having problems with gnome on 11.04, the top panel is not showing any notification symbols in the right hand corner (wifi account name ect) how do i fix this panel?
[19:28] <nit-wit> [lan3y], are you updated and which servers are you using what country?
[19:31] <[lan3y]> i;ve found it now, im another victim of the new GTK+2.0 package
[19:36] <[lan3y]> how do i downgrade it again?
[19:45] <[lan3y]> nit-wit, i keep getting errors when  i try and downgrade
[19:47] <nit-wit> [lan3y], downgrade what's the meaning of that
[19:47] <[lan3y]> the bug for the problem i got says downgrade the package
[19:48] <nit-wit> [lan3y], and how does it do that or do you go to synaptic and get the earlier reinstalled
[21:09] <matrixa1> i bet somebody already has noticed this, but the latest updates have nuked most gnome-panel applets
[21:14] <charlie-tca> see the topic
[21:14] <charlie-tca> oops. You are correct, matrixa1
[21:14] <charlie-tca> It has been noticed...
[21:22] <matrixa1> ah that explains it
[21:23] <matrixa1> didn't read the topic tbh
[21:25] <charlie-tca> I read the topic everytime it changes and I am in the channel. But read it when logging in???
[21:26]  * charlie-tca thinks it is a good idea, though :-)
[21:32] <patdk-wk> there be a topic? :)
[21:38] <charlie-tca> I don't know if there is when I first log in to the channel ;-)
[22:00] <leagris> Hope noone will kill compiz enhanced zoom. As a visually impaired, this tool is an unavoidable extraordinary help.
[22:01] <leagris> I left trying to run Kde4 because the same feature is a pain without mouse wheel event ton control zooming.
[22:02]  * leagris missing the resolution agnostic CRTs. Now I can't use an LCD display without extensive dynamic zooming.
[22:05] <charlie-tca> +1
[22:43] <BUGabundo> oi
[22:43] <charlie-tca> Hello, BUGabundo
[23:19] <BUGabundo> ON NOES
[23:19] <BUGabundo> recent X update is broken
[23:19] <BUGabundo> can't copy or paste :S
[23:20] <yofel> welcome to the club
[23:20] <charlie-tca> Happy Holidays :-)
[23:21] <BUGabundo> ahahahahaa
[23:21] <BUGabundo> what's the bug id?
[23:23] <yofel> did anyone report that yet? I didn't get to it yet
[23:23] <BUGabundo> I'm busy re-flashing my phone, putting mail into zero, and spamming all my contact list with a xtmas message!
[23:23] <BUGabundo> you ?


[04:46] <LjL> ompaul, hi
[04:46] <ompaul> how do :)
[04:47] <LjL> ompaul: better than a few days ago...
[04:47] <LjL> i've made a few (not really radical) changes to DialupModemHowto, mainly putting all the repeated instructions on "how to download stuff from another machine", "how to install gcc", "how to install gcc 3.4" into a single place
[04:48] <LjL> what would be the best way to reference that sort of thing from inside the page? -- in other words, whenever a step is mentioned that involves setting up GCC (etc), i'd like to have a link to the relevant section
[04:49] <ompaul> why 3.4
[04:49] <ompaul> gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)
[04:49] <ompaul> that is for dapper
[04:49] <LjL> ompaul: i don't know... it's mentioned on the page several times, as something you need to install for compiling certain drivers
[04:49] <ompaul> that was true up to breezy
[04:49] <LjL> ompaul: i didn't investigate whether that's really necessary, or gcc 4.0 is fine
[04:50] <LjL> i basically just changed the layout
[04:50] <ompaul>  s/gcc 3.4/gcc :)
[04:50] <ompaul> back in a few mins
[04:50] <LjL> ompaul: *shrug* i know that page's a mess, and a lot of the advice in it is probably doubtful, but what should i do
[04:51] <LjL> i don't *have* all those modems, so i can't just scrap everything that is there and rewrite it differently ;)
[04:51] <LjL> all i can do i make the page a little more structured...
[04:52] <LjL> ompaul: also, have a look at https://launchpad.net/distros/ubuntu/+spec/winmodem-support , and in "Read more", go to the "Discussion" section, where i've just added a suggestion... what do you think?
[04:53] <LjL> after all, DialupModemHowto is a mess, but that's partially because making those modems works *is* a mess, i'm afraid =)
[04:56] <ompaul> been a long time since I did one
[04:58] <LjL> ompaul: me too... actually, i *never* had to deal with that stuff, since when i was using a modem, it was a real one. ;)
[04:59] <LjL> ompaul: anyway, the question at hand is... was is the way (if any) in the wiki to make (long) footnotes? -- i think all that GCC stuff would be much better formatted as footnotes
[05:00] <LjL> you know, having whole sections at the top of the page, and then making links such as DialupModemHowto#head-e2fda33ea2fad3f2139a25629c62504fbbbd6abe , is not what i consider particularly elegant
[05:00] <ompaul> LjL, when I could not use real internal I got external serial one
[05:00] <ompaul> :)
[05:00] <ompaul> sorry dude I am running around like a headless chicken
[05:01] <LjL> ompaul: i've got too external 56K modems, but i never really used them... i always went with my internal (but real) 33.6K modem, then switched to fiber
[05:01] <ompaul> LjL, the bug is nuts - then we have to get licences and check against
[05:02] <ompaul> LjL, 200+ modems
[05:02] <ompaul> in my personal opinion much better if people are told that they are being cheated out of good hardware cos this one wants to rob your cpu cycles for modem work :)
[05:02] <LjL> ompaul: you mean that proposal for auto-installing drivers? well yeah, that's one of the reason i suggested that we just *check* for unsupported modems, and inform the user
[05:03] <ompaul> yeap
[05:03] <ompaul> it seems to me that the "open cd" aspect of our CD should give way to being something that rocks more
[05:04] <LjL> ompaul: well, you could make the "friendly dialog window" i proposed a bit different if you want to convey that message... like, "Your modem is software-defined and only comes with software for the Windows operating systems, thus ...."
[05:04] <LjL> ompaul: like what?
[05:05] <ompaul> LjL, well to accomidate the "your hardware is not supported out of the box here is a page with the steps that get it rocking"
[05:06] <ompaul> then after that they get a "Some hardware gives pain, WHY?" links
[05:06] <ompaul> sorry my english is broken as is my brain today
[05:06] <LjL> ompaul: uhm, yeah, but doesn't necessarily have to be an "Open CD" sort of feature imho... it could just be a [prominent]  topic in the Help system
[05:07] <ompaul> LjL, sorry, you misread my intention
[05:07] <LjL> ompaul: but the foundamental aspect in my opinion is that the system should *automatically* detected undetected hardware (err... sorry for the pun) and tell the user. you know, users just *don't* reach for the documentation, unless you force them to
[05:08] <ompaul> LjL, the Open CD aspect, should be replaced with CODE that does what you say
[05:08] <ompaul> three penguins sitting on the edge of an iceberg and they see a killer whale circling just off the shore, one of them mutters, "guess it is just fries again this evening"
[05:09] <LjL> ...
[05:10] <LjL> ompaul: oh by the way, i installed Ubuntu on a relative's computer with a WiFi network... *and it worked out of the box* ;-) i'd never have expected that, given the quantity of people coming and complaining about ndiswrappers and whatever it is
[05:11] <LjL> well, didn't really work out of the box because i didn't know the various machine IP, gateway address, SSID, and all that... but that was definitely a user problem
[05:11] <ompaul> penguin home on a linksys
[05:12] <LjL> ah honestly i don't even know what that Wifi PCI card's brand was
[05:12] <LjL> i was already having enough trouble trying to mount the wrong fan on the wrong dissipator of the wrong processor, to bother looking at hardware specs :\
[05:13] <LjL> ever heard the noise from a 7500RPM fan? i hope i won't again
[09:22] <mdke> it's high time we branched for edgy
[09:49] <nixternal> woohoo
[10:05] <mdke> nixternal: how are you placed for the next few days? I'm going to need some help with edgy translations
[10:05] <nixternal> im open
[10:05] <nixternal> i can help you out
[10:06] <mdke> good news :)
[10:06] <mdke> I'll do some testing first then give you a shout
[10:06] <nixternal> no..the good news is "i just a ton of money by switching to geico"
[10:06] <nixternal> hmm..i wonder if geico commercials are as great in the UK as they are in the US :)
[10:06] <mdke> saved?
[10:07] <mdke> I'm not sure we have em in the UK
[10:07] <nixternal> that should have said "i just SAVED a ton of
[10:07] <nixternal> hahaha
[10:07] <nixternal> you got the idea though...there is a lizard that speaks with a brit accent...great stuff
[10:07] <nixternal> ya, just let me know when you need a hand, and i will hop in
[10:08] <mdke> lizards are good
[10:08] <nixternal> hehe
[10:08] <mdke> thanks, I will mail ya
[10:09] <nixternal> sounds good to me
[10:09] <mdke> damn jobs, taking up too much Ubuntu time
[10:09] <nixternal> i have noticed
[10:09] <mdke> yeah?
[10:09] <mdke> no, that was me being on holiday.
[10:10] <nixternal> you have been rather idle around the channel since you got back...see, i switched from working to go back to school..only reason i am here as much as i am
[10:10] <mdke> ah
[11:02] <FireRabbit> https://help.ubuntu.com/community/CompositeManager i updated this entire secure with information about Edgy and Beryl, if anyone wants to look it over
[11:14] <pepsiman> FireRabbit: "You may just want to put export XLIB_SKIP_ARGB_VISUALS=1 in your ~/.bashrc if this fixes the problems. It is probably better to do it just for the programs that break with Composite, so new problems don't appear."  Is "so new problems don't appear" supposed to be in the first sentence?
[11:15] <FireRabbit> ah i didnt write (or read) that
[11:16] <FireRabbit> ill just get rid of that bit
[11:16] <pepsiman> yeah
[11:16] <FireRabbit> yipes that whole thing is horribly written
[11:18] <FireRabbit> if someone encounters a program that goes bonkers when run along with a composite manager, they should file a bug with that program
[11:21] <pepsiman> yes, but a workaround is still useful
[11:21] <FireRabbit> yes, i am rewriting it, it will still include the workaround
[11:22] <pepsiman> good
[11:28] <FireRabbit> pepsiman: reload
[11:28] <FireRabbit> doh, s/is/are/
[11:29] <FireRabbit> fixed :P
[11:30] <pepsiman> the & has gone from the command line
[11:32] <FireRabbit> hm i suppose i could put that back
[11:33] <theCore> Burgundavia, ping


[00:36] <smgoller> Hey all, I'm running into a situation with a fresh maas install where it's trying to download cloud-init information from the subnet's router instead of the rack controller. Any ideas on how to debug this?
[00:37] <smgoller> basically cloud-init runs through all these things then gives up.
[00:39] <smgoller> so looking at /etc/maas/preseeds/enlist, I see a reference to a variable metadata_enlist_url. Anyone know how that is calculated?
[00:39] <pmatulis> smgoller, what version of maas? are you talking about importing boot images?
[00:41] <smgoller> maas 2.0. I'm talking about trying to add a node to maas automatically via PXE.
[00:41] <smgoller> the machine pulls down the boot image, starts up, then cloud-init runs on the enlisting machine to get information, but it is never able to get anything from the rack controller so enlisting doesn't happen.
[00:42] <smgoller> it basically ends up netbooting an ubuntu image that just sits there and i can't get into it.
[00:42] <pmatulis> odd
[00:43] <smgoller> ayup
[00:43] <pmatulis> did you check the rackd and regiond logs?
[00:43] <smgoller> nothing particularly interesting but i'll check again.
[00:44] <mup> Bug #1633271 opened: [1.9,2.0,2.1] IP addresses without a subnet can cause IP allocation to permanently fail <MAAS:Triaged> <https://launchpad.net/bugs/1633271>
[00:45] <smgoller> regiond logs has a bunch of stuff something trying to connect to itself and failing
[00:49] <smgoller> "provisioningserver.rpc.clusterservice.ClusterClientService"
[01:02] <smgoller> ok, it looks like the problem stems from the fact that i'm running the region and rack controllers on the same machine.
[01:03] <smgoller> so i'm going to split the region and rack controllers back into separate machines.
[01:52] <mup> Bug #1633064 changed: [0-day SRU] MAAS 2.1.0 <verification-done> <maas (Ubuntu):Fix Released> <maas (Ubuntu Yakkety):Fix Released> <maas (Ubuntu Z-series):Fix Committed> <https://launchpad.net/bugs/1633064>
[03:57] <pmatulis> smgoller, that would be surprising. the recommended setup is to have them together. i've certainly never had the problem you're describing
[05:24] <smgoller> eh, it's a home setup, nothing production, so i'm taking it as an opportunity to learn how maas works under the hood
[05:36] <smgoller> so I see when it pxe boots that it's getting a metadata url but it seems to be ignoring it. anyway, I'll mess with it more tomorrow.
[08:56] <mup> Bug #1633378 opened: [Device Discovery] Rename the section Header in the Settings page <MAAS:Triaged> <https://launchpad.net/bugs/1633378>
[10:08] <mup> Bug #1633397 opened: [Device Discovery] In the subnet details page change the label of the  "Active discovery" to "Active mapping" <ui> <MAAS:New> <https://launchpad.net/bugs/1633397>
[10:08] <mup> Bug #1633399 opened: [Device Discovery] Rename the action in the action button in Subnet details to Map <ui> <MAAS:New> <https://launchpad.net/bugs/1633399>
[10:08] <mup> Bug #1633401 opened: [Device Discovery] In device discovery in Settings, remove the header of the first dropdown field (Host discovery and network observation) <ui> <MAAS:New> <https://launchpad.net/bugs/1633401>
[12:48] <mup> Bug #1633452 opened: [Device discovery] In settings, rename the option Disabled (suppress active scanning) in the Active discovery interval field to Never (disabled). <ui> <MAAS:New> <https://launchpad.net/bugs/1633452>
[12:48] <mup> Bug #1633457 opened: [Device Discovery] In settings rename the header "Active discovery interval" to "Active subnet mapping interval" <ui> <MAAS:New> <https://launchpad.net/bugs/1633457>
[12:51] <mup> Bug #1633462 opened: [Device Discovery] In settings in the device discovery section reduce the text of the explanation of the fields. <ui> <MAAS:New> <https://launchpad.net/bugs/1633462>
[13:03] <mup> Bug #1633462 changed: [Device Discovery] In settings in the device discovery section reduce the text of the explanation of the fields. <ui> <MAAS:New> <https://launchpad.net/bugs/1633462>
[13:09] <mup> Bug #1633462 opened: [Device Discovery] In settings in the device discovery section reduce the text of the explanation of the fields. <ui> <MAAS:New> <https://launchpad.net/bugs/1633462>
[13:18] <mup> Bug # opened: 1633467, 1633468, 1633469, 1633470
[17:00] <mup> Bug #1633555 opened: [2.1] link-subnet API should allow arbitrary subnets if interface is disconnected <MAAS:Triaged> <https://launchpad.net/bugs/1633555>
[19:34] <mup> Bug #1633598 opened: [2.1.1] Unable to set local boot-source via the API <MAAS:Confirmed for ltrager> <https://launchpad.net/bugs/1633598>
[19:34] <mup> Bug #1633600 opened: [2.1.1] Docs do not mention the need to mirror bootloaders <MAAS:Confirmed for ltrager> <https://launchpad.net/bugs/1633600>
[19:37] <mup> Bug #1633598 changed: [2.1.1] Unable to set local boot-source via the API <MAAS:Confirmed for ltrager> <https://launchpad.net/bugs/1633598>
[19:37] <mup> Bug #1633600 changed: [2.1.1] Docs do not mention the need to mirror bootloaders <MAAS:Confirmed for ltrager> <https://launchpad.net/bugs/1633600>
[19:46] <mup> Bug #1633598 opened: [2.1.1] Unable to set local boot-source via the API <MAAS:Confirmed for ltrager> <https://launchpad.net/bugs/1633598>
[19:46] <mup> Bug #1633600 opened: [2.1.1] Docs do not mention the need to mirror bootloaders <MAAS:Confirmed for ltrager> <https://launchpad.net/bugs/1633600>
[21:31] <mup> Bug #1595279 changed: [2.0] ipaddresses API doesn't show hostname when reading <oil> <MAAS:Won't Fix> <https://launchpad.net/bugs/1595279>
[21:38] <TheCompWiz> quick question... on 16.04lts... what do I need to get MAAS to manage DHCP? ... I've followed every bit of direction I can find on the wiki... but I'm still stumped.
[21:41] <TheCompWiz> do I need to install the dhcpd?  or is that part of the default install? or what am I missing?
[21:43] <TheCompWiz> scratch that... I see isc-dhcp-server is already installed...
[21:43] <TheCompWiz> so... why didn't it start?
[22:40] <mup> Bug #1633641 opened: A "termination protection"-like feature would be cool <MAAS:New> <https://launchpad.net/bugs/1633641>
[22:46] <mup> Bug #1633641 changed: A "termination protection"-like feature would be cool <MAAS:New> <https://launchpad.net/bugs/1633641>
[22:49] <spaok> hey guys, how can I create a GPT partition via the maas command line? I don't see where I can set partition_table_type
[22:49] <mup> Bug #1633641 opened: A "termination protection"-like feature would be cool <MAAS:New> <https://launchpad.net/bugs/1633641>


[20:39] <enoch85> during the update I mean
[20:39] <enoch85> so it's not apt that is failing, it's when running the php command
[20:39] <enoch85> could the issue be with php?
[20:39] <enoch85> hmm
[20:40] <enoch85> seems www-data is triggering it
[20:40] <jdrv_> somebody has tried to setup a google online account recently, i mean, in the last 24 hours?
[20:40] <jdrv_> i think there is a problem with google online account settings
[20:41] <YankDownUnder> enoch85: How's about momentarily disabling any web services...and then trying again...hmm?
[20:41] <enoch85> YankDownUnder, will do a restore again
[20:41] <enoch85> hold on for 20 mins :)
[20:41] <minimec> enoch85: could you try to set nextcloud into mainenance mode manually first? See... https://docs.nextcloud.com/server/11/admin_manual/maintenance/enable_maintenance.html
[20:43] <enoch85> as you can see in the output I set maintenance mode --on
[20:43] <enoch85> and what happens next is that is tries to update, and it's failing during the update of "calendar"
[20:43] <enoch85> (an app in nextcloud)
[20:44] <enoch85> so maybe disabling calendar or any other apps as well and then update
[20:44] <enoch85> will try
[20:44] <enoch85> have a lot of options here
[20:44] <YankDownUnder> enoch85: You're getting further along than you were an hour ago.
[20:45] <enoch85> YankDownUnder, that's pleasing :)
[20:45] <minimec> enoch85: disable "calendar" seems a good idea
[20:46] <enoch85> still I think it's very strange that Nextcloud or any of its apps should cause a kernel panic
[20:46] <minimec> enoch85: I agree. That should not happen...
[20:46] <enoch85> I'm an experienced ownCloud/Nextcloud user/contriutor and this just seems strange
[20:46] <enoch85> but I won't know until I tried :)
[20:47] <enoch85> it's more likley it's something in MySQL or the webserver itself imo
[20:47] <enoch85> but, running the same version on other servers works
[20:47] <enoch85> so, hmm
[20:48] <YankDownUnder> enoch85: Aliens.
[20:48] <enoch85> YankDownUnder, zombies
[20:48] <enoch85> for sure :)
[20:48] <YankDownUnder> enoch85: TRUMP!
[20:48] <enoch85> HAHA
[20:48] <enoch85> :D
[20:49] <enoch85> YankDownUnder, best internet joke today :D
[20:49] <enoch85> YankDownUnder, you like "no joke" lol
[20:49] <YankDownUnder> enoch85: Trump orders NSA to crash "Nextcloud" application and causes consternation for admin
[20:49] <enoch85> loool, long shot but heck who knows right :D
[20:50] <YankDownUnder> enoch85: Maybe Trump thinks you're Mexican.
[20:50] <enoch85> arrriiba
[20:50] <enoch85> better build a better fireWALL
[20:55] <enoch85> ok, so my plan is to change network adapter to E1000 (VMware) disable contcts before the upgrade and then run the upgrade
[20:56] <enoch85> restore done in 10 minute
[20:56] <enoch85> s
[20:58] <mate_> hex
[21:05] <Pennth> Xenial->Zesty woe. ipython3-notebook got removed from my machines because of an incomplete package dependency in 17.04. I had to install jupyter-core by hand before I could reinstall ipython3-notebook :p
[21:17] <enoch85> YankDownUnder, minimec it IS when updating the apps
[21:17] <enoch85> just tried to update them from GUI and I got kernel panic again
[21:19] <enoch85> yup, disabling the apps prior to update solved it
[21:19] <enoch85> VERY strange
[21:19] <enoch85> deficiently trump
[21:20] <YankDownUnder> enoch85: Yes...strange...more than strange...however, that being said, it begs one to inspect all the aspects of this particular machine...hmm...
[21:20] <enoch85> YankDownUnder, it sure does
[21:21] <YankDownUnder> enoch85: Coffee, donuts, and time to read through all the system logs, web logs, etc etc etc...
[21:22] <enoch85> YankDownUnder, would be easier to just create a new VM and resotre the data actually
[21:22] <enoch85> something is pretty nasty here
[21:23] <YankDownUnder> enoch85: There ya go...easy enough done...
[21:23] <enoch85> just tried to activate the calendar app after a sucesfull update, kernel panic again
[21:24] <enoch85> well, will shit this server down in a few months, it will just have to run without those apps
[21:24] <enoch85> don't think any one uses them anyway :)
[21:24] <YankDownUnder> enoch85: Just as a "thought" - since this is in a VM, have you check the HW clock settings of the VM?
[21:24] <enoch85> hmm
[21:24] <enoch85> can see
[21:24] <YankDownUnder> enoch85: See where I'm going with this "thought"?
[21:25] <enoch85> the time on the Hypervisor and VM isn't the same which causes stuff to go wrong..?
[21:26] <YankDownUnder> enoch85: Not sure...but - for whatever reason - something to do with "time" has caused issues...ergo...
[21:26] <enoch85> YankDownUnder, yeah, worth to check at least
[21:26] <enoch85> hold on
[21:27] <enoch85> nope, they are the same
[21:27] <enoch85> synced over ntp from my firewall
[21:27] <enoch85> opnsense btw
[21:27] <enoch85> great stuff
[21:28] <YankDownUnder> enoch85: Kernel boot params? UTC or HWC?
[21:30] <enoch85> YankDownUnder, ok, so the timezone in the DB tables are NULL in the calendar app
[21:30] <enoch85> hmm
[21:30] <enoch85> going to check the other tables
[21:32] <enoch85> they doesn't seem to have timezone in the same way
[21:32] <enoch85> YankDownUnder, kernel boot params, how do I check that?
[21:34] <YankDownUnder> enoch85: Look at: /boot/grub/grub.cfg
[21:34] <minimec> enoch85: in the grub screen with 'e' or in '/etc/default/grub' --> 'LINUX_DEFAULT', but if you did not change anything manually, you will not have anything special in there.
[21:35] <enoch85> minimec, nope default install of Ubuntu Server 16.04
[21:35] <enoch85> and no UTC or anything now when I checked
[21:37] <enoch85> well, problem is located and I'm satisfied with that at least
[21:37] <enoch85> a new version (major) will be released soon, will see if that helps
[21:37] <enoch85> thanks guys for your help
[21:37] <enoch85> appriciate it!
[21:38] <YankDownUnder> enoch85: Peace, bro
[21:59] <Squarism> what is the first place to look if a hacker entered your ubunutu machine?
[22:00] <kk4ewt> are your logs missing
[22:00] <kk4ewt> if you suspect it has been hacked reinstall period
[22:00] <liplit> "ext4magic" shows a list of all deleted files. for security, how can I wipe those names to avoid "ext4magic" or other software read them. thank you
[22:01] <genii> !info wipe | liplit
[22:02] <liplit> ubottu: is not one file, are thousands of deleted files that "ext4magic" still showing the name.
[22:17] <ArchDebian> "ext4magic" shows a list of all deleted files. For security, how can I Wipe those names to avoid "ext4magic" or other software list deleted filenames? thank you.
[22:23] <ArchDebian> What is the security way to clean the filesystem Journal?
[22:24] <Ben64> ArchDebian: don't use a journal
[22:28] <ArchDebian> Ben64: I agree, but if I'm using, how can I delete it now?
[22:30] <Ben64> turn off journaling, unmount, mount, fill free space with zeros?
[22:51] <bmomjian> Did anyone get an odd sweepstakes notification on Ubuntu today on the OS notification bar at the top of the screen?  I did.
[22:52] <underd0g> no
[22:53] <bmomjian> It mentioned AnandTech
[22:53] <rizonz> meh I still cannot fix my 64 bits preseed issues
[22:54] <oborot> I got a systemd process set to auto restart, I sent it's process a kill -11 and it seems to be in a permanent auto restart loop now? Looks like it tries to restart and gives up too fast. ANybody got any ideas?
[22:54] <oborot> RestartSec is 10
[22:55] <underd0g> oborot: give it more time to restart?
[22:57] <oborot> I tried setting it to 50 seconds
[22:57] <oborot> But it seems RestartSec is just the time it waits before trying to restart again
[22:58] <oborot> My problem seems to be it gives performing the actual restart task too fast
[23:05] <oborot> Found the problem
[23:07] <blackflow> oborot: what was it?
[23:09] <oborot> The process I was killing is binding to a unix socket
[23:09] <oborot> And I'm guessing I need to do some sort of cleanup when the process is killed prior to restarting
[23:10] <oborot> Because nginx was complaining that the socket was already in use
[23:11] <oborot> If I just delete the .sock file it restarts fine...
[23:22] <th34lch3m1st> hi
[23:26] <th34lch3m1st> 16.04 fresh install. amd mobo pci-e radeon. I want to set refresh rate to 75hz. now is 60hz. xrandr  works on session, not on reboot.
[23:28] <th34lch3m1st> two days ago I was using 12.04 with catalyst control center. refresh rate was working at 75hz with no issue.
[23:38] <Umeaboy> Hi!
[23:39] <Umeaboy> Whenever I upgrade from 16.04 to 16.10 or 16.10 to 17.04 I end up with a frozen window when it comes to installing unattended-upgrades.
[23:39] <Umeaboy> Anyone else experienced that?
[23:39] <Umeaboy> I'm NOT using Backports.