=== thumper-gym is now known as thumper
=== pHcF_ is now known as pHcF
=== railsraider_ is now known as railsraider
[12:25] <yolanda> jamespage, the nova-compute-vmware package is correctly tested? i'm having errors when installing nova-compute package after nova-compute-vmware has been installed
[12:26] <yolanda> http://paste.ubuntu.com/6750184/
=== railsraider_ is now known as railsraider
[12:36] <yolanda> jamespage, i saw my problem is related with that bug: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1062336
[12:36] <uvirtbot> Launchpad bug 1062336 in nova "nova-compute expects libvirtd group" [High,Triaged]
[12:36] <jamespage> yolanda, its untested
[12:36] <yolanda> but there is a won't fix from your side , can you explain me why?
[12:36] <jamespage> and its a hack for < icehouse
[12:36] <jamespage> yolanda, that's actually fix commited for trusty
[12:37] <yolanda> ok, i'm testing that on precise machines
[12:38] <yolanda> jamespage, testing with that version from cloud archive: 1:2013.2-0ubuntu1~cloud0
[12:38] <yolanda> that needs updating?
=== huats_ is now known as huats
[12:40] <jamespage> yolanda, I suspect it needs a workaround in that charm for the moment
[12:40] <yolanda> just create the group manually?
[12:40] <jamespage> yolanda, its going to be horrible - something like creating the group manually
[12:40] <jamespage> but just for < icehouse
[12:41] <jamespage> yolanda, the objective is to get this charm running in LXC containers so that we can nest them in amongst other openstack services
[12:41] <yolanda> you meant that installing these package is a workaround for icehouse? what changes in icehouse?
[12:41] <jamespage> yolanda, the next drop of icehouse packages fix this
[12:41] <yolanda> the group issue, you mean
[12:41] <jamespage> nova-compute no longer depends on libvirt
[12:41] <yolanda> ok
[12:41] <yolanda> got it
[12:41] <jamespage> we have a nova-compute-libvirt package
[12:41] <jamespage> which -kvm etc.. depend on
[12:42] <yolanda> ok, i'll create the group just for < icehouse
[12:45] <jamespage> roaksoax, OK if I assign you some other maas related MIR stuff?
[13:02] <jamespage> yolanda, fancy doing an MIR alongside your charm work?
[13:02] <jamespage> https://bugs.launchpad.net/ubuntu/+source/fping/+bug/1268920
[13:02] <uvirtbot> Launchpad bug 1268920 in qstat "[MIR] fping and qstat, recommends of nagios-plugins" [Undecided,Incomplete]
[13:02] <jamespage> (its good distro experience)
[13:05] <roaksoax> jamespage: please do!
[13:08] <zul> jamespage:  beanstalk got fixed so ill kick off the builds in the lab as well
[13:25] <jamespage> roaksoax, https://bugs.launchpad.net/ubuntu/+source/pycountry/+bug/1268915
[13:25] <uvirtbot> Launchpad bug 1268915 in python-dns "[MIR] pycountry and python-dns, b-d's of python-formencode" [Undecided,Incomplete]
[13:25] <jamespage> ta
[13:25] <jamespage> zul, good-oh
[13:25] <jamespage> zul, how are we looking for b2 generally?
[13:25] <yolanda> jamespage, ok
[13:25] <jamespage> yolanda, thanks!
[13:25] <roaksoax> jamespage: thanks!
[13:28] <zul> jamespage:  ill let you know today
[13:29] <zul> jamespage:  fping and qstat was not part of nagios-plugins at one point we specifically disabled them at one point
[13:29] <jamespage> zul, oh - so that might have got re-enabled?
[13:29] <jamespage> yolanda, ^^
[13:29] <zul> jamespage:  qstat -  Command-line tool for querying quake (and other) servers ;)
[13:29] <jamespage> zul, oh ffs
[13:30] <jamespage> yolanda, thats probably actually a package update for nagios to drop those deps
[13:31] <jamespage> yolanda, I think that got missed on the last merge (I'll let you read the changelog :-))
[13:31] <yolanda> so i should do the MIR for those 2 packages, and drop then from nagios, right?
[13:34] <zul> jamespage:  i feel like abraham simpson now
[13:34]  * zul ties an obion to his belt
[13:34] <zul> onion even
[13:36] <jamespage> yolanda, no - fixup the package and mark those bug reports as invalid
[13:37] <jamespage> yolanda, I think the problem is that they are reverse-recommends of nagios-plugins-standard
[13:38] <jamespage> yolanda, xnox did an update on the previous ubuntu version to make them depends of the -extra package which is in universe
[13:39] <yolanda> and this got lost? i need to take a look at the packages to know about them
[13:40] <roaksoax> jamespage: hey! so I seek your advice. The latest kombu Depends on python-librabbitmq | python-amqp. This preference over librabbitmq causes that when celery (used by MAAS) install kombu, it installs librabbitmq by default causing celery to crash, meaning a broken MAAS
[13:41] <jamespage> roaksoax, I'm assuming celery does not like librabbitmq then?
[13:41] <roaksoax> jamespage: so, given that we also use kombu for openstack, do you think we should make a strong preference for python-amqp over python-librabbitmq (as in Depends on python-amqp | python-librabbitmq ? )
[13:41] <roaksoax> jamespage: you are correct!
[13:42] <roaksoax> jamespage: i can work around it in MAAS by depending on python-amqp and possibly conflicting with python-librabbitmq, however, I'm concern of the effect it could also have in openstack the fact that its preference is python-librabbitmq
[13:44] <jamespage> roaksoax, hmm
[13:44] <jamespage> roaksoax, why does celery crash?
[13:45] <jamespage> roaksoax, librabbitmq provides native bindings so should be more performant
[13:46] <roaksoax> jamespage: http://paste.ubuntu.com/6750300/
[13:48] <jamespage> roaksoax, well surely that is a bug?
[13:49] <roaksoax> jamespage: it is indeed. rvba has been looking at it, and it seems he can't figure out why it doesn't like librabbitmq
[13:51] <jamespage> roaksoax, https://github.com/celery/librabbitmq/commit/3bacd49cdfaa77a318f99b4f02fabe6bf73301a9
[13:52] <jamespage> roaksoax, we are a couple of point releases out-of-date - I'd suggest updating to 1.0.3 and re-testing
[13:52] <jamespage> 1.0.2 includes that fix
[13:55] <jamespage> roaksoax, funny - I can't actually reproduce that issue
[13:56] <roaksoax> jamespage: uhmm weird.. we have lab integration tests failing because of that
[13:56] <jamespage> roaksoax, I'd recommend the bump anyway
[13:58] <roaksoax> jamespage: will do :) thanks for the input
[13:58] <jamespage> roaksoax, np
[14:03] <roaksoax> rvba: ^^
=== mjohnson15_2 is now known as mjohnson15
[14:53] <zul> jamespage: https://code.launchpad.net/~zulcss/nova/ftbfs-jan14/+merge/201600
[14:54] <jamespage> zul, why's the tests failing?
[14:55] <zul> jamespage:  sqlalchemy
[14:55] <zul> https://bugs.launchpad.net/nova/+bug/1269008
[14:55] <uvirtbot> Launchpad bug 1269008 in nova "Icehouse failing with sqlalchemy 0.8.3" [Undecided,New]
[14:56] <jamespage> zul, I think I saw the same in neutron actually
[14:56] <jamespage> zul, i'd rather we did not ignore that test error
[14:56] <jamespage> its actually quite badly broken
[14:56] <jamespage> so we should fix it properly rather than by-passing the tests IMHO
[14:56] <zul> jamespage:  not surprising i think the db stuff is being synched from oslo-incubator
[14:57] <zul> jamespage:  yeah i totally agree but sqlalchemy is not my strong suit
[14:58] <jamespage> zul, SQLAlchemy>=0.7.8,<=0.7.99
[14:58] <jamespage> so they won't have seen this upstream right?
[14:58] <zul> nope
[14:58] <zul> the mirantis guys usually care about sqlalchemy 0.8
[15:02] <zul> jamespage:  also seeing this at the end of builds http://pastebin.ubuntu.com/6750843/
[15:03] <jamespage> zul, oh - ignore that
[15:03] <jamespage> thats jenkins
[15:03] <zul> jamespage:  its causing the redballs though ;)
[15:04] <smoser> jamespage, can you quick sanity check http://paste.ubuntu.com/6750876/
[15:04] <smoser> just that the format of the commit is right.
[15:04] <jamespage> zul, dang
[15:04] <smoser> thats debian/source/format 1.0 and i've not done anything like that in quite a while.
[15:05] <jamespage> smoser, looks ok
[15:05] <jamespage> 1.0 urhg
[15:13] <jamespage> smoser, zul: can you sanity check this for me - http://paste.ubuntu.com/6750912/
[15:14] <zul> jamespage:  looks ok
[15:16] <smoser> jamespage, do you not need any version checking in the postinst/postrm on the mv_conffile ?
[15:16] <smoser> i gues because the older version wouldn't exist if you'd already done it.
[15:17] <smoser> and i'm guessing mv_conffile does something sane if the new name exists already.
[15:17] <jamespage> smoser, I think that the helper handles that all - hence the pass of "$@"
[15:17] <smoser> jamespage, well i dont know how it could possibly know that.
[15:17] <smoser> it wouldn't have any idea what version supported the new confi file and what supported the old.
[15:17] <jamespage> thats passed as a param
[15:18] <smoser> ah. ok. i was thinking that was just a old-conf extension.
[15:18] <smoser> that makes sense then.
[15:23] <jamespage> smoser, coolio
[15:23]  * jamespage waits for 25 mins to be able to test
[15:27] <yolanda>  do we have some rationaly for fping and qstat, or some main reasons why we want a MIR?
[15:29] <jamespage> yolanda, they don't need to be MIR'ed
[15:29] <jamespage> yolanda, just drop them from the Recommends on the -standard package
[15:29] <yolanda> oh, i misunderstood it
[15:29] <yolanda> easier then
[15:29] <jamespage> yolanda, the mir was raised automatically
[15:30] <jamespage> yolanda, however it should not be required
[15:30] <yolanda> ok, understand now
[15:42] <jamespage> zul, fixing up plugins on the jenkins server now
[15:42] <zul> jamespage:  ack thanks
[15:47] <zul> jamespage:  i have a fix for the nova problem
[15:51] <jamespage> zul, OK _ I think jenkins is fixed now
[15:51] <zul> jamespage:  cool thanks
[15:52] <jamespage> zul, out of date plugins
[15:52] <jamespage> for the version in raring at least
[15:53] <jamespage> zul, OK - better
[15:54] <zul> jamespage:  coolio
[15:57] <yolanda> sent debdiff here: https://bugs.launchpad.net/ubuntu/+source/fping/+bug/1268920
[15:57] <uvirtbot> Launchpad bug 1268920 in qstat "[MIR] fping and qstat, recommends of nagios-plugins" [Undecided,In progress]
[16:10] <paco1> hi folks!
[16:13] <paco1> i have an issue with my new openldap servers on ubuntu 12.04.3 x64 > (Too Many Open Files). I put on "/etc/security/limits.conf" "* hard nofile 4096" but when it comes at 1800 (with lsof | wc -l comand), it's the same > (Too Many Open Files).
[16:16] <paco1> with ulimit comand, come back to 1024 after a reboot
[16:36] <jamespage> zul, 585M
[16:36] <zul> jamespage:  hmm?
[16:36] <jamespage> zul, size of the server iso now!
[16:36] <zul> jamespage:  wtf?
[16:37] <jamespage> zul: I applied the seed changes to drop a load of stuff
[16:37] <zul> jamespage:  ah good...maybe we can get it smaller :)
[16:38] <zul> jamespage:  i need to do the MIR for workflow
[16:38] <zul> er...taskflow
[16:39] <paco1> if anyone can help me, thanks!
[16:53] <paco1> how can i grow the nomber of open files that by defaults it's 1024?
=== melter is now known as Guest57678
[16:54] <TheLordOfTime> what's ulimit -N and why isn't it documented in the manpage?
[16:56] <glosoli> hey folks, any ideas how could one edit PATH in Ubuntu server with no user available except root ?
=== melter_ is now known as melter
[16:56] <glosoli> I am not sure where the bashrc belongs
[17:03] <hitsujiTMO> glosoli: as in the global PATH? that should be in /etc/environment
[17:03] <psivaa> hallyn: bug #1269073 is for tomcat failure that i said in the meeting
[17:03] <uvirtbot> Launchpad bug 1269073 in tomcat7 "test_tomcat_daemon smoke test failure on images with 3.13 kernel " [Undecided,New] https://launchpad.net/bugs/1269073
[17:03] <glosoli> hitsujiTMO: Oh thanks sir, is it safe to add smth in there ?
[17:03] <hallyn> psivaa: ok, i think jamespage sounded interested
[17:03] <jamespage> thanks hallyn
[17:03] <psivaa> hallyn: ohh, ack. sorry about that
[17:04] <jamespage> psivaa, trying to reproduce that but I can't locally
[17:04] <hitsujiTMO> glosoli: as long as you don't break it. a malformed PATH will cause major headaches.
[17:04] <psivaa> jamespage: i installed manually and was able to reproduce
[17:04] <glosoli> hitsujiTMO; ok thanks mr
[17:05] <psivaa> jamespage: the issue is only with images 20140109 onwards
[17:05] <hitsujiTMO> glosoli: is it just for one user you want to change or for all users?
[17:05] <jamespage> psivaa, looking that that bug report the control port is not listening
[17:05] <jamespage> 8005 normally
[17:05] <jamespage> on 127.0.0.1
[17:05] <psivaa> right. when i downgraded the kernel it did
[17:05] <glosoli> hitsujiTMO: I am the only one behind administrating this my very private server for hosting stuff to show others, and there is only one user which is root and I see no point of creating new user
[17:06] <glosoli> it's mostly experiment usage like
[17:06] <glosoli> to deploy project, to check how it works and bla bla
[17:06] <glosoli> I am not sys admin, just some young dev, trying to play with deploying of stuff
[17:06] <hitsujiTMO> glosoli: then maybe have it in /root/.profile              as:             PATH=/path/to/new/path:$PATH
[17:07] <glosoli> hitsujiTMO: aaa I see, thanks!
[17:07] <hitsujiTMO> glosoli: even just when playing around you should use a normal user with sudo priviledges. Its a much more secure way of doing things
[17:09] <glosoli> hitsujiTMO: I do understand that, though if someone hacks your server, they probably have all the knowledge to go all the way through, consider is just for testing purposes, I don't see anyone interested in it, at least now, maybe I am just naive
[17:09] <hitsujiTMO> glosoli: even a tersting server someone will want to hack. they'll want it so they can run their own software on it, may it be spam software or a bot net or what not
[17:10] <glosoli> I see, it's just for ~4 days I hope it goes well hmm
[17:11] <jamespage> psivaa, is the securerandom stuff taking longer that normal under 3.13
[17:11] <jamespage> psivaa, INFO: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [87,453] milliseconds.
[17:11] <jamespage> and I pushed that in by install havegd
[17:15] <TheLordOfTime> what's `ulimit -N` for, and why isn't it documented in the manpage?  anyone know?
[17:15] <jamespage> smb, can you take a glance at bug 1269073
[17:15] <uvirtbot> Launchpad bug 1269073 in tomcat7 "test_tomcat_daemon smoke test failure on images with 3.13 kernel " [Undecided,New] https://launchpad.net/bugs/1269073
[17:15] <jamespage> it appears related to the 3.13 kernel bump
[17:16] <smb> jamespage, yeah, can have a look
[17:16] <jamespage> smb, thanks - anything that might cause less entropy in /dev/random in virtual machines is probably relevant
=== keee is now known as w0rmie
[17:18] <smb> jamespage, Ok, well just something in  a minor kernel version update... :)
[17:18] <jamespage> smb, I'm sure you will find it easy to ID the issue and resolve :-)
[17:20] <rbasak> smoser: your thoughts on bug 1258113 please?
[17:20] <uvirtbot> Launchpad bug 1258113 in cloud-init "Cannot determine boot-finished state reliably" [Undecided,New] https://launchpad.net/bugs/1258113
[17:24] <semiosis> jamespage: ping
[17:24] <semiosis> jamespage: https://code.launchpad.net/~semiosis/ubuntu/trusty/glusterfs/fix-for-1268064
[17:24] <jamespage> semiosis, hello
[17:25] <semiosis> hi!  i made a merge proposal.  it includes an update to the new (latest) glusterfs release, and also updates the upstart stuff
[17:25] <semiosis> i figured out the instance line issue btw
[17:28] <jamespage> semiosis, I think you forgot to add the mounting-glusterfs upstart job to your branch
[17:29] <semiosis> uhhh
[17:29] <semiosis> pretty sure i built & tested this
[17:29] <semiosis> let me check
[17:30] <semiosis> wow, how did that happen
[17:31] <jamespage> :-)
[17:31] <semiosis> my change to the rules file was committed, and the glusterfs-server.mounting-glusterfs.upstart file was removed & re-added verbatim, instead of the glusterfs-server.mounting-glusterfs.upstart being added
[17:32] <semiosis> i mean instead of the glusterfs-client.mounting-glusterfs.upstart being added
=== keee is now known as w0rmie
[17:34] <semiosis> looking at my working dir and i have the right stuff here... so the test build i did with pbuilder was correct.  somehow the commit/push didnt include this change
[17:35] <semiosis> i never ran bzr add on the new file!
[17:37] <psivaa> smb: the raid1 installation issue that we are seeing after 3.13 is reported in bug #1269086
[17:37] <uvirtbot> Launchpad bug 1269086 in linux "RAID1 installations fail to complete on trusty server images with 3.13 " [Undecided,New] https://launchpad.net/bugs/1269086
[17:39] <semiosis> jamespage: ok i wasnt reading the diff correctly in regards to the glusterfs-server.mounting-glusterfs.upstart being re-added verbatim.  it was removed as it should have been
[17:39] <semiosis> i've pushed a new commit with the glusterfs-client.mounting-glusterfs.upstart file, the diff shows it now
[17:39] <smb> psivaa, Thanks
[17:40] <semiosis> thx for catching this!
[17:43] <smb> jamespage, psivaa For the tomcat thing... Not really sure whether I just look in the wrong place... Where would be any kernel messages during the daemon start (if there are any)?
[17:44] <semiosis> jamespage: fixed. https://code.launchpad.net/~semiosis/ubuntu/trusty/glusterfs/fix-for-1268064/+merge/201280
[17:45] <jamespage> semiosis, yup - got it
[17:45] <semiosis> ok great
[17:46] <psivaa> smb: i could not find any specific kernel messages for this in syslog, or kern.log
[17:49] <jamespage> semiosis, might be tomorrow before i get to upload but looks good
[17:49] <semiosis> thats great! thanks :D
[17:50] <semiosis> jamespage: this was a lot easier than i remember it being back in 2012
=== keee is now known as w0rmie
[17:57] <jamespage> semiosis, uploaded - thanks!
[17:57] <semiosis> wow that was fast
[17:57] <semiosis> you're welcome
[17:58] <semiosis> jamespage: should i set the bug to Fix Released now?
[17:59] <jamespage> semiosis, that will happen automatically
[17:59] <semiosis> oh nice!
=== hypernet is now known as Rallias
[18:12] <mndo> hi! I am trying to configure openldap to use ssl but these https://help.ubuntu.com/community/SecuringOpenLDAPConnections instructions don't work, anyone has any pointers to put me in the right path? Thank you
[18:14] <psivaa> smb: jamespage: fyi, port 8005 in fact starts to listen in about 14+ mins after the reboot. checked once. could try a few more times to see the timing if that helps
[18:14] <psivaa> rewtraw: the tomcat issue that is
[18:14] <smb> psivaa, I think before spending too much time on those two bugs, there is currently a newer kernel which is still in proposed. Could you re-run the two tests when 3.13.0-3.18 or later becomes current. And if problems persist with that I go back looking at them.
[18:15] <psivaa> smb: ok, if that's in -proposed i could test that
[18:16] <smb> psivaa, Yes it sits in proposed right now
[18:31] <biggdadd73> join #ubuntu
[18:54] <rharper> smoser: looking for some help debugging maas-import-ephemerals importing trusty images from the daily stream;  right now maas-import-ephemerals doesn't print anything and returns 0; but it doesn't download the trusty image into /var/lib/maas/ephemeral
[19:12] <Kaffien> anyone here with setting up a scsi target on  ubuntu server?
[19:12] <Kaffien> iscsci
[19:12] <zanzacar> My work is finally making the switch from being a Novel server to a ubuntu server. Everything seems to be going alright but the higher ups are worried about tech support/IT support if one of us set up the server and then there isn't anyone to support it if there is any problems. Does anyone know if any Ubuntu/Linux tech support to reassure the higher ups?
[19:12] <Kaffien> darnit i meant  iscsi.
[19:17] <genii> zanzacar: You can find out about paid support for Ubuntu Server here: http://www.ubuntu.com/server/management   ( anywhere from $320-$1200 USD  annually) . There's also always this channel where you can ask for free.
[19:19] <smoser> rharper, it probably thinks it has stuff in /var/lib/maas/ephemeral/.[something]
[19:19] <smoser> which it shouldnht have.
[19:19] <smoser> genii, that was a really good answer to zanzacar's question.
[19:19] <smoser> thanks.
[19:21] <psivaa> smb: the tomcat issue is still present with kernel version 3.13.0-3.18
[19:21] <sarnold> zanzacar: paid or unpaid, you can also files bugs into launchpad using 'ubuntu-bug'
[19:24] <genii> smoser: Maybe I should make a factoid containing the essential for future use :)
[19:25] <zanzacar> genii: Thanks I did see that but when I contacted them it doesn't seem to be for one off servers and more like larger scale things.
[19:27] <genii> zanzacar: Most times answers can be had here in the channel for many questions. Did you speak to a Canonical representative in person, or by email, etc, about your specific needs?
[19:29] <zanzacar> I have my own server at home. I think it is great, I also find this channel very helpful as well. The higher ups want to be able to pay al-a-carte for support as they seem fit. ( Mainly emergencies ). We really are a small firm ( 4 people ) using minor server needs mainly just a file server.
[19:30] <zanzacar> Its the higher up that want something to help ease their feelings about going this route. Linux to them is a proprietary weird thing that they will never be able to get anyone to work on if I left. So if I can just show them there are people out there that are reasonably trained I can move forward essentially.
[19:33] <zanzacar> I tried to look up San Diego Linux Support and I can't seem to find very many tech/computer repair places that meet my needs.
[19:33] <sarnold> zanzacar: it's true that landscape would probably not that useful with only a single machine, but I would hope that the rest of the support and services for a single machine would be pretty straightforward if you wanted it..
[19:35] <genii> zanzacar: Canonical has certification programs with Linux Professional Institute ( www.lpi.org/ ) , If you contact one of their regional people for your area, they may be able to help you find a qualified person which you can hire on an as-needed basis.
[19:35] <sarnold> zanzacar: that's not a big surprise; I suspect most linux experts would be professional system administrators or "devops" depending upon if they like the new lingo :) -- I suspect you might be able to find someone through a local users group or stack exchange careers -- the folks behind askubuntu.com
[19:35] <genii> ( alternately, get someone in the company certified by them)
[19:36] <zanzacar> genii: Excellent certified and everything. I will look into lpi.org. I would get certified but that doesn't help the company if I leave.
[19:36] <TJ-> zanzacar: For ad-hoc don't discount remote admins ... often you can get better skills and lower cost and faster response
[19:37] <zanzacar> That is very true.
[19:38] <sarnold> which is one of the nice aspects of irc :) free ad-hoc remote debugging advice :)
=== jmedina_ is now known as jmedina
[19:41] <zanzacar> I have found that ubuntu has one of the better user communities which is also the reason I am suggesting going with this over redhat or a paid for system of sorts. If only it was my choice.
[19:49] <zanzacar> Thanks for all the tips/thoughts.
=== _thumper_ is now known as thumper
[19:54] <TheLordOfTime> how can I force a time update on a server off a time server
[19:55] <hitsujiTMO> TheLordOfTime: ntpupdate ip.of.ntp.server
[19:55] <hitsujiTMO> TheLordOfTime: with sudo ofc
[19:58] <TheLordOfTime> hitsujiTMO: do i need to worry about it not giving me any output?
[19:58] <TheLordOfTime> hitsujiTMO: is there anything I can install to automate this too?
=== YamakasY_ is now known as YamakasY
[20:00] <sarnold> some folks shove ntpdate calls into a cronjob, so if one server doesn't respond, they'll get a chance to call another one soon enough
[20:00] <hitsujiTMO> TheLordOfTime: set it as a cron job
[20:01] <TheLordOfTime> i should've read the server guide, ntpd continually calculates the drift and adjusts it, according to the server guide (12.04)
[20:02] <TheLordOfTime> would ntpd work for what I need without me needing to fuss with cron?
[20:06] <sarnold> TheLordOfTime: yes, ntpd is preferred if you can use it
[20:07] <sarnold> TheLordOfTime: the discontinuous time jumps of ntpdate are best tolerated during early boot; e.g. select(2) timeouts can take longer or shorter than expected if ntpdate jumps the time around
[20:08] <TheLordOfTime> sarnold: ntpd should be fine for what I need.
[20:08] <sarnold> yay :) use that :)
[20:08] <TheLordOfTime> sarnold: purely curious, why is the package that provide ntpd called `ntp` and not `ntpd`?
[20:09] <rharper> smoser: I cleaned the dir out; it literally produces no output; I'm trying to just see what's happening; it doesn't appear that the ephemeral_script.py does any logging what so ever, so it's really hard to tell whats going wrong
[20:09] <sarnold> TheLordOfTime: guessing, because it provides multiple tools around the network time protocol, and not just the daemon..
[20:10] <TheLordOfTime> sarnold: looks like ntp, ntp-doc, and ntpdate are all part of the same source package, ntp.
[20:10]  * TheLordOfTime shrugs
[20:10] <TheLordOfTime> maybe you're right though
[20:11] <pmatulis_> TheLordOfTime: yeah, ntpd or openntpd don't work if the time discrepancy is too large (5 minutes?)
[20:11] <smoser> rharper, i haven't looked at it in a while.
[20:11] <smoser> that program has all sorts of improvements it could have.
[20:11] <rharper> smoser: hehe
[20:12] <smoser> i really suspect that it is finding a cache and thinks its "done"
[20:12] <TheLordOfTime> pmatulis_: so ntpdate before setting up ntpd is not a bad idea, then
[20:12]  * TheLordOfTime ran ntpdate prior to ntpd being installed, to grab the server data
[20:12] <TheLordOfTime> and to update the time :P
[20:13] <pmatulis_> TheLordOfTime: i've never had to do the cron job thing.  i've only had a problem when running a guest in virtualbox
[20:13] <pmatulis_> vmware too prolly
[20:14] <TheLordOfTime> pmatulis_: ah.  considering i have three servers I need the time to be accurate for (one for IRC logs for certain channels, one for bitcoin data timestamps to be accurate, and one for webserver logs to be accurate), I kinda need it updated, so ntpd should work for what I need
[20:14] <TheLordOfTime> i did use ntpdate to update the time first though, so maybe all shall be good
[20:15] <bekks> use ntpdate once, and ntpd afterwards.
[20:16] <bgardner> bekks: +1
[21:11] <semiosis> my launchpad karma doesnt count any PPA uploads in the last year, since Jan '13.  did something change so PPA uploads no longer add karma?
[21:11] <Pici> semiosis: You might want to ask in #launchpad (too)
[21:11] <semiosis> Pici: thx, I will
=== mjohnson15_2 is now known as mjohnson15