[00:09] <SpaceBass> had a software raid5 array fail yesterday - was a bad disk connection. Fixed the connector and its been rebuilding for over 24 hours - does that sound right?
[03:03] <sponzor> hi is there any kdump in ubuntu?
[03:35] <sponzor> hi what to use for crash dump? that it captures kernel panic etc..?
[05:53] <Roxyhart0> hi somebody know what is automonth for ldap, what is does?
[05:59] <ja660k> hello, what directory is the php pear modules in?
[06:01] <smoser> soren, erichammond anyone else who cares: "Query Interface" at https://wiki.ubuntu.com/EC2UpgradesSpec is updated. tree at http://uec-images.ubuntu.com/query/ has info
[06:01] <smoser> i'm going to bed now.
[07:49] <fluvvell> i want to display photos on the screen of a server, and use eog -s -f --display= {second monitor} but don't know the syntax
[07:50] <fluvvell> any ideas?
[08:28] <pts_> anyone know if hb_gui is available for CRM (pacemaker-openais CIB manager) in any ubuntu repos?
[08:40] <_ruben> pts_: according to packages.ubuntu.com, no
[08:43] <pts_> I hoped it maybe was hidden somewhere :) Anyone knows why it hasnt been added? Using the pacemaker-openais package and wondering even if its compatible in a case a find the sources and want to try to compile it
[08:51] <Speedy1> www.search2.net
[09:02] <_ruben> pts_: wouldnt know, i hadnt had a chance to dive into the "new" pacemaker stuff, hell, i even havent had a change to even look into the crm stuff :p
[09:28] <c0dem4gnetic_> what would a reasonable textmode mail client to use be?
[09:30] <Jeeves_> mutt
[09:31] <c0dem4gnetic_> mutt it is then, thanks :)
[09:32] <pts_> could suggest pine too, but no idea how it compares to mutt
[10:05] <rossouwap> hi, can anyone give me some info on the KVM -incoming command?
[10:24] <TeTeT> ttx: is the cloud installation from CD already quite stable, or will it be changed? If not I can start to update the training materials
[10:28] <ttx> TeTeT: it should be quite stable now.
[10:28] <TeTeT> ttx: thanks!
[10:57] <AnAnt> Hello, why did Ubuntu use w3m instead of elinks-lite for building doc for mutt package ?
[11:04] <jpds> AnAnt: apt-cache showsrc mutt - shows that elinks is used?
[11:04] <AnAnt> jpds: look at changelog of -5ubuntu1
[11:07] <jpds> AnAnt: Ask mathias when he's online.
[11:08] <AnAnt> ok
[11:09] <pts_> is there any repos with updated pacemaker/corosync and DRBD?
[11:10] <RoyK> isn't that in the default repo?
[11:10] <RoyK> or is that just heartbeat?
[11:11] <pts_> pacemaker 1.0.5, but 1.0.6 is newest I think
[11:11] <pts_> and corosync is also outdated
[11:15] <RoyK> outdated as in doesn't work?
[11:17]  * RoyK still has a Solaris 7 running
[11:18] <RoyK> s/run/box run/
[11:19] <pts_> well, maybe. I'm totally new with clustering and it makes it a bit harder when CRM crashes while I follow a howto. When running the command sequence crm configure <enter> property no-quorum-policy=ignore <enter> commit <enter> crm crashes. CIB havent been changed at all before this, just made sure it exists as I expect
[11:33] <Sorell> hey guys,
[11:34] <Sorell> does anyone on here know anything about how LTSP uses it's DHCP server
[11:34] <Sorell> I'm having a bear of a time getting this setup.
[11:40] <pts_> If I remmeber correctly it uses /etc/ltsp/dhcpd.conf. The "special" options you need are 	filename "/ltsp/i386/pxelinux.0";
[11:40] <pts_> 	option root-path "/opt/ltsp/i386";
[11:40] <pts_> you could try #ltsp if you need more help
[11:43] <Sorell> k
[11:43] <Sorell> I will give it a try ty
[12:08] <sabgenton> I want to use cup-lpd
[12:09] <sabgenton> anyone know the package name?
[12:09] <dholbach> heya!
[12:09] <dholbach> is something with php pear known to be broken at the moment?
[12:09] <dholbach> bug 513765 looks like it
[12:12] <sabgenton> oks cups-bsd
[12:33] <kaushal> hi
[12:47] <kaushal> i have a issue about Maximum Capacity: 4 GB while running dmidecode,but the actual memory is 8GB on san box. please suggest ?
[12:53] <sherringham> kaushal: a) Check your BIOS settings (RAM/memory mapping) b) What arch - 32bit or 64 bit kernel? uname -a
[12:53] <kaushal> 64 bit
[12:53] <kaushal> 2.6.24-16-generic
[12:57] <kaushal> sherringham: any clue ?
[12:57] <sherringham> kaushal: Did you check your BIOS settings?
[12:58] <kaushal> yes
[13:00] <sherringham> BIOS sees 8 GB? Some chipsets don't support > 4GB RAM - see if you can find out for sure. Maybe try switching RAM around in the slots ...
[13:00] <kaushal> sherringham: i was interested in how much RAM my san box would support ?
[13:01] <kaushal> I mean the Max Total RAM Support
[13:01] <kaushal> with out trying to contact the manufacturer
[13:01] <kaushal> is there a way to find out that information ?
[13:01] <kaushal> from the OS Side
[13:02] <sherringham> Don't think so - you need hardware/system specs e.g. chipset. If it's Intel or AMD, should be easy to find though - or google.
[13:03] <sherringham> Normally, the manufacturer will have this information.
[13:27] <pts_> anyone know why I cant start corosync via the init.d script? Have to run corosync -f to start it
[13:29] <zul> morning
[13:50] <pmatulis> anyone heard of apache2 on 8.04 to suddenly stop logging?  this might be happening because of logrotate config
[13:50] <zul> a new release is a paper cut?
[13:50] <ivoks> is meeting today or tomorrow?
[13:51] <zul> pmatulis: ive seen it before the large file becomes too large
[13:51] <pmatulis> zul: this is the logrotate config if it matters:
[13:51] <pmatulis> http://pastebin.com/f69bab815
[13:52] <pmatulis> zul: maybe i should specify a log file size?
[13:52] <zul> pmatulis: no it should be ok, what if they do the default one?
[13:53]  * pmatulis looking for default one...
[13:54] <pmatulis> zul: i'll have them try it
[13:59] <incorrect> i've had a request to upgrade a 8.04 to 9.10
[14:00] <incorrect> i am guessing i will have to go via 8.10 and 9.04
[14:00] <RoAkSoAx> ivoks, today i believe
[14:00] <Pici> incorrect: yes, you will
[14:08] <Daviey> zul: My main concern with 5.3 was upstream php switching to default of short tags off.  Just had a look at debian experiment 5.3, and there is a debian/patch that re-enables it.  This will reduce stuff broken, so i am happy.
[14:08] <zul> Daviey: good
[14:09] <incorrect> oh i have to edit something to allow me to upgrade from 8.04 to .10
[14:28] <smoser> command line completion is mostly fixed, kirkland ?
[14:29] <kirkland> smoser: well, chris added the code upstream, but it's not working just yet
[14:29] <smoser> like bash completion ?
[14:29] <kirkland> smoser: yes
[14:29] <kirkland> smoser: see /etc/bash_completion.d/
[15:00] <kirkland> smoser: euca_conf with bash completion just uploaded to lucid!
[15:01] <stgraber> kirkland: do we have anything against running tftpd-hpa as a standalone daemon ?
[15:01] <stgraber> that's what would cause the biggest delta with Debian
[15:02] <kirkland> stgraber: as opposed to under inetd?
[15:02] <stgraber> the rest is basically a two line diff to change the default path and debconf priority
[15:02] <stgraber> kirkland: yes
[15:02]  * Daviey tends to deploy tftpd-hpa as a daemon
[15:05] <stgraber> pushing an updated package to my PPA
[15:08] <kirkland> stgraber: i don't care much either way, as long as the damn thing starts on boot ;-)
[15:08] <kirkland> stgraber: most of the documentation in the Ubuntu wiki and server guide talks to running it under inetd
[15:08] <kirkland> stgraber: we'd just need to ensure that those docs are updated (not hard to do, certainly not a blocker)
[15:11] <ttx> I agree that changing the location of the tftpboot is a nice killer :)
[15:12] <ttx> kirkland: btw, I didn't get a copy of your mirror rsync script, could you email/pastebin it to me ?
[15:12] <kirkland> oh, sure
[15:14] <kirkland> ttx: http://pastebin.com/f26ee31bd
[15:14] <kirkland> ttx: you may want to tweak it, but you should get the idea
[15:14] <ttx> sure, I'll use it as a starting point
[15:15] <kirkland> ttx: btw, one paper cut down ;-)
[15:16] <kirkland> ttx: just uploaded euca_conf with bash completion
[15:16] <ttx> I'll make sure we count it :)
[15:27] <kirkland> ttx: okay, uploaded iptables/db-deadlock fix for karmic/eucalyptus to ~ubuntu-virt ppa
[15:27] <kirkland> ttx: updated the bug
[15:28] <kirkland> nijaba: could you talk to TeTeT and/or laclasse about perhaps helping test?
[15:29] <nijaba> kirkland: for euca ?
[15:29] <nijaba> kirkland: url?
[15:29] <kirkland> nijaba: https://bugs.edge.launchpad.net/ubuntu/+source/eucalyptus/+bug/503180/comments/11
[15:29] <nijaba> kirkland: ok, will ask them to test
[15:31] <kirkland> nijaba: ack, thanks!
[15:31] <kirkland> nijaba: hopefully this will put the worst karmic/euca bug to bed ;-)
[15:31]  * nijaba crossing his finger
[15:32] <nijaba> my fingerS too
[15:32] <TeTeT> nijaba + kirkland : booting my karmic UEC :)
[15:33] <kirkland> TeTeT: the package is building in the PPA
[15:33] <kirkland> TeTeT: should be published any minute now
[15:33] <TeTeT> kirkland: need to update the systems anyway, they haven't been touched for a while
[15:34] <kirkland> TeTeT: great, please try to reproduce the bug before you upgrade to the ppa version
[15:34] <kirkland> TeTeT: i think you can reproduce it easily by rebooting, and seeing that you can't talk to the CLC for a long time (like 10-20 minutes)
[15:34] <kirkland> TeTeT: at least, that's how I experienced the bug
[15:35] <kirkland> TeTeT: then, I upgrade the packages, reboot again, and the CLC is up and communicative almost immediately (within 1 minute of login)
[15:35] <TeTeT> kirkland: will do
[15:35] <TeTeT> kirkland: I can reproduce it on the training cloud in the datacenter, but I don't have access to it right now
[15:39]  * dholbach tries asking again: is something with php pear known to be broken at the moment? bug 513765 looks like it
[15:39] <dholbach> mathiaz, zul: ^
[15:41] <zul> dholbach: looking
[15:42] <sarthor> Hi, My pppoe-server is according this url "  http://ubuntuforums.org/showthread.php?t=291926  " and is working, but same username and passwords can connect from several computers, I to solve this problem. example, if username is "username" and password is "passwdd" So serveral clients can connect this  username from same time from several computers, My clients are on my lan, HELP,
[15:44] <kirkland> TeTeT: okay, amd64 is built
[15:44] <kirkland> TeTeT: and published
[15:44] <TeTeT> kirkland: bummer, I only have a 32bit cloud at home
[15:45] <kirkland> TeTeT: 32 is built too now
[15:47] <nijaba> kirkland: reproduce 1 --> done, ow updating to current packages (no ppa) to reproduce again, will add ppa afterward
[15:50] <TeTeT> kirkland: reproducing problem now, will wait for 15 minutes
[15:53] <kaushal> hi
[15:57] <kaushal> i am still not convinced about the response i got from ubuntu-server mailing list about dmidecode. please suggest
[15:59] <kaushal> so what i understand from that email thread is to consult the manufacturer and not dmidecode to know the Maximum Capacity a san box can support ?
[15:59] <kaushal> am i understanding it correctly ?
[15:59] <nijaba> kirkland: :( can't reproduce after doing a normal update (without your ppa)
[16:00] <kirkland> nijaba: hrm?
[16:00] <nijaba> kirkland: running euca 1.6~bzr931-0ubuntu7.4
[16:00] <kirkland> TeTeT: you should be able to just wait ~5 minutes
[16:01] <kirkland> TeTeT: if it's not up by then, your db is wedged
[16:02] <TeTeT> kirkland: after 15 minutes it's there
[16:02] <TeTeT> kirkland: should I do another reboot and test after 5?
[16:02] <kirkland> TeTeT: right, it takes ~15 to get unwedged
[16:02] <kirkland> TeTeT: sure, if you like
[16:02] <kirkland> TeTeT: basically, eucalyptus loses connection to the database
[16:02] <mathiaz> kirkland: hm bug 519653 - seems that running an NC and a front-end on the same system is working
[16:02] <kirkland> TeTeT: due to the changing network configuration
[16:03] <kirkland> TeTeT: after ~15 minutes or so, the connection gets reset
[16:03] <kirkland> TeTeT: with the fix, the db connection should be ready immediately on boot
[16:03] <kirkland> TeTeT: were you able to confirm that you could not talk to the CLC for a feew minutes after boot?
[16:04] <kirkland> mathiaz: with system mode network, yes, Ng told me as much
[16:04] <mathiaz> kirkland: oh ok.
[16:04] <kirkland> mathiaz: i have not tried it
[16:04] <kirkland> mathiaz: and none of the other, advanced networking modes will work, though
[16:04] <kirkland> mathiaz: but Ng has documented it on the topologies page in the wiki
[16:05] <TeTeT> kirkland: yes, could not take to it immediately after boot
[16:06] <TeTeT> kirkland: bummer, now it is available :(
[16:06] <TeTeT> right away
[16:09] <kaushal> checking in again for my query ?
[16:11] <TeTeT> kirkland: ok, can't reproduce the bug anymore on my UEC here. 2 out of 3 reboots the cloud is responding to 'euca-describe-availability-zones' right awya
[16:14] <TeTeT> kaushal:  sudo dmidecode | grep "Maximum Total Memory Size"  works for me
[16:15] <kaushal> TeTeT: yeah i have already done it
[16:16] <kaushal> TeTeT: shall i pastebin the output ?
[16:17] <TeTeT> kaushal: afraid I'm not of any more help, that's all I had to offer.
[16:18] <zul> dholbach: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546164
[16:18] <kaushal> http://paste.ubuntu.com/373246/
[16:18] <dholbach> zul: ah ok, I'll see what it's about
[16:26] <kklimonda> any idea whenever django 1.2 is going to make it to lucid?
[16:44] <rbrunhuber9729> Can init/upstart start every (cli) application or just daemonized applications?
[16:44] <kreuter> howdy #ubuntu-server.  can upstart run a service as a non-root user?
[16:48] <karlheg> kreuter: dpkg --listfiles upstart | less
[16:48] <karlheg> kreuter, that will show you what files it installed... see if it uses shell scripts to start the services.
[16:48] <karlheg> kreuter, ps wwwauxf | less
[16:49] <karlheg> kreuter, You'll see many services running as non-root users.
[16:50] <kreuter> am I reading you as saying that it's necessary to indirect through a shell script to run as non-root (i.e., the upstart configuration files don't have any special support for it?)
[16:50] <mathiaz> kreuter: correct - upstart doesn't natively support running programs as a non-root user
[16:51] <karlheg> RTFM.
[16:51] <karlheg> ... but it runs as root so it can do anything you program it to do via a shell script. The script can call 'su'.
[16:52] <karlheg> So, there's no need to put that kind of functionality into upstart itself.
[16:53] <kklimonda> zul, what is your opinion about django 1.2 in Lucid? I'm asking as you were the one requesting MIR for it. It's still likely to be released in march.
[16:53] <kreuter> karlheg: sure, of course.  I just couldn't find anything about this by googling, so I figured I'd ask.
[16:53] <kreuter> karlheg: while I'm at it, which FM did you have in mind?
[16:54] <zul> kklimonda: i dont have a problem with it it probably wont get into main for lucid though
[16:55] <karlheg> dpkg --listfiles upstart | grep '/usr/share/\(man\|doc\)'
[16:55] <karlheg> FM
[16:56] <kklimonda> zul, so MIR was a one time only? I guess there is no problem then as universe is known not to be perfect anyway :)
[16:56] <karlheg> man 5 init
[16:56] <karlheg> man 8 init
[16:56] <zul> kklimonda: it was rejected for main because it has a poor security track record but no problems with universe
[16:57] <karlheg> man 8 pizza
[16:58] <kklimonda> zul, it was? hmm.. was it discussed somewhere after MIR was accepted? I must have missed it.
[16:59] <zul> kklimonda: MIR was never accepted and wasnt filed because of the security history review done while considering the MIR
[17:01] <kirkland> TeTeT: nijaba: so are you suggesting that the fix is not necessary for SRU to karmic?
[17:01] <nijaba> kirkland: no, I am not suggesting this.  I am just saying that I am havig trouble reproducing on my setup today, but that does not mean it does not occur at all
[17:02] <kklimonda> zul, Are we both talking about python-django? It was promoted to main in karmic.. I'm confused :)
[17:02] <nijaba> zul: me too am confused...
[17:03] <zul> kklimonda: yeah i was confused :)
[17:03] <nijaba> zul: python-django | 1.1.1-1ubuntu1 |        karmic | source, all
[17:03] <nijaba> python-django | 1.1.1-2ubuntu1 |         lucid | source, all
[17:04] <zul> kklimonda: march is cutting a bit close for me but submit a bug to launchpad and we'll have a look closer to the day
[17:04] <nijaba> kklimonda: AFAIK it won't be demoted for lucid, and I don't know of anyone suggesting that we should
[17:08] <kklimonda> zul, there is already a bug 505440 - the problem is during 1.1 cycle django developers have decided to postpone RC for two or three months after the planned release. The number of opened bugs with milestone set to 1.2 on their tracker is also quite big. Can we just wait and request an exception from FeatureFreeze?
[17:09] <zul> kklimonda: probably ill have to look at it
[17:42] <smoser> mathiaz, ping.
[17:45] <mathiaz> smoser: hi!
[17:45] <smoser> mathiaz, i got an answer elsewhere. you were too slow :)
[17:50] <TeTeT> kirkland: same here, the latest I saw the problem happening was on the cloud training. I will try to reproduce it there tomorrow
[18:26] <tolik> Привет всем.
[18:33] <smoser> jjohansen, ping
[18:33] <jjohansen> smoser: whats up
[18:34]  * smoser knows that jjhohansen really hates it when i piing
[18:34] <smoser> i'm looking at a mail to ec2ubuntu
[18:34] <jjohansen> smoser: only if it involves more work :)
[18:34] <smoser> err, wait
[18:34] <smoser> not that list.
[18:35] <smoser> looking for mail
[18:35] <smoser> https://lists.ubuntu.com/archives/ubuntu-ec2/2010-February/001270.html
[18:35] <smoser> it looks like there are some broken package dependencies in karmic right now
[18:36] <smoser> i've just booted the ami in question (ubuntu-karmic-9.10-amd64-server-20091027.1.manifest.xml)
[18:36] <smoser> then done apt-get update
[18:36] <smoser> sudo apt-get install linux-ec2 --dry-run
[18:36] <smoser> The following packages have unmet dependencies:
[18:36] <smoser>   linux-ec2: Depends: linux-image-ec2 (= 2.6.31.303.3) but 2.6.31.302.2 is to be installed
[18:36] <smoser> E: Broken packages
[18:37] <jjohansen> hrmm, yep that looks like broken deps
[18:38] <smoser> :-(
[18:39] <smoser> interestingly, though, the broken packages "save" him
[18:39] <smoser> while nothign bad would happen, installing those new abi kernels is useless as he can't use them.
[18:55] <smoser> jjohansen, bug 520015
[18:56] <sponzor> http://pastebin.com/m75d80fca what should be wrong? after this only established connections work. if i try to connect to server on 80 ssh etc.. everyting is denied. and ping from server also? any ideas?
[19:04] <sponzor> nevermind i got it
[19:17] <ZimCS> Hey guys.  I am not really new to linux, but usually have the installer partition the drives for me.  This time I would like to do it myself using a software RAID 1 setup.  If I make a boot partition and and apply it to RAID, if disk 1 fails and is removed from the system and the system is rebooted, will drive to be able to boot the system using GRUB?
[19:17] <alkosmurf> Hi. How do i setup MRTG for Apache2 on Ubuntu-Server edition?
[19:19] <lifeless> I hear and obey
[19:21] <kirkland> lifeless: yo
[19:21] <lifeless> ok
[19:21] <lifeless> so I had a few teething problems I've filed as bugs
[19:21] <lifeless> missing directories
[19:21] <kirkland> lifeless: okay, so i gather you're running everything on a single machine?
[19:21] <lifeless> missing files
[19:21] <lifeless> yah
[19:22] <kirkland> lifeless: yup, yup, i was looking into those
[19:22] <lifeless> its a karmic desktop (started life as jaunty)
[19:22] <kirkland> lifeless: i'm surprised you're the first to hit that
[19:22] <lifeless> kirkland: I'm not
[19:22] <lifeless> kirkland: there are a bunch of random 'help me' on the web that appear to have the same symptoms I saw at different stages
[19:22] <kirkland> lifeless: oh, interesting; i wonder how network manager will play with eucalyptus' crazy networking and bridging stuff
[19:22] <lifeless> NM is disabled
[19:22] <kirkland> lifeless: nice
[19:23] <kirkland> lifeless: i'll nail those missing dirs in the packaging
[19:23] <lifeless> well, I say disabled - told not to touch etho0/br0
[19:23] <kirkland> lifeless: i just need to figure out which package they belong in, and why others don't hit that problem
[19:23] <lifeless> sure
[19:24] <lifeless> I'm happy to purge and retry tests for you once we get it all working ;)
[19:24] <lifeless> now, networking
[19:24] <lifeless> iface eth0 inet manual
[19:24] <lifeless> auto br0
[19:24] <lifeless> iface br0 inet dhcp
[19:24] <lifeless>     bridge_ports eth0
[19:24] <lifeless>     bridge_fd 9
[19:25] <lifeless>     bridge_hello 2
[19:25] <lifeless>     bridge_maxage 12
[19:25] <lifeless>     bridge_stp off
[19:25] <lifeless> (just under my pastebin threshold :P)
[19:25] <lifeless> the iface eth0 stanza tells NM to go jump :)
[19:25] <kirkland> lifeless: okay
[19:25] <kirkland> lifeless: looks okay to me
[19:26] <lifeless> my home server is 192.168.1.2, it does DNS and DHCP
[19:26] <kirkland> lifeless: cool
[19:26] <kirkland> lifeless: can you set static dhcp leases?
[19:26] <lifeless> when I installed UEC I told it 192.168.1.100-192.168.1.110
[19:26] <kirkland> lifeless: okay, and you told your dhcp server not to touch that range?
[19:26] <lifeless> as 'public addresses', but that seemed silly in hindsight: nothing could get to it
[19:26] <lifeless> kirkland: yah
[19:26] <lifeless> it allocates down in the 20's
[19:26] <kirkland> lifeless: yeah, we should work on that wording
[19:27] <kirkland> lifeless: sabdfl said he didn't like the wording either
[19:27] <lifeless> so, given I have 192.168.1.0/24 at home
[19:27] <lifeless> and complete control
[19:27] <lifeless> and I don't care what happens above (say) 80
[19:27] <kirkland> lifeless: okay
[19:27] <lifeless> what should I have put it ?
[19:28] <kirkland> lifeless: well, just any range of addresses that eucalyptus can assign to your vm's
[19:28] <kirkland> lifeless: and not conflict with ips that your dhcp server will dole out
[19:28] <lifeless> and by assign, it has them dhcp initially on virbr0, and then later on br0 ?
[19:29] <lifeless> because they seem to end up with my main dhcp server issuing ip addresses to them
[19:29] <lifeless> they get 192.168.1.100   192.168.1.14   for example
[19:30] <kirkland> lifeless: grep VNET_MODE /etc/eucalyptus/eucalyptus.conf
[19:30] <lifeless> MANAGED_NOVLAN
[19:30] <glphvgacs> hi, apt-get install openssh-server says pkg is not avail. (samba karmic) /etc/apt/sources.list looks fine, I think
[19:30] <kirkland> lifeless: https://help.ubuntu.com/community/UEC/Topologies
[19:30] <kirkland> lifeless: your topology is "1 Physical System"
[19:30] <kirkland> lifeless: see the notes there
[19:31] <lifeless> ok, so I need to use SYSTEM ?
[19:31] <kirkland> lifeless: i have never personally installed this topology; it was actually Ng who told me this was actually possible, and added the entry to that wiki page
[19:31] <kirkland> lifeless: yes, according to Ng;  we might need his assistance to move you along much further
[19:31] <kirkland> lifeless: otherwise, you're welcome to attempt my suppositions
[19:31] <jjohansen> smoser: ogasawara updated the linux-ec2 meta package and it should be uploaded soon
[19:32] <lifeless> ok, well I can switch to SYSTEM in a second now that I know of the 'CLEAN=' upstart parameter
[19:32] <smoser> jjohansen, so what happened ?
[19:32] <smoser> it appeared that the meta depended on a newer version that was available?
[19:32] <kirkland> lifeless: yes, CLEAN=1
[19:32] <kirkland> lifeless: also ....
[19:33] <lifeless> kirkland: I'm guessing that the CC is expecting to issue 172.19.1.x addresses to the VM's
[19:33] <kirkland> lifeless: have you hit a problem where it takes a *really* long time to get your CLC to start responding to requests?
[19:33] <lifeless> kirkland: god yes
[19:33] <kirkland> lifeless: yes; the 172.* is the internal addresses that nodes can use to communicate with one another
[19:33] <lifeless> kirkland: and massive long waits for 'ec2 metadata server' on the console
[19:33] <kirkland> lifeless: and the 192.* is how external network users talk to the vms
[19:33] <lifeless> kirkland: and finally when it does come up the key doesn't seem to be on the vm
[19:33] <kirkland> lifeless: okay, I think have a fix for that
[19:34] <kirkland> lifeless: it's in the ~ubuntu-virt ppa, or I can give you a 2-line patch to add to your /etc/init/eucalyptus.conf
[19:34] <kirkland> lifeless: i'd like to SRU this fix, but I'm looking for someone to verify it ;-)
[19:34] <lifeless> 2-line me baby
[19:35] <kirkland> lifeless: http://paste.ubuntu.com/373451/
[19:35] <lifeless> actually what do you mean by CLC to start.. just so that I know we're measuring the same thing.
[19:35] <kirkland> lifeless: just apply those two lines by hand
[19:35] <kirkland> lifeless: that's the full debdiff
[19:35] <jjohansen> smoser: I'm not sure.  This was the first round of updates to ec2 and the arm topic branches, there was a series of updates and the final abi is 304.10 so there was more than one thing missing
[19:35] <kirkland> lifeless: well, there's a boatload of related problems...  basically, takes a long time for the web interface on 8443 to respond
[19:36] <kirkland> lifeless: which stems from the fact that the CLC can't talk to the database
[19:36] <lifeless> ah, no I see the API service timing out
[19:36] <lifeless> giving permission errors
[19:36] <kirkland> lifeless: right, i think that's related
[19:36] <lifeless> and then it will come good
[19:36] <lifeless> ok
[19:36] <lifeless> so thats applied
[19:36] <lifeless> rebooting - clean test for you
[19:36] <kirkland> lifeless: yeah, so the problem is that the ip connection tracker from iptables is not getting loaded before eucalyptus services come up
[19:37] <kirkland> lifeless: so network connections established before the network settles get dropped
[19:37] <lifeless> makes sense
[19:37] <kirkland> lifeless: eventually (10-20 minutes later), everything resets, and it starts working again
[19:37] <kirkland> lifeless: those two iptables commands ensure that iptables comes up in time
[19:37] <lifeless> it'll be a sec before that machine comes back :)
[19:37] <kirkland> lifeless: no problem
[19:40] <lifeless> so to fix one-machine installs
[19:40] <Mack> hi
[19:40] <lifeless> kirkland: which service embeds the crazy dhcp server?
[19:40] <tolik> hi
[19:40] <kirkland> lifeless: the eucalyptus-cc
[19:40] <kirkland> lifeless: this is the "cluster controller"
[19:40] <Mack> can anyone help me install the ioncube loaders?
[19:40] <kirkland> lifeless: nodes are associated with -cc's
[19:41] <kirkland> lifeless: well, nodes are associated with clusters
[19:41] <kirkland> lifeless: clusters are controlled by the cc
[19:41] <kirkland> lifeless: the cc doles out the dhcp addresses to the VMs
[19:41] <kirkland> lifeless: i *think* this should be disabled, though, when you're in SYSTEM mode
[19:41] <kirkland> lifeless: i *think* your networking is pretty much on your own, if you're in SYSTEM mode
[19:42] <lifeless> kirkland: so, to make MANAGED_NOVLAN work with a single machine
[19:42] <kirkland> lifeless: don't think it can be done
[19:42] <lifeless> kirkland: I don't see why not, iptables is sex
[19:43] <lifeless> kirkland: filter dhcp replies that are not from the cc and heading to nodes
[19:43]  * Mack can't get the ioncube loaders installed no matter what i try
[19:43] <kirkland> lifeless: i defer to those with more iptables notches in their bedpost
[19:44] <lifeless> kirkland: I've made a note to try
[19:45] <lifeless> if I get it happy with something crude I'll let the devs polish it ;)
[19:45] <kirkland> lifeless: ack
[19:45] <kirkland> lifeless: okay, so your system is back up now?
[19:45] <RoAkSoAx> kirkland, Maybe you can help me out. What network management tools are good to monitor networks that implement the UEC and, by any chance, do you have any document on how network have changed to be used in UEC?
[19:45] <lifeless> kirkland: yes seeing if it hangs like before
[19:46] <lifeless> kirkland: the ugly hanging I was seeing appears gone
[19:46] <lifeless> kirkland: \o/
[19:46] <kirkland> lifeless: nice
[19:46] <kirkland> RoAkSoAx: docs are all under: https://help.ubuntu.com/community/UEC?action=fullsearch&context=180&value=UEC%2F&titlesearch=Titles
[19:46] <lifeless> kirkland: so please SRU that :)
[19:47] <RoAkSoAx> kirkland, thanks :)
[19:47] <lifeless> whats the bug number
[19:47] <kirkland> lifeless: okay, i'll upload to -proposed
[19:47] <kirkland> lifeless: if you could update to that package and ack it at your earliest convenience, that would be shiny
[19:48] <lifeless> kirkland: sure, drop me a ping when its built in -proposed and I'll do that
[19:49] <Mack> kirkland: do you know how to install the ioncube loaders with php5?
[19:49] <lifeless> just on the bug wil be fine, I've subscribed
[19:49] <kirkland> lifeless: uploaded
[19:49] <kirkland> Mack: no idea whatsoever
[19:49] <Mack> :( i cant get this to wrk
[19:49] <Mack> work*
[19:50] <lifeless> kirkland: ok, now I get stuck on Waiting for EC2 meta-data service
[19:50] <lifeless> kirkland: which is I presume another ip routing fail
[19:50] <kirkland> lifeless: what's sticking?
[19:50] <kirkland> lifeless: is this running a VM?
[19:50] <lifeless> yeah
[19:50] <kirkland> lifeless: okay, we need smoser for that
[19:50] <kirkland> smoser: ping
[19:50] <smoser> here
[19:50] <lifeless> INSTANCEi-40670700emi-E027107D192.168.2.101172.19.1.3running mykey ...
[19:50] <lifeless> bah copy paste _fail_
[19:51] <lifeless> smoser: I have a new all-on-one machine UEC
[19:51] <kirkland> smoser: lifeless is having trouble starting an instance on 9.10
[19:51] <kirkland> smoser: hanging at ec2 meta-data
[19:51] <smoser> is the metadata service running?
[19:51] <kirkland> smoser: what's the bug on that one, and is there a fix, or workaround for Karmic
[19:51] <lifeless> my nodes are coming up ok, and being given a public ip like 192.168.2.100 and a private lke 172.19.1.2
[19:51] <smoser> "all-in-one".
[19:51] <sarthor> Hi, My pppoe-server is according this url "  http://ubuntuforums.org/showthread.php?t=291926  " and is working, but username  and passwords in /etc/ppp/pap_secrete "sarthor9"      *               "99999999" can be used by several clients on the same time from the different computers, how to solve this problem? help
[19:52] <smoser> what odes that mean?
[19:52] <lifeless> smoser: I have one physical machine running sc, cc, nc, clc
[19:52] <smoser> if there is no metadata service (and i think som eof the Eucalyptus modes have no metadata service) than images in karmic will hang waiting for it.
[19:52] <lifeless> smoser: its a test environment so that I can check a code change I'm making to a EC2 using project to UEC enable it works
[19:53] <lifeless> smoser: its running in MANAGED_NOVLAN at the moment
[19:54] <lifeless> how can I tell if the metadata service is running
[19:54] <smoser> well, reading about that mode http://open.eucalyptus.com/wiki/EucalyptusNetworking_v1.5 and http://open.eucalyptus.com/forum/startup-scripts-vms , it "should" be running
[19:54] <smoser> but it would appear that it is not.
[19:54] <smoser> lifeless, what i would suggest, for debugging is:
[19:55] <smoser> - mount image loopback
[19:55] <Mack> smoser: you know how to install ioncube?
[19:55] <smoser> (this is karmic, right)?
[19:55] <lifeless> kirkland: note that I will need to get MANAGED_NOVLAN working :P
[19:55] <lifeless> smoser: yes
[19:55] <smoser> karmic instance
[19:55] <smoser> right?
[19:55] <smoser> mount image loopback
[19:55] <lifeless> karmic on karmic
[19:56] <lifeless> emi-E027107D specifically
[19:57] <smoser> modify  /etc/ec2-init/is-compat-env (or remove it -- i think thats the file, i have
[19:57] <smoser> and put your public ssh keys manually into /root/.ssh/authorized_keys (or /home/ubuntu/.ssh/authorized_keys)
[19:57] <smoser> umount image
[19:58] <smoser> upload image, register, boot
[19:58] <smoser> then, i think that what you will find is that there is no metadata service.
[19:58] <lifeless> so, the metadata service is 169.254.169.254 8773 ?
[19:58] <smoser> metadata service is a web service that runs on http://169.154.169.254 forom the guests point of view
[19:59] <smoser> shouldn't be 8773, should be 80
[19:59] <smoser> and its per-instance data
[19:59] <smoser> so each instance has a different world view of that web service
[19:59] <lifeless> smoser: its dnatted to 8773
[19:59] <lifeless> I totally agree it should be port 80 :)
[19:59] <lifeless> PREROUTING
[20:00] <lifeless> DNAT       tcp  --  *      *       172.19.0.0/16        169.254.169.254     tcp dpt:80 to:169.254.169.254:8773
[20:00] <smoser> that might be magic
[20:00] <smoser> idont know.
[20:00] <lifeless> ok
[20:00] <lifeless> I'll follow this thread
[20:00] <smoser> you'd have to see how its configured elsewhere.
[20:00] <lifeless> I suspect insufficient mangling in iptables
[20:00] <smoser> but seriously, mount hte image and modify it as i suggested.
[20:00] <lifeless> will do
[20:00] <smoser> then you should be able to ssh to it and poke around from inside
[20:01] <smoser> fwiw, there is a package now https://launchpad.net/ubuntu/+source/cloud-utils that has some scripts to make publishing an image easier.
[20:01] <smoser> mainly 'uec-publish-image' might be of use. its one command for bundle upload register
[20:02] <kirkland> smoser: saaaaweeet
[20:02] <kirkland> smoser: i so need that
[20:02] <kirkland> lifeless: send along patches, if you have any
[20:03] <kirkland> lifeless: and, of course, I'll note that the lucid packages are ***far*** better than the karmic ones :-)
[20:04] <lifeless> kirkland: do they depend on other changes in karmic ?
[20:04] <lifeless> kirkland: or could I reasonably sensibly snarf eucalyptus-* from lucid?
[20:05] <kirkland> lifeless: hrm ...  well, there's a few jars and libraries that have been updated
[20:05] <smoser> lifeless, also, i'm sure that kirkland and i are not the only people that would love to see "all in one system" working
[20:05] <kirkland> lifeless: so i can't quite recommend that yet
[20:05] <kirkland> lifeless: and we haven't yet solved the karmic -> lucid euclayptus upgrade path yet
[20:05] <lifeless> kirkland: so you're going to tease me. Fffffiine
[20:05] <kirkland> lifeless: well, just saying :-)
[20:05] <smoser> but then as soon as you get that someone is going to want you to do it with virtual-box, or no-hardware-virt ...
[20:05] <lifeless> seriously though, I don't care about upgrade
[20:06] <kirkland> lifeless: and warning not to live-upgrade to lucid yet and expect UEC to work
[20:06] <lifeless> I can purge the packages and start over, if it is likely to make a different
[20:06] <lifeless> *difference*
[20:06] <smoser> i suspect that there is a bug with the metadata service in this setup.
[20:06] <lifeless> smoser: I'm sure there is, I have money on iptables
[20:06] <Mack> so nobody here knows how to install ioncube? :(
[20:06] <lifeless> Mack: I don't even know what it is.
[20:07] <Mack> lifeless: stupid encoder php devs use so you cant steal their code
[20:07] <Mack> but the loader required to use encoded files is such a pain to install
[20:07] <smoser> Mack, sorry , i had no idea what it was either.
[20:08] <Mack> nobody knows what it is, and the ioncube support site sucks :(
[20:08] <kirkland> encoding php files sounds like an awful idea; i'll avoid ioncube
[20:09] <kirkland> lifeless: i can try to push eucalyptus to a karmic ppa and see if it builds, if you like
[20:09] <kirkland> lifeless: i just haven't even tested the build, so i don't know how deep the rabbit hole goes
[20:10] <lifeless> kirkland: please!
[20:10] <lifeless> kirkland: that would rock
[20:15] <kirkland> lifeless: pushed to ~kirkland ppa for karmic
[20:16] <smoser> mathiaz, ping
[20:16] <smoser> https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-aws-client-libraries . i'm not shooting for main inclusion on those, right?
[20:16] <smoser> ie, its ok for me to build-depend or runtime depend on universe
[20:17] <kirkland> lifeless: you *might* need a newer euca2ools too
[20:17] <kirkland> smoser: i doubt we're looking for main inclusions on those libraries
[20:17] <lifeless> kirkland: you know what to do :)
[20:17] <kirkland> lifeless: heh
[20:18] <smoser> you "should not" need a newer euca2ools
[20:18] <smoser> that is something that actually needs to function, as the api has not changed so we will need to support older euca2ools clients interacting with lucid euca
[20:20] <lifeless> whats the poll frequency on the wait-for-metadata thing
[20:22] <kirkland> lifeless: euca2ools karmic build pushed to same ppa
[20:22] <lifeless> kirkland: thanks
[20:22] <kirkland> smoser: oh
[20:22] <kirkland> lifeless: okay, you might not need newer euca2ools
[20:22] <lifeless> I won't install it until it appears obvious that its needed ;)
[20:23] <smoser> lifeless, i think it tries, waits for 2*N seconds, adds one to N, tries again.
[20:23] <smoser> something like that.
[20:23] <smoser> it will timeout in an hour or so, or maybe half a day
[20:23] <smoser> its painful
[20:24] <kirkland> smoser: jeebus
[20:24] <kirkland> smoser: that sucks
[20:24] <smoser> yeah. soren copied the boto author on that.
[20:25] <lifeless> so, ipv6 for uec ? :)
[20:28] <kirkland> lifeless: i think it supports both
[20:28] <kirkland> lifeless: kinda
[20:28] <lifeless> uses dnsmasq, which doesn't do ipv6  ;)
[20:28] <kirkland> lifeless: tries to, anyway
[20:32] <lifeless> kirkland: did you see my http_proxy bug ? kinda fun
[20:32] <kirkland> lifeless: not yet
[20:32] <lifeless> on euca2ools
[20:39] <_lance_> i seem to have hosed my system with a careless apt-get install. any easy way to revert a bunch of packages to hardy? i've been doing a few by dpkg -i, but there's dozens to go.
[20:41] <bwallen> My machine sounds like it's constantly powering off and on my second hard drive. What causes this?
[20:55] <lifeless> kirkland: is there a document somewhere that describes /what/ euca does with networking as nodes come up or down?
[20:55] <lifeless> or should I just finish reverse engineering it?
[21:16] <Sorrel> :/
[21:16] <Sorrel> hey guys
[21:16] <Sorrel> I'm having an issue setting up dhcp
[21:16] <Sorrel> server
[21:16] <Sorrel> on my 9.10 box.
[21:16] <Sorrel> I have installed dhcp3-server
[21:17] <Sorrel> but it comes up and says that it can't start
[21:17] <Sorrel> I'm setting this up on a small local network
[21:17] <Sorrel> any suggestions?
[21:18] <Spanglish_7776> sorrel, have you tried to configure it?
[21:18] <Sorrel> I have edited the dhcpd.conf
[21:18] <Sorrel> file
[21:18] <Sorrel> still fails
[21:18] <Sorrel> to start
[21:18] <Sorrel> and I can't seem to find the log file
[21:18] <Spanglish_7776> did you check the error log? (possibly syslog)
[21:18] <Spanglish_7776> maybe syslog.
[21:18] <Spanglish_7776> /var/log/syslog
[21:19] <Sorrel> cd /var/log/syslog
[21:19] <Sorrel> err
[21:19] <Sorrel> sry
[21:19] <Spanglish_7776> cd /var/log
[21:19] <Spanglish_7776> vi or nano syslog
[21:20] <lifeless> don't use vi on syslog, has a tendancy to rename files if you edit by mistake :)
[21:20] <lifeless> less /var/log/syslog
[21:20] <Spanglish_7776> or tail ;)
[21:20] <lifeless> anyhow, dhcpd logs to daemon.log, I think
[21:21] <Sorrel> is there a place that I can upload this too?
[21:21] <Spanglish_7776> hmm
[21:21] <Sorrel> nvr mind
[21:21] <Sorrel> looking at the file right now.
[21:22] <Sorrel> it's a little overwhelming :)
[21:22] <Spanglish_7776> try to start dhcpd and then check the end of the file
[21:22] <Sorrel> k
[21:23] <lifeless> kirkland: all working
[21:23] <lifeless> kirkland: starting documentation now
[21:28] <Sorrel> Not configured to listen on any interfaces!
[21:28] <Sorrel> that's what I'm getting in the tail end of the log file
[21:28] <Sorrel> :/
[21:28] <Spanglish_7776> 1 sec
[21:29] <Sorrel> :)
[21:29] <Sorrel> googleing now
[21:29] <Spanglish_7776> http://www.ubuntugeek.com/how-to-install-and-configure-dhcp-server-in-ubuntu-server.html
[21:29] <Spanglish_7776> give that a go, ubuntugeek has been invaluable to me.
[21:30] <Sorrel> thanks I will take a look
[21:30] <Spanglish_7776> Sorrel: INTERFACES=”eth0″ may be your fix
[21:31] <Spanglish_7776> where eth0 specify your interface (usually eth0, but verify)
[21:31] <Sorrel> I have a 1 and a 0
[21:31] <Sorrel> it was complaining on the install that I only had one NIC
[21:32] <Sorrel> so I put in another and then did the install
[21:32] <Sorrel> ( LTSP from the alt CD )
[21:33] <Spanglish_7776> hmm
[21:33] <Sorrel> the documentation is really ambiguious for LTSP
[21:33] <Sorrel> btw
[21:33] <Spanglish_7776> which one is the active interface, eth0 or 1?
[21:34] <Spanglish_7776> you're trying to get LTSP going?
[21:34] <Sorrel> yeah
[21:34] <Sorrel> um
[21:34] <Sorrel> I guess 1 would be
[21:35] <Spanglish_7776> what I mean is, which interface is plugged into the network where dhcp is going to be used.
[21:37] <Spanglish_7776> i wonder why you need two intefaces.
[21:37] <Spanglish_7776> interfaces*
[21:38] <Sorrel> IDK
[21:38] <Spanglish_7776> Sorrel, you using ubuntu?
[21:38] <Sorrel> it doesn't say
[21:38] <Sorrel> yes
[21:38] <Sorrel> well it's from the alternatives CD
[21:38] <Sorrel> but yeah
[21:38] <Sorrel> 9.10 I think
[21:38] <Spanglish_7776> ltsp iso, gotcha
[21:38] <Sorrel> yeah
[21:38] <Sorrel> all sorts of issues
[21:38] <Sorrel> :(
[21:40] <Spanglish_7776> yea, a few years ago, I got it going but didn't really utilize it. it was a pain, that is for sure.
[21:40] <Spanglish_7776> hmm.
[21:41] <Spanglish_7776> Sorrel: on the dhcpd.conf, you specified an INTERFACES="eth1" and tried again?
[21:41] <Sorrel> yeah gives me
[21:41] <Sorrel> No subnet declaration for eth0 (10.42.43.11).
[21:41] <Sorrel> Feb 10 16:40:53 ubuntu dhcpd: ** Ignoring requests on eth0.  If this is not what
[21:41] <Sorrel> Feb 10 16:40:53 ubuntu dhcpd:    you want, please write a subnet declaration
[21:41] <Sorrel> Feb 10 16:40:53 ubuntu dhcpd:    in your dhcpd.conf file for the network segment
[21:41] <Sorrel> Feb 10 16:40:53 ubuntu dhcpd:    to which interface eth0 is attached. **
[21:42] <Sorrel> no idea what's happening
[21:42] <lifeless> you haven't configured it with a range that is to be served out on eth0
[21:42] <Spanglish_7776> yep, looks that way.
[21:43] <Sorrel> do I have to specifiy that in /etc/dhcp3/dhcpd.conf ?
[21:43] <Sorrel> what's in there now
[21:43] <Sorrel> ddns-update-style none;
[21:43] <Sorrel> #option domain-name-servers 145.253.2.75, 193.174.32.18;
[21:43] <Sorrel> default-lease-time 86400;
[21:43] <Sorrel> max-lease-time 604800;
[21:43] <Sorrel> authoritative;
[21:43] <Sorrel> subnet 192.168.0.0 netmask 255.255.255.0 {
[21:43] <Sorrel>         range 192.168.0.200 192.168.0.229;
[21:43] <Sorrel>         option subnet-mask 255.255.255.0;
[21:44] <Sorrel>         option broadcast-address 192.168.0.255;
[21:44] <Sorrel>         option routers 192.168.0.1;
[21:44] <Sorrel> }
[21:44] <mathiaz> !paste | Sorrel
[21:44] <Sorrel> ( is it okay to cp that much into the chat window?
[21:44] <Sorrel> kk
[21:44] <Sorrel> ty
[21:44] <Spanglish_7776> http://paste.ubuntu.com/
[21:45] <Sorrel> http://paste.ubuntu.com/373512/
[21:45] <Roxyhart0> i i have a question. can i just move a ldap certificate form a server to another i mean without create again?
[21:46] <Spanglish_7776> Sorrel: ifconfig, is your eth0 on the 192.168.0.0 subnet?
[21:47] <Sorrel> no
[21:47] <Sorrel> it seems to be completely ignoring that file
[21:48] <Sorrel> http://paste.ubuntu.com/373515/
[21:48] <Sorrel> there's my ifconfig
[21:49] <Spanglish_7776> ah, I don't think dhcpd likes that.
[21:49] <Sorrel> :(
[21:50] <Spanglish_7776> you're specifying 192.168.0.0/24 and you have a different subnet alltogether
[21:50] <Spanglish_7776> do you know how to configure the IP for the second NIC? eth1
[21:50] <Sorrel> no
[21:51] <Sorrel> been trying to figure it out
[21:51] <Sorrel> :/
[21:51] <Spanglish_7776> http://www.ubuntugeek.com/ubuntu-networking-configuration-using-command-line.html
[21:51] <Spanglish_7776> shows you how to set the ip via command line
[21:51] <Sorrel> ty
[21:51] <Spanglish_7776> but
[21:52] <Spanglish_7776> are you on the physical machine? (the one you're trying to configure ltsp on)
[21:52] <Sorrel> yes
[21:52] <Sorrel> do I need to get off it?
[21:53] <Spanglish_7776> no  do this, plug in the second NIC(eth1) and
[21:53] <Spanglish_7776> follow the instructions and use eth1 instead of eth0
[21:53] <Sorrel> k
[21:53] <Sorrel> that page really doesn't want to pull up for me
[21:55] <Spanglish_7776> 1 sec
[21:55] <guntbert> Sorrel: try again
[21:55] <Spanglish_7776> http://paste.ubuntu.com/373520/
[21:55] <Sorrel> ty
[21:56] <Spanglish_7776> hope you're familiar with vi.
[21:56] <Spanglish_7776> you can substitute nano if you want to.
[21:57] <Sorrel> I like nano a good bit better :)
[21:58] <Spanglish_7776> use nano (me too)
[21:59] <Spanglish_7776> brb
[21:59] <Sorrel> k
[22:01] <Roxyhart0> hi can i use a ldap certificate from a difirent server, i mean move it?
[22:06] <kirkland> bug 518911
[22:06] <Sorrel> Roxyhart0,  have you tried copying the file from the old server onto the new one
[22:06] <Sorrel> ?
[22:06] <Sorrel> IDK if it will work
[22:06] <Sorrel> but you could try it.
[22:07] <Roxyhart0> hi Sorrel...no yest, it is just copy that?
[22:07] <Sorrel> no idea
[22:07] <Sorrel> but it seems like it could work
[22:08] <Sorrel> that's going from the assumption that linux treats everything like a file
[22:08] <Sorrel> ( which it does )
[22:08] <Roxyhart0> i will try
[22:08] <Sorrel> if you could get a server setup and put the file in the right place
[22:09] <Sorrel> you may have to edit some config files as well.
[22:10] <Sorrel> Spanglish_7776: I think I got it to work
[22:11] <Sorrel> be back in a sec
[22:12] <lifeless> kirkland: success
[22:12] <kirkland> lifeless: \o/
[22:12] <lifeless> https://help.ubuntu.com/community/UEC/Topologies#preview
[22:12] <kirkland> lifeless: do you have a list of hacks required?
[22:12] <lifeless> kirkland: no hacks
[22:12] <lifeless> kirkland: the PackageInstall instructions created a bad config
[22:13] <lifeless> because eucalyptus is a tad redundant with the live system config, changing that config means you need to also change eucalyptus - specifically putting stuff onto br0 not eth0
[22:14] <Ng> lifeless: did you get your one-machine setup going?
[22:15] <lifeless> Ng: yes
[22:15] <lifeless> easy once I finished reverse engineering what it was doing
[22:16] <lifeless> Ng: I've rewritten the one machine topology notes
[22:17] <kirkland> lifeless: cheers, thanks
[22:17] <kirkland> Ng: i'm curious why the Bug:123456 works on wiki.ubuntu.com, but not on wiki.ubuntu.com/community ?
[22:17] <lifeless> kirkland: no probs; let me know if anything is unclear. I'm happy to write more prose if you want.
[22:17] <kirkland> Ng: are they different instances?
[22:18] <kirkland> lifeless: thanks for documenting; i might bust those config instructions out to a separate page, and link to it from the Topologies page
[22:18] <lifeless> kirkland: pretty sure they are, yeah.
[22:18] <mathiaz> kirkland: are you still doing testing with tamarind?
[22:18] <kirkland> lifeless: just to keep the Topos page simple
[22:18] <lifeless> kirkland: sure
[22:18] <kirkland> mathiaz: i've been side tracked; i need to run the tests on the current Topo/install
[22:18] <lifeless> kirkland: I'm going to blog as well I think
[22:18] <kirkland> lifeless: thanks for doing in any case
[22:19] <kirkland> lifeless: please do ;-)
[22:19] <mathiaz> kirkland: ok - do you plan to reinstall soon?
[22:19] <kirkland> mathiaz: let me kick the test ...
[22:19]  * kirkland puts everyone else on pause
[22:19] <mathiaz> kirkland: I'd like to test the new code I added for installation
[22:19] <kirkland> mathiaz: how long does your tests take to run?
[22:19] <mathiaz> kirkland: I don't want to *reinstall* the UEC now
[22:19] <kirkland> mathiaz: oh
[22:20] <mathiaz> kirkland: just test that the layout on tamarind is correct
[22:20] <kirkland> mathiaz: okay, i won't be reinstalling now
[22:20] <mathiaz> kirkland: great - thanks
[22:21] <kirkland> mathiaz: http://pastebin.ubuntu.com/373535/
[22:21] <mathiaz> kirkland: hmm - twisted is not installed on tamarind
[22:21] <mathiaz> kirkland: hm wait
[22:21] <mathiaz> kirkland: where did you run that command?
[22:21] <lifeless> is there a simple way to get the root user enabled in the UEC images?
[22:22] <kirkland> mathiaz: kirkland@tamarind:~/uec_testing/testing$  ./uec_test.py -c config_single.yaml
[22:22] <mathiaz> kirkland: right - you can't run the test on tamarind
[22:22] <kirkland> mathiaz: oh, i need to be on the CLC
[22:22] <mathiaz> kirkland: because the euca2ools commands are not there
[22:22] <mathiaz> kirkland: yop
[22:23] <mathiaz> lifeless: hm - we're really trying to avoid the use of the root account on UEC images
[22:25] <Ng> lifeless: I'm curious now what I did to make it work. I wasn't really making notes at the time
[22:26] <Ng> kirkland: as far as I know they're the same wiki
[22:28] <Ng> lifeless: ah yes, I set my bridge up identically to how you've done it. The only difference is I didn't bother even trying MANAGED_NOVLAN, I just went for SYSTEM so the nodes would appear as any other machine on my LAN
[22:28] <lifeless> mathiaz: you may be trying to avoid it, but umpteen million third party tools assume it is where the key is loaded when you use EC2
[22:28] <Ng> I hope you have something significantly more useful to do with you local cloud than I do. I only really set it up to see if I could ;)
[22:29] <lifeless> Ng: making Hudson run with UEC
[22:29] <lifeless> which it looks like it would, if root was usable.
[22:29] <mathiaz> lifeless: what do you mean by the key is loaded?
[22:29] <lifeless> euca-run-instances -k mykey emi-E027107D
[22:29] <lifeless> installs a ssh key to use to log into the machine and $do $stuff
[22:29] <mathiaz> lifeless: if you use the ubuntu account instead, you'll have passwordless sudo
[22:30] <lifeless> mathiaz: yes, but that means changing about 4 layers of code and writing a UI to say 'use the ubuntu account and do sudo'
[22:30] <mathiaz> lifeless: right - the root account is disabled in the Ubuntu images - instead use the ubuntu account with sudo
[22:30] <lifeless> mathiaz: which is _not_ the same as EC2
[22:30] <dasunsrule32> I am having a grub issue I believe, I cannot boot into the system. I have a seperate part for /boot on /dev/sda5, / is /dev/sda6. How can I go about getting this to boot again?
[22:30] <mathiaz> lifeless: well - it's not the same as the images published in EC2
[22:30] <lifeless> right
[22:30] <lifeless> thus it gets in the way of 'seamless transition'
[22:31]  * lifeless whinges some more
[22:31] <TrickFinlay2> clear
[22:31] <TrickFinlay2> ooops sorry
[22:31] <mathiaz> lifeless: right - we had that discussion at the very begining
[22:32] <lifeless> mathiaz: can one take the AMI's from EC2 and just use them ?
[22:32] <mathiaz> lifeless: on one hand there is the Ubuntu policy that says: not root account enabled by default
[22:32] <mathiaz> lifeless: OTOH there is the fact that EC2 images are run with the root account by default
[22:32] <mathiaz> lifeless: yes
[22:33] <lifeless> mathiaz: I can see the rationale, I'm just expressing my displeasure at the time and effort it is costing me; and the suspicion I have that it will add this cost and overhead to many other users too
[22:33] <mathiaz> lifeless: it's an issue with the image itself and its sets itself up
[22:33] <mathiaz> lifeless: running an unmodified EC2 EMI should work
[22:34] <mathiaz> lifeless: *porting* an application to run on an UEC image requires some work
[22:34] <lifeless> mathiaz: This means that you can't seamless transition though: when you exceed UEC capacity you need to move to a different image to spill onto EC2
[22:34] <lifeless> mathiaz: thats the bit I have trouble understanding why we did this
[22:35] <mathiaz> lifeless: not really - the image that is running on UEC can be rebundled to EC2
[22:35] <mathiaz> lifeless: the part that sets the ssh key for the root|ubuntu account is done by the image itself
[22:35] <lifeless> sure, if you weren't using vanilla images
[22:36] <lifeless> mathiaz: yes, I am aware of that, it looks it up in the 16KB user data region or thereabouts.
[22:36] <TrickFinlay2> if I want to install JeOS from my 9.10 CD, is it F4 -> OEM install?
[22:38] <lifeless> mathiaz: given that UEC lives behind a firewall, I don't really see that avoiding root is really important.
[22:39]  * lifeless adds this to his blog post
[22:41] <mathiaz> lifeless: well - it's a policy in Ubuntu to not enable the root account by default
[22:41] <lifeless> then the EC2 Ubuntu images should not enable it either ;)
[22:41] <mathiaz> lifeless: whether you're behind a firewall or not is irrelevant here
[22:41] <mathiaz> the EC2 Ubuntu images don't have the root account enabled by default
[22:41] <lifeless> mathiaz: I think it is relevant, because the policy exists to solve specific problems, not as a fait accompli
[22:42] <lifeless> TrickFinlay2: its ubuntu-vm-builder these days
[22:42] <lifeless> TrickFinlay2: there is a wiki page about it.
[22:43] <dinda> sommer: ping - you around?
[22:44] <mathiaz> lifeless: hm - I'm not sure I get your point
[22:44] <mathiaz> lifeless: none of the products in Ubuntu have the root account enabled by default
[22:44] <mathiaz> lifeless: we decided that images published to EC2 and for UEC should behave the same way as any other Ubuntu product
[22:44] <lifeless> mathiaz: I thought based on your earlier comment that the Ubuntu official EC2 AMI's put the supplied key into the root account
[22:45] <mathiaz> lifeless: oh no - I don't think so
[22:45] <lifeless> mathiaz: if they don't, then thats fine, its not a difference
[22:45] <mathiaz> lifeless: I didn't not express myself correctly
[22:45] <lifeless> still annoying to find bugs where folk assume it goes into root on EC2, but not unique to UEC in that case
[22:45] <erichammond> lifeless: http://alestic.com/2009/04/ubuntu-ec2-sudo-ssh-rsync
[22:46] <mathiaz> lifeless: yes - that's one of the difference the Ubuntu images and other images
[22:46] <erichammond> lifeless: If you ssh to root@ on an official Ubuntu image on EC2, it prints out a message pointing you to use ubuntu@ instead.
[22:46] <mathiaz> lifeless: you'd have to adapt your deployment/configuration scripts to use the ubuntu account when you deploy to an Ubuntu image
[22:47] <lifeless> mathiaz: yeah
[22:47] <lifeless> erichammond: thanks
[22:47] <erichammond> lifeless: In the above article I also describe one command which can enable the root ssh if you really want to use the EC2 standard instead of the Ubuntu  standard.
[22:48] <erichammond> I don't think I've been excommunicated yet for listing that.
[22:48] <lifeless> As I need to change third party code anyhow
[22:48] <jMyles_> I'm interested in using subversion on my ubuntu-server, but I don't know where to begin.
[22:48] <lifeless> I'm just going to teach it how to use an arbitrary username
[22:48] <lifeless> and a command prefix when running admin code
[22:50] <erichammond> lifeless: The older community Ubuntu AMIs I published used ssh to root@ because I didn't think I could as an unknown individual sway the EC2 community to adopt the Ubuntu standard, but when Canonical started publishing AMIs, I encouraged them to do it the consistent (Ubuntu) way.  It did require a lot of back and forth and a compromise with passwordless sudo, but I am happy with the result.
[22:52] <lifeless> ok
[22:52] <lifeless> I was semi ranting because of the wrong end of the stick; I thought we were publishing UEC images differently to EC2 ones.
[22:52] <lifeless> *that* would be very hard to justify
[22:53] <lifeless> now I'm totally happy (though still with code changes to make to get this thing working)
[22:54] <erichammond> lifeless: Not only is the behavior the same with EC2 and UEC, but the images themselves are exactly the same, except for the kernel.
[22:54] <erichammond> lifeless: Can you share what product you're working on?
[22:54] <lifeless> hudson-ci.org
[22:55] <lifeless> moving the dx team test environment into the internal UEC instance once that comes online
[22:57] <sherringham> jMyles_ : Google? https://help.ubuntu.com/9.10/serverguide/C/subversion.html