[02:13] <neonixcoder> Hay Arnold. The issue is number of max connection limit
[02:13] <neonixcoder> Our hosts reached that value.
[02:13] <sarnold> neonixcoder: ah! :)
[02:13] <sarnold> fun
[02:13] <neonixcoder> Now I increased that count and it is working fine now..
[02:48] <nameuser_> I'm looking for an easy way to do full server backup. Something like Macrium Reflect ( http://www.macrium.com/reflectfree.aspx)
[02:49] <nameuser_> I know Clonezilla, but it requires the system to reboot
[02:50] <nameuser_> Rsnapshot is more for backing up files
[03:00] <patdk-lap> duplicity :)
[03:00] <patdk-lap> or if you want to go the payed route, acronis
[03:44] <Logos01> nameuser_: bacula.
[03:44] <Logos01> rsnapshot can do the job, but bacula is a very robust enterprise-ready fully OSS backup engine.
[03:44] <Logos01> (And it's block-level)
[03:46] <nameuser_> Thank you!
[04:32] <nameuser_1> Just bought a SSD for my self hosted web server. Expected a huge i
[04:32] <nameuser_1> Expected a hugh improvement
[04:33] <nameuser_1> But disappointed
[04:35] <patdk-lap> heh?
[04:35] <patdk-lap> why?
[04:36] <nameuser_1> Except when installing or backup/restore server, the postgresql query speed doesn't seem to improve mouch
[04:37] <patdk-lap> and you tested that disk speed was the problem?
[04:37] <nameuser_1> Test disk speed with hdparm and dd
[04:37] <patdk-lap> heh?
[04:37] <nameuser_1> The ssd is fine
[04:38] <patdk-lap> what does those have to do with anything?
[04:38] <patdk-lap> hdparm doesn't do anything
[04:38] <patdk-lap> and dd doesn't test anything, that has to do with sql
[04:38] <patdk-lap> and on an ssd, dd really is horrid
[04:38] <nameuser_1> so give me some tips then
[04:39] <patdk-lap> instead of doing a streaming test, using dd, with all 0's
[04:39] <patdk-lap> do a test that is correct for your usage
[04:39] <patdk-lap> what that is, I dunno, that depends on your usage
[04:39] <patdk-lap> first, ask postgresql what the problem is
[04:39] <patdk-lap> I dunno postgresql, but it's simple enough in mysql
[04:39] <patdk-lap> if you have cpu issue, locking issues, disk issues, ...
[04:42] <nameuser_1> Yea
[10:52] <znf> Hi
[10:52] <znf> Doesn't ubuntu-server have a way to finish a install over ssh?
[11:47] <asheesh_> Need some help with openstack single install on an Ubuntu server using Juju
[11:52] <asheesh_> The installer is waiting for creating some machines for 4 hours now
[13:22] <theptr> Is it a good idea to run an ms active directory on ubuntu 14.04 with samba ?
[13:44] <patdk-wk> theptr, never had that work, good enough, personally
[13:45] <theptr> patdk-wk, I want to keep as many as possible linux so
[13:46] <patdk-wk> you asked my thoughts, I gave them, now you want to say they are invalid?
[13:58] <rbasak> hallyn, stgraber: is lxc on vivid trying to run a xenial container known to be broken? Wily works, but Xenial doesn't. I see an init process with a bunch of subprocess zombies and nothing else. I also see an apparmor denial but I think I get that in the success case with wily too.
[13:58] <rbasak> audit: type=1400 audit(1450447067.190:28): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default" name="/" pid=18303 comm="systemd-machine" flags="rw, rslave"
[13:59] <rbasak> Using lxc-start-ephemeral.
[14:16] <ifohancroft> Hello, guys. I am having trouble creating a software RAID 0 on Ubuntu Server 14.04.3 x86_64 using two discs (/dev/sdb and /dev/sdc) using mdadm
[14:18] <ifohancroft> I've created it using mdadm --create /dev/md0 --level=raid0 --raid-devices=2 /dev/sdb /dev/sdc
[14:19] <ifohancroft> Then I've created folder 'storage' (without the quotes) in / then I've put in fstab Then I've put this in /etc/fstab /dev/md0 /storage ext4 defaults 0 0
[14:19] <ifohancroft> Then I rebooted and after grub times expires and ubuntu loads i pretty much get a black screen
[14:20] <patdk-wk> well, that isn't going to work
[14:20] <patdk-wk> you never told mdadm to *mount* your raid
[14:20] <ifohancroft> How to do that?
[14:22] <patdk-wk> mdadm --detail --scan >> /etc/mdadm/mdadm.conf
[14:23] <ifohancroft> I will execute that in a minute, as soon as the server boots (well from recovery console)
[14:27] <ifohancroft> btw I've manually put lines in mdadm.conf now I executed the command and will check the conf
[14:27] <ifohancroft> well it looks the same
[14:27] <ifohancroft> first line: DEVICE /dev/sd[bc]
[14:28] <ifohancroft> second line: ARRAY /dev/md0 devices=/dev/sdb,/dev/sdc
[14:31] <patdk-wk> that is strange
[14:31] <patdk-wk> it doesn't do something like, ARRAY /dev/md0 UUID=xxxxx
[14:31] <patdk-wk> generally, depending on the drives to be called the correct letters, is a horrible thing to depend on
[14:32] <patdk-wk> such as, replacing a disk, adding a disk, or even installing a new hba
[14:32] <patdk-wk> will cause that all to get changed
[14:32] <patdk-wk> a disk failing
[14:33] <ifohancroft> actually i think for some reason it's not writing in the conf
[14:33] <ifohancroft> i just checked
[14:33] <ifohancroft> i deleted it and executed the command again and the conf was empty
[14:33] <ifohancroft> also i don't think it was created after i installed mdadm and created it manually
[14:34] <ifohancroft> mdadm after being installed mentionend mdamd.cf maybe its conf is somewhere else?
[14:35] <patdk-wk> it's not
[14:35] <patdk-wk> I have a few systems, including this one I'm on now, using 14.04.3 with mdadm
[14:36] <ifohancroft> so maybe if I change it to use UUID? however which UUID is that of which drive or of what and how do i find it?
[14:36] <patdk-wk> first I would comment out DEVICE line
[14:36] <patdk-wk> blkid will give you the UUID
[14:37] <patdk-wk> hmm, it will give it in a different format though
[14:37] <patdk-wk> what does mdadm -Es, give you?
[14:38] <ifohancroft> oh awesome it gives me the UUID and stuff of /dev/md0
[14:38] <ifohancroft> it gives:
[14:38] <patdk-wk> you do NOT want the uuid of md0
[14:38] <ifohancroft> ARRAY /dev/md/0 metadata=1.2 UUID=uu:id:etc name=os1.0
[14:38] <patdk-wk> unless your putting it into /etc/fstab
[14:38] <ifohancroft> name=os1:0 i mean
[14:39] <patdk-wk> no, that iline is good
[14:39] <patdk-wk> I meant blkid one
[14:39] <patdk-wk> from blkid:  /dev/md0: UUID="626a5a92-b783-44ff-8a7d-a0236287892f" TYPE="ext4"
[14:39] <ifohancroft> should I put the uuid in fstab instead of '/dev/md0'
[14:39] <patdk-wk> that UUID is of the ext4 filesystem installed ON md0 :)
[14:39] <patdk-wk> that is optional, but generally better
[14:39] <ifohancroft> well it doesn'ty give me uuid of md0
[14:39] <ifohancroft> blkid i mean
[14:39] <patdk-wk> incase md0 is called something else, but not *as* likely to happen
[14:40] <patdk-wk> is md0 started/assymbled?
[14:40] <patdk-wk> did you format it with a filesystem yet?
[14:40] <ifohancroft> maybe i should not put it in fstab as /dev/md0 but as /dev/md/0?
[14:40] <ifohancroft> the md0?
[14:40] <ifohancroft> let me check
[14:40] <patdk-wk> ya
[14:41] <ifohancroft> fdisk can't find it
[14:41] <patdk-wk> fdisk finds partitions
[14:41] <patdk-wk> did you put a partition on md0?
[14:41] <ifohancroft> i don't think i did though (stupid tutorials on the web, show you how to do something and what to do but not how)
[14:41] <patdk-wk> I never do
[14:41] <ifohancroft> i don't think i have
[14:41] <ifohancroft> but not why i mean
[14:41] <patdk-wk> you are not suppose to use tutorials
[14:42] <patdk-wk> a tutorial is notes someone created for their usage
[14:42] <patdk-wk> documentation is created to explain to others
[14:42] <ifohancroft> good point, thank you (didn't know that to be honest)
[14:42] <patdk-wk> so a tutorial/blog/... is only useful if you already know how to use something
[14:42] <ifohancroft> btw atm mdadm --detail /dev/md0 gives me mdadm: cannot open /dev/md0 no such file or directory
[14:42] <patdk-wk> well, that is cause most poeple advertize it wrong :)
[14:43] <patdk-wk> they make a tutorial thinking to help other people
[14:43] <patdk-wk> forgetting to put in all their *thoughts* on why they did any of it
[14:44] <ifohancroft> i guess the raid is not created atm because i executed mdadm --create /dev/md0 --level=raid0 --raid-devices=0 /dev/sdb /dev/sdc and it asks me to create it again
[14:44] <ifohancroft> says they appear to be part of a raid array and that partition table exists there etc and asks to continue the array creation
[14:45] <ifohancroft> at this point how should I proceed into creating the array, making it stick after reboot and making it auto-mount on boot etc
[14:46] <ifohancroft> create it, check the uuid, put it in mdadm.conf then reboot?
[14:46] <rbasak> hallyn, stgraber: fyi, upgrading to wily fixed the issue. I can start xenial containers now. I don't know if that's due to a side effect of the upgrade or an actual package version difference though.
[14:52] <ifohancroft> patdk-lap: I created the raid again, used the command to make mdadm put stuff in its conf, cleared the conf from my stuff so only what it put in there stays in there, saved it, rebooted and pretty much the same thing (a black screen)
[14:53] <patdk-wk> I think your having a different issue
[14:53] <patdk-wk> and don't think mdadm is the problem :(
[14:56] <ifohancroft> I will boot into recovery console and check if the raid is up and running, if it is i will try to find what else might be the problem, if not, I will try to get it to work and then see if the problem presists
[14:59] <patdk-wk> at this point
[15:00] <patdk-wk> I would just remove mdadm.conf and your line from fstab (thought shouldn't be needed)
[15:00] <patdk-wk> even with it failing, it should not give you a blank screen
[15:01] <ifohancroft> ok, I removed them and am now rebooting to see what will happen
[15:04] <ifohancroft> yeah, still the same, let me try few things
[15:07] <ifohancroft> without the drives inside, it's booting and even the grub timeout time (you know the time after which the chosen option will be auto loaded )
[15:07] <ifohancroft> but that is probably because of less drives and because the only drive now inside is an ssd on which is the os
[15:07] <ifohancroft> also i think with the drives formated and without partitions it can also boot
[15:08] <ifohancroft> i will try to erase them and try to boot with them inside
[15:10] <ifohancroft> before I start creating the raid should i have some partition on the drives and any flags set?
[15:10] <ifohancroft> or should i keep them as unallocated space
[15:13] <patdk-wk> optional
[15:14] <patdk-wk> generally it can be a good idea to create a parition, and use that parition to mdadm
[15:14] <ifohancroft> I think the problem now may have been that the raid was still running, I stopped it now and rebooted now we will see
[15:14] <patdk-wk> just so you don't accidently think it's a blank disk and create a partition on it later, wiping it
[15:15] <ifohancroft> so create ext4 on each then create raid then I guess I should create a partition on /dev/md0 then mount it?
[15:15] <patdk-wk> flags are completely useless these days, really
[15:15] <patdk-wk> dunno what you mean by create ext4
[15:15] <ifohancroft> btw yes, now that the raid is stopped (using sudo mdadm --stop /dev/md0 and sudo mdadm --zero-superblock /dev/sdX... for each drive)
[15:15] <patdk-wk> disk, partition, mdadm on partition, ext4/... on md
[15:16] <ifohancroft> i mean create ext4 partition
[15:16] <patdk-wk> why?
[15:16] <patdk-wk> there is no such thing as an ext4 partition
[15:16] <ifohancroft> didn't you mean that is a good idea to do so i don't think the disk is empty?
[15:16] <ifohancroft> ah yeah it's a filesystem
[15:16] <ifohancroft> so i guess i didn't realize there is a difference between a partition and filesystem
[15:17] <ifohancroft> so i am starting from scratch now in creating the raid, what is the first thing i should do?
[15:17] <patdk-wk> the filesystem type in the partition table is also mostly useless
[15:17] <jrwren> one of those important subtle distinctions
[15:17] <patdk-wk> normally set to 83 == linux filesystem
[15:17] <patdk-wk> but it is mdadm, not linux filesystem
[15:17] <patdk-wk> so generally fd is perferred
[15:17] <patdk-wk> mdadm auto mount
[15:17] <patdk-wk> fd  Linux raid auto
[15:18] <patdk-wk>    Device Boot      Start         End      Blocks   Id  System
[15:18] <patdk-wk> /dev/sda1            2048   128901119    64449536   fd  Linux raid autodetect
[15:19] <ifohancroft> so I should operate on /dev/sdb1 not /dev/sdb?
[15:19] <ifohancroft> or?
[15:19] <patdk-wk> optional, but most people expect partition table to exist
[15:19] <patdk-wk> so if it does, you can future protect yourself
[15:19] <patdk-wk> but it's strictly not needed
[15:20] <patdk-wk> I used to never use partitions
[15:20] <ifohancroft> ok now I have /dev/sdb1 start 2048 End 1953525167 Blocks 976761560 ID 83 System Linux
[15:20] <patdk-wk> then I found several *utilities* they kept wiping out my drives that didn't have partitions, really upset me
[15:20] <ifohancroft> lol
[15:20] <ifohancroft> so your point about creating a partition is a very good one
[15:20] <patdk-wk> oh? you have an uninitialized disk, let me fix that for you!
[15:21] <ifohancroft> :D
[15:22] <ifohancroft> how did you set Linux raid autodetect to your drive and does it matter if it's just Linux or Linux raid autodetec or is this just a comment to the partition?
[15:22] <patdk-wk> it doesn't matter what it is
[15:22] <ifohancroft> ah yeah I found it
[15:22] <patdk-wk> but I think mdadm checks it
[15:22] <ifohancroft> the id
[15:24] <ifohancroft> ok so what should I do next? Create raid with mdadm -C /dev/md0 --level=raid0 --raid-devices=2 /dev/sdb1 /dev/sdc1 ?
[15:25] <patdk-wk> sure
[15:26] <ifohancroft> Ok it is created. Now I should make mdadm put the conf for the array in its conf?
[15:26] <patdk-wk> yes
[15:26] <patdk-wk> post that line here too
[15:26] <ifohancroft> mdadm --detail --scan >> /etc/mdadm/mdadm.conf
[15:26] <patdk-wk> well, I meant of the line added to mdadm.conf
[15:27] <ifohancroft> ah :D
[15:27] <ifohancroft> ARRAY /dev/md0 metadata=1.2 name=os1:0 UUID=700:long:etc
[15:27] <patdk-wk> ok
[15:27] <patdk-wk> that looks good
[15:28] <patdk-wk> blkid has stuff
[15:28] <ifohancroft> so I should check blkid now?
[15:28] <patdk-wk> should show linux_raid_member lines
[15:28] <ifohancroft> well it shows /dev/sdb1, /dev/sda1, /dev/sda3, /dev/sda4 and /dev/sdc1 (no /dev/md0)
[15:29] <patdk-wk> yes
[15:29] <ifohancroft> on both /dev/sdb1 and /dev/sdc1 it says that its TTYPE is linux_raid_member
[15:29] <patdk-wk> mdadm --assymble
[15:29] <ifohancroft> mdadm --assemble?
[15:29] <patdk-wk> probably
[15:29] <patdk-wk> english was my first language
[15:29] <ifohancroft> :D
[15:30] <ifohancroft> it says an md device must be given in this mode
[15:30] <ifohancroft> so mdadm --asemble /dev/md0?
[15:31] <ifohancroft> (btw i will go for a cigarette)
[15:31] <patdk-wk> ah
[15:31] <patdk-wk> mdadm --assemble --scan
[15:35] <ifohancroft> back and ok
[15:35] <ifohancroft> done
[15:36] <patdk-wk> now blkid shows md0?
[15:36] <patdk-wk> or it might not
[15:36] <patdk-wk> but md0 exists now right?
[15:36] <patdk-wk> probably best to, cat /proc/mdstat
[15:37] <ifohancroft> yes, it doesn't show md0 and yes catting /proc/mdstat shows md0:active raid0 sdc1[1] sdb1[0]
[15:37] <patdk-wk> ok, time to mkfs.ext4 /dev/md0 ....
[15:38] <ifohancroft> done
[15:38] <patdk-wk> blkid
[15:38] <patdk-wk> add to /etc/fstab using the UUID
[15:38] <ifohancroft> yes it now shows UUID
[15:38] <ifohancroft> of md0
[15:41] <ifohancroft> defaults for options and 0 0 for dump and pass?
[15:42] <patdk-wk> well, likely 1 or 2 for pass
[15:42] <patdk-wk> but it shouldn't matter much
[15:43] <ifohancroft> ok i put 1 like on /
[15:43] <ifohancroft> so now in theory it's all done and a reboot follows?
[15:43] <patdk-wk> yes
[15:43] <patdk-wk> since you don't need it in initramfs
[15:44] <patdk-wk> as it's not a boot/root drive
[15:44] <ifohancroft> ok, time to pray to the server :D
[15:48] <ifohancroft> It works! Thank you so much dude! I will write the stuff down and look at documentation to fill in the gaps (learn the stuff I now figured out I don't know)
[15:48] <ifohancroft> btw as my user I don't have write permission on there atm, did I not mount it well or it's normal
[15:48] <ifohancroft> I mean I didn't mount it as read only or something?
[15:48] <patdk-wk> dunno
[15:48] <patdk-wk> but you didn't setup permissions
[15:48] <patdk-wk> so likely only root has write access
[15:48] <ifohancroft> well I can write as root
[15:49] <ifohancroft> if it was read write I won't be able to write even as root, right?
[15:49] <patdk-wk> yes
[15:49] <ifohancroft> Thank you very much!
[15:49] <ifohancroft> I should really start like right now to see what I don't know much about or don't understand and fill in the gaps
[16:18] <capoderra> hello, all. I've just install ubuntu server and the top and left portions lay off screen so I am having a hard time configuring files.
[16:18] <capoderra> xrandr only works in GUI
[16:18] <capoderra> I've tried fbset, but I can't get it to change my resolution
[16:19] <capoderra> i've tried fbset -xres=1360 -yres=850, but that outputs the usage for fbset
[16:20] <capoderra> this last command supposedly worked for somebody, but it doesn't work for me, even with the same version of fbset
[16:42] <teward> capoderra: have your monitor autoconfigure
[16:53] <stgraber> rbasak: well, that's pretty odd seeing how lxc is identical in vivid and wily (exact same source)
[16:54] <stgraber> rbasak: the behavior you describe sounds like a broken or crashed lxcfs though
[16:54] <capoderra> teward, sorry, it's a TV connected via HDMI
[16:55] <teward> capoderra: oh.  I typically see HDMI TVs cut off things, and I never found a way to resolve it, server or otherwise
[16:55] <teward> (TVs aren't the best for that stuff)
[16:56] <ogra_> capoderra, find the "overscan" option in your TV settings menu ... and toggle it
[16:56] <capoderra> teward, it's all I got. It's funny, I never had that problem on my old machine.
[16:56] <davidic657> Hi guys, had a server with hetzner for a while now and never seem to get kernel updates, just the kernel dev, Ubuntu 12.04.5 its currently at Linux 3.11.0-26-generic on x86_64 is this normal?  I ticket hetzner and they just said they have nothing to do with software etc as usual
[16:57] <capoderra> ogra_, I don't think I have that
[16:57] <ogra_> it might be named differently ... but it should be there ... TVs that dont have it are rare
[16:58] <capoderra> teward, the old machine used a VGA cable. This one has to be HDMI because it doesn't have a vga port
[16:59] <davidic657> anyone tell me what the current kernel should be for Ubuntu 12.04.5 64 bit server should be please
[17:00] <davidic657> Do not understand why I do not get main kernel updates, just the dev updates
[17:01] <ogra_> davidic657, https://launchpad.net/ubuntu/+source/linux
[17:01] <ogra_> (scroll to the bottom)
[17:01] <davidic657> ty
[17:04] <davidic657> ogra_:  hetzner wont answer me why it does not upgrade?
[17:04] <ogra_> upgrade from what to what ?
[17:05] <ogra_> the latest kernel in precise is obviously  3.2.0-96.136  ...
[17:06] <davidic657> ogra_: says Linux 3.11.0-26-generic on x86_64 here
[17:06] <davidic657> sry bit confused here
[17:06] <quantic> likely installed a hwe kernel.
[17:06] <ogra_> 3.11 ?
[17:06] <ogra_> well, hwe kernels come from other LTS releases
[17:06] <davidic657> quantic: all I get is the dev updates
[17:06] <ogra_> there is no 3.11 in either of them
[17:07] <ogra_> the hwe kernel for 14.04 would be 3.14 based
[17:07] <quantic> 3.11 is the kernel from saucy.
[17:07] <davidic657> not sure what they are up to
[17:07] <quantic> 12.04 has an hwe kernel that's 3.11. 12.04.4, I believe.
[17:07] <ogra_> yeah, that looks like a broken release upgrade
[17:08] <quantic> ogra_: not necessarily.
[17:08] <quantic> https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2BAC8-Support.A12.04.x_Ubuntu_Kernel_Support
[17:08] <davidic657> just want to know if the kernel is ok and no security problem, never get any updates
[17:09] <davidic657> thanks guys for the input
[17:09] <quantic> davidic657: install the "linux-generic-lts-trusty" package.
[17:09] <quantic> davidic657: And review https://wiki.ubuntu.com/Kernel/LTSEnablementStack
[17:09] <davidic657> noob here proberbly mess everything up :)
[17:10] <davidic657> should be ok fingers crossed
[17:10] <ogra_> yeah, what quantic said "linux-generic-lts-trusty" should get you 3.13
[17:10] <quantic> davidic657: Just install a single package, it will pull in the currently-supported kernel.
[17:11] <davidic657> thanks
[17:26] <rbasak> stgraber: I think that's reasonably consistent with what I've seen. If the latest SRU is broken but the release pocket works in both Wily and Vivid, then that is consistent with my observations.
[17:26] <rbasak> stgraber: I only upgraded in Wily to work around a different bug.
[17:41] <stgraber> rbasak: except that we also use the exact same lxc source in xenial as wily and vivid (1.1.5 + 2 bugfix uploads for all 3)
[17:42] <stgraber> rbasak: anyway, the symptoms point towards lxcfs (as mentioned in the bug), hopefully hallyn can take a look when he's back
[17:42] <rbasak> That makes sense. Thanks.
[19:11] <capoderra> is anybody familiar with fail2ban? Do I need it if I'm going connecting to my server from my local network?
[19:12] <patdk-wk> nothing
[19:12] <patdk-wk> except if you are in a habbit if not using the right password, you might want to add yourself to the exceptions
[19:12] <patdk-wk> or adjust what it blocks, to only block external
[19:13] <patdk-wk> or add a firewall rule that overrides fail2ban rules
[19:13] <patdk-wk> so many things you can do
[19:13] <capoderra> wait wait
[19:13] <capoderra> ok, fail2ban, as I understand, prevents brute force attempts to crack ssh password... but if I'm going to only connect to my server from another computer on the same local network, do I need fail2ban?
[19:14] <capoderra> What i'm saying is..
[19:14] <capoderra> my server is not facing the wide open internet
[19:14] <genii> capoderra: If the ssh port is not forwarded at the router from the internet at alrge to that machine, you're pretty safe without it
[19:14] <patdk-wk> it protects against attacks that it is programmed to notice
[19:14] <genii> *large
[19:15] <patdk-wk> if the attacks cannot attack your server, why do you care?
[19:15] <capoderra> genii, that's what I was thinking
[19:15] <capoderra> patdk-wk, I'm not a security expert, so I just wanted to confirm my assumptoins
[19:16] <patdk-wk> well, it doesn't help to have an extra layer
[19:16] <patdk-wk> just incase someone opens it up later
[19:16] <patdk-wk> or someone attacks it on the local network (though probably easier ways to do it)
[19:16] <patdk-wk> but strictly, if what you say is true, it's not required
[19:17] <capoderra> ok, thanks so much
[19:17] <patdk-wk> and it's really not for security too much
[19:17] <patdk-wk> though it can help slow down brute force attempts
[19:19] <capoderra> I have another question. In my /etc/ssh/sshd_config file, there is a %h before the pathway to my authorized_keys... what is that?
[19:24] <quantic> capoderra: Thats a shorthand for the user's home directory. I.e. the authorized keys file for each user is located in that path relative to the users home directory.
[19:25] <capoderra> got it
[19:41] <jarkinox> how can I make ubuntu server detect and mount my external drive on reboot?
[19:41] <jarkinox> i have to unplug/plug every time
[19:45] <Synthead> jarkinox: what do you have now?
[20:00] <jarkinox> Synthead what do you mean?
[20:12] <Synthead> jarkinox: how are you mounting it?  Do you have any /etc/fstab or auto-mount settings?  What do you mean by "have to unplug/plug"?  When you do that, what happens?
[20:19] <jarkinox> fdisk -l doesn’t even show the drive after reboot
[20:19] <jarkinox> i unplug the harddrive, and then it shows up
[20:37] <jarkinox> Synthead ^
[22:50] <Synthead> jarkinox: is there any kind of error in the ring buffer (dmesg) about the drive after the server is booted with it plugged in?
[22:50] <Synthead> jarkinox: is it usb?
[23:00] <Synthead> jarkinox: what make/model of the drive?  if it's usb, what does it show in lsusb?
[23:32] <jarkinox> Synthead: It is usb
[23:32] <jarkinox> it’s a western digital 3tb drive
[23:32] <jarkinox> let me check on those other items you asked for
[23:32] <Synthead> jarkinox: a lot of hard drives hang a while as they spin up
[23:33] <Synthead> jarkinox: maybe it's timing out as it's being queried by some means?
[23:33] <jarkinox> what am i looking for in dmesg?  there’s a lot there.  can you give me a grep command?
[23:34] <Synthead> jarkinox: might check lsusb first and grep for its description
[23:34] <Synthead> jarkinox: perhaps grep for /dev/sd ?
[23:34] <Synthead> jarkinox: I recommend dmesg | less and just / to try to look for it
[23:35] <Synthead> -i (without /) toggles case sensitivity
[23:36] <jarkinox> jarkinox@Ubuntu:~$ lsusb
[23:36] <jarkinox> Bus 001 Device 002: ID 0480:a003 Toshiba America Info. Systems, Inc.
[23:36] <jarkinox> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[23:36] <jarkinox> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[23:36] <jarkinox> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[23:36] <jarkinox> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[23:36] <jarkinox> not in there
[23:36] <Synthead> jarkinox: is your drive plugged in?
[23:36] <jarkinox> yup
[23:36] <Synthead> jarkinox: are you able to use it?
[23:36] <jarkinox> yes, but after a reboot, i need to physically remove the usb and plug it back in
[23:36] <jarkinox> then it’s detected
[23:37] <Synthead> jarkinox: what does lsusb say when you unplug it, then plug it back in?
[23:37] <Synthead> by the way, is this drive going to be permanently installed on this box?
[23:37] <jarkinox> Bus 001 Device 007: ID 1058:1230 Western Digital Technologies, Inc.
[23:37] <jarkinox> Bus 001 Device 002: ID 0480:a003 Toshiba America Info. Systems, Inc.
[23:37] <jarkinox> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[23:37] <jarkinox> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[23:37] <jarkinox> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[23:38] <jarkinox> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[23:38] <jarkinox> yes, permanently on the box
[23:38] <Synthead> jarkinox: you might seriously reconsider using it via the usb enclosure
[23:38] <Synthead> jarkinox: there's is almost always a data drive inside
[23:38] <Synthead> sata*
[23:38] <jarkinox> what does that mean?
[23:39] <Synthead> jarkinox: if you remove the drive from the enclosure and plug it directly into your motherboard with sata, not only will you circumvent this issue, but you'll have an enormous speed improvement
[23:39] <Synthead> jarkinox: usb 2 or 3?
[23:39] <jarkinox> ok now there’s something in dmesg
[23:39] <jarkinox> can i paste a bunch of lines without it looking like spam?
[23:39] <Synthead> jarkinox: pastie.org
[23:39] <jarkinox> it’s usb 3 on a very old Dell box
[23:39] <Synthead> usb 3 isn't so bad
[23:40] <Synthead> jarkinox: does the dell box have usb 3 as well?
[23:40] <jarkinox> http://pastie.org/private/uvsblr2ncn5nubgzanjr9w
[23:40] <jarkinox> i seriously doubt it has usb 3
[23:40] <jarkinox> it’s ancient
[23:41] <jarkinox> back when 80 gigs was a lot
[23:41] <Synthead> jarkinox: are you ok with your read and write speed being a combined 30 MiB/s ?
[23:41] <jarkinox> yeah, i don’t use it a whole bunch.  it’s like cold storage
[23:42] <jarkinox> but i like to tinker with things :)
[23:42] <jarkinox> don’t mind a little speed improvement
[23:43] <Synthead> jarkinox: ok, as long as you're aware.  sata 2 will operate at 3 GiB/s, which is ~100x faster.  Your drive will likely peak at a couple hundred MiB/s though, being a disk with platters
[23:43] <Synthead> jarkinox: do you see "Western Digital" anywhere in your ring buffer before plugging that disk in?
[23:44] <jarkinox> dmesg | grep Western
[23:44] <jarkinox> [14339.730100] usb 1-4: Manufacturer: Western Digital
[23:44] <jarkinox> nope, only after I plugged it in
[23:45] <Synthead> jarkinox: what about "USB"?
[23:45] <Synthead> jarkinox: anything worth mentioning?
[23:46] <Synthead> jarkinox: also, when the drive is unplugged with the platters stopped, how long does it take to spin up and be recognized?
[23:46] <Synthead> just generally
[23:46] <Synthead> 5-10 seconds ish?
[23:46] <jarkinox> yeah it’s pretty quick
[23:46] <Synthead> some motherboards have a setting in the bios that goes by the tune of "wait for disks" or something
[23:47] <Synthead> it doesn't continue to boot until all attached storage responds
[23:47] <jarkinox> http://pastie.org/private/cv1dpaa1wqmedwcfj3hblg
[23:47] <jarkinox> the box boots fine even with the hard drive attached
[23:47] <jarkinox> there’s another Toshiba drive attached that doesn’t have the problem
[23:48] <Synthead> you might look at dmesg via less as just grep'ing dmesg will remove a lot of nice errors
[23:48] <jarkinox> how far back does dmesg go?
[23:48] <Synthead> jarkinox: since the box was booted unless you clear the buffer
[23:49] <jarkinox> i rebooted today after some updates
[23:49] <Synthead> what is the model of your dell?  dmidecode will tell you
[23:50] <jarkinox> DE051
[23:50] <jarkinox> released 2006
[23:50] <Synthead> jarkinox: do you have a visible grub boot loader when the machine is turned on?
[23:50] <jarkinox> there’s no monitor attached to it
[23:50] <jarkinox> and no gui
[23:50] <Synthead> jarkinox: oh right on
[23:51] <jarkinox> so paste the whole dmesg?
[23:51] <Synthead> jarkinox: the reason I mentioned it is because you might check if this is the problem preemptively by interacting with the grub menu while the disk spools up
[23:51] <Synthead> after ~15 seconds, boot the os and see if the disk was detected
[23:52] <Synthead> jarkinox: if you really wanted, you could
[23:52] <jarkinox> i could go that route but that would require attaching a monitor and keyboard, and I’m determined to figure this out via ssh :)
[23:52] <Synthead> jarkinox: that's a lot of text
[23:52] <jarkinox> yeah i don’t want to but i’m not sure what i’m looking for in dmesg
[23:52] <Synthead> jarkinox: what is your grub timeout value?
[23:53] <jarkinox> where would I find that?
[23:53] <Synthead> jarkinox: probably /boot/grub/grub.cfg
[23:53] <Synthead> jarkinox: ubuntu will kill any changes make directly in that file via scripts, but this would only be a temporary test
[23:54] <Synthead> jarkinox: actually, if you have to wait for the disk to spool up before it works properly, maybe just putting a longer timeout in there would be good enough
[23:54] <Synthead> you'll probably want to do it the "formal" way via /etc/defaults/grub, though
[23:54] <jarkinox> it’s either 2 or 30
[23:54] <jarkinox> not too sure how to read this bash script
[23:54] <Synthead> gruc.cfg shouldn't be a bash script
[23:55] <Synthead> what does the line say?
[23:55] <jarkinox> sorry, it’s not.  I think it’s perl
[23:55] <jarkinox> I’m a C# guy so it’s all jibberish to me ;-)
[23:55] <Synthead> jarkinox: what file?
[23:56] <jarkinox> ok hold on, there was a note in there to go to /etc/default/grub
[23:56] <jarkinox> GRUB_TIMEOUT = 2
[23:57] <Synthead> jarkinox: as mentioned, grub.cfg is the real config script for grub.  grub doesn't care about /etc/default/grub, but it's where you'd make permanent changes
[23:58] <Synthead> if you want to make a temporary test, /boot/grub/grub.cfg is fine.  If you want to make permanent changes, /etc/default/grub is where you'd likely put it, then run some kind of grub updater script
[23:58] <Synthead> tbh, I'm more of an Arch guy, so I hand-write grub.cfg
[23:58] <jarkinox>  terminal_output gfxterm
[23:58] <jarkinox>  85 if [ "${recordfail}" = 1 ] ; then
[23:59] <jarkinox>  86   set timeout=30
[23:59] <jarkinox>  87 else
[23:59] <jarkinox>  88   if [ x$feature_timeout_style = xy ] ; then
[23:59] <jarkinox>  89     set timeout_style=menu
[23:59] <jarkinox>  90     set timeout=2
[23:59] <jarkinox> Arch guy?
[23:59] <Synthead> bleh
[23:59] <jarkinox> Architect?
[23:59] <Synthead> Arch Linux
[23:59] <jarkinox> whoa
[23:59]  * jarkinox bows down
[23:59] <Synthead> heh, nah, it's not like that