[05:47] <cpaelzer> good morning
[06:16] <ruben23> hi there guys anyone can help with this command i get syntax error ------>   fakeroot make-kpkg –initrd –append-to-version=-custom kernel_image kernel_headers
[06:16] <ruben23> anyone can help correct the command
[06:21] <cpaelzer> ruben23: you might post the actual error via pastebinit
[06:21] <cpaelzer> ruben23: maybe -- after the fakeroot?
[06:21] <cpaelzer> to ensure it is not picking up make-kpkg's options?
[06:23] <cpaelzer> also at least what you copied here has merged unicode "–" instead of "--"
[06:23] <cpaelzer> ruben23: ^^
[06:24] <ruben23>  cpaelzer:  Thanks a lot it works..
[06:24] <cpaelzer> yw
[09:25] <adrian_1908> if anyone here is using Nginx on 16.04, for the resolver directive (http://nginx.org/en/docs/http/ngx_http_core_module.html#resolver), do I use 127.0.1.1 (Dnsmasq) or is 127.0.0.1 the right IP? I found almost no examples of the former, so I'm a bit confused.
[09:27] <cpaelzer> adrian_1908: well if you set nothing you should use the default which on your system should be 127.0.1.1
[09:27] <cpaelzer> adrian_1908: see /erc/resolv.conf
[09:28] <adrian_1908> cpaelzer: yes, that's set to nameserver 127.0.1.1 and dig reports that IP too.
[09:28] <cpaelzer> adrian_1908: so I'd assume you do either nothing at all with that directive or have a reason to set something really different like an external nameserver
[09:29] <adrian_1908> cpaelzer: you mean, if I omit it, Nginx will try to go through dnsmasq anyway?
[09:29] <cpaelzer> I'm only 98% sure, but yes
[09:30] <adrian_1908> cpaelzer: ok. Alas, I'm not experienced in networking related things, so i often don't know how to test these things. thanks.
[09:31] <adrian_1908> my VPS provider uses Ubuntu cloud images that already point dnsmasq to their nameservers, and that works really well, so I didn't want to use Google's 8.8.8.8 or whatever most guides use.
[09:34] <cpaelzer> I think you are fine without setting somethnig
[09:34] <cpaelzer> if you need a better expert ask teward later on (not around yet I'd think)
[09:35] <adrian_1908> I might, but for now thanks man!
[19:16] <Tripps> Curious here, how can I transfer one disk to another; meaning the data on the drive to my 2tb harddrive?
[19:24] <tarpman> cp(1)?
[19:30] <Polarcraft> tarpman, well I don't want to use the normal drive at all, I want to migrate over to the 2tb and have it run on reboot without any issues.
[20:10] <Poster> you might look at something like clonezilla to do the imaging, if you used LVM the resizing should be pretty easy, if not gparted should help
[21:22] <semiosis> i'm running into a problem since upgrading my ec2 API servers from trusty to xenial.  a server will run fine for a day or two, then it will stop serving requests.  when i SSH into the machine, if I can login at all, it is extremely slow.  it takes a few seconds for each character i type into the shell to be echoed back.  there's no errors in the system log, no problems showing in dmesg, and my API logs look fine.  any ideas what this
[21:22] <semiosis>  could be?
[21:23] <semiosis> cpu usage is minimal, system load is near zero, and there is free memory available
[21:23] <semiosis> all the usual stuff checks out fine
[21:37] <sarnold> semiosis: any luck yet?
[21:37] <sarnold> semiosis: give this a view and see if it provides anything useful to work with http://www.brendangregg.com/blog/2015-12-03/linux-perf-60s-video.html
[21:38] <semiosis> no luck trying to figure this out on my own, so coming here for help.  been dealing with this for a few weeks.
[21:38] <semiosis> will check. thanks
[21:43] <tarpman> semiosis: problem on the server, or between you and the server? run a few commands with `time` prepended and see if things actually take longer than expected just executing on the server?
[21:44] <semiosis> my hunch is it is a network issue.  kernel tcp stack maybe.
[21:45] <semiosis> i just deployed an increase of the tcp memory limits.  when these servers die i'll try timing some commands.  thanks for the tip
[23:06] <Epx998> aha
[23:33] <SupaYoshi> HJHi
[23:33] <SupaYoshi> I've tried enabling TLS support with Pure-FTPD, got that working
[23:33] <SupaYoshi> But everytime I enable UFW (I've got port 21 TCP open)
[23:33] <SupaYoshi> I cannot access the directory listings with Ufw enabled and TLS
[23:33] <SupaYoshi> (FTPS)
[23:33] <SupaYoshi> but I can with FTP
[23:34] <SupaYoshi> what ports does FTPS use
[23:36] <sarnold> don't you need both 20 and 21 for ftp?
[23:38] <mason> sarnold: Only if you want data *and* commands.
[23:38] <sarnold> mason: picky picky :)
[23:39] <mason> SupaYoshi: FWIW, "grep ftp /etc/services" will show the ftps ports, and also sftp.
[23:43] <SupaYoshi> im not using sftp
[23:43] <SupaYoshi> im using ftps
[23:43] <nacc> SupaYoshi: ok, so grep what mason said
[23:44]  * mason contemplates an RFC describing sftps, just to be difficult.
[23:44] <nacc> mason: :)
[23:44] <nacc> SupaYoshi: also, mason didn't say you were using sftp, they said it shows ports for both ftps and sftp
[23:44] <SupaYoshi> ok
[23:44] <mason> I are plural! \o/
[23:44] <SupaYoshi> its odd that it works fine without ufw
[23:45] <SupaYoshi> and stops with ufw enabeld.
[23:45] <SupaYoshi> http://paste.ubuntu.com/24731516/
[23:46] <nacc> SupaYoshi: you didn't need to paste it, we all have it on our systems too
[23:52] <SupaYoshi> so what port
[23:52] <SupaYoshi> is needed for it to work? :P
[23:52] <SupaYoshi> 21 is open, 22 is.