=== markthomas_zz is now known as markthomas === markthomas is now known as markthomas_away === markthomas_away is now known as markthomas === markthomas is now known as markthomas_away === thumper is now known as thumper-afk === markthomas_away is now known as markthomas === thumper-afk is now known as thumper === markthomas is now known as markthomas_away === thumper is now known as thumper-afk === markthomas_away is now known as markthomas === Daviey_ is now known as Daviey === markthomas is now known as markthomas_away === markthomas_away is now known as markthomas === thumper-afk is now known as thumper [09:01] hi there [09:01] I'm trying to learn juju and to connect it to my rackspace cloud [09:01] I'm generating the environments.yaml [09:02] and I think I've everything fine, but I'm getting this error: [09:02] ERROR required environment variable not set for credentials attribute: Secrets === rogpeppe1 is now known as rogpeppe [09:03] the Secrets variable is not even in the environments.yaml file [09:03] so I don't know how to fix it [09:03] any idea why is asking for that variable= [09:03] any idea why is asking for that variable? [09:27] I'm told by jcastro that I can set a backup dir with the postgres charm using some of the backup variables at https://jujucharms.com/fullscreen/search/precise/postgresql-52/?text=postgresql#bws-configuration. How do I set them? [09:51] ERROR juju.state.open.go:92 TLS handshake failed: x509 certificate has expired or is not yet valid [09:52] any clues where to start looking? === Tribaal_ is now known as Tribaal [10:02] anybody? [10:05] ashipika: are you using a self signed cert? [10:06] this is what i get when i run juju bootstrap.. [10:06] sure, but against *what* [10:06] but i see now that it might be a "user" problem.. since it appears that juju bootstrap was ran as another user [10:06] juju has multiple providers, and we know that say, ec2, has a valid cert [10:06] null environemnt [10:06] environment [10:08] ashipika: and can you say, curl something from bootstrap-host without it complaining about the cert? [10:09] curl to boostrap-host from another host? [10:14] ashipika: or ssh, probably more appropriate [10:14] check the host you're actually conecting to at any rate [12:45] aquarius: It'll automatically backup to /var/lib/postgresql/backups, but you can `juju set postgresql backup_dir=/path/` to change configuration [12:46] marcoceppi, oh, that's already happening? sweet! [12:46] so I don't need to change anything [12:46] aquarius: nope! Charms should always do the right thing(tm) by default [12:46] that's excellent. [12:46] aquarius: in this case it'll have the last 5 days of backups in that directory [12:47] I should probably have a separate thing to send the backups elsewhere, mind :) [12:47] aquarius: a great case for a suborindate charm [12:47] not sure that's a charm; it's a one-liner in my crontab ;) [12:48] aquarius: sure, I was just trying to slyly convince you to write a subordinate charm for backups ;) [12:48] yeah, that's not happening ;) [12:48] I barely understand how to do it myself [12:49] trying to write a thing which keeps every sysadmin in the world happy is nowhere near my priority list :P [12:49] eh, worth a shot [12:57] :) === gary_pos` is now known as gary_poster === morty_ is now known as morty [14:40] How does a subordinate charm works? I have an logstash-agent charm, then I deployed it... later I add a relation logstash-agent service2, now logstash is subordinated to service2. If I add a relation to logstash-agent (let's say redis). Will it update de service2 logstash-agent? [14:46] X-warrior: yes, it will === jose- is now known as jose === jose is now known as 64MAA3JWF === 64MAA3JWF is now known as jose- === wedgwood_ is now known as wedgwood === smoser` is now known as smoser === freeflying is now known as freeflying_away [15:47] marcoceppi: ty still trying to get this logstash to work [15:47] :D [15:47] btw, why when I use upgrade-charm I get an "already running latest charm", but I just updated one of the files... [15:51] oh forgot, just found my error [15:52] bac, gary_poster staging.jujucharms.com is sending connection refused messages about mongo. I am going to investigate [15:52] thanks sinzui. let me know if i can help [15:53] ty sinzui [16:02] bac, gary_poster mongodb filled the disk with logs. I deleted some and restarted mongo. I see staging is happy [16:03] yay [16:03] sinzui: can we turn down the log level? logrotate? [16:04] bac, I think we need to update the charm to handle rotation. Te log-level also seem to be permanently on spew [16:05] sinzui: ok, i'll make a card for us === jose- is now known as jose === freeflying_away is now known as freeflying [17:29] good morning [17:29] getting this error on Azure when bootstrapping: [17:29] 2013-12-07 04:23:00 ERROR juju supercommand.go:282 POST request failed: BadRequest - The affinity group name is empty or was not specified. (http code 400: Bad Request) [17:29] juju bootstrap --show-log --upload-tools 6.01s user 5.05s system 12% cpu 1:28.15 total [17:29] i'm running everything out of west us but trying to run the juju command from a non-azure machine. [17:58] back [18:06] hey mxc, sorry, no responses while you were away [18:06] sarnold: thanks for the heads up === mhall119 is now known as mhall119|afk === mhall119|afk is now known as mhall119 === CyberJacob|Away is now known as CyberJacob [20:00] http://askubuntu.com/questions/388419/juju-bootstrap-fails-in-azure-badrequest-the-affinity-group-name-is-empty-or <- would appreciate if anyone could take a look === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying [22:51] mxc, natefinch is who you should keep an eye out, he's the azure guy afaict [22:52] jcastro: thanks! [22:56] mxc, did you have the mail to the list on juju bootstrap failing? [22:58] http://askubuntu.com/questions/388419/juju-bootstrap-fails-in-azure-badrequest-the-affinity-group-name-is-empty-or [22:59] mxc if you run "apt-get update && apt-get install juju-core" on your stand along machines does that give you 1.16.4? [23:00] was that a bad use of the list? [23:00] if so, apologies [23:01] mxc, no it was a great use [23:01] arosales: 1.16.4-saucy-amd64 [23:01] mxc, just wante to confirm mxc and the list mail was the same subject [23:01] oh, yeah, that was me [23:02] cool, so an apt-get update gets you the latest juju [23:02] mxc which reagion is your ubuntu stand alone instance? [23:02] all west us [23:02] mxc sounds like you are using an azure instance as the juju client (ie to issues juju deploys from) [23:03] but also trying to get this working from a non-azure, plain old windows machine [23:04] arosales: so, yes, that would be ok [23:07] mxc, I was able to bootstrap from my ubuntu client outside of azure [23:07] does the machine that I am running juju bootstrap from need to have certain ports open? [23:07] I will see if I can reproduce your environment but bootstraping from within azure. [23:07] i get this from inside and outside of azure [23:08] is it possible to get even more debug output than just --show-log? [23:08] --debug [23:09] ty [23:09] doesn't help much in this case [23:10] ooh, a bit more [23:10] }: mirror data for "com.ubuntu.juju:released:tools" not found [23:11] mxc, can you pastebin your full --debug output? [23:12] mxc, it should retry if a local mirror isn't found. [23:13] mxc, hmm . . . I don't know what port juju client [23:13] http://pastebin.ubuntu.com/6548362/ [23:13] mxc, can you drop the --upload-tools [23:14] sec [23:15] mxc, it also looks like jujustorewestdocmunch may not be fully configured [23:15] 2013-12-09 19:45:38 ERROR juju supercommand.go:282 cannot obtain storage account keys: GET request failed: ResourceNotFound - The storage account 'jujustorewestdocmunch' was not found. (http code 404: Not Found) [23:17] oops, i accidentally copied way too much [23:17] sorry [23:17] ah I see you last attempt is at the bottom [23:18] http://pastebin.ubuntu.com/6548391/ [23:18] sorry, here's the fixed on [23:20] mxc, also be interesting to see what "juju bootstrap --debug" returns [23:24] same [23:24] Hi every one [23:25] utlemming: I just tried your tuto about quick start with Juju and I found a little "bug" [23:25] winael: k.... [23:26] winael, hello [23:26] hi arosales [23:26] mxc, what metadata index does it read prior to the affinity error [23:27] https://jujustorewestusdocmunch.blob.core.windows.net/juju-azure-private/tools%2Fstreams%2Fv1%2Findex.json?se=2023-12-09T23%3A25%3A35Z&sig=AYXhLWBbLAfaigM%2B%2BHq2OueWOCi7SU6o56l1JnOgejg%3D&sp=r&sr=b&sv=2012-02-12 [23:28] utlemming: let's me explain, as i read your post, I undestand that it is a way to easly test Juju... but in the practice, ip forwarding doesn't work. So when you expose a service like Mediawiki, you can't access to it out of the vagrant box, unlike the Juju GUI [23:29] winael: that is correct....you need to follow the SSHuttle instructions [23:29] I think it could be a little confusing for people who want just give it a try but don't know linux very well and specially iptables rules [23:29] mxc, can you paste bin this attempt (ie without --upload-tools). I want to see if you are trying to hit "http://cloud-images.ubuntu.com/releases/streams/v1/index.sjson" [23:29] winael: I wouldn't do IP tables. Just use SShuttle, which forwards everything for you. [23:31] Oh ok... that's not clear in fact. I think about none Ubuntu user, it a little bit confusing [23:33] winael: the big problem here is that every OS has some convoluted method of forwarding ports, and looking at it made my head nearly explode for Windows. [23:33] but the idea to use a vagrant image to easly deploy a Juju server I love it [23:35] yeah I can understand that. In fact, I think it will be more easly to just add a note into your post (if you want to test a charm you've just deployed, use sshuttle) [23:35] and make the sshuttle part non optional [23:36] arosales: http://pastebin.com/AQArivJz [23:36] ubuntu paste bin is super slow at the moment [23:36] winael: I'll take a look. [23:36] winael: thanks for the feedback [23:36] I said that because I talk about this at work, but if they tried and fail for that, they just think Juju doesn't work [23:36] And I imagine lot's of people can think the same [23:36] you're welcome :) [23:38] is there a way to turn on HTTP request logging so that I can see every http request going out? [23:40] winael: updated, hopefully that helps [23:40] In fact this project inspire me. I am thinking about how I can try to bring Juju for my client which use VM on ESX, and I said to my self, wooooooooooh if I can have a QuickStart MaaS+Juju vagrant image as master, it'll fixe all my problems (it's just a fantasy, but...) [23:42] mxc, taking a look [23:42] mxc, thanks for the info [23:42] ty [23:49] oh, i've been using an ubuntu 13.10 machine to run juju from. could that be part of the problem? [23:49] winael, the vagrant images are more for supporting local development, not so much for serving things in an environment [23:50] for your idea you're going to just use manual provisioning, which will be finished in january [23:57] mxc, no running the juju client from 13.10 should be fine [23:57] mxc I am still working on reproducing your error [23:57] mxc I did confirm that if storage and instance were in different regions you would get a different error along the lines of [23:57] The source image must reside in a storage account that has the same affinity group or location as the cloud service East US. (http code 400: Bad Request) [23:58] jcastro: I have to take a look on the Manuel Provisioning doc in deed [23:58] and in those cases you should still hit cloud-images.ubuntu.com [23:59] I try very hard to push Ubuntu/Juju in my company but it's not easy [23:59] they prefere to try to re invent the wheel