[09:44] <Syria> Hello!! I have deleted all the users in the phpmyadmin by accedent!! How can create a new user agian?? I can't log in.
[09:46] <andol> Syria: http://dev.mysql.com/doc/refman/5.0/en/resetting-permissions.html#resetting-permissions-unix
[09:53] <Syria> andol:  After submitting the query I got this "Rows matched: 0  Changed: 0  Warnings: 0"
[09:53] <Syria> I don't think that I have a "root" user now, I have deleted all the users.
[09:55] <Syria> andol:  Can I remove it compeletly and re-install it agian from the scratch please? I don't have important information like data bases or something.
[09:58] <andol> Syria: You can do that too.
[10:06] <Syria> Lost the connection!
[10:29] <dchevak> hello all how are you
[10:32] <dchevak> I wish I new about IRC before changing anyway I was running ubuntu 12.04 server on 2 pc's for a small wireless intranet anyway switched one to CentOS 6.3 I always seem to have problems with ubuntu updates with apt-get
[10:34] <dchevak> can someone give me a link to search for IRC chat rooms looking for BIND NAME server ISC maybe I should go there maybe they have it posted on there web site
[10:51] <psivaa> jamespage: hallyn: Reported a new bug on lxc test cases, for a failure in SimpleLxcTests: bug 1144111
[13:56] <zul> jamespage:  quantum has testrepository support now maybe we should consider switching the packaging to use it? (i havent tested it though)
[13:57] <jamespage> zul, if you would like to test and propose it please feel free :-)
[13:57] <zul> jamespage:  ack
[14:17] <hallyn> psivaa: yeah i hadn't had a chance to verify, but some comments after stgraber's PEP8 cleanup patch made me think he might have accidentally undone a fix
[14:17] <hallyn> i'll merge a fix, thanks
[14:18] <zul> jamespage:  yeah not going to happen
[14:21] <hallyn> (i'll address stgraber's other comments - which i hadn't yet - at the same time :)
[14:21] <psivaa> hallyn: ack, thank you
[14:21] <g0tcha> hey guys, everytime i try to install something using apt-get i get this msg http://paste.ubuntu.com/5585178/
[14:22] <g0tcha> can someone help me out with this? i tried to run 'apt-get -f install' and 'apt-get autoremove' and still the same problem
[14:23] <stgraber> hallyn: oops, sorry about the breakage... I thought the diff looked reasonable here after I handled the conflict, but apparently not...
[14:24] <hallyn> stgraber: it's a long string of chrooted commands, eye-numbing.  completely understandable :)
[14:35] <hallyn> psivaa: fix should be pushed.  are you goign to be doing a new run very soon, or should i?
[14:37] <psivaa> hallyn: i could run once the fix goes to  lp:ubuntu-test-cases/server. Until then our tests wont pick the fix, but if you want me to run it against your personal branch, i could try
[14:37] <hallyn> psivaa: i pushed the fix to there
[14:38] <psivaa> hallyn: ahh ok, ill run the tests then. thanks
[14:39] <hallyn> psivaa: thanks.  (i had to nuke themachine i was last testing on :)
[14:40] <psivaa> hallyn: np, the tests are running now, I'll let you know the results once they are done
[14:45] <lyda> Looking at the ubuntu cloud server images here: http://cloud-images.ubuntu.com/precise/current/
[14:45] <lyda> is there an easy way to go from the .img files to an AMI?
[14:46] <lyda> in other words can i configure server images locally, run them through local testing and then release them as AMIs?
[15:24] <SpamapS> lyda: IIRC there's a tool that does exactly that
[15:26] <SpamapS> lyda: curious though, why not customize an EBS root instance and then just snapshot it and turn it into an AMI?
[15:32] <lyda> SpamapS: that's a valid way to do things of course, but I'd like to create an instance that i can use on open stack as well.
[15:32] <lyda> in addition i'd like to use it for running tests locally - without fears of incurring huge costs.
[15:40] <eagles0513875_> hey guys i am looking for documentation on how to setup sieve on ubuntu 12.04 does anyone have a good link on how to configure it
[15:41] <lyda> why bzr, why?
[15:41] <eagles0513875_> ?
[15:41] <eagles0513875_> that came out of nowhere lol
[15:41] <lyda> (sorry, nothing against bzr, but the rest of the world has chosen git.)
[15:42] <eagles0513875_> lyda: canonical seem to enjoy being different. hwo did you find setting up openstack on ur system? when i read the open stack documentation i find it rather daunting and intimidating
[15:43] <lyda> i find it a bit of a pain.  we don't really have a decent setup yet.
[15:43] <eagles0513875_> lyda: have you taken a look at cloud stack
[15:43] <eagles0513875_> citrix open sourced it under the apache license nto sure if that would be any easier
[15:43] <lyda> not really, no.
[15:43] <lyda> is it an openstack setup tool?
[15:44] <lyda> they often seem worse than openstack!
[15:44] <eagles0513875_> no
[15:44] <eagles0513875_> concept i would say is similar to that of open stack but its focus is infrastructure as a service
[15:45] <eagles0513875_> lyda: i guess it depends on the project
[15:45] <lyda> ah.  well, an amazon compatable api is important.
[15:46] <lyda> and honestly i think open stack is the right direction.
[15:46] <lyda> specifically i'm interested in the lxc "virtualisation."
[15:46] <lyda> ha!
[15:46] <eagles0513875_> :) lyda thanks for confirming with me though that im not the only one who finds open stack setup and configuration daunting
[15:46] <lyda> sudo pip install bzr
[15:47] <eagles0513875_> bzr is python based O_o
[15:47] <lyda> git clone bzr::lp:cloud-init
[15:47] <eagles0513875_> O_o
[15:48] <eagles0513875_> lyda: are you setting up your own instance of launchpad
[15:48] <lyda> i'm just checking out the code.  but with git, not bzr.
[15:48] <eagles0513875_> interesting
[15:49] <eagles0513875_> i have heard that launchpad isnt an easy thing to work with or setup
[15:49] <eagles0513875_> lyda: are you looking for a bug tracker of some sort?
[15:49] <lyda> nope.
[15:50] <lyda> internally we use jira.
[15:50] <lyda> and for SCM we use gitlab.
[15:50] <eagles0513875_> nice :) im hosting a few personal repos on a virtual server of my own but i think im going to start using bitbucket more
[15:50] <eagles0513875_> with bitbucket you have a choice between mercurial and git
[15:51] <eagles0513875_> lyda: if you looking for an external bug tracker checkout redmine as I have heard alot of good things about it
[15:52] <lyda> i have two oss projects and i actually use all the major git code hosters so contributors can use what they feel comfy with.
[15:53] <psivaa> hallyn: the LXC tests have another failure, http://pastebin.ubuntu.com/5585410/. Please let me know I should report a separate bug
[15:53] <lyda> see the README for https://github.com/lyda/misspell-check
[15:54] <eagles0513875_> lyda: have you used any web frameworks or anything seeing as you like using python
[15:55] <lyda> i've been trying out bottle (framework) and waitress (for serving).
[15:55] <lyda> they seem to work well.
[15:55] <eagles0513875_> does anyone know if i install the dovecot-sieve package on 12.04 if that will effect the current operation of my mail server? or will i still continue to to get emails and send them
[15:55] <eagles0513875_> lyda: if you like python check out django its is probably the most complete in terms of documentation
[15:56] <lyda> it is, but it also seems kind of heavy.
[15:56] <lyda> i have played with it.
[15:56] <eagles0513875_> lyda: what webserver did you try it out on
[15:57] <eagles0513875_> i need to when i have the time migrate all myservers away from apache prefork
[15:57] <eagles0513875_> that thing is a memory hog and implement php-fpm
[15:58] <lyda> for waitress i just used it directly for an internal deployment.
[15:58] <lyda> i think if i was actually deploying it i'd put it behind ngnix or apache.
[15:58] <eagles0513875_> what exactly is waitress like a pos system for restaurants or something
[15:58] <eagles0513875_> what about lighttpd lyda i have been told that has virtually 0 memory footprint somehow
[16:11] <sliddjur> Can someone help me out with enabling pam module cracklib to set password complexity rules? I've come to the point where I dont know what im doing anymore... :s
[16:12] <sliddjur> ./etc/pam.d/common-password:password     required        pam_cracklib.so retry=3 minlen=8 difok=3 dcredit=1 ucredit=1 lcredit=1 ocredit=1
[16:12] <hallyn> psivaa: d'oh.  typo.  sorry
[16:12] <hallyn> oen sec,
[16:12] <sliddjur> I thought this would enable password rules, but it doesnt seem to be enabled when I change my users password (not with root)
[16:13] <hallyn> psivaa: fix pushed, thanks
[16:14] <psivaa> hallyn: ok thanks, running again
[16:19] <SpamapS> lyda: perhaps have a look at https://github.com/stackforge/diskimage-builder
[16:20] <SpamapS> lyda: it will output a raw image that, I think, will boot just fine on ec2
[16:23] <rbasak> jamespage: hey! I've prepared an upload for ipmitool in bug 1074443 that I'd like to get in before feature freeze. Should I put this in the sponsor queue as usual in the hope that it'll go in on time, or could you review/upload it for me please?
[16:24] <SpamapS> eagles0513875_: also re "why bzr" its not so much that canonical enjoy being different as the fact that bzr and git grew at the same time... git in the kernel community (and later everywhere else) and bzr in canonical and its projects....
[16:24] <SpamapS> lyda: ^^
[16:25] <eagles0513875_> SpamapS: what advantages does it have over the already established ones such as git svn mercurial
[16:25] <SpamapS> lyda: anyway, since you are interested in openstack .. di-b is nice.. and developed using the same model.
[16:25] <SpamapS> eagles0513875_: bzr is already established too ;)
[16:25] <SpamapS> eagles0513875_: its just not widely adopted
[16:25] <eagles0513875_> what advantages does it have over the main stream ones  SpamapS
[16:25] <SpamapS> eagles0513875_: bzr doesn't ever rewrite history unless you explicitly say "delete that commit" and it can only pop them off the top.
[16:26] <SpamapS> eagles0513875_: instead it folds them down into commits underneath the larger ones
[16:26] <eagles0513875_> interesting but technically isnt that what the others do as well?
[16:26] <SpamapS> eagles0513875_: it also is *FAR* easier to learn how to use the whole bzr toolset. If you've never used bzr or git, bzr will take maybe a week to master.. git .. well I've been using git since December and I know f*** all about it.
[16:27] <SpamapS> eagles0513875_: forget svn, its not even in this conversation.
[16:27] <eagles0513875_> interesting
[16:27] <eagles0513875_> lol
[16:27] <SpamapS> eagles0513875_: hg I know very little about
[16:27] <eagles0513875_> lyda: have you looked at juju and charms for what you are doing to help ease your deployments of frameworks etc
[16:27] <SpamapS> eagles0513875_: git does rewrite history.. you can delete commits going back forever w/ rebase.
[16:28] <SpamapS> heh... IMO juju is not quite there for "easing deployment of frameworks"
[16:28] <SpamapS> It eases deployment of infrastructure like a champ
[16:28] <SpamapS> databases, monitors, logging, queues, all good. frameworks.. well.. just go try the django charm. :-/
[16:31] <rbasak> Technically git doesn't rewrite history, and you can't delete commits. You only create new history and generally choose to forget about old branches by moving branch tips. What I find interesting is that when we say we "merge" an Ubuntu package with a newer Debian package, what we actually do is in git parlance a "rebase" (despite what we might commit in bzr UDD).
[16:34] <SpamapS> rbasak: yeah, the way bzr is abused for separate tracking of upstream source and debian changes is definitely more git's territory
[16:35] <SpamapS> rbasak: you are tainted by git mastery .. git masters *HATE* bzr
[16:35] <SpamapS> and, I get it now
[16:35] <SpamapS> because git has all the tools to do the appropriate surgery on your VCS to make it be representative of what you want.
[16:35] <SpamapS> bzr hides them or outright makes them impossibly hard to find, because bzr is a perfectionist
[16:35] <rbasak> I think the problem is that bzr is very poorly documented for git masters. It hides what's really going on. So yeah, exactly what you're saying.
[16:36] <SpamapS> I also have the bad fortune to be dealing with OpenStack's limited git workflow, which isn't helping me love git ;)
[16:37] <rbasak> All the documentation is workflow based, which works until I have an unusual workflow. Then there is no documentation, and all I can do is ask others what they do. With git, the documentation is extremely details always enough (if you're willing to delve into the data structures, which is easier with a CS background).
[16:41] <jamespage> rbasak, ok - I'll take a look
[16:55] <jamespage> rbasak, is it actually a merge from upstream or a new upstream release?
[16:55] <rbasak> jamespage: I meant upstream as in not Debian. New upstream release that I've merged with previous Ubuntu package.
[16:56] <rbasak> As you're asking, I guess the answer is "new upstream release". I guess I shouldn't call it a merge then in this case?
[16:57] <jamespage> rbasak, yeah - I'll fix it up locally and upload for you
[16:57] <rbasak> Thank you!
[16:57] <jamespage> rbasak, uploading now
[16:58] <jamespage> rbasak, thanks for picking that up
[17:24] <jamespage> rbasak, build failure on powerpc - https://launchpad.net/ubuntu/raring/+source/ipmitool/1.8.12-0ubuntu1
[17:24] <rbasak> jamespage: :-(
[17:25] <rbasak> jamespage: looking at it now. Looks like a simple endianness/porting issue.
[17:36] <tkeith> I upgraded a package and it asked me what I want to do about changed configuration and I hit N for "keep current config". Now I want to know what the changes were. How do I get apt or dpkg to give me that option again?
[17:54] <rbasak> tkeith: sounds like a conffile prompt. Usually you'll end up with .dpkg-dist or .dpkg-old files in the same directory as the conffile affected. I'm not sure how to identify which conffile was affected after the prompt though. Searching for files with a .dpkg-dist suffix in /etc might be your best bet.
[17:54] <tkeith> rbasak: Ah, thanks! I knew which file it was, and there's a .dpkg-disk
[17:55] <rbasak> Great!
[18:32] <smoser> hallyn, i dont know if you're aware and it is by design or not
[18:32] <smoser> but i think that default memory size to kvm changed
[18:32] <smoser> i think at one point in ubuntu it was 256 maybe.
[18:32] <smoser> now it seems like 128
[18:32] <smoser> but i could be just mis-remembering
[18:32] <hallyn> smoser: yeah, kirkland carried a patch setting it actually to 356 i think,
[18:32] <hallyn> no you're right
[18:33] <hallyn> smoser: we can re-add that patch if it's needed for something, i'm just trying to get delta from debian as small as possible
[18:33] <hallyn> i do agree default size is useless :)
[18:33] <hallyn> shout if you want the patch back
[18:34] <smoser> hallyn, perhaps try to push that to debian?
[18:34] <smoser> to keep the delta small
[18:34] <mattrae> anyone familar with apt-mirror? my first download completed but i wanted to run again to just get anything that updated. now its saying its downloading the same amount of data i initially downloaded. anybody know if this is actually an incremental download?
[18:34] <hallyn> smoser: lemme ask there real quick
[18:34] <mattrae> i don't want to re-download everything if i can avoid it
[18:58] <tasslehoff> on my synology-nas it was possible to have an encrypted volume that I could decrypt and share via samba. how can I do the same on ubuntu? must I manually do the decrypt, and then restart samba with an added share on the mount point?
[18:58] <tasslehoff> or are there more elegant solutions?
[19:00] <sarnold> tasslehoff: how did you give the key to the synology to decrypt the data?
[19:01] <tasslehoff> sarnold: I think I only had to give a password when creating the share
[19:01] <tasslehoff> so, not sure exactly how secure it was
[19:01] <sarnold> tasslehoff: aha, so it stored the key somewhere?
[19:02] <RoyK> or used the password hash as the key?
[19:02] <sarnold> tasslehoff: you could re-create that with ecryptfs or dm-crypt and store the key on the server somewhere, so it doesn't require your interaction to mount it every boot...
[19:02] <sarnold> RoyK: ah, another good possibility
[19:03] <RoyK> meaning !secure
[19:05] <tasslehoff> I would have to make sure samba starts after the encrypted folder is mounted?
[19:09] <tasslehoff> Is truecrypt a good solution as well? Have used it on my desktop before, but never on a server.
[19:09]  * tasslehoff will google
[19:25] <guntbert> Where resides the setting if I want be prompted for non-LTS upgrades or not?
[19:26] <guntbert> s/if/whether/
[19:27] <patdk-wk> /etc/update-manager/
[19:27] <guntbert> patdk-wk: thx so much :-)
[19:31] <guntbert> hmm - two systems (12.04.02 LTS), both have "prompt=lts", one prompts me for 12.10 on login, one does not
[20:02] <zul> jamespage:  ping i filed the MIR for python-json-patch and python-json-pointer fyi
[20:29] <hallyn> stgraber: triggered a few pre-existing bugs in my cgroup patch, so the patchset i'm sending out is growing...  on the bright side it'll survive all the tests i can throw at it
[20:30] <hallyn> stgraber: interestingly, lxc-destroy isn't yet lxcpath aware (be careful with that!).  (patch to fix that going out now)
[20:34] <stgraber> hallyn: oh, so apparently I just used rm and not lxc-destroy when doing lxcpath testing ;) good catch
[21:06] <hallyn> smoser: mjt says he intended to send a patch to up default memory size upstream.  so we'll get this fixed through debian at least - thanks
[21:06] <utlemming> smoser: Bug #1145215
[21:10] <smoser> utlemming, what release is this ?
[21:10] <utlemming> precise
[21:11] <utlemming> I booted this on a non-EC2/Openstack cloud
[21:18] <axisys> how to install netbackup client?
[21:18] <axisys> dont see one
[21:18] <axisys> should this question be in offtopic ?
[21:22] <smoser> utlemming, it seems there is a bug there, but i dont understand how it would ocur with the /etc/cloud/cloud.cfg that is packaged.
[21:24] <utlemming> smoser: I am overriding the cloud-config. See: http://paste.ubuntu.com/5586309/
[21:24] <RoyK> axisys: heh - call support ;)
[21:26] <smoser> buti i think your file inside the image is busted.
[21:26] <smoser> as it should look like: http://paste.ubuntu.com/5586315/
[21:28] <utlemming> smoser: is the apt_mirrors syntax deprecated?
[21:29] <axisys> RoyK: heh
[21:32] <smoser> utlemming, yes. https://bugs.launchpad.net/cloud-init/+bug/1006963 has the correct way to do that.
[21:33] <smoser> it was intended for what you did to work, but clearly it did not.
[21:33] <utlemming> smoser: ack, thanks for the clarification
[21:45] <smoser> utlemming, fwiw, i cannot reproduce this.
[21:47] <smoser> it works as expected on openstack.
[21:47] <hallyn> stgraber: hm, (testing now, but) does /etc/init/lxc.override work in lucid?
[21:47] <stgraber> hallyn: not sure, I can't remember using those back then
[21:47] <utlemming> smoser: interesting. I'm doing another test
[21:48] <utlemming> smoser: I'll give you access once its booted
[21:48] <smoser> http://paste.ubuntu.com/5586373/
[21:50] <hallyn> stgraber: oh, sorry, that wasn't the problem...
[22:21] <jcastro> smoser: do you have any generic cloud talks? We have that cloud talk in Ann Arbor on Wednesday btw.
[22:22] <jcastro> smoser: I was just going to do Juju but I think some info about Guest would be welcome.
[22:51] <aleza84> how can I connect to a wireless lan wpa2 encrypted via console?
[22:57] <tsaavik> Anyone know if/where there are docs on the various default user groups in ubuntu?
[23:08] <tsaavik> Yes, there is checkout:
[23:08] <tsaavik> https://wiki.ubuntu.com/Security/Privileges
[23:09] <sarnold> tsaavik: neat, thanks
[23:22] <azbyin> hi all..
[23:23] <azbyin> what is the essential difference between  %admin ALL=(ALL) ALL     and   %sudo   ALL=(ALL:ALL) ALL  in the sudoers file?
[23:24] <sarnold> azbyin: depends on the contents of the 'admin' group vs the 'sudo' group
[23:24] <sarnold> oh, there's the (ALL) vs (ALL:ALL) difference, too...
[23:24] <azbyin> i have identical sudoers files on my local workstation and a uec image running on a vm. both os are precise lts. on my local workstation my user is 'azbyin' and am in the 'sudo' group. on the cloud machine the user is 'ubuntu' and is in the 'admin' group
[23:25] <azbyin> now, my workstation asks for my passwd when i try any command with sudo (with the obvious credential caching (for 15 mins?)) while on the cloud machine ubuntu is able to run any sudo command without request for passwd
[23:26] <azbyin> from my understanding of reading the sudoers manpage, it should ask for a password _unless_ NOPASSWD is present in the rule
[23:26] <azbyin> so, i don't understand the difference in behaviour
[23:26] <bmoyles> is there a defaults line in sudoers that specifies anything around authentication?
[23:26] <azbyin> oh, also.. on my workstation my user is uid 1000, on the cloud machine ubuntu user is uid 999
[23:26] <bmoyles> you can turn off authentication globally in sudoers
[23:27] <azbyin> bmoyles, as i mentioned above, the sudoers files on my machine and the cloud machine are *identical*
[23:28] <azbyin> does it differentiate between 'system' users with uid < 1000 and non-system users where uid >= 1000 ?
[23:28] <azbyin> if yes, i do not see this in the manpage
[23:29] <azbyin> so, i assume it must be because of the differing group membership and consequently differing rule being applied
[23:29] <azbyin> but the rule by itself does not indicate that passwd will not be authenticated! so i do not see how this behaviour occurs
[23:30] <bmoyles> yes, they're identical, but look in /etc/sudoers.d
[23:32] <azbyin> ah indeed
[23:32] <azbyin> i was accidentally looking at the wrong tab
[23:32] <azbyin> i.e. i looked at /etc/sudoers.d/ on my own workstation *twice* and saw only the README file
[23:32] <azbyin> grr..
[23:33] <azbyin> thanks for the clarification. and i'm happy that i could understand the manpage by myself :)
[23:33] <sarnold> bmoyles: nice :)
[23:35] <bmoyles> the sudoers manpage has to rank as one of the more confusing manpages to ever exist :)
[23:36] <azbyin> well, it does list the BNF grammar
[23:36] <azbyin> but compensates by giving very clear examples at the end
[23:53] <sarnold> the downside is that the examples it gives are for a very comprehensive deployment suitable at a business or something
[23:54] <sarnold> it needs a "dumb guy" section for simple uses for people like me :)