[00:20] <Rayfloyd> Hi everyone, I'm trying to install 12.04.2 LTS, however after the install finishes configuring DHCP, the install gui closes... Are the servers down and it doesn't tell me or is it something else? Thanks for the ehlp.
[00:28] <Patrickdk> gui?
[00:33] <Rayfloyd> well the install screen
[00:36] <sarnold> Rayfloyd: are there error messages that you can find anywhere? try looking through all the virtual consoles..
[00:37] <Rayfloyd> I had left the pc open since it disappeared, just checked back and it's back
[00:37] <Rayfloyd> odd
[02:29] <dassouki> what do you guys recommend to add an opensource application that helps me share documents with my staff as well as assign them task (online interface)
[02:38] <delinquentme> Ok so lets say i'm staring to build out prototype devices
[02:39] <delinquentme> and I want to automate configuration and setup ... includes sshing in, downloading files via github, specificiying branches
[02:40] <delinquentme> would this be a better use of puppet or just a shell script
[02:40] <delinquentme> I guess depends on the scale ?
[03:51] <nate15329> 13.04 64x server had powerloss & memory damage, hangs on pci_bus resource mem x28-xfcffffffffff; any ideas?
[03:52] <nate15329> i removed the damaged memory as well
[05:19] <nate15329> ok...i have a pci_root PNP0A03:00: fail to add MMConfig information and then it hangs on pci_bus resource mem
[05:49] <thomasbiege> hi
[08:02] <morph> can someon eplease help me with my body
[08:02] <morph> ive been taking vicodin for 1 56 year
[08:02] <morph> todayi started laughing outso ba
[08:02] <morph> but they were good
[08:03] <morph> i havent been asleep ainsce 10. slept for 1 hrs. got up at 12:30
[08:07] <babinlonston> morph:
[08:08] <morph> yo
[08:08] <morph> oh woops
[08:08] <morph> chatted that in the wrong channel
[08:08] <morph> sry
[08:11] <babinlonston> lol
[09:09] <lotia> greetings all. in upstart (specifally the version on 12.04 LTS), is it possible for the job to have a "reload" action that sends a specific signal to the process?
[09:10] <sgran> reload sends HUP
[09:10] <sgran> if you need something else, I don't see a way to change it
[10:10] <lotia> I'm looking at haproxy, which has a "reload" command
[10:10] <lotia> @sgran thanks
[12:33] <Koheleth> hardly surprising mysql updates this morning
[13:11] <banzounet> Hey guys to update phpmyadmin, what else should  I do besides moving the new folder?
[13:21] <pehden-> what should the server 12.04 kernel be?
[13:23] <andol> pehden-: That depends :) If you did a fresh install from a point you might have a backported kernel installed
[13:23] <andol> pehden-: Otherwise the regular 12.04 kernel would now be something like 3.2.0-49*
[13:24] <pehden-> 3.2.0-48-generic
[13:24] <pehden-> hmm
[13:25] <pehden-> it wont go past this one
[13:25] <pehden-> every update says its keeping this one back
[13:27] <ogra_> pehden-, do you use dist-upgrade (as you should for kernel upgrades) ?
[13:27] <ogra_> just "ugrade" wont work ...
[13:27] <ogra_> *up
[13:28] <pehden-> eee
[13:28] <pehden-> see i want to only use LTS
[13:28] <ogra_> (see the description of upgrade ad dist-upgrade in the apt manpage)
[13:28] <ogra_> nobody will stop you :)
[13:28] <JanC> somebody should give dist-upgrade another name  :)
[13:28] <ogra_> ++
[13:28] <ogra_> :)
[13:28] <Pici> !dist-upgrade
[13:28] <JanC> maybe an alias
[13:29] <pehden-> ahh ok
[13:29] <pehden-> apt-get dist-upgrade?
[13:29] <ogra_> yes
[13:29] <pehden-> ok
[13:29] <pehden-> wait is there a list of things removed before I do this
[13:30] <JanC> yes
[13:30] <pehden-> 3.2.0-48-generic #74-Ubuntu SMP Thu Jun 6 19:43:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
[13:30] <pehden-> is what I have now...
[13:30] <pehden-> anyone know the link right off?
[13:31] <JanC> link for what?
[13:31] <pehden-> the list
[13:31] <JanC> apt-get will show you
[13:31] <pehden-> ok
[13:31] <JanC> just like it shows what it's about to install, upgrade or hold back
[13:32] <pehden-> i only have ssh access to this server so I dont want to screw it up
[13:32] <JanC> most likely it will remove nothing
[13:32] <andol> pehden-: Feels like you could use a dev environment, where you can do a bit of safe testing :)
[13:32] <andol> pehden-: Something like a local virtual machine or something.
[13:32] <pehden-> maybe, but this server is live
[13:33] <pehden-> looks like its only upgradeing the kernel
[13:33] <JanC> you already upgraded the other packages with 'upgrade'
[13:34] <pehden-> exactly
[13:34] <JanC> which is a good idea BTW, to always do upgrade before dist-upgrade
[13:34] <pehden-> i made a script that i use to update everything at once but this command is not on there
[13:36] <JanC> best to check the results of every upgrade command anyway
[13:37] <pehden-> oh yea, figured that out the hard way  a year ago
[13:37] <pehden-> ran upgrade and it removed programs i used and replaced them with alternatives I was furious
[13:38] <pehden-> until i learned how to use the alternatives
[13:39] <JanC> what programs were that?
[13:39] <pehden-> i dont remember that much
[13:42] <pehden-> it just removed nvidia driver i think
[13:42] <pehden-> and virtualbox
[13:42] <JanC> that wasn't on a server, I suppose  :)
[13:42] <pehden-> it was
[13:42] <pehden-> both were
[13:43] <pehden-> from the original install
[13:43] <pehden-> its a desktop converted to a server
[14:03] <bobz_zg> anyone can help please. I have installed wordpress on nginx, user group www-data, and have created new ftp user and added user to group, but when I upload files over FTP client my wordpress cannot read files?
[15:00] <roaksoax> Daviey: o/! if you have a second could you please process the crmsh binary from the NEW queue?
[15:02] <Daviey> roaksoax: done
[15:02] <roaksoax> Daviey: awesome, thanks!!
[15:25] <smb> zul, hallyn: In case one of you feeling adventurous... chinstrap:~smb/4review/qemu+xen.debdiff (for Saucy) ;)
[15:31] <hallyn> smb: looking
[15:32] <smb> hallyn, It is a cherry-pick of three supposedly stable worthy changes on top of qemu to avoid it segfaulting when used for a PV Xen guest and libxl.
[15:33] <hallyn> smb: the cp of commit 62fc403f11523169eb4264de31279745f48e3ecc drops a lot of the original commit
[15:33] <hallyn> how come?
[15:33] <hallyn> oh no
[15:33] <hallyn> lol.  weird formatting on my screen confused me
[15:34] <hallyn> smb: +1
[15:34] <smb> Ah ok... I was not sure I had done something like this
[15:34] <smb> :)
[16:02] <thafreak> So, I upgraded my test lxc box to the newer 3.8 kernel from raring
[16:02] <thafreak> and now it's saying the memory controller cgroup is missing
[16:03] <thafreak> is there a work around? or should i go back to the quantal kernel?
[16:13] <jsonperl> Patrickdk/sarnold: I declare the issue fixed!
[16:13] <jsonperl> open files limit was the problem
[16:30] <redderhs> Hi, the link in this message is in regards to an Open Source Computing to further the developments of hardware for the mobile industry. It's time for Linux to be the #1 Consumer Operating System, Ubuntu Edge movement! http://pastebin.com/j57Dc29E  We can all make a difference for as little as One Dollar! Thank You for your time.
[16:47] <genii> Hm.
[16:48] <sarnold> jsonperl: great success!
[16:48] <jsonperl> totally… the relief I am feeling this friday is magical
[16:48] <jsonperl> thanks so much for the help
[16:48] <patdk-wk> :)
[16:48] <sarnold> man, I'm both glad and embarrassed it was something so much simpler than I feared..
[16:49] <jsonperl> same
[16:49] <patdk-wk> ya, normally that issue is easily solved, cause of error logging
[16:49] <jsonperl> I'm actually digging through logs some more to make sure I didn't miss anything
[16:49] <patdk-wk> atleast the memory *leak* was fixed though too
[16:50] <patdk-wk> and a few other scalability issues that haven't hit yet :)
[16:50] <jsonperl> Yea some great stuff happened here…
[16:50] <jsonperl> We're just getting rolling too… This is just the beginning of scaling issues ;)
[16:50] <jsonperl> I switched all machines to 64 bit after jemalloc magically fixed "the leak"
[16:50] <jsonperl> Also… btw… jemalloc NO LIKE 32 bit
[16:51] <patdk-wk> I have never used jemalloc on 32bit
[16:51] <patdk-wk> no wonder I never hit that issue
[16:51] <jsonperl> And you should not :D
[16:51] <jsonperl> I got random segfaults after running for a while
[16:52] <jsonperl> Yea really… NOTHING in the logs
[16:53] <patdk-wk> not suprised
[16:54] <patdk-wk> normally issues like this is what drive poeple to worry about spending time to add them
[16:55] <jsonperl> Found some good articles about tweaks for scaling
[16:55] <jsonperl> One from urban airship about 500,000 concurrents! http://urbanairship.com/blog/2010/09/29/linux-kernel-tuning-for-c500k/
[17:09] <sarnold> hah, nice, when c10k is just too damned cute :)
[17:10] <jsonperl> now THAT is some serious scale
[17:12] <sarnold> wow, their guide has -way- less in it than used to be necessary for scaling out to even 1/100th that load.
[17:12] <sarnold> and their advice for limits is just plain wrong ;) hehe
[17:13] <jsonperl> which ones do you feel are wrong
[17:14] <sarnold> jsonperl: you found out the other day that limits.conf is only used if the user's processes are started via the PAM stack somehow, which isn't terribly likely for production servers..
[17:15] <sarnold> granted, I think they knew that they didn't know what they were doing with the caveat about "look at the manpage" but not say -which- of the myriad manpages would be enlightening. :)
[17:15] <jsonperl> correct… so obviously that one was way off!
[17:15] <sarnold> jsonperl: did you set your maximum socket buffers to 16MB as well?
[17:15] <jsonperl> yep :/
[17:16] <sarnold> jsonperl: give this a skim and then consider dropping it :)  http://en.wikipedia.org/wiki/Buffer_bloat
[17:16] <jsonperl> net.ipv4.tcp_rmem = 4096 4096 16777216; net.ipv4.tcp_wmem = 4096 4096 16777216
[17:16] <jsonperl> k
[17:16] <jsonperl> what do you think are more sain levels?
[17:16] <jsonperl> sane
[17:16] <sarnold> 16M might be fair enough for locally connected gigabit or huge latency fat pipes (transatlantic? transpacific?)
[17:17] <sarnold> jsonperl: probably 512K or so.
[17:17] <jsonperl> We certainly get some pretty latent connections… but not THAT much data
[17:17] <jsonperl> maybe 2k/s
[17:18] <jsonperl> so more like 4096 4096 524288
[17:20] <jsonperl> Looks like the default is 4096	87380	6291456
[17:21] <sarnold> that seems pretty sane. how many connections will you have? multiply that by the middle number and hopefully it'll still be reasonable..
[17:23] <jsonperl> We're really not looking for more tha 400 or so concurrent per machine
[17:23] <jsonperl> At that point we'll start to see cpus chuggin
[17:46] <patdk-wk> ya, I only use 256 to 1meg on mine
[17:46] <sarnold> patdk-wk: maximum or default?
[17:47] <patdk-wk> max
[17:48] <sarnold> cool, thanks :)
[17:48] <patdk-wk> now, I did adjust my tc rules for outgoing though :)
[17:49] <patdk-wk> if more than 10 packets are waiting to go out, 11+ get dropped
[17:49] <patdk-wk> so doubt I ever hit that limit anymore :)
[17:49] <sarnold> haha
[17:49] <patdk-wk> ya, used to really annoy me
[17:49] <sarnold> tc has been on my todo list for a decade now..
[17:49] <patdk-wk> scp transfer done, and then wait 5min for the buffer to flish
[17:49] <patdk-wk> flush
[17:50] <patdk-wk> it's limited 10 per class
[17:51] <patdk-wk> also figured out how to proplerly match my *prenat* ip's so they match correctly in outgoing
[17:51] <patdk-wk> that really fixed my ruleset I had made
[20:46] <soren> Does anyone happen to know if restarting iscsid will cause existing connections to be dropped?
[20:47] <patdk-wk> defently, why wouldn't it?
[20:48] <pdevine> users love it when storage goes away
[20:48] <patdk-wk> well, that shouldn't cause a user an issue
[20:48] <soren> patdk-wk: Because the iscsi daemon is just provides the control plane.
[20:48] <patdk-wk> as it should auto-reconnect
[20:49] <soren> patdk-wk: The kernel itself provides the data plane.
[20:49] <streulma> hello what is errors=remount-ro in /etc/fstab?
[20:49] <soren> patdk-wk: So it should necessarily cause the connections to be dropped.
[20:49] <patdk-wk> soren, never been my experience
[20:49] <patdk-wk> always dropped when I restarted
[20:49] <soren> patdk-wk: Ok, thanks.
[20:49] <patdk-wk> had to use the command thing to adjust it, if I didn't want to restart to drop it
[20:49] <patdk-wk> but this might have changed
[20:50] <soren> patdk-wk: I'm not saying they won't, I'm just responding to your "why wouldn't it".
[20:50] <patdk-wk> considering the this is from 8.04 :)
[20:51] <soren> streulma: It tells the kernel what to do in case of errors.
[20:51] <soren> streulma: remount-ro means "remount the filesystem as read-only".
[20:51] <streulma> soren: on boot or on running?
[20:51] <patdk-wk> as in, disk went missing, unable to read from disk, writes failing to disk, ...
[20:51] <patdk-wk> anytime
[20:52] <patdk-wk> if you yank the disk out, it will take 30seconds, then go ro mode
[20:52] <soren> streulma: Other options: "continue" (pretend like nothing happened) and "panic" (make the entire system fall over)
[20:52] <soren> streulma: Running.
[20:52] <pdevine> what is /var/lib/dpkg/cmethopt used for?
[20:52] <pdevine> s/^/does anyone know/
[20:53] <pdevine> I'm going through debootstrap and was just curious
[20:53] <soren> pdevine: IIRC, it's a config file for dselect.
[20:56] <pdevine> I love peeling the onion back on this stuff.  it's like an archeological expedition
[20:59] <pdevine> I discovered the other day that dpkg can't handle pre-depends correctly.. and today discovered a comment in debootstrap complaining about how dpkg doesn't handle pre-depends
[21:00] <pdevine> I wish I'd known that last week.  :-D
[23:00] <nate15329> my server gets stuck at here time to time any ideas? http://pastebin.ubuntu.com/5916517/
[23:04] <mic_> nate15329: did you do the usual suspect removal?
[23:04] <mic_> nate15329: aka noacpi acpi=off
[23:04] <mic_> ?
[23:04] <mic_> also which kernel is there?
[23:07] <nate15329> 3.8.0-26-generic; i tried removing my pci-x sata card recently; but no change...weird part is that it hangs there even in recovery mode, but in normal mode this sometimes happens
[23:09] <nate15329> ill try the noacpi & acpi=off on next boot; i got it up temporary for a quick backup
[23:10] <mic_> another option would be to go for a different kernel
[23:10] <mic_> pick something from the lower shelf.
[23:10] <nate15329> tried that as well...the one below it
[23:10] <mic_> is it some ancient hardware?
[23:10] <nate15329> which i think is 3.8.0-18 or so
[23:10] <mic_> commodity or server?
[23:10] <mic_> nate15329: by lower shelf I was thinking like reaaaaally lower ;)
[23:11] <nate15329> server 13.04 hp dl385 g1...old hardware indeed
[23:11] <mic_> nate15329: 3.x & 2.6.x
[23:11] <mic_> G1?
[23:11] <mic_> a bit old, indeed.
[23:11] <nate15329> lol yep g1
[23:12] <mic_> acpi and HPET if available
[23:12] <mic_> disable and check
[23:12] <mic_> and with such hardware - go lower with kernels
[23:12] <mic_> and as I wrote - seriously lower ;)
[23:12] <nate15329> does older kernels support sata II drives?
[23:13] <mic_> no problem
[23:14] <nate15329> ok how would i install 2.6.x kernels on 13.04 xD
[23:15] <mic_> I haven't tried 13.04
[23:15] <mic_> I did downgrade 12.04.02 once from 3.5 to 3.2
[23:15] <sarnold> nate15329: try booting a lucid livecd on it first or something similar, make sure it works at all..
[23:16] <mic_> yes, that's a sane suggstion
[23:16] <mic_> (sorry, I am up at work for 14 hours now ;)
[23:18] <sarnold> oh that's trouble :)
[23:18] <sarnold> ;q
[23:22] <nate15329> ah yeah i will...mostly i perfer running the latest though xD