[00:00] <stokachu> rstarmer: ok I'll need to mess with it inside a VM, why not run it on baremetal? it  allocates everything to containers anyway
[00:02] <rstarmer> when you only have access to big VMs from your provider, you use VMs :)
[00:03] <rstarmer> was about to spin up another machine, I'll give you access when it's up if you've got time to look at it.
[00:10] <rstarmer> stokachu: try ubuntu@conjurephy.opsits.com, lxd init, using ppa:conjure/ppa, but havent' run conjure-up yet.
[00:10] <stokachu> ok it may be a bit
[00:11] <rstarmer> no worries, it'll be there at least until tomorrow.
[01:44] <agronholm> hi, I'm trying to boot my servers in UEFI mode (ubuntu 16.04) but no success
[01:44] <agronholm> installation works fine
[01:44] <agronholm> but attempting to boot drops me to a grub prompt
[01:45] <agronholm> further, grub can't read any of my XFS partitions though grub is supposed to work with XFS
[01:45] <agronholm> any pointers would be helpful
[02:38] <nick125> Hey everyone. I just installed 16.04 LTS on a box and I'm having problems with my ethernet interface changing name on every boot. I have 3 NICs in my box (2x Intel, 1x Realtek), and the Realtek NIC keeps getting named either enp3s0 or enp4s0...but it seems to change on every boot. Any thoughts on how to make this consistent?
[02:53] <Werewolf> hello
[02:53] <Werewolf> after upgrading, I experience dependency hell.
[02:53] <Werewolf> Please assist. The server is not working at all.
[02:53] <agronholm> Werewolf: specifics
[02:53] <Werewolf> 	http://pastebin.com/4UzB5Dnp
[02:53] <Werewolf> agronholm
[02:54] <agronholm> Werewolf: does apt-get install -f help?
[02:54] <Werewolf> on first update attempt, it hung, now i have 7 broken packages.
[02:54] <Werewolf> and no
[02:54] <agronholm> what happens then?
[02:54] <Werewolf> same error, they seem to be blocking anything with APT
[02:55] <Werewolf> the issue is with
[02:55] <Werewolf>  mysql-server-5.7
[02:55] <Werewolf>  mysql-server
[02:56] <agronholm> /var/lib/dpkg/info/keyboard-configuration.postinst: line 103: /etc/default/keyboard: Permission denied
[02:56] <agronholm> this caught my eye
[02:56] <Werewolf> i'm root.
[02:56] <Werewolf> currently
[02:56] <agronholm> how do you get permission denied with root
[02:56] <Werewolf> i have no idea, a distro update hung
[02:56] <Werewolf> and this is me trying to recover from it
[02:56] <agronholm> can you try to purge the offending package and reinstall it?
[02:56] <agronholm> keyboard-configuration that is
[02:56] <Werewolf> no, i have a production database
[02:56] <Werewolf> in mysql
[02:57] <Werewolf> and i tried that
[02:57] <Werewolf> with keyboard configuration
[02:57] <agronholm> and?
[02:57] <Werewolf> it errors out in the end, regardless
[02:57] <Werewolf> i did
[02:57] <Werewolf> sudo apt-get remove keyboard-configuration
[02:57] <Werewolf> sudo apt-get install keyboard-configuration
[02:57] <Werewolf> on reinstall, it causes issues again
[02:57] <agronholm> I said purge, not remove
[02:57] <Werewolf> sec
[02:57] <agronholm> "remove" doesn't delete configuration files
[02:57] <Werewolf> rm: cannot remove '/etc/default/keyboard': Operation not permitted
[02:58] <agronholm> that's the real problem you need to solve
[02:58] <agronholm> is that a normal file?
[02:58] <Werewolf> yes
[02:58] <Werewolf> i can edit it in nano
[02:58] <Werewolf> but i have no write permission to save
[02:58] <agronholm> and rm -f /etc/default/keyboard gives you the error?
[02:59] <Werewolf> yes
[02:59] <agronholm> run a filesystem check
[02:59] <agronholm> it sounds like fs corruption
[03:02] <Werewolf> okay, running
[03:04] <Werewolf> i am still concerned; why would file system error over a simple distro upgrade?
[03:04] <agronholm> Werewolf: you got it backwards
[03:04] <Werewolf> ?
[03:05] <agronholm> the distro upgrade would error because of a file system error
[03:05] <agronholm> distro upgrades don't generally cause file system errors
[03:05] <agronholm> but if you have any, your upgrade may go wrong
[03:08] <Werewolf> root@rescue:/# fsck /dev/sda1
[03:08] <Werewolf> fsck from util-linux 2.20.1
[03:08] <Werewolf> e2fsck 1.42.5 (29-Jul-2012)
[03:08] <agronholm> ?
[03:08] <Werewolf> trying to fix
[03:09] <agronholm> fix what?
[03:09] <agronholm> did it find errors?
[03:09] <Werewolf> it says clean
[03:09] <agronholm> can you move the file?
[03:09] <agronholm> what are the permissions on it?
[03:09] <Werewolf> which file?
[03:09] <agronholm> that only file we discussed
[03:10] <Werewolf> no
[03:10] <Werewolf> i can't write to it
[03:10] <Werewolf> even from rescue mode
[03:10] <agronholm> that's not what I asked
[03:10] <Werewolf> can i move it?
[03:10] <agronholm> I asked what its permissions are
[03:10] <agronholm> moving the file does not involve writing to it
[03:11] <Werewolf> -rw-r--r-- 1 root root   70 Jan 14  2015 keyboard
[03:11] <agronholm> and "mv /etc/default/keyboard /tmp/" does what?
[03:12] <Werewolf> nothing
[03:12] <Werewolf> silently fails
[03:12] <agronholm> so no errors, but the file stays in place?
[03:12] <Werewolf> yes
[03:12] <Werewolf> root@rescue:/mnt/etc/default# mv keyboard key2
[03:12] <Werewolf> mv: cannot move `keyboard' to `key2': Operation not permitted
[03:12] <Werewolf> that also fails
[03:13] <agronholm> then I'm out of tricks
[03:13] <Werewolf> :(
[03:13] <agronholm> Werewolf: but other files in the directory can be moved?
[03:13] <Werewolf> yes
[03:14] <Werewolf> can't chmod keyboard either
[03:15] <agronholm> I had the same problem years ago but it was due to file system corruption
[03:16] <Werewolf> i don't thin kfsck is doing anything
[03:16] <Werewolf> because it immediately says clean
[03:16] <Werewolf> without going through any steps
[03:16] <agronholm> ah
[03:16] <agronholm> Werewolf: use the -f option
[03:16] <agronholm> e2fsck -f -p
[03:17] <Werewolf> hm
[03:17] <Werewolf>  /dev/sda1: 150597/3141600 files (0.3% non-contiguous), 3506720/12594944 blocks
[03:18] <agronholm> still no errors?
[03:18] <agronholm> or did it not finish yet
[03:18] <Werewolf> that is the only oputput
[03:20] <Werewolf> wow
[03:20] <Werewolf> tons of errors
[03:20] <Werewolf> i did sudo mkfs.ext4 -S /dev/sda1
[03:20] <Werewolf> now it is catching a ton
[03:20] <agronholm> is that not your root drive though?
[03:20] <agronholm> oh, you're in rescue mode
[03:20] <Werewolf> yes
[03:23] <Werewolf> it's fixing a buttload of things
[03:23] <Werewolf> either this will hopefully work
[03:23] <Werewolf> or i fucked up the file system beyond repair
[03:23] <agronholm> you're doing mkfs
[03:24] <agronholm> so
[03:24] <Werewolf> ?
[03:24] <agronholm> how would you screw up a filesystem with mkfs?
[03:24] <Werewolf> no idea, but i didn't even know my file system was broken until this distro update fell all over itself
[03:25] <Werewolf> but a file system error
[03:25] <Werewolf> would also explain why some PHP files
[03:25] <Werewolf> were just spitting out their source
[03:25] <Werewolf> right?
[03:25] <agronholm> maybe...dunno
[03:25] <agronholm> you're probably running apache
[03:26] <Werewolf> yes
[03:26] <Werewolf> until this udpae
[03:26] <Werewolf> no problems
[03:26] <agronholm> I've never seen that happens with the nginx+php-fpm combo that I prefer whenever I have to run a PHP thing
[03:26] <agronholm> -s
[03:26] <Werewolf> after, the php files spit out their soure
[03:26] <Werewolf> also, how long will this take? :P
[03:26] <agronholm> depends on the size of your disk
[03:27] <Werewolf> 100gb
[03:27] <Werewolf> ...
[03:27] <Werewolf> i lsot everything
[03:27] <agronholm> it shouldn't take that long if you're not forcing it to overwrite everything
[03:28] <Werewolf> root@rescue:/mnt# ls
[03:28] <Werewolf> dev  lost+found  srv
[03:28] <agronholm> ?
[03:28] <Werewolf> that's all
[03:28] <Werewolf> that's in /sda1/
[03:28] <Werewolf> now
[03:28] <agronholm> yes?
[03:29] <agronholm> what were you expecting?
[03:29] <Werewolf> how is that normalo?
[03:29] <Werewolf> where are my files?
[03:29] <agronholm> you just formatted your drive
[03:29] <agronholm> that's what mkfs does
[03:29] <Werewolf> so i lost all data?
[03:29] <agronholm> everything that's not backed up (which you surely have done?)
[03:29] <Werewolf> lovelhy
[03:29] <Werewolf> yes, i have a daily
[03:30] <agronholm> mkfs = make filesystem
[03:44] <arooni> was examining why my server is full.  apparently i have 1.4G in /usr/src ;; there is quite a bit of old linux headers
[03:44] <arooni> how would i clean out old versions without breaking anything
[03:46] <agronholm> arooni: apt-get remove them?
[03:46] <agronholm> also, apt-get autoremove should remove them anyways
[03:47] <arooni> agronholm so i can trust autoremove not to remove any headers etc that i need?
[03:47] <agronholm> arooni: yeah
[03:47] <arooni> nice;  you just helped me free of 2.6GB
[03:48] <arooni> agronholm is autoremove something i can set up to run automatically
[03:48] <arooni> or is that something that should only be run manually
[03:49] <arooni> and also;  is there a way of checking to make sure ubuntu will still boot without rebooting; i need to check what.. /etc/fstab ?
[03:49] <arooni> seeing as i'm removing this
[06:03] <rstarmer> stokachu: I was finally able to validate access to a DO based deployment (loaded an even larger DO instance), and with a little SSH-fu (port-forwarding to horizon) was able to get in and launch an instance.
[06:05] <rstarmer> stokachu: one thing to add, either the IP of the keystone instance, or the OS_AUTH_URL so you can create an rc file.  Saves me figuring out how to discover it ;)
[06:10] <rstarmer> stokachu: routing isn't working (can map from ext->instance, but can't get there), and console access doesn't appear to work either.
[06:21] <rstarmer> stokachu: in looking in the router namespace, it appears that while the interfaces are properly configured, it is not currently possible to ping from the router namespace (in the neutron-gateway container) to the vm.
[06:22] <rstarmer> stokachu: I can get to/from the neutron-gateway container to the base OS so the failed connection appears to be gateway to nova container container (where I presume the LXD instance of xenial was started).
[06:23] <rstarmer> stokachu: I'm going to kill this machine now, can recreate at some point when you might have bandwidth to have a look.
=== athairus is now known as afkthairus
[09:03] <lordievader> Good morning.
=== Piper-Off is now known as Monthrect
[10:35] <bittin> Hello is there any Ubuntu Server mailinglist?
[10:35] <bittin> for announces and stuff?
[10:36] <bittin> nevermind found it: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
=== arlen is now known as Guest16718
[13:34] <deadnull> I just did a clean install of 16.04, is vmstat supposed to run all the time? Seems kind of odd to me.
[13:37] <lordievader> No? The first output it gives is some sort of a summary... I usually run it as 'vmstat 1'.
[13:39] <deadnull> lordievader so I am not actually running vmstat myself, root is running the process (i was looking into the changes with systemd) and discovered this.
[13:40] <deadnull> was about to file a bug but wanted to check
[13:40] <lordievader> Hmm, not sure about that.
[13:41] <deadnull> yeah, its very odd, for sure. I might be waiting a little bit before I deploy on 16.04.
[13:47] <patdk-lap> I don't have vmstat running on any of my 16.04 machines
[13:49] <deadnull> patdk-lap desktop or server
[13:50] <patdk-lap> this is the server channel, I hope you are not discussing desktop
[13:50] <deadnull> I just finished a clean install, no options installed, nothing, of server 16.04 in VMware
[13:50] <deadnull> I am not :)
[13:50] <deadnull> Just wanted to triple check
[13:50] <patdk-lap> exactly where is vmstat running?
[13:51] <deadnull> `ps aux | grep vmstat` -> "root 29 [vmstat]"
[13:51] <patdk-lap> heh?
[13:51] <patdk-lap> that is NOT vmstat
[13:51] <patdk-lap> that is a kernel thread
[13:52] <deadnull> :facepalm:
[13:52] <deadnull> ty sir for resetting my brain
[13:52] <deadnull> totally missing that, b/c in top its not displayed like that
[15:29] <jonah> Hi I'm running a couple of new storage servers and just wondered how other Ubuntu Server users back up their data. Currently I use rysnc with a NAS with some hug hard drives in but because I have such a volume of files to backup each backup run takes 3-4 days... Most of the time when doing backups the last run hasn't finished when the next one starts!!
[15:30] <jonah> I'm only backing up on the local network, I use gigabit ethernet wired connection but things are still too slow. could it be the slow CPU of the NAS where the bottleneck is??
=== InfoTest1 is now known as InfoTest
=== chuck__ is now known as zul
=== afkthairus is now known as athairus
=== arlen is now known as Guest92524