[03:30] is there a /var/mail directory in 16.04? [03:31] Hey All, anyone had issues with Samba 4.3.11-Ubuntu on Ubuntu Server 14.04.4 and being able to Read/Write Data from Windows Clients? ""An Unexpected Network Error has occurred"" [03:31] log.smbd - http://paste.ubuntu.com/23336705/, log. seeing a tonne of - http://paste.ubuntu.com/23336648/ [03:36] are /var/mail and /var/spool/mail somehow linked? [03:37] i deleted a file in var/mail and the same file gets rmed from /var/spool/mail. but i cant tell that there is a symlink or anything [03:38] oh, I fuound it [03:38] looks like /var/spool/mail is a symlink to /var/mail [04:22] How can I have execute permissions on my files in an NTFS drive? Can't I use it as my /home ? [06:01] do you guys prefer to run LTS or non-LTS for your servers/ [06:17] Gorian: I only use LTS, but it is personal preference really. Depending if you *need* newer packages. [06:22] hmm.. okay === _ruben_ is now known as _ruben [06:27] Gorian: and depending on your scale of course [06:27] upgrading every 6-9 months can be a headache [06:27] that's a good point === tinwood_ is now known as tinwood [09:44] Hi [09:45] my user is in the group www-data, ownership of /var/www/html is www-data:www-data, why I don't have permission to execute "touch myfile.txt" in this directory ? [09:46] what are the permissions on /var/www/html? [09:47] sorry, my bad, chmod g+w fixed it [09:48] :) [09:50] maxagaz: investigate the bsdgroups mount option; with that you can setgid on the directory, and all new files/directories in a setgid directory will get the group ownership set correctly === caribou_ is now known as caribou === gnuoy` is now known as gnuoy === _degorenko|afk is now known as degorenko [13:45] ddellav, coreycb`: creating stable/newton branches in all git repos now [13:45] jamespage, sounds good [13:47] jamespage, I have a pull-uca-source script working. think I should push this to ubuntu-dev-tools? http://paste.ubuntu.com/23338714/ [13:50] coreycb`, I don't see why not [13:51] jamespage, ok doing that now then === coreycb` is now known as coreycb [14:00] jamespage, zul, ddellav: I pushed pull-uca-source to ubuntu-dev-tools: http://bazaar.launchpad.net/~ubuntu-dev/ubuntu-dev-tools/trunk/revision/1451 [14:00] coreycb nice [14:00] coreycb: sweet === Ussat is now known as They-All-Suck-20 === They-All-Suck-20 is now known as They-suck-2016 === mfisch` is now known as mfisch === mfisch is now known as Guest56218 === They-suck-2016 is now known as VoteCthulu2016 === baggar11_ is now known as baggar11 === MrBIOS_ is now known as MrBIOS === Guest56218 is now known as mfisch === mfisch is now known as Guest8770 === Guest8770 is now known as mfisch === dames is now known as thedac [16:31] rbasak: still around? [16:34] powersj: o/ [16:34] rbasak: there are 4 heimdal bugs all reporting install failures because of version mismatches. [16:34] thoughts on adding to backlog? [16:35] Are they using yakkety-proposed by any chance? [16:35] all four have the tag "package-from-proposed" [16:35] Dupe of bug 1617963? [16:35] bug 1617963 in heimdal (Ubuntu) "package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured because libasn1-8-heimdal:i386 is at a different version (1.7~git20150920+dfsg-4ubuntu1)" [Undecided,Invalid] https://launchpad.net/bugs/1617963 [16:36] Looks like yakkety-proposed has not yet been cleared for SRUs. [16:36] So using yakkety-proposed is currently still wrong. [16:36] Though that's interesting, because I wonder if that's a problem for users? [16:37] * rbasak asked in #ubuntu-devel [16:39] rbasak: looks like the version each is trying to install is in fact the one from proposed. [17:00] coreycb: ping [17:12] zul, coreycb: any reason why we can't make the pylxd integration tests run in autopkg test [17:13] jamespage: no [17:13] jamespage: ill open up a bug to remind me [17:14] jamespage: #1634207 === degorenko is now known as degorenko|afk [18:03] Noticed 4.4.0-43 kernel has added in xenial-updates on 10-14-2016. But the same didn't get added in trusty-updates. Does anyone know whether it is expected? === nodouble` is now known as nodoubleg [18:46] basilAB: new kernels are added to the repos, but not installed automatically. If you (really) need the new kernel with its new features (read the changelog), just apt-get install it [18:47] or apt install it, if you prefer the new method === alexisb is now known as alexisb-afk [19:02] RoyK: I was looking at the trusty-updates repo and not seeing the 4.4.0-43. Still can see only 4.4.0-42. === med_` is now known as medberry [19:03] basilAB: oh - I see - possibly some mirrors being out of sync [19:04] In xenial-updates, I can see the latest though. Yeah, may be a sync problem [19:05] I am running trusty lxd containers on top of Xenial with 4.4.0-43. To install new packages on trusty, some of dependencies are failing because of this. [19:09] doesn't look like a mirror sync issue - there's no 4.4.0-43 upload on https://launchpad.net/ubuntu/+source/linux-lts-xenial either === alexisb-afk is now known as alexisb === med_ is now known as Guest62846 [20:42] smoser: you still the right person to poke about maas-images? Need a merge to fix arm64/yakkety - https://code.launchpad.net/~dannf/maas-images/xgene-uboot-compressed-images/+merge/308515 [20:46] dannf, myself or ltrager [20:46] i am ok with that change, i assume you've tested ? [20:48] smoser: i've built trusty & yakkety images and verified that the image has the correct metadata in each case. i have not pointed a maas server at a custom stream w/ it (maas server w/ those systems is production) [21:09] dannf, merged [21:10] smoser: thx! [22:20] hi, anybody running 14.04 on a proliant DL585? [22:21] this box has s 4 ports nic loadind the e1000 module, but then only one port is recognized per adapter [22:21] 2xquad nics pci-e [22:21] the weird this is that ifconfig -a shows 8 eth [22:22] but then I get no link on any of them [22:24] drab_: never seen that - I've used ubuntu with quad e1000 cards, and it's worked well [22:25] drab_: does ethtool tell you anything about link status? [22:25] the weird thing is that in both cases it's the top port that works, the bottom 3 don't on either [22:25] checking that, was trying with mii-tool [22:28] RoyK: it gives the same exact info as the ones that work minus Link detect: no [22:28] switch config correct? [22:28] snd speed/duplex set to Unknown [22:29] drab_: tried bringing the interface up to see if that does anything? [22:29] yeah I even tested taking out the cable of the nic that works [22:29] and putting into the one that does't, no joy [22:29] so port/cable is not the issue [22:29] what happens if you do an ifconfig ethx up? [22:31] I need a /dighole alias I guess... === yoink_ is now known as yoink [22:31] RoyK: it worked. I don't get it tho [22:32] why wouldnt' the light on the card come up? I don't think I've seen that before [22:32] drab_: pastebin /etc/network/interfaces, please [22:32] I get tyhat an interface may not come up if you don't configure it, but the link should still show I thought [22:32] even if the itnerface is unconfigured [22:33] RoyK: it only has the two interfaces that were working [22:33] I guess my problem is that I assume link light should have shown regardless [22:33] ok, add some more ;) [22:33] will you be trunking some of these? [22:34] nah, gonna run 8 VMs, each one gets one [22:34] well, 7 [22:34] one for the host [22:34] erm - why? wouldn't VLANs be easier? [22:35] just setup a trunk and VLANs and so on [22:36] RoyK: pardon my ignorance, why is it easier? [22:37] drab_: it's not necessarily easier, but it's far more flexible and will give you more bandwidth to the switch [22:37] drab_: and perhaps you learn a thing or two on the way ;) [22:38] I'm always up for learning, but I'd need at least a pointer, right now I' [22:38] m having issues to even see how that'd work [22:38] given your switch supports VLAN, that is... [22:39] sure, it does, it's hp 2626, I'm using vlans on another that's the same model [22:41] you'd trunk 8 ports and put them on their own vlan and then the VMs would get an ip on that trunked host interface? [22:43] I'd use 802.1Q between the host and the switch with as many ports as you might need and then allocate VLANs where needed - usually VMs can be on the same VLAN without issues unless there you need to isolate them due to security [22:44] if the uplink on the switch isn't 10G, or perhaps just a few gigs, it doesn't make sense to use too many links in the trunk [22:45] don't put VMs on separate VLANs unless they're on separate IP (v4 or v6, doesn't matter) networks === tsimonq2 is now known as simon-says === simon-says is now known as tsimonq2