[01:37] <Troy^> Hey anyone here a virtualbox(vboxwebsrv) user? I'm using ubuntu 16.04 and can't seem to get phpvirtualbox to work with vboxwebsrv. configured config.php in /var/www/html/phpvirtualbox as well configured /etc/default/virtualbox. When I navigate to the phpvirtualbox page it loads up with a config.php error. Even tried starting from scratch and still get a php error. It's like it's not talming to
[01:37] <Troy^> vboxwebsrv and it should be
[01:40] <nacc> Troy^: is 'phpvirtualbox' an ubuntu package?
[01:43] <nacc> Troy^: if it is not, does it work with php7?
[01:54] <Troy^> nacc apparently i needed to install php-soap and php-xml it's working now though
[02:18] <nacc> Troy^: if you could let me know if that's a packaging issue,t he latter might be due to php7 pulling php-xml out of hte core, and the former might be a missed dep
[02:18] <nacc> Troy^: *if* it's an ubuntu pacakge :) -- i can fix it
[04:25] <kgirthofer> hey alll - trying to ping my domain, getting a unknown host if I leave off the www
[04:25] <kgirthofer> any ideas?
[04:28] <andol> kgirthofer: Any chance that you don't have any A record for the bare domain? Seem to recall that being ping is looking for.
[04:28] <kgirthofer> yea I got that part - I tried cname too
[04:28] <kgirthofer> used to work
[04:28] <kgirthofer> even if I edit my host file with the ip i'm trying to resolv still no route to host
[04:29] <andol> Might be easier for everyone if you specify the domain in question.
[04:30] <kgirthofer> mydelphic
[04:30] <kgirthofer> .com
[04:31] <kgirthofer> it's just a local
[04:33] <andol> What by you mean by local? It kind of exists in DNS.
[04:36] <andol> Anyway, I do get a DNS response for mydelphic.com, and while that ip (173.15.136.74) don't appear to respond to ICMP Ping it is responding to http requests.
[04:36] <kgirthofer> yea we have ping off
[04:36] <kgirthofer> nah if I do an ns for that domain i get no route to host
[04:36] <kgirthofer> I should get 10.201.1.100
[04:37] <andol> Why would you expect to get 10.201.1.100? Aside from that being an RFC1918-address, that is not what it says in DNS.
[04:37] <kgirthofer> because that's what my internal dns shows
[04:37] <andol> Also, why do you use the ping too. if you purposely don't expect it to respond to pings? :)
[04:37] <kgirthofer> not from outside
[04:38] <kgirthofer> i'm internal - I can ping what ever I want
[04:38] <kgirthofer> but I'm expecting mydelphic to resolve internally to 10.201.1.100 - one of our webservers
[04:38] <andol> Also, strictly speaking ping doesn't do a DNS lookup, it does hostname lookup, where DNS is one source, but not neccesarily the default/primary one.
[04:39] <kgirthofer> ya ping resolves
[04:39] <kgirthofer> so does internet
[04:39] <kgirthofer> they translate to www.
[04:40] <kgirthofer> ugh
[04:40] <kgirthofer> no parent folder
[04:40] <kgirthofer> got it
[04:40] <kgirthofer> fuck i'm exhauted. I'm at 45 hours this week... it's wednesday
[04:41] <andol> Oh, well, sounds like you solved the issue, whatever it was?
[04:41] <kgirthofer> ya
[04:41] <kgirthofer> thanks for your help
[07:08] <Repox> Hi. So, I just pinged a domain name and I got this result "64 bytes from 149.126.72.171.ip.incapdns.net (149.126.72.171)" I'm unsure as to what the ip.incapdns.net is (I mean, why do I get that information and what do I call it in this context)?
[07:09] <sarnold> Repox: reverse dns lookup -- it converts IPs back to names
[07:09] <sarnold> Repox: https://en.wikipedia.org/wiki/Reverse_DNS_lookup
[07:10] <sarnold> Repox: most tools provide an -n option to disable this lookup
[07:10] <Lope> If anyone here is running a 4.4 kernel (type `uname -r` to check, you will be if you use Ubuntu 16.04). So if you have a 4.4 kernel and you're running an NFS server, if you could be so kind as to try mounting one of your NFS shares with NFSv3 (instead of the default NFSv4) I would really appreciate you to provide feedback on my Kernel Bug report. https://bugzilla.kernel.org/show_bug.cgi?id=118881
[07:10] <Repox> sarnold , great, thank you for the info. I'll try and look it up.
[07:10] <Lope> Just test like this: `mount NFSSERVERIP:/nfs/shared/path /tmp/testmount -o ro,vers=3`
[07:14] <sarnold> Lope: this worked without error: sudo mount -tnfs -o ro,nfsvers=3 192.168.122.1:/srv/mirror/ubuntu /tmp/testmount/
[07:15] <sarnold> Lope: note nfsvers=3 vs vers=3
[07:15] <Lope> sarnold: what's the diff between nfsvers and vers ?
[07:16] <sarnold> Lope: sigh. i typoed "vers3" the first time and didn't notice.
[07:16] <sarnold> Lope: vers=3 also works
[07:16] <Lope> what kernel version is your server?
[07:17] <sarnold> 4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016
[07:18] <Lope> can you please try in this format? `mount 192.168.122.1:/srv/mirror/ubuntu /tmp/testmount -o ro,vers=3`
[07:19] <sarnold> Lope: worked fine
[07:20] <Lope> what do you get for `cat /proc/filesystems | grep nfs`
[07:20] <sarnold> nfs and nfs4
[07:20] <Lope> ah, same as my ubuntu server. so it's normal not to see nfs3 there.
[07:23] <Lope> what do you get for these? `cat /proc/sys/fs/nfs/nlm_tcpport` `cat /proc/sys/fs/nfs/nlm_udpport`
[07:26] <sarnold> Lope: 0 0
[07:27] <Lope> hmm, i wonder if it's my setup.
[07:27] <Lope> I'm gonna document my settings as well in the bug report.
[07:38] <jatin30> I am trying to set up LAMP in my system. It syas in the instructions "Change the DocumentRoot to point to the new location. For example, /home/user/public_html/" but there is no such directory currently present in the system. what to do?
[07:49] <Lope> sarnold: thanks, I've identified it's my iptables rules somehow blocking NFSv3 but not NFSv4
[07:49] <sarnold> Lope: woot. :) iirc nfs4 moved to fixed ports, nfs3 still had the portmap and ostensibly selected-at-random ports, right?
[07:50] <Lope> Yes!
[07:51] <Lope> exactly, So i scripted and set some options in various config files to try to control those random ports so I could make effective iptables rules.
[07:51] <Lope> But maybe NFSv3 is not obeying those ports anymore?
[07:51] <Lope> I don't know.
[08:11] <Lope> all of the guides I've seen for setting up NFS to work with a firewall say that you must set the various services to use a specific port number. I've been unable to set the port for mountd using the command they recommend: `mountd -p 32767` mountd not found. Yet my nfs server is installed and working, what's going on?
[08:12] <sarnold> are they fro mthe era of user-land nfs server/
[08:13] <Lope> I've got no idea.
[08:13] <Lope> 1. http://nfs.sourceforge.net/nfs-howto/ar01s06.html#srv_security_nfsd_mountd
[08:13] <Lope> 2. http://tldp.org/HOWTO/NFS-HOWTO/security.html
[08:16] <Lope> oh, i see the command has changed. now it's rpc.mountd
[09:29] <jamespage> coreycb, xenial/ironic builds fixed - for some reason, the schroot's where not getting a /etc/hosts - I added this to the copyfiles for the sbuild profile and we're all good again..
[10:44] <jatin30> can anyone help me with this http://imgur.com/cMB4zM1 ?
[10:47] <hateball> jatin30: < and > are used for redirecting in the shell, use \ to escape
[10:47] <ankitkulkarni> jatin30, can you post the output of pwd
[10:48] <hateball> jatin30: like \<b\>
[10:48] <jatin30> ankitkulkarni: yes just a min
[10:49] <jatin30> ankitkulkarni: here, http://imgur.com/cMB4zM1 and can i please dm you?
[10:50] <ankitkulkarni> yea
[10:56] <shauno> I think you're overthinking it.  you're trying to >/home/user/public_html/index.html instead of /home/jatin...
[10:56] <hateball> I only looked at the syntax error bits, heh
[10:58] <shauno> yeah.  you expect <> to go horribly wrong, and miss that bash is complaining /home/user... doesn't exist
[11:15] <jatin30> Why am I getting http://imgur.com/Fw6kC2R after installing apache 2 properly
[11:16] <shauno> jatin30: see my last couple of lines; where your instructions have /home/user you need to replace that with your actual username
[11:17] <jatin30> yeah I did that
[11:17] <jatin30> I completed all steps properly
[11:17] <jatin30> i followed this link https://help.ubuntu.com/community/ApacheMySQLPHP
[11:17] <jatin30> everything was fine and it initally detected apache so i did not troubleshoot it
[11:18] <jatin30> and went straight to the virtual hosts and did all what was required , now its not detecting
[11:35] <coreycb> jamespage, interesting on ironic, thanks
[11:40] <jamespage> coreycb, I suspect some cruft due to the long running nature of that installation...
[13:22] <Ergo^> hello, im provisioning 16.04 VM's, they have the "predictable network interface" systemd scheme, now when someone gets an OVA and uses it - the network interface might be completly different however /etc/networking/interfaces has "auto IFACENAME
[13:22] <Ergo^> " hardcoded, how to deal with that
[13:23] <rbasak> Ergo^: if you're preparing an image and it'll only get used with one interface, then perhaps turn off the renaming and rely on it being eth0?
[13:23] <rbasak> I'm not exactly sure how to do that but I believe it's configurable.
[13:24] <Ergo^> yeah, its supposed to take a symlink for udev to disable it, but its not working
[13:27] <rbasak> nacc: if you're about during the next hour, shall we sync?
[13:29] <Odd_Bloke> Ergo^: Ubuntu doesn't ship an /etc/networking/interfaces with hard-coded interface names; how are those getting created?
[13:29] <Ergo^> Odd_Bloke: maybe during install?, i wrote the provisioning scripts so im not doing it
[13:30] <Odd_Bloke> Ergo^: Where is the install happening?
[13:30] <Odd_Bloke> Ergo^: (If you're installing VMs from the ISO, you might want to consider using the cloud images instead :)
[13:30] <Ergo^> hmm, wait, im actually using a seed file
[13:30] <Ergo^> let me consult that
[13:31] <Ergo^> maybe there is something there
[13:31] <Ergo^> im provisioning with packer
[13:31] <rbasak> That uses the installer I believe.
[13:31] <Odd_Bloke> Ah, OK, that makes sense; packer doesn't support the cloud images AFAIK.
[13:31] <rbasak> File a bug with packer.
[13:32] <Ergo^> and https://friendpaste.com/O1nBAQvyRzvxprmecZjpT i end up with that
[13:32] <rbasak> Ubuntu's answer to the general problem is cloud images that use cloud-init.
[13:32] <Odd_Bloke> Ergo^: But, yeah, if you're doing VMs you'll want to ensure that (a) /etc/network/interfaces isn't being overwritten, and (b) cloud-init runs on boot so it can handle changing interface names for you. :)
[13:32] <rbasak> cloud-init handles the fact that an image can end up running in a different environment.
[13:33] <rbasak> Running the installer to set up a VM image that will then run in a different environment is a hack. We'll consider fixes for issues, but we don't think it's the right path forward. Cloud images work far better for this use case.
[13:34] <Ergo^> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ - i wanted to use the solution from here
[13:34] <Ergo^> ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
[13:34] <Ergo^> but its not working
[13:35] <rbasak> I don't know if that exact method applies to Ubuntu, but the general idea should work. If it doesn't, it's either a bug or different instructions need to be followed.
[13:37] <Ergo^> https://friendpaste.com/2BFcFawTd8D5opSHqClAue - this is my preseed file
[13:39] <Ergo^> no other places where it can be rewritten
[13:40] <Ergo^> but I can overwrite it on my own at the end of provisioning... what the /etc/network/interfaces should look like on a cloud image?
[13:40] <rbasak> http://askubuntu.com/questions/689070/network-interface-name-changes-after-update-to-15-10-udev-changes says to pass net.ifnames=0 on the kernel command line.
[13:40] <rbasak> Have you tried that?
[13:41] <Ergo^> that works, i wanted to avoid this solution though :-)
[13:41] <Ergo^> I guess i can work with that if no other options are available
[13:41] <rbasak> That seems to be the formal interface in Ubuntu to disable this.
[13:41] <rbasak> I'm sure you can do it in userspace afterwards, but you'll need to figure out how by following the implementation.
[13:42] <Ergo^> ok, thx
[14:18] <tanja84> I would like to know if there could be some problems upgrading a "old" 14.10 server ( with zfs support installed ) to a 16.04 LTS. The reason is that I would be sad if my zfs went down just because of the dist upgrade ( I have a backup but its in the cloud )
[14:20] <compdoc> I upgraded from 14.04 that used ZOL, to 16.04 without ZOL. works great
[14:21] <compdoc> I installed 16.04 from scratch, tho
[14:22] <patdk-wk> why would it go down?
[14:22] <patdk-wk> if you have dkms installed, the zfs dkms module will override the other module
[14:23] <tanja84> patdk-wk: well its the zfs kernel module I'm worried for, because I have never tried to dist-upgrade from a non lts to a lts before
[14:23] <patdk-wk> well, you cannot upgrade from 14.10 to 16.04
[14:24] <Pici> welll, you can attempt it, but it definitely isn't a supported path
[14:24] <tanja84> so its a reformat then. Thanks for the answer, I guess it has to run 6 month still
[14:25] <tanja84> reformat = reinstall
[14:26] <tanja84> and yes I do know that 14.10 almost have been EOL for a year
[14:28] <tanja84> I guess it wont be ubuntu next time because if the hazzle to upgrade
[14:38] <Odd_Bloke> tanja84: There is an upgrade path; you upgrade to vivid, then to wily, then to xenial. :)
[14:38] <patdk-wk> after you adjust your stuff to use the archive/old-releases servers
[14:46] <tanja84> Odd_Bloke: well and how much will breake then
[14:46] <tanja84> after all those steps
[14:47] <Odd_Bloke> tanja84: They're the same steps that everyone who upgraded from utopic through to xenial will have taken, so they should be pretty well tested.
[14:47] <tanja84> I guess I just have to change distro when I get some new drive's home to get the local backup but that is still first in 5 - 6 month
[14:48] <tanja84> Odd_Bloke: well you mean tested as in ubuntu fails
[14:48] <Odd_Bloke> tanja84: If you aren't interested in a constructive discussion, I can't help you. :)
[14:48] <tanja84> I du remember kernels from ubuntu failing to boot after upgrades
[14:49] <tanja84> Odd_Bloke: and do you recover my zfs raid then if it cant find it after the first upgrade
[14:50] <nacc> rbasak: i'm here now
[14:50]  * patdk-wk doesn't remember this
[14:51] <patdk-wk> tanja84, you are also not using lts, so your not exactly using the most stable, and well tested version
[14:51] <patdk-wk> so having problems, sounds like something you opted for when you started
[14:51] <tanja84> patdk-wk: that was only because I was miss informed when the server was installed
[14:51] <patdk-wk> misinformed?
[14:51] <patdk-wk> the documentation is everywhere
[14:52] <tanja84> I got the disk from one because I didnt had internet where the pc were
[14:52] <patdk-wk> installing zfs also, on that ubuntu version is not *supported*
[14:52] <tanja84> it was in here I was recommended that
[14:53] <patdk-wk> if the goal was to run zfs, yes, good recommendation
[14:53] <patdk-wk> if the goal is to have a stable system, without issues, without constant upgrades, no, zfs or that version where not the answer
[14:54] <patdk-wk> but yes, it does sound like your goal and priorities have changed
[14:54] <tanja84> well the goal was to secure the data for corruptions wich ext cant
[14:55] <patdk-wk> yes, good solution
[14:55] <tanja84> wich the reason there were created a zfs mirror of 3 disks
[14:55] <patdk-wk> but the side effects of that is, maintaince, and upgrades, and sometimes things breaking
[14:55] <patdk-wk> cause the solution isn't supported by ubuntu, atleast wasn't till 16.04
[14:56] <patdk-wk> the solution is not supported at all by anyone else yet
[14:56] <patdk-wk> except I think debian is starting to
[14:56] <tanja84> I guess then its complete bye bye linux for recommending things there arent supported
[14:57] <tanja84> specially in the official channels
[14:57] <patdk-wk> heh?
[14:57] <nacc> tanja84: you would have been quite clearly indicated something wasn't supported by adding PPAs, or building from source, or whatever
[14:58] <nacc> tanja84: and this is all volunteer response in here, anyways
[14:58] <nacc> tanja84: *technically*, anyone can say anything they want in response to your query
[14:58] <nacc> IMO, as a system installer, it is on you to make technical decisions about how to install
[14:59] <nacc> finally, ubuntu != linux
[15:03] <nacc> tanja84: i'm not trying to be rude, to be clear -- but your responses seem like an overreaction/misunderstanding
[15:03] <nacc> rbasak: i'll be free to chat after the meeting too
[15:04] <tanja84> nacc: well since canonical bought ubuntu back in the days then it always sounds like ubuntu is the only linux now a days
[15:04] <nacc> tanja84: uhhhh
[15:05] <nacc> tanja84: ok, that's further misunderstanding, let's be clear
[15:07] <patdk-wk> bought?
[15:07] <patdk-wk> strange world you live in
[15:08] <patdk-wk> there are so many, and even more versions of linux os's today, than there where 10years ago
[16:10] <nacc> rbasak: so we assumed security and updates were in lockstep; perhaps that wasn't always the case. clamav 0.92~dfsg-2~dapper1ubuntu0.2 (security) followed 0.92.1~dfsg2-1.1~dapper1 (updates).
[16:30] <nacc> rbasak: let me konw if you want to do a hangout today, i know it's getting (is) late your time
[16:35] <notthistime> can anyone help me port forward. i have port 80 forwarded on a PK5000 but the online port checker says it port 80 ist still closed
[16:43] <coreycb> jamespage, qemu - 1:2.2+dfsg-5expubuntu9.7~cloud4 is ready to promote to kilo-proposed
[16:43] <jamespage> coreycb, \o/ - I'll do that now
[16:44] <jamespage> coreycb, done
[16:44] <coreycb> jamespage, thanks!
[16:44] <jamespage> you'll need to manually handle in the bug unless you added it to the changelog
[16:45] <rbasak> nacc: is now OK?
[16:45] <nacc> rbasak: sure
[16:52] <nacc> rbasak: https://launchpad.net/ubuntu/+source/clamav/+publishinghistory?batch=75&direction=backwards&memo=525&start=450
[16:56] <synchronet> bugs are built in I reckon
[16:57] <synchronet> bit like the law legal system and solicitors and future work
[16:58] <nacc> rbasak: https://launchpad.net/ubuntu/+source/clamav/0.92.1~dfsg2-1.1~dapper1
[16:58] <nacc> rbasak: https://launchpad.net/ubuntu/+source/clamav/0.92~dfsg-2~dapper1ubuntu0.2
[17:06] <rbasak> http://pad.ubuntu.com/clamav-dapper
[17:18] <genii> dapper?
[17:24] <rbasak> Dapper.
[17:24] <nacc> genii: crazy publishing history :)
[17:54] <synchronet> Ubuntu can you stop the updates by hiring decent developers
[17:54] <synchronet> especially server reboot needed ones
[17:55] <Pici> I don't even know how to respond to that.
[17:56] <jrwren> synchronet: please remember: http://www.ubuntu.com/about/about-ubuntu/conduct
[17:58] <patdk-wk> synchronet, why are you compaining about updates?
[17:59] <patdk-wk> updates coming out often is a good thing
[17:59] <patdk-wk> but maybe you mean security patches
[18:00] <patdk-wk> though, dunno what ubuntu developers have to do with any of the above
[18:05] <synchronet> patdk-wk:  just tired I suppose
[18:07] <dasjoe> I'm not sure I follow
[18:08] <synchronet> narrow mindedness is no excuse
[18:59] <Lope> how can I disable the fancy boot screen in ubuntu-server? I want to see the log
[18:59] <b4r> funny I was wondering about acquiring a fancy boot screen so as to *not* see the log
[19:00] <\9> I was wondering today about having a fancy boot screen *with* the log
[19:00] <sarnold> probably 'plymouth' is the answer to both questions :)
[19:00] <Sling> Lope: see /etc/default/grub and remove the 'splash quiet'
[19:00] <teward> sarnold: ohai!
[19:00] <Sling> (or wherever thats at now)
[19:00] <sarnold> morning teward :)
[19:00] <Lope> sling: thanks!
[19:13] <coreycb> jamespage, neutron 2:8.1.0-0ubuntu0.16.04.2~cloud0 is ready to promote to mitaka-proposed
[19:15] <b4r> anyone in particular working on php7.0 package and updating to 7.0.7 from currently 7.0.4?
[19:33] <nacc> b4r: in which release?
[19:33] <b4r> uh
[19:33] <b4r> 16.04
[19:34] <nacc> b4r: well, a SRU microrelease exception has been filed: LP: #1569609
[19:34] <b4r> nacc: oh nice, are they filed usuallly on launchpad? I wouldn't mind attempting to keep up with this
[19:34] <nacc> if that were to be granted, we'd be able to update to 7.0.x
[19:34] <b4r> tbh it was more of a "woah they updated today and it's not in the repos"
[19:34] <nacc> b4r: until that happens though, we have to selectively backport
[19:35] <b4r> understood
[19:35] <nacc> b4r: well, no package gets updated just becuase upstream does, at least not automatically, in a released version
[19:40] <sarnold> ... in fact it's fairly rare. firefox, chrome-browser, mysql / mariadb are the most common ones.. there's a few others that get it periodically but it's rare
[19:40] <nacc> sarnold: good point!
[19:40] <nacc> b4r: hence the explicit bug requesting it for php7.0
[21:17] <emdub> hmm, what's the deal with mysql-server on xenial?  dpkg-reconfigure used to prompt for setting the root password, but it doesn't do that in xenial anymore so my database has some root password that i didn't enter
[21:17] <emdub> (asked in #ubuntu, but this is a -server install so figured i would try here too)
[21:18] <emdub> i can obviously make it bypass the grant table and fix it, but i feel like i'm missing something or there is a bug here with the package
[21:25] <emdub> aha, this is a xenial change: https://anonscm.debian.org/cgit/pkg-mysql/mysql-5.7.git/tree/debian/NEWS?id=1025a9fa9c6c112913c59138db49dbc94891d20f
[21:40] <dasjoe> madwizard: did you see https://github.com/b333z/beadm?
[22:01] <jjohnston> hello I have a question about booting new nodes in MaaS 1.9
[22:02] <jjohnston> on new nodes (non-ready) is there a way to force maas to repartition the disks?
[22:03] <jjohnston> that doesn't include me deleting/recreating the arrays on my storage controller?
[22:52] <notthistime> i have port 8080 open in router but cannot connect to server. any ideas?
[22:53] <notthistime>  i can get the server by going localhost:8080
[22:53] <sarnold> notthistime: check netstat -lnp output, see what address the process it bound to
[22:56] <notthistime> did netstat not sure what im looking for
[22:57] <sarnold> if the local address looks like this: 127.0.0.1:2628  then it's not listening externally
[22:57] <notthistime> 127.0.0.1:53
[22:57] <sarnold> if it looks like 0.0.0.0:22 or 192.168.122.1:53 then it is listening externally -- the first case, all interfaceds, the second case only that specific IP address
[22:58] <sarnold> that's probably just a dns server :) look for :8000
[22:58] <notthistime> no 8000
[22:59] <notthistime> 8080
[22:59] <notthistime> listening on 8080
[22:59] <nacc> notthistime: ok, look for 8080 :)
[22:59] <sarnold> ah. apparently I'm getting old.
[23:00] <notthistime> tcp6       0      0 :::8080                 :::*                    LISTEN
[23:00] <notthistime> im not sure what im looking for
[23:01] <sarnold> that's an ipv6 address; did you let tcp6 port 8080 through as well? do you have an ipv6 address? should you configure your application to also listen on 0.0.0.0:8080 so it works on ipv4?
[23:03] <notthistime> ipv6 was set to ignore. changed to DHCP
[23:04] <notthistime> it works on 0.0.0.0:8080