[17:27] <frew> does anyone know if there is a way to detect a restart?  That is, I would like to run a command when a service is restarted automatically, but not when it is started via stop then start
[17:30] <frew> I sorta expect the start on reason or something to be in an env var?
[17:32] <chras> frew: yeah
[17:32] <chras> you can do this
[17:32] <chras> sec, lemme look for my code which does this
[17:32] <frew> awesome, thanks
[17:32] <frew> oh is it UPSTART_EVENTS ?
[17:33]  * frew *just* found http://upstart.ubuntu.com/cookbook/#standard-environment-variables
[17:33]  * frew would guess a "respawn" in UPSTART_EVENTS means it crashed
[17:34] <chras> yeah you can check on that
[17:35] <chras> so when you do an initctl restart you want another event to fire?
[17:35] <chras> or when you kill the running process, and upstart restarts it automatically
[17:35] <chras> or both?
[17:35] <frew> no, really all I want, if possible, is that if it crashes (or if I killed it directly)
[17:35] <frew> so the latter (I think)
[17:36] <frew> basically if it restarted due to a crash
[17:36] <chras> right, k, so i have an event which does this
[17:36] <chras> sec lemme pastebin it
[17:36] <frew> thanks
[17:37] <chras> https://pastebin.mozilla.org/8870501
[17:37] <chras> but, when i test it, it doesnt trigger on an initctl restart $process
[17:37] <frew> which is the goal here.
[17:38] <frew> huh, so are scripts bash?
[17:38] <chras> more or less
[17:38] <chras> with a set -e
[17:38] <frew> ok
[17:38] <frew> I assumed they'd be sh
[17:38] <chras> well my sh is linked to bash
[17:38] <frew> mine's dash
[17:38] <chras> i dont use dash
[17:38] <frew> gotcha.
[17:38] <chras> dash does ... unexpected things
[17:38] <frew> heh
[17:39] <frew> so you install this upstart config
[17:39] <frew> and it captures basucally all events?
[17:40] <frew> (hence the JOB!=self_help, which is what this is)
[17:41] <chras> yeah im having trouble getting it to trigger on a restart though
[17:42] <frew> restart meaning a crash?
[17:42] <chras> my thing triggers on a crash
[17:42] <chras> just not an 'initctl restart'
[17:42] <frew> ok that's how I want it
[17:42] <frew> yeah
[17:42] <frew> that's what I want.
[17:42] <frew> if someone manually restarts, I think I'm ok with that not being logged especially
[17:42] <frew> though it would be nice to know as well
[17:42] <chras> i made this event back when i had heartbeat dying unexpectedly
[17:43] <chras> and then i had a config file which took actiosn based on what happened
[17:43] <chras> ie
[17:43] <chras> heartbeat XCPU echo "nas_self_help: heartbeat died unexpectedly with XCPU Signal, restarting" | wall -n
[17:43] <chras> so heartbeat was getting a XCPU kill flag for whatever reason (ended up being a bug in heartbeat debug)
[17:43] <chras> and then id wall it out for instance
[17:44] <frew> right my thought here is to either page or create an issue or osmething
[17:44] <frew> not sure
[17:44] <chras> and it does trigger on a stop / kill / etc
[17:44] <chras> but not sure about restart atm
[17:44] <frew> ok well I need to get this installed and I'll see how well it works
[17:45] <frew> so GCONFIG and PCONFIG (currently) do nothing
[17:45] <frew> so key signal rest is like
[17:45] <frew> who did what
[17:46] <frew> what they did
[17:46] <frew> and other info?
[17:46] <frew> or something?
[17:46] <frew> oh sorry I am reading this and learning more
[17:46] <frew> I hsould talk to my rubber duck before asking here
[17:47] <chras> well thoes are just configs that i use
[17:47] <frew> right
[17:47] <chras> i can paste thoes in the thing, sec
[17:47] <frew> thanks that'd be helpful
[17:48] <chras> https://pastebin.mozilla.org/8870503
[17:49] <chras> i guess the main thing i wanted you to originally see was the 'start on stopped JOB=${some_job}
[17:50] <chras> and then have a task which does whatever you want in a script stanza
[17:50] <frew> right
[17:50] <frew> well and having a single task that does it is very elegant
[17:51] <frew> I was gonna have a script I put in all my scripts
[18:09] <chras> frew: yeah i cant get it working in the context of an 'initctl restart'
[18:11] <chras> as a workaround you could do an initctl emit in your pre-stop
[18:27] <chras> yeah a restart never emits a 'stopping' or 'stopped' event
[18:31] <frew> chras: fwiw the z thing is not really needed anymore iirc
[18:31] <chras> frew: ug. i got it
[18:31] <chras> its definately a bug
[18:31] <frew> yeah
[18:31] <chras> if you have a pre-stop script
[18:32] <chras> then the job goes running -> pre-stop -> start
[18:32] <chras> and never emits a stopping/stopped
[18:32] <frew> you think the maintainers of upstart would fix it?
[18:32] <frew> I was telling my boss about this and he was a little hesitant since upstart is destined for the void
[18:32] <frew> but so is everything so I'm gonna keep going
[18:32] <chras> if you DONT have a pre-stop script, then it works as intended
[18:32] <frew> interesting.
[18:32] <chras> it MIGHT be this bug, https://bugs.launchpad.net/upstart/+bug/703800
[18:33] <frew> btw logger ~~ syslog?
[18:33] <frew> I'd say even if it is that bug, that bug is 4y old and will probably never get fixed
[18:33] <chras> right
[18:34] <frew> I think I'm gonna make an "ANY" job too.
[18:34] <frew> at least so I can get started with this reasonably.
[18:36] <chras> anyways, sorry couldnt be more help
[18:37] <frew> no way this is great
[18:37] <frew> you 100% solved my issue and added more
[18:38] <chras> great
[20:15] <frew> chras: actually I guess I maybe misunderstand you; I don't get logging or anything for a respawn (crash and restart)
[20:15] <frew> is that what you were saying is broken?
[20:17] <chras> hi
[20:18] <chras> k the quick summary was
[20:18] <chras> IF you have a pre-stop, then an initctl restart does start -> pre-stop -> start , and skips doing a stopping, or stopped event
[20:18] <frew> ok that's what I thought you were saying.
[20:19] <frew> this is neither a start, stop, nor restart, but a service that starts and crashes after about 3s, consistently
[20:19] <frew> and I get no events
[20:20] <chras> so your event fails to start at all
[20:20] <chras> and thats what you're trying to catch ?
[20:21] <frew> well I mean, it never forks, so as long as upstart knows, it worked correctly for 3s
[20:21] <frew> and then crashed
[20:21] <frew> but yes, I'm trying to catch an error causing a respawn, likely a compile error
[20:21] <chras> right. ok, i think i understand
[20:21] <frew> though it could have been running for three hours
[20:21] <chras> so your daemon forks, and upstart isnt detecting that it died?
[20:21] <frew> it would still be the same situation
[20:21] <frew> no
[20:21] <frew> it never forks
[20:21] <frew> it just exec's
[20:21] <chras> ah
[20:22] <frew> hence upstart not knowing it's ready
[20:22] <chras> does your upstart throw an error like
[20:23] <chras> main process ($pid) terminated with status $exit?
[20:23] <frew> if it would place an error in the syslog, no
[20:23] <frew> not sure where else to look
[20:23] <chras> check dmesg
[20:23] <chras> do you 'console log' ?
[20:24] <frew> I don't know?
[20:24] <chras> mind putting your event on pastebin?
[20:24] <frew> yeah it's super basic
[20:25] <frew> https://gist.github.com/frioux/0e4e4c1dc0b02f82a9a1a327ae55c248
[20:25] <chras> right k
[20:26] <chras> i think you want to add a 'console log' to that
[20:26] <chras> so you can get some minimal logging
[20:26] <frew> ok
[20:26] <frew> (fwiw I know why it's crashing, I just want to be able to detect better in the future)
[20:27] <chras> and you're trying to throw another event when that one fails to start?
[20:27] <frew> well, I just want to find out, somehow
[20:28] <frew> originally I was gonna write a pre-start that looked at
[20:28] <frew> UPSTART_EVENTS
[20:28] <frew> and if respawn was in there, do a thing
[20:28] <frew> but your solution was a lot more elegan
[20:29] <chras> so, when i do this
[20:32] <chras> https://pastebin.mozilla.org/8870543
[20:32] <chras> when my main process ends with a non 0 exit code (which i assume is your failureA)
[20:32] <chras> it still triggers my self_help
[20:32] <frew> surely it is
[20:33] <frew> although... it's probably exiting 255
[20:33] <frew> any chance upstart ignores high errors?
[20:33] <chras> should be anything non-zero
[20:33] <frew> ok
[20:33] <chras> unless you told it to ignore certain exit codes
[20:33] <frew> I don't even know how I'd do that?
[20:33] <frew> where would that be done
[20:33] <chras> its just a main-config command
[20:34] <chras> sec
[20:34] <chras> lemme find it
[20:35] <chras> http://upstart.ubuntu.com/cookbook/#normal-exit
[20:35] <frew> well I showed you the whole file
[20:35] <frew> unless you can glboally do it, I didn't do that
[20:36] <chras> yeah so itll be non-zero exit codes
[20:36] <chras> will cause it to fail
[20:37] <chras> so my self_help event isnt triggering on your thing exiting weirdly?
[20:38] <frew> correct
[20:38] <frew> I have to admit though
[20:38] <chras> does your reaper fork ?
[20:38] <chras> or is it a foreground process
[20:38] <frew> I did clean up your self_help thing to be shorter and simpler
[20:38] <frew> no it doesn't fork
[20:38] <frew> it's foreground
[20:39] <frew> lemme paste the changes I made
[20:39] <chras> did you run an initctl reload-configuration?
[20:39] <frew> they shouldn't harm anything
[20:39] <chras> to get the new event
[20:39] <frew> yes
[20:39] <chras> does an initctl start self_help work?
[20:39] <frew> well I get output about other services
[20:39] <frew> but let's see
[20:39] <chras> ah interesting so you know it IS working, just not with your reaper?
[20:40] <frew> oh wait
[20:40] <frew> wtf
[20:40] <frew> initctl: Unknown parameter: JOB
[20:40] <frew> does that mean antyhing to you?
[20:40] <chras> yeah
[20:40] <chras> initctl start self_help JOB=test
[20:40] <chras> thats just the instancing stuff triggering
[20:41] <chras> normally JOB is emitted automatically by other upstart events
[20:41] <frew> initctl: Job failed to start
[20:41] <frew> right
[20:41] <frew> no obvious reason why it's failing
[20:41] <chras> hm, pastebin it ?
[20:41] <frew> the modified self_help or what?
[20:41] <chras> yea
[20:41] <frew> k
[20:42] <frew> https://gist.github.com/frioux/953fe2f4b950c2bef58521f0ca0e0ad9
[20:42] <frew> should be effectively the same, but work with any POSIX shell (and only allow one extra config file)
[20:42] <frew> (and I renamed it watchdog)
[20:43] <chras> right
[20:45] <chras> you're using dash right?
[20:45] <frew> I wrote it with dash in mind, since we are moving to dash soon, but it's still bash now (12.04)
[20:46] <frew> oh no
[20:46] <chras> its just a syntax error for me
[20:46] <frew> 12.04 is dash
[20:46] <frew> oh?
[20:46]  * frew eyeballs
[20:47] <chras> ./foo.script: 24: ./foo.script: Syntax error: "(" unexpected (expecting "then")
[20:47] <frew> I wonder why that's wrong
[20:47] <frew> it's supposed to work
[20:47] <frew> `(expression)  True if expression is true.` from dash(1)
[20:48] <chras> yeah it looks right
[20:48] <chras> sec, seeing if i can fix
[20:48] <frew> can repro fwiw
[20:49] <frew> fwiw the ()'s are not needed, since -o binds more tightly than -a
[20:49] <frew> but I thoguht it made it easier to read
[20:50] <frew> dash -c '[ ( -f /bin/dash ) ] && echo 1'
[20:51] <frew> I think this must be a bug in dash.
[20:52] <chras> dash does unexpected things :P
[20:52] <frew> I never claimed it was perfect
[20:53] <frew> I jsut can't switch what /bin/sh is
[20:54] <frew> ok I'll just leave out the () for now
[20:54] <chras> yeah i cant use ()'s in dash for whatever reason
[21:06] <frew> oh derp
[21:06] <frew> dash -c '[ \( -f /bin/dash \) ] && echo true'
[21:07] <frew> gotta escape them for some reason
[21:08] <frew> must be a history expansion or something.
[21:09] <frew> nonetheless I do see this: `self_help(pt-heartbeat-update-mysql): caught job[pt-heartbeat-update-mysql] instance[] process[respawn] result[failed] status[] signal[]` in syslog, but nothing about my reaper
[21:20] <chras> hm
[21:20] <frew> trying a different route, but 90% sure that upstart is just not creating an event for that
[21:20] <frew> I don't see where it would in the lifecycle anyway, fwiw
[21:21] <chras> you can try bumping the debug up with log-priority debug
[21:21] <chras> and see where its dying
[21:23] <frew> hm.
[21:23] <frew> I have a theory.
[21:23]  * frew "simplifies"
[21:28] <frew> yeah, it catches start and stop, but not respawn
[21:29] <chras> respawn, when the main process dies?
[21:29] <frew> yeah
[21:29] <frew> respawn is an even that's not real, to be clear
[21:29] <frew> I thought it might be
[21:29] <frew> s/even/event
[21:30] <frew> I sorta thing consuming events won't work for this, since there isn't one for what I'm thinking of
[21:32] <chras> lemme try here
[21:32] <chras> k so
[21:33] <chras> we're triggering self_help/watchdog on the upstart event 'stopped'
[21:33] <chras> after something is completely stopped
[21:33] <chras> for it to also hit your respawn, you need to change that to be 'start on stopping ...'
[21:34] <chras> i should make that change for my own needs as well i guess
[21:37] <chras> with it only being set to 'stopped'
[21:38] <chras> it will wait for upstart to give up on respawning before its triggered
[21:38] <chras> like i suppose, its the difference between if your job fails 10 times in a row, and upstart gives up on it
[21:38] <chras> getting 10 emails, or 1
[21:38] <chras> if your watchdog sends email out at least.
[21:51] <chras> oo, interesting though
[21:52] <chras> the respawn attempts have a result[ok] instead of a result[failed]


[14:59]  * D4RKS1D3 Hi
[17:34] <f1gjam> ahasenack, trying again - new clean install
[17:34] <f1gjam> fingers crossed
[19:35] <f1gjam> ahasenack, failed
[19:36] <f1gjam> fails on deploying landscape
[19:36] <f1gjam> which logs should i grab
[20:46] <mup> Bug #1598937 opened: [2.0 RC1 ] Following fresh install maas command fails -  PermissionError: [Errno 13] Permission denied: '/home/ubuntu/.maascli.db' <oil> <MAAS:New> <https://launchpad.net/bugs/1598937>
[21:07] <mup> Bug #1598941 opened: [2.0 RC1] maas ipranges <> command does not work <oil> <MAAS:New> <https://launchpad.net/bugs/1598941>


[05:49] <infinity> elmo : I have no objections to it, in fact, I sent dholbach your way.
[02:49] <jbailey> w/in 4
[02:50] <elmo> GRR
[02:51] <elmo> lamont/infinity: royal's chroot is ghc-fux0red


[00:00] <davecheney> niemeyer: sure thing
[00:29] <niemeyer> davecheney: ping
[00:31] <davecheney> niemeyer: ac
[00:37] <davecheney> niemeyer: ack
[00:49] <niemeyer> davecheney: Yo
[00:49] <niemeyer> davecheney: I was having a look at go-cmd-jujud-services
[00:50] <niemeyer> davecheney: A few points:
[00:50] <niemeyer> - You mention the actual meat of the change. Has anything changed within the moved files themselves? Just wondering if I should review that or not.
[00:51] <niemeyer> - I was expecting the package to be service/<service name>/*.go
[00:51] <niemeyer> More precisely, juju-core/service/<service name>/*.go
[00:52] <niemeyer> Moving them out of jujud but keeping all of the services within the same file would allow importing, but preserve the "mess" which is having all of those unrelated things in the same place
[00:53] <niemeyer> I think that's it.. otherwise the idea of moving sounds great
[01:27] <davecheney> niemeyer: thanks for the feedback, i'll fix up the CL and repropse
[01:41] <davecheney> niemeyer: i'm going to do the service CL in three parts, which might make it easier to review and merge
[01:42] <davecheney> 1, cmd/services
[01:42] <davecheney> 2, split provisioner and provisioning
[01:42] <davecheney> 3, move provisioner to the new package
[01:43] <niemeyer> davecheney: Sounds good
[01:43] <davecheney> niemeyer: does bzr have the concept of hg cp ?
[01:43] <niemeyer> davecheney: Btw, I suggest juju-core/services
[01:43] <niemeyer> davecheney: Hmm.. not sure
[01:43] <davecheney> niemeyer: yes, good idea, they dont' belong directly in cmd
[01:44] <davecheney> niemeyer: just trying to reduce the size of the CL that just bifurcate provisioning.go
[01:56] <niemeyer> davecheney: Cool.. as long as we don't move + change the code at the same time, it's easy to review either way I think
[01:56] <niemeyer> davecheney: If there are changes that are tricky to avoid, it's fine to just mention them in the description so we can have a more careful look rather than assuming it's just coded being moved
[01:57] <davecheney> niemeyer: https://codereview.appspot.com/6350064 << just moves Provisioner into it's own file (and tests)
[01:58] <davecheney> which will make the other change easier to digest
[01:59] <niemeyer> davecheney: If it's just moving, +1 for sure
[01:59] <davecheney> niemeyer: yeah, just splits so I can move later and the diff will just show the package header changed and a few imports
[01:59] <niemeyer> davecheney: Awesome, thanks, sent the LGTM there too
[02:00] <davecheney> niemeyer: this will have a small impact on williams test CL as well
[02:00] <davecheney> i'll work with him this afternoon to help unbreak it
[02:01] <davecheney> niemeyer: can I propose a branch on top of his banch ? ie, can I do the fixes for his branch and he can import them ?
[02:03] <niemeyer> davecheney: Absolutely
[02:04] <davecheney> niemeyer: right, sounds fair, and I want his coretesting and zksuite types
[02:05] <niemeyer> davecheney: Neat, branches are lovely in those cases
[02:05] <niemeyer> davecheney: What would otherwise be a blocker is just a branch + merge
[02:29] <davecheney> niemeyer: https://codereview.appspot.com/6344071 << much smaller
[04:18] <niemeyer> Phew'
[04:21] <niemeyer> davecheney: LGTM
[04:26] <niemeyer> Okay.. time to sleep now
[04:26] <niemeyer> Good night all
[04:26] <niemeyer> davecheney: and good afternoon for you
[06:08] <fwereade> davecheney, morning
[06:09] <davecheney> fwereade: howdy
[06:09] <davecheney> you've got a green light to drop that massive branch
[06:09] <davecheney> but i've spent the day making conflicts
[06:09] <davecheney> so sorry about that
[06:10] <fwereade> davecheney, ah, no worries, I expect I can manage :)
[06:10] <davecheney> fwereade: let me know if I can be of use, the faster I can get your changes, the better
[06:11] <fwereade> davecheney, you can just merge from that branch and work on top of it -- but then the requested changes to that will lead you to have to deal with probably as many conflicts
[06:11] <davecheney> fwereade: yeah, i've got a few branches in the air at the moment
[06:12] <davecheney> but i'm truing to keep my main 'provision on ec2' as close to trunk as possible
[06:44] <davecheney> error: cannot upload tools: cannot make S3 control bucket: The specified location-constraint is not valid
[06:44] <davecheney> s3 can get stuffed
[06:44] <davecheney> you _must_ specify a LocationConstraint if you are _not_ using us-east-1 or us-west-1
[06:45] <davecheney> but you _mustnot_ specify one if you _are_ using us-east-1
[06:45] <davecheney> which is bullshit
[07:02] <fwereade> davecheney, eww
[07:15] <davecheney> fwereade: going to be a bit of a shit to write a mock for
[07:15] <fwereade> davecheney, yeah, I bet
[07:23] <davecheney> fwereade: this is a nasty wart from us-east-1 being special because it's the first region
[08:41] <TheMue> Hi fwereade
[08:42] <fwereade> TheMue, heyhey
[08:44] <TheMue> fwereade: Just watching the I/O talks.
[08:46] <fwereade> TheMue, I must get to those
[08:46] <fwereade> TheMue, somewhat code-obsessed at the moment
[08:48] <TheMue> fwereade: Yeah, with your great change
[08:49] <fwereade> TheMue, I'm going through an obsessive set of running the presence tests
[08:49] <fwereade> TheMue, sadly they are not 100% reliable
[08:50] <fwereade> TheMue, *but* I'm pretty sure that every failure is now timing-related and can be attributed to impolite schedulers and/or GC pauses
[08:51] <TheMue> fwereade: Hard to fix stuff.
[08:52] <fwereade> TheMue, yeah, GOMAXPROCS seems to help
[08:52] <fwereade> TheMue, but that could just be my monkey-brain overlaying patterns where none exist
[08:53] <TheMue> fwereade: *rofl*
[09:59] <TheMue> fwereade: Could you please help me with todays firewall code?
[10:00] <TheMue> fwereade: It's regarding line 278ff.
[10:00] <fwereade> TheMue, sure, lookin for it...
[10:01]  * fwereade looks somewhat apprehensive
[10:02] <TheMue> fwereade: Thx, and there especially  line 281.
[10:02] <TheMue> fwereade: Here a machine, not the machine state, is retrieved from the provider.
[10:02] <TheMue> fwereade: Sadly I don't find yet what has this role in our code today.
[10:03] <TheMue> fwereade: Did it change or isn't it yet ported?
[10:03] <fwereade> TheMue, in go I think that's called an Instance
[10:03] <fwereade> TheMue, corresponds to ProviderMachine, right?
[10:04] <TheMue> fwereade: That's what I want to find out.
[10:04] <fwereade> TheMue, I'm 99% sure it corresponds directly to environs.Instance
[10:05] <TheMue> fwereade: OK, will take a deeper look. That may be the missing link.
[10:05] <TheMue> fwereade: Thank you.
[10:05] <fwereade> TheMue, a pleasure :0
[10:07] <fwereade> TheMue, *dammit*, I have to go to the bank, wanted to finish this off before :/
[10:07] <fwereade> TheMue, meeting in 50 mins, right?
[10:58] <davecheney> niemeyer: thanks for your review
[10:58] <davecheney> niemeyer: figuring out how to test a condition that can only be false if you're talking to the real us-east-1 is tricky
[10:59] <niemeyer> Yo!
[10:59] <niemeyer> davecheney: Hmm
[10:59] <niemeyer> davecheney: Does it fail if you keep the constraint while talking to us-east-1?
[11:00] <davecheney> niemeyer: yes
[11:00]  * davecheney facepalms
[11:00] <davecheney> that was the first thing i tried
[11:00] <davecheney> us-east-1 is ... special
[11:00] <niemeyer> davecheney: Lovely
[11:00] <niemeyer> davecheney: Anyway, that still sounds easy to test in s3_test.go
[11:00] <davecheney> niemeyer: otherwise it would be straight forward
[11:00] <davecheney> niemeyer: i
[11:01] <davecheney> i'll take another crack tomorrow
[11:01] <niemeyer> davecheney: We have the payload at hanhd
[11:01] <niemeyer> davecheney: And also have the test region at hand
[11:01] <niemeyer> davecheney: We can tweak the region however we want, and see the effect on the payload
[11:02] <niemeyer> Isn't it meeting time?
[11:03] <niemeyer> fwereade, TheMue, davecheney: Meeting?
[11:03] <fwereade> niemeyer, SGTM
[11:03] <TheMue> Yes, but currently phone.
[11:03] <TheMue> In a few moments.
[11:04] <davecheney> niemeyer: sure, two secs
[11:04] <niemeyer> Hmm.. Aram isn't around
[11:05] <niemeyer> Starting a Hangout
[11:05] <davecheney> niemeyer: send the invite to david.cheney@canonical
[11:07] <niemeyer> Done
[11:25] <niemeyer> fwereade: ping
[11:49] <davecheney> nouns that are taken: service, agent, command, process
[11:51] <niemeyer> worker?
[11:51] <davecheney> possible nouns: daemon,
[11:52] <davecheney> ^ pretentious ?
[11:54] <davecheney> http://laughingmeme.org/2005/12/23/there-are-only-two-hard-things-in-computer-science-cache-invalidation-and-naming-things/
[11:56] <fwereade> davecheney, and off-by-one-errors
[12:08] <niemeyer> fwereade, davecheney: Suggestion: Life, SetLife and WatchLife..
[12:26] <TheMue> +1
[12:29] <davecheney> good discussion tonight
[12:30] <davecheney> just for reference, i'll sleep on the renaming stuff we discussed and email tomorrow
[12:30] <TheMue> davecheney: ;)
[12:31] <davecheney> i am in agreement that we want to avoid the situation of a bug report that says 'something something agent did not blah'
[12:32] <davecheney> and we have to ask for clarification on if they mean the agent process, or the one of several agent 'services' we had running inside that binary
[12:36] <Aram> hello.
[12:36] <Aram> grr, dreadfully sorry I couldn't make it to the meeting.
[12:36] <Aram> had internet problems all morning.
[12:36] <Aram> meh.
[12:42] <davecheney> i blame the leap second
[13:35] <TheMue> Hmm, could it be that todays "provider".get_opened_ports() has no counterpart?
[13:41] <hazmat> TheMue,  what would the counterpart be? get closed ports?
[13:42] <TheMue> hazmat: Hi, eh, wrong wording. I mean the ported part, which I expected in environs.Environ.
[13:44] <hazmat> ah
[13:44] <hazmat> yeah.. status will need that, else its not really used outside of the provider
[13:45] <hazmat> er. provisioning agent
[13:45] <fwereade> TheMue, seems that way, it's not in the interface
[13:49] <TheMue> hazmat: Yes, I'm porting firewall.py for the provisioning agent. And this type needs it to retrieve the current open ports to compare it with the state.
[15:00]  * niemeyer waves
[15:03] <Aram> hi niemeyer.
[15:03] <niemeyer> Aram: Yo
[15:03] <Aram> niemeyer: sorry for not making it to the meeting :(.
[15:03] <Aram> my internet didn't work.
[15:03] <Aram> which is a first, after an year of staying here.
[15:03] <niemeyer> Aram: It's ok, we can catch up later.. just a bit unfortunate because we talked about the proposal in the ML and covered a few angles, but we can revive that again
[15:05] <Aram> yes, I really want to hear opinions about that.
[15:08] <niemeyer> Aram: Well, me too ;)
[15:26] <Aram> niemeyer: more lbox trouble...
[15:26] <Aram> http://paste.ubuntu.com/1073238/
[15:34] <fwereade> niemeyer, hey, I have something that looks very similar: http://paste.ubuntu.com/1073263/
[15:34] <niemeyer> Hmm
[15:34] <fwereade> everyone, I have to go a bit early today... I will certainly be back on in the evening to submit that change, by hook or by crook ;)
[15:34] <niemeyer> fwereade: Cheers
[15:34] <Aram> niemeyer: maybe it's a leap second bug ;)
[15:34] <Aram> fwereade: have fun.
[15:34] <niemeyer> Aram: Possibly :)
[15:34] <fwereade> Aram, haha :)
[15:35] <fwereade> cheers guys, see you later
[15:37] <niemeyer> Aram: Can you please run with -debug?
[15:37] <niemeyer> Aram: It looks like codereview might be blowing up
[15:37] <Aram> niemeyer: sure thing
[15:38] <niemeyer> Aram: Seems that reaching that point is returning without err
[15:38] <niemeyer> Aram: oh, wait, maybe I misread
[15:39] <Aram> niemeyer: http://paste.ubuntu.com/1073272/
[15:39] <niemeyer> Aram: The code on goetveld definitely looks wrong
[15:40] <niemeyer> Aram: Hah, it's the same problem as before :(
[15:40] <niemeyer> Aram: Just in a different package
[15:41] <Aram> heh.
[15:41] <niemeyer> Aram: The change in redirect semantics sucks
[15:51] <Aram> niemeyer: yeah, I don't think this should have happened, document the old behavior and stick with it until at least go 1.1.
[15:52] <niemeyer> Aram: I'll see what I can do to workaround the issue.. the change in semantics is actually a problem in this case, because I want the response before the redirect, and there's apparently no way to do this now
[16:48] <Aram> lunch
[17:46] <niemeyer> Aram: lbox is coming
[17:46] <Aram> niemeyer: fantastic
[17:46] <niemeyer> Aram: I'll rebuild against golang-stable.. filed a bug against golang and Brad F. will revert his change next week
[17:47] <niemeyer> Aram: There's simply no way to grab a response before a redirect with his change
[17:47] <niemeyer> Aram: Which is needed in this case, because the login endpoint redirects, and we want its Cookie before we move on
[17:47] <Aram> niemeyer: I see.
[17:47] <Aram> niemeyer: so you bakported the exp/ stuff we're using?
[17:48] <niemeyer> Aram: We're not using anything experimental
[17:48] <niemeyer> Aram: It was using golang-tip just for historical purposes (IOW, before Go 1 was out, we depended on tip)
[17:49] <niemeyer> Aram: It turns out that it's handy to depend on tip, though..
[17:49] <niemeyer> Aram: I may well roll it back after next week
[17:49] <niemeyer> Aram: I wouldn't have caught the bug on time otherwise
[17:56] <niemeyer> Aram: Silly me.. apparently it does need exp/ from tip
[17:56] <Aram> yeah, I remembered I couldn't compile it at some point.
[17:56] <Aram> because of this.
[18:00] <niemeyer> Aram: You were totally right
[18:00] <niemeyer> Aram: I'll just embed it for the moment
[18:17] <niemeyer> Aram: lbox should be good
[18:18] <Aram> niemeyer: thanks.
[20:29] <niemeyer> Aram: ping
[20:29] <Aram> pong
[20:29] <Aram> seen your email
[20:35] <niemeyer> Aram: Cool, i was actually going to suggest something, but I'm just reviewing the pre-req.. will work out well
[20:57] <Aram> niemeyer: updated that CL, also seen your bug report, will fix it tomorrow, will retreat for now, it's kind of late here :).
[20:59] <niemeyer> Aram: I can imagine.. almost finishing the last review
[20:59] <niemeyer> Aram: Thanks a lot for your help on that stuff
[21:00] <Aram> my pleasure.
[21:59] <niemeyer> davecheney: Morning!
[21:59]  * niemeyer heads off for dinner
[22:00] <davecheney> ziing
[22:02] <fwereade_> davecheney, heyhey, I just merged that monster
[22:03] <fwereade_> davecheney, I hop it didn't mess with your Machiner plans too badly
[22:12] <davecheney> fwereade_: nah, it was a few minutes work to rebranch and do it again
[22:12] <davecheney> fwereade_: the benefits far outweigh the cost
[22:21] <fwereade_> davecheney, btw, if you ever spot the presence tests misbehaving, scream and should and send me the log output please :)
[22:21] <fwereade_> s/should/shout/
[22:37] <davecheney> m_3: you around ?
[22:38] <davecheney> niemeyer: I had to repropose the machiner -> service/machiner branch here https://codereview.appspot.com/6348077
[22:39] <davecheney> additionally, now it's not a prereq, the branch is much cleaner
[23:28] <m_3> davecheney:
[23:28] <m_3> yo
[23:32] <m_3> davecheney: my reply probably just got out on smtp
[23:33] <davecheney> m_3: cool
[23:33] <m_3> tomorrow'd probably be great for Ultimo if that works for you
[23:33] <davecheney> yeah, that sounds good


[01:19] <nhaines> Oh, if anyone wanted my presentation from the installfest: http://people.ubuntu.com/~nhaines/documents/events/2014/oc-installfest-may/Welcome%20to%20Ubuntu%2014.04%20LTS.odp
[01:19] <darthrobot> Content type: [application/vnd.oasis.opendocument.presentation] Size: [689419]
[01:19] <nhaines> pleia2: ^^
[02:06] <pleia2> nhaines: thanks!
[03:41] <nhaines> Also!  http://www.nhaines.com/blog/2014/06/02/ubuntu-installfest-with-oclug/
[03:41] <darthrobot> Title: [Ubuntu Installfest with OCLUG | Nathan Haines]
[03:41] <nhaines> Coming to a Planet Ubuntu near you.
[04:42] <pleia2> nhaines: great writeup :)
[04:49] <nhaines> pleia2: thanks!  I wasn't so sure after I finished if it came out well or not.  But it's been 9 days so I hit publish anyway!  :P
[04:50] <pleia2> hehe
[05:21] <nhaines> pleia2: oh, before I forget.  Are there any plans as far as recording who gets how many discs?
[05:21] <nhaines> I have a spreadsheet at the moment but wasn't sure where to put the data.
[05:32] <rww> wiki
[05:33] <nhaines> rww: [citation needed]
[05:38] <rww> oh hrm, i thought we had a page for that
[05:39] <rww> throw it in a google doc or something, i guess
[05:41] <nhaines> I do have one of those.
[13:57] <Roguehorse> Good Morning
[15:18] <pleia2> nhaines: I haven't traditionally kept track super closely, LUGs tell me they need them when I visit and just grab a handful


[00:00] <godbyk> My current organization is that I have ~/bzr/ubuntu-docs/{saucy,trusty} and ~/bzr/serverguide/{saucy,trusty}, etc.
[00:00] <godbyk> I try to keep the directory name the same as the repository name.
[00:00] <godbyk> But that's just so I can figure out where I'm at ('cause I'm often lost). :)
[00:05] <dsmythies> godbyk: Sounds as though you agree with delete of "Advanced". Do you have an opinion on "Updating a check-out"? I have never used "bzr update". I only use "bzr pull".
[00:14] <godbyk> dsmythies: I always use bzr pull, too.
[00:14] <godbyk> Not sure what update does..
[00:14]  * godbyk reads the man page
[00:15] <godbyk> Okay, I just finished reading 'bzr help update' and 'bzr help pull' and I don't really know what the difference is.
[00:29] <dsmythies> godbyk: Me neither.
[00:33] <dsmythies> pleia2: Does xubuntu doc have a task list? I couldn't find one. Please refer to (where I currently have nothing for xubuntu):
[00:33] <dsmythies> pleia2: https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation/Tasks
[00:35] <pleia2> dsmythies: all we do is create a blueprint each cycle which has tasks: https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-t-docs
[00:38] <dsmythies> pleia2: does the -t- part mean trusty? (it looks like yes) i.e. if it were to be linked, would it need to be updated each cycle?
[00:38] <pleia2> dsmythies: yes
[00:39] <dsmythies> pleia2: your call. Do you want it linked on the task page or no?
[00:40] <pleia2> dsmythies: I don't think so, but I'll follow up with our docs lead to see what he thinks
[00:42] <dsmythies> pleias2: Do you have any input on what I am doing with the repository page? (Note: my notes to you early today may have scrolled off your screen.)
[00:42] <dsmythies> pleia2: And godbyk perferred the include file option.
[00:47] <pleia2> dsmythies: I saw, but haven't had a chance to take a closer look, hope to have some time this evening (wrapping up work in a half hour or so)
[00:47] <dsmythies> pleia2: O.K. thanks. Sorry to have asked again.
[00:49] <pleia2> dsmythies: no worries, thanks for the reminder :)
[00:50] <dsmythies> pleia2: To help all of us, I think I'll temporarily add "begin included file" and "end included file" notes. I'll also go ahead and change the Desktop page, as a test, and we can revert if we do not like it.
[03:24] <pleia2> dsmythies: +1 to including solution, seems most reasonable :) nice work on these pages!
[03:26] <dsmythies> pleia2: Thanks very much for having a look. Yes, the thinking is that maybe we can use includes to get around having to edit the same thing multiple times.
[03:27] <pleia2> yeah, includes are great
[03:28] <dsmythies> pleia2: In this case the cost was just a lillte bit of non desktop info getting into its page.
[21:48] <ruliezz> dsmythies: ping
[21:48] <dsmythies> ruliezz: Yes, I am here.
[21:49] <ruliezz> Lets start a private chat
[21:49] <dsmythies> ruliezz: I am somewhat IRC challenged. I do not know how to do private chats.
[21:50] <belkinsa> dsmythies, what do you use as a client?
[21:50] <dsmythies> irssi
[21:50] <ruliezz> Pidgin ;)
[21:50] <ruliezz> I have start a private chat now
[21:50] <belkinsa> Irssi as in the ptablet app?
[21:50] <ruliezz> dsmythies:  do you see it now?
[21:51] <belkinsa> You can always use /msg ruliezz text or whatever the command is
[21:51] <ruliezz> indead
[21:51] <dsmythies> belkinsa: I run irssi on a server. no GUI. I ssh to that server from a windows computer.
[21:51] <belkinsa> Ah.  I see.
[21:52] <dsmythies> ruliezz: I don't see anything. Am I supposed to?
[21:52] <ruliezz> dsmythies: 'from a windows computer' != Ubuntu == 'ERROR, Please reinstall your pc with Linux Ubuntu
[21:53] <dsmythies> ruliezz: lol
[21:53] <ruliezz> Uhmm use pidgin :)
[21:53] <ruliezz> is works on Linux and Windows too
[22:00] <ruliezz> Maybe it would be a nice idea to make a hangout about Nagios
[22:00] <ruliezz> I will do it but my english is more dutch english then correct English :)
[22:03]  * dsmythies did manage to find the private chat
[22:04] <ruliezz> :)
[22:04] <ruliezz> sleep well everyone!
[22:04] <ruliezz> talk to you tomorrow or othertime ;)
[22:04] <dsmythies> O.K. bye
[22:04] <ruliezz> ;)