User1: hi I'm trying to run tshark remotely over ssh to pipe to my local wireshark, I'm getting an error that I do not have permission to the device? I've created the wireshark group, added myself to it, reconfigured the package, and I get a permission error relating to the device. How do you grant permission to a device? There is nothing in udev either which is strange...
User2: User3 User20  hm, is libvirt on xenial working for you? I get
User2: Feb 16 19:03:53 sl libvirtd[2705]: Cannot set property Before, or unknown property.
User2: Feb 16 19:03:53 sl libvirtd[2705]: Cannot open log file: '/var/log/libvirt/qemu/cdboot.log': Device or resource busy
User2: (which i've seen mentinoed in a bug somewhere)
User2: iirc it was a systemd machinectl problem
User2: hm, i'l lhave to look into it tomorrow
User3: hallyn_, Not sure I had been trying to do boots from CD. I'll check. Sounds a bit like either missing file or something wrong with aa profile(s)
User4: Good morning.
User5: not sure what happened, but most of my server's services stopped connecting. znc, apache, owncloud
User5: and oddly, my server and desktop are connected to the same router, and my desktop can ssh in to the server, and the desktop can browse the web, but my server can't ping google.
User5: the default gateway for both machines is the same
User6: User5 how are you trying to ping google?
User5: ping google.com
User6: User5 try ping 91.69.162.6
User6: it that works, DNS is probably not working for you
User5: that doesn't work
User6: what happens when you try?
User4: Does pinging the gateway work?
User5: that's so messed up. It's not doing anything
User5: yes, I get a response from the gateway's lan ip
User4: User5 What is the output of 'ip r'?
User5: default via 91.69.162.6 dev eth0
User5: 5202398459 via 91.69.162.6 dev tun0
User5: 91.69.162.6 dev tun0  proto kernel  scope link  src 91.69.162.6
User5: 5202398459 dev eth0  scope link  metric 1000
User5: 5202398459 dev eth1  proto kernel  scope link  src 91.69.162.6
User5: 5202398459 dev eth0  proto kernel  scope link  src 91.69.162.6
User4: !paste
User7: For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic.
User4: I suppose you do dhcp?
User5: yes, static dhcp from the router
User4: Does the gateway run a firewall which is dropping icmp by any chance?
User5: I believe so
User5: checking
User5: well, it's not set to ignore or forbid, but icmp-flood attack filtering is enabled
User5: oh dammit. that's it, isn't it. how did you figure that? the only thing I've changed recently is stats in the router, and didn't notice that icmp-flood filtering is only enabled with stats.
User4: I guess I can conclude from this that you have access to the gateway? Can you ping 91.69.162.6 from there?
User5: correct. ping from router works
User4: Odd. Well perhaps it is that. Can you ping 91.69.162.6 from the problem host when the icmp-flood filtering is disabled?
User5: oh udp-flood and tcp-syn-flood filtering too
User4: That shouldn't matter for ping ;)
User5: lol. and my server is on blocked list
User5: in router. no it's like my router is seeing too many icmp packets and cutting off the server
User5: one sec though. I'll disable and test
User5: yeah, as soon as I remove the server ip from the blocked list, it starts working again.
User5: so the router is seeing too many of some packet type
User4: Heh, and the firewall strikes once again ;)
User5: thanks for the help. I made some changes, and know where to look if it happens again.
User8: hey! is there any know Juju bug regarding network interfaces not named eth?
User4: User8 What version of Ubuntu is this?
User9: going to need to be more specific than "a bug regarding network interfaces not named eth"
User10: how large is the size of a mirror, without sources, for 14.04 ?
User10: only 64bit btw
User8: lordievader 14. should we use 15?
User4: User8 No, I was asking since 15.10 uses a newer version of udev which uses bios dev names instead of the old naming scheme. Perhaps the udev of Trusty got updated to the same version though.
User4: User8 What kind of network names do you have now?
User3: hallyn_, As a follow-up on libvirt: I can boot kvm guests via libvirt. I realized that "cdboot" would be your guests name. I'd check whether /var/lib/libvirt/qemu is a directory owned by libvirt-qemu.kvm and writable at least for that user.
User8: lordievader VLAN
User4: User8 What? We were talking about interface names right?
User8: lordievader well it might be, I have no idea, but what I know is that with eno1 juju basically fails
User4: User8 Well look on Launchpad if this has been reported before, else make a new bug report.
* ChanServ changed the topic of #ubuntu-server to: Ubuntu Server discussion and support | For general (not server specific) support, try #ubuntu | IRC Guidelines: https://wiki.ubuntu.com/IrcGuidelines | https://wiki.ubuntu.com/ServerTeam/GettingInvolved | Docs and resources: https://help.ubuntu.com/14.04/serverguide/ | Updates for CVE-2015-7547 have been released: http://www.ubuntu.com/usn/usn-2900-1/
User11: Silly question, but after installing a fresh ubuntu-server and assigning a static IP and nameserverâ¦ where is the nameserver saved? Should it be in /etc/netwrok/interfacesâ¦ because I do not see it thereâ¦?
User12: I have a Lenovo ThinkServer running 14.04 LTS. I'm trying to get the health of its primary drive raid, but I get: https://gist.github.com/freeone3000/4cc6e1633f22796de875 . (The server has a hardware raid controller with two SATA drives connected as SAS)
User12: jelly-home: "04:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS 2108 [Liberator] [1000:0079] (rev 05)"
User11: Ah okay, /etc/network/interfaces is the correct thing
User13: hi, i'm trying to test out SingleSignOn was going through the instructions and just wanted to ask about faking the domain names, if i put the server down in the /etc/hosts files, is that loopback for the server itself and the server's LAN ip on the clients?
User12: jelly-home: Always prints "ioctl: no such device", but man pages say it doesn't take an argument and should autodetect.
User12: Did the autoload bit, tried specifying '-u /dev/sda' and '-u 0:40' but no change.
User14: jelly-home: look at you :)
User15: jgrimm, cyphermox: Any idea if docker on 16.04 will be compiled with golang (other than gccgo) for ppc64el?
User16: leitao, the plan is to build docker1.10 with golang-1.6 for most architectures including ppc64el
User15: thanks
User16: leitao, do you have a preference on technical merits?
User15: jgrimm, that is what we need. Thank you!
User15: 1.9 seems to have some issue
User15: jgrimm, btw, any chance to move docker from universe to main?
User16: leitao, no plans to do so
User15: jgrimm, it means docker is not supported by Canonical, right?
User16: leitao, community supported is the way its described -> https://help.ubuntu.com/community/Repositories/Ubuntu
User17: anyone have suggestions for something like Crashplan which has a Linux client?  I really liked Crashplan, until they decided to change their pricing structure and doubled everything since I last renewed 4 years ago...
User18: User19 not sure if you saw, but i updated the numactl merge reuqest yesterday
User18: if you could ack, that'd be great
User12: User17 tarsnap
User17: freeone3000, hm that's one I have not heard of before
User19: User18 what's the url again?
User19: User3 uh, no, nothing to do with cds.  my old windows vista vm also doesn't start
User18: User19 one sec, https://code.launchpad.net/~nacc/ubuntu/+source/numactl/+git/numactl
User18: merge branch
User19: User3 "Cannot set property Before, or unknown property." is the critical line I think.  (or I'm wrong and it's a red herring :)
User3: hallyn, hm odd. me and arges did notice no such errors.
User20: User19 is this only with windows guests?
User19: User20 no
User19: User20 User3 it probably ha snothing to do with libvirt itself, though, bc it seems to be a dup of https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079
User7: Launchpad bug 1529079 in systemd (Ubuntu) "Can't start virtual machines after upgrade to Xenial" [High,Confirmed]
User20: User19 i take a look.. my uvtool vms have been working fine
User19: User18 thx, lemme do that right now
User3: arges, and I was using virt-manager. Only difference is that the host is a fresh Xenial install
User18: User19 thanks!
User19: User3 hold on;  fresh install did work, or did not work?
User3: hallyn, fresh install does work for me
User3: hallyn, you and the other reporter seem to use upgraded hosts
User19: User3 yup
User20: ok yea I have been using fresh xenial installs
User20: so we need some upgrade testing I suppose
User19: well that gives ideas of where to start looking at least, that's good :)
User19: bugs.debian.org is down?
User19: can the bot tell me about debian bug 814952 ?
User7: Error: Could not parse data returned by Debian:
User19: User18 is debian bug 814952 the one you filed ?
User3: hallyn, and since the other bug was opened last year it already happened with an earlier update of libvirt ...
User3: hallyn, hm you happen to use special args for libvirtd (which might be ignored by the old service conversion)? Though I do read the right file now
User19: User3 yes but it didn't hapen until i upgraded to xenial.  i *think*
User19: no special args,
User19: root      2705     1  0 Feb13 ?        00:00:00 /usr/sbin/libvirtd
User3: ok, well still allows for breakage with the xml definitions which would not be new
User3: hallyn, have you tried to virsh edit the config and do a small change then write it back
User3: validation is done for writes... though the error messages for that used to be poor
User19: User18 LGTM, wish i could see the debian bug, but th
User19: x
User19: User18 did you do a merge request against anything?  Should I just push the package to x?
User20: User19 can you dumpxml the faulty vm and pastebin it somewhere
User19: i'll object to "the faulty vm" :-)
User19: User20 just a min
User20: User19 well the one that libvirt cant parse
User20: and perhaps there is a qemu log somewhere to see if that cmdline it produced looks messed up
User19: User20 it can't parse any of several I had.  I deleted all but one, and created one new one.
User19: http://paste.ubuntu.com/15101328/
User19: User20 the logfile has : libvirt:  error : libvirtd quit during handshake: Input/output error
User19: User18 hm, having trouble building a source pkg
User19: why is debuild being stupid and trying to include .git?
User19: there msut be  a better way to build than to mv .git .. first
User19: that is to ohacky
User20: ok i'll look
User19: User18 ffs can't you file a debian bug to fix the pkging to be 3.0 quilt? :)  kills me
User19: anyway, pushing, thx
User18: User19 :) i can do that for the next release
User21: teward|: around but otp. Do you want to provide a summary here please?
User22: NP, teward. It happens all the time.
User19: User3 User20 all right, sorry, focusing on the libvirt thing now
User19: oh, one more thing first,
User20: User19 no problem, ive downloaded the xml files from you and the bug report, trying to look at what the differences are and repo on my end
User20: User19 ok no problem
User19: User20 saving xml works fine, sothat's not the problem
User19: lemme set up two vms, one with upgrade and one with clean install, and compare...
User20: User19 yea that's what I was trying to do, but hopefully that points us in the right area. wondering if its osmething to do with how the disk controllers are setup
User20: that would be my swag
User19: User20 wtf.  failed to reproduce in a vm
User20: User19 yea i'm not having luck here either.
User20: User19 what did you upgrade from? wily?
User19: User20 yeah, maybe i need to start from vivid, which my laptop apparently did
User19: (though not directly)
User19: i'll try from trusty - upstart->systemd seems more likely to e a trigger
User20: User19 ok
User19: User20 i think when we find the cause we're gonna laaaaaugh
User20: User19 : ) progres?
User19: wiating on the trusty vm install
User19: oh it's done
User20: User19 grabbing lunch... keep me posted
User19: k
User21: User23 extras is in universe, right? So no security team main concern about whether to follow Debian's import or take from nginx upstream.
User23: User21 correct - extras is in Universe
User23: User21 though, once dynamic modules are applied, we're going to have to scramble to make sure some are in Main, some aren't
User23: because it's not nice when that's taken into account
User21: User23 my remaining question would be about user visible differences. Is there a cost to committing to one over the other now? IOW, will any user have a reason to care if you take one approach now and switch later?
User23: (that's the future though)
User23: User21 AIUI, no, there won't be any major reasons for Users to care.  However, one reduces the plugin-specific future merge delta by one tiny commit, the other reduces it to zero when merging in from Debian
User21: If that's not a concern then I'd pick the easiest thing, which I guess you get to trade off. Following Debian is nice, but the benefit depends on how much we've diverged in this aresa.
User21: area
User23: mmm
User21: OTOH, cherry-picking a trivial patch may be far easier.
User21: That's what we'd probably want to do after FF anyway.
User23: User21 they're both available on git - patches are nice anyways :P
User23: indeed
User23: though, every new release of nginx will have to get an FF exception
User23: which is fine, but it's one of those annoying little headaches :)
User21: I thought we had an understanding with the release team on the plan? Or did that not get fully resolved?
User21: Keep ubuntu-release advised, certainly. I'm not sure if you need an explicit and formal FFe approval for each step though.
User23: i'm not sure we did since the policy change, the TB discussion was one fo "everything still gets standard FF review before upload" iirc
User23: User21 well, from this point on, each nginx will likely have some minor feature changes
User23: so it'd need FFe if standard policy is followed
User21: Ah, OK.
User23: plus HTTP/2 bugfixes which don't affect the builds currently
User23: (because it's not enabled)
User23: User21 i'm going to nitpick the minor change form upstream that enables building and doesn't implement an rc version of the third party module
User23: seems like the lesser evil
User21: OK, that sounds good. Thank you for considering carefully, as always!
User23: that's my job :)
User23: and thank you for being a sounding board and for the ongoing advice
User23: it's always nice to bounce opinions off others first :)
User21: np
User21: I forgot the other option was rc
User21: That makes your choice sound even better.
User23: mhm
User19: User20 hm, not reproduced in trusty vm either.  so i guess i'll have to look more closely at my own setup.
User19: fascinating
User20: User19 yikes, ok
User19: eureka
User19: User20 User3 systemd-machined, provided by systemd-container, is causing the problem
User20: User19 so your hunch in the bug earlier was corrupt
User20: correct
User19: accuse me of corruption?   I'll sue!
User20: haha
User19: yeah i just don't get why systemd-machined woudl ship in systemd-container.  that's weird
User19: mind you the bug may still actually be in libvirt
User19: but i find that hard to believe, as we're on 1.3.x
User19: anyway with that found i'll lower it's priority and defer it :(
User20: cool hopefully we can catch it before release
User24: arrrghhh
User24: are you there?
ubuntu-server
Ubuntu IRC