[02:04] <EmilienM> coreycb: I found out why aodh fails
[02:04] <EmilienM> alembic.ini is missing
[02:06] <EmilienM> coreycb: actually no, neverming. I have another issue now
[02:14] <EmilienM> coreycb: I found the bug
[02:14] <EmilienM> I had to do cp -r /usr/lib/python2.7/dist-packages/aodh/storage/alembic /usr/lib/python2.7/dist-packages/aodh/storage/sqlalchemy/
[02:16] <EmilienM> coreycb: https://bugs.launchpad.net/cloud-archive/+bug/1533014/comments/4
[02:16] <ubottu> Launchpad bug 1533014 in Ubuntu Cloud Archive "aodh can't be installed" [High,Fix committed]
[02:41] <fibes> about to do a large scale migration about 20k servers to ubuntu corp mandate after we were bought out by another company
[02:41] <fibes> i dont understand it because we are already running debain seems backwerds someone help prove me wrong
[02:42] <fibes> the main point being steady release cycles and LTS, is that not avaialble else where?
[02:43] <sarnold> in some sense, debian "invented" the LTS idea with years between releases.. they do better these days :)
[02:43] <fibes> im excited for something new but seems like alot of work for what value
[02:43] <fibes> never having used it on an enterprise level only in home
[02:43] <sarnold> there's plenty of choice in the LTS release world though -- debian's usual releases, ubuntu LTS releases, SLES, RHEL, Centos (RHEL rebuilds)
[02:46] <fibes> i was reading that spotify did this, maybe its a trend in large companys
[02:47] <sarnold> could be;
[02:48] <sarnold> ubuntu says they'll support the packages in main for five years; with debian, you don't know how long it'll be. rhel, sles, cost a fair chunk of change.. centos is free, but not much inthe way of support
[02:48] <tarpman> fibes: I have some sympathy for the idea that the entire company should be on the same platform, but for the record, debian also introduced LTS these days -> https://wiki.debian.org/LTS
[02:49] <fibes> i think that was just introduced maybe that decided in that window before
[02:49] <fibes> all the dev guys seem happy, not us admins that have to do the work
[02:49] <tarpman> the official announcement was april 2014, maybe your decision happened before then
[02:51] <fibes> o wow  yea that was awhile ago now, who knows when the suits had meetings
[03:02] <fibes> i just hope alot of things dont change, logging locations etc because we havge so many script already written that help out day to day support
[03:03] <fibes> while its probably more an nsd thing i noticed aolserver is now looged with aolserver4
[03:03] <fibes> we are at 8.40 deb
=== stevenroose|BNC is now known as stevenroose
=== cpaelzer is now known as cpaelzer_afk
=== cpaelzer_afk is now known as cpaelzer
=== med_ is now known as Guest77121
[08:30] <Blinkiz> Hello. I have hardware LSI raid 6 currently on 16TB. It will grow up to 100TB within a couple of years. Am in no need of partitions on this volume, can someone point me in a direction about the discussion if placing a filesystem directly on the volume is bad or not?
=== cpaelzer is now known as cpaelzer_afk
=== cpaelzer_afk is now known as cpaelzer
=== Lcawte|Away is now known as Lcawte
[09:16] <lordievader> Good morning.
=== Lcawte is now known as Lcawte|Away
=== cpaelzer is now known as cpaelzer_afk
[11:23] <OlofL> someone can help setting up snmp v3 on ubuntu server 14 ?  https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-an-snmp-daemon-and-client-on-ubuntu-14-04 this guide and I cannot  create a user with snmpusm. I dont get the user successfully created msg
=== cpaelzer_afk is now known as cpaelzer
[13:01] <EmilienM> coreycb, jamespage: I talked with zigo, and the aodh issue https://bugs.launchpad.net/cloud-archive/+bug/1533014/comments/4 is in Debian. He's currently building a new package. Once it's done, can I ping you so you update 'proposed' ?
[13:01] <ubottu> Launchpad bug 1533014 in Ubuntu Cloud Archive "aodh can't be installed" [High,Fix committed]
[13:20] <dencaval> Hey guys, I'm also having the issue: https://bugs.launchpad.net/maas/+bug/1499934 . Is there some workaround?
[13:20] <ubottu> Launchpad bug 1499934 in MAAS "Power State could not be queried (vmware)" [High,Triaged]
[13:25] <rbasak> dencaval: if you don't get an answer here, try #maas
=== cpaelzer_ is now known as cpaelzer_afk
=== cpaelzer_afk is now known as cpaelzer_
[13:48] <dencaval> rbasak ok
[15:22] <teward> was there a server team meeting yesterday that I missed, or...?
[15:34] <rbasak> teward: it didn't happen.
[15:34] <teward> cool.
[16:11] <mastahh|work> Hi guys. Has anyone utilised Heartbeat in a production environment before to configure two servers as a HA pair?
[17:04] <iamnotgreg> I'm trying to open a port for a server that is running on my localhost so that it is accessible on my network. What do I need to do? My google skills are weak
[17:06] <tarpman> iamnotgreg: http://portforward.com/
[17:07] <iamnotgreg> tarpman: I don't need to set it up for wan...just my local network
[17:08] <tarpman> iamnotgreg: what's preventing it from working right now? some kind of firewall on your server?
[17:19] <iamnotgreg> tarpman: so I ran netstat and see that the port is open on my localhost...however when I use nmap and scan my localhost I don't see the port as being open. Additionally, when I try and scan my ip within the network there is no port open. I want to forward that port for my network to the port for my localhost
[17:19] <iamnotgreg> tarpman: I'm trying to add hylafax to my network
[17:21] <tarpman> iamnotgreg: maybe you want https://wiki.debian.org/HylaFax#Configuring_Network_Faxing
[17:22] <iamnotgreg> tarpman: I did that...but before I try to add people to the network, shouldn't I be able to see the port open on my computer?
[17:24] <tarpman> iamnotgreg: check the BINDTO setting in /etc/default/hylafax
[17:24] <tarpman> iamnotgreg: cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561253
[17:24] <ubottu> Debian bug 561253 in hylafax-server "hylafax-server: /etc/default/hylafax leads to wrong usage of BINDTO parameter" [Normal,Open]
[17:27] <iamnotgreg> tarpman: then just restart the server I guess?
[17:28] <iamnotgreg> I mean the hylafax server...not the computer
[17:28] <tarpman> probably
[17:28] <iamnotgreg> tarpman: this will allow other computers on the network to communicate with the sevrer?
[17:29] <tarpman> iamnotgreg: I don't know, sorry. I have never installed or run hylafax, and I don't have time to right now
[17:29] <tarpman> iamnotgreg: I'm just throwing out guesses based on brief googling and experience with other packages
[17:29] <tarpman> if that's not helpful, I'll shut up :)
[17:29] <iamnotgreg> lol. thanks
[17:31] <tarpman> iamnotgreg: basically, read the man page for hylafaxd, and see what arguments the init script actually invokes it with (specifically -l, if present), and update your configuration until the init script runs it the way you need it to be run :)
[17:33] <iamnotgreg> Hey I just restarted my comp and lost records of where it was that I made the suggested modification.
[17:33] <iamnotgreg> Can you tell me what the file path was again?
[17:37] <tarpman> /etc/default/hylafax ?
[17:38] <iamnotgreg> tarpman: yes...was there a file too?
[17:38] <tarpman> that is a file
=== tomaw_ is now known as tomaw
=== ubuntu is now known as Guest53713
[19:06] <arges> hallyn: fyi your libvirt SRU to wily needs to be rebased on a security update (unless you're ok with me doing that)
=== nodouble1 is now known as nodoubleg
[19:27] <hallyn> arges: please go ahead
[19:42] <henkjan> the last libvirt update on wily stopped al my virtual machines on updating
[19:54] <arges> henkjan: where did the wily upload go?
[19:54] <arges> henkjan: sorry
[19:54] <arges> hallyn: ^^
[19:56] <arges> hallyn: and if you have a debdiff lying around that would help most
=== hxm- is now known as hxm
[20:45] <hallyn> henkjan: which version exactly?
[20:51] <henkjan> hallyn: 2016-01-13 11:00:58 status installed libvirt-bin:amd64 1.2.16-2ubuntu11.15.10.2
[20:52] <hallyn> henkjan: ok - the security update then.  Thanks, I will look into it
[20:52] <hallyn> henkjan: did you file a bug?  (if not, could you, to collect info?)
[20:54] <henkjan> hallyn: did not yet file a bug. i'll do it now
[21:00] <arges> henkjan: also if you can note the last version which worked properly that may help identify where the code change was introduced. Thanks
[21:00] <stevef> hi, i have looked all over the web and i simply cannot figure out how to get a fresh 15.10 server installation connected to wireless. it did during installation, and now i can't, i tried modifying /etc/network/interfaces in a bunch of ways, it just won't and iwconfig gives me wlp3s0 instead of wlan0 (i saw online it is new naming method); anyhow, it seems impossible to connect this even though it did during instalation; please h
[21:02] <teward> if I have a question regarding the Ubuntu Server QA stuff, that's for the QA contact during the next Server Team meeting, yes?  Or is it under Xenial Development?  (Adding something to the agenda)
[21:07] <RoyK> stevef: what sort of NIC is this?
[21:08] <stevef> a d-link wireless pci
[21:09] <henkjan> hallyn: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1533839
[21:09] <ubottu> Launchpad bug 1533839 in libvirt (Ubuntu) "vms shutting down on libvirt upgrade" [Undecided,New]
[21:09] <hallyn> thanks
[21:10] <stevef> i even tried with a dlink usb dongle
[21:10] <RoyK> stevef: what chipset?
[21:12] <RoyK> stevef: pastebin output of 'lshw', please
[21:13] <stevef> i can't pastebin it's a native install
[21:15] <sarnold> hallyn: odd that the apparmor profiles are unloaded :/
[21:18] <stevef> AR2413/AR2414 Wireless Network Adapter [AR5005G(S) 802.11bg]
[21:18] <stevef> and it names it wlp3s0
[21:21] <stevef> lshw tells me all three networks are disabled
[21:22] <stevef> says driver=ath5k driverversion=4.2.0-16-generic
[21:23] <teward> matsubara: ping
[21:23] <teward> (if you're busy, no rush)
[21:23] <matsubara> teward, hi
[21:24] <teward> matsubara: so, a question came to me re: Server ISO testing, and the lack of 32bit tests.  Apart from the person asking me about it being slightly naggy and annoying, trying to get an authoritative answer regarding why there's no 32bit ISO tests for Server, so I can get them off my back
[21:24] <teward> s/back/[censored]/
[21:24] <teward> balloons said that those tests were killed off, and it's up to the 'owner' of the ISO tests/release to provide or not provide them, rbasak pointed me to you for better input / reply to the inquiry
[21:25] <teward> basically: why are there no 32bit Server ISO tests in QA, and if they were killed off is there a detailed reason as to why
[21:26] <matsubara> teward, It's in my todo list to have those moved on to the server team CI infrastructure. I don't know the reason for not having 32bits tests. AFAICT, I'll move on to the server CI infrastructure only the existing tests
[21:27] <matsubara> teward, sorry if this doesn't answer your question.
[21:27] <teward> matsubara: explains it well enough for me, but if there's not an answer, i'll fall back to balloons' statement that "No test cases were provided, therefore we don't have them."
[21:27] <teward> and then the one person trying to get a clear answer can just sit there with a non-answer
[21:27] <teward> since there's no clear answer that I've been able to find
[21:28] <teward> IMO the test cases are identical, but I think servers run amd64 moreso than 32bit now, no?
[21:28] <teward> and those that aren't can still install the ISOs or run the tests themselves without testcases and id bugs
[21:29] <matsubara> teward, Yes, I think that's fair to say. Basically anyone running the server ISOs are likely to be running the amd64 ones
[21:30] <sarnold> 32bit might still be popular on e.g. m1.tiny, where 4 vs 8 bytes for pointerrs might make a difference
[21:30] <matsubara> and if there's a reasonable need for 32bit tests then we need to hear about it
[21:30] <teward> matsubara: might I suggest then that you reach out to phillw and take his concerns?
[21:31] <stevef> royk are you still here? :S
[21:31] <matsubara> sarnold, aren't those using the cloud images rather than the isos to install? I think those are tested in a separate infrastructure
[21:31] <teward> i'm usually the last one to ISO test - only reason I did so recently was to trace backwards an issue that originated on Lubuntu's alts, which we confirmed happened on our dailies too
[21:31] <RoyK> stevef: almost - -14°C outside so I'm thawing
[21:32] <sarnold> matsubara: probably. isos seem so quaint ;)
[21:32] <RoyK> bloody russians sending their high pressure systems to us again
[21:32] <teward> matsubara: though, I'm happy to tell phillw that if he has a specific reasonable need he should poke the server team in a meeting or via the ML
[21:32] <teward> if you have no issues with that, of course
[21:33] <stevef> :P
[21:33] <balloons> matsubara, perhaps it's enough to simply add the tests back to the 32-bit images; while not requiring any of them
[21:33] <tsimonq2> teward: and it was turned off because technically Ubuntu has no more support for i386 server
[21:33] <balloons> we can mark every one as optional
[21:33] <tsimonq2> AFAIK
[21:33] <RoyK> stevef: what up?
[21:33] <teward> matsubara: i wouldn't mind seeing i386 tests, but have them as Optional non-mandatory tests
[21:33] <stevef> i can't pastebin it's a native install
[21:33] <matsubara> teward, yep, that sounds reasonable. Ask him to reach out to me or the server ML or join the weekly meeting. we can discuss there. It'll give the opportunity for the rest of the server team to reply back as others might have better knowledge of the reasons we don't have such tests
[21:33] <teward> basically, voluntary ones
[21:33] <coreycb> jamespage, zul: can one of you sponsor the debdiff at the end of bug 1533014 ?  it's a hot one for EmilienM
[21:33] <ubottu> bug 1533014 in Ubuntu Cloud Archive "aodh can't be installed" [High,Fix committed] https://launchpad.net/bugs/1533014
[21:33] <stevef> AR2413/AR2414 Wireless Network Adapter [AR5005G(S) 802.11bg]
[21:33] <teward> to quote balloons there
[21:33] <stevef> and it names it wlp3s0
[21:33] <stevef> lshw tells me all three networks are disabled
[21:34] <teward> matsubara: though, i will also make a note to these logs here, so he can see our discussion on it here
[21:34] <stevef> lshw tells me all three networks are disabled
[21:34] <EmilienM> coreycb: appreciate your help, thanks
[21:34] <RoyK> teward: https://wiki.debian.org/ath5k
[21:34] <RoyK> perhaps
[21:35] <stevef> thank you, will check that; what i find odd is that it connected and everything was well during installation, and now, nothing works :S
[21:36] <teward> matsubara: though, i will also make a note to these logs here, so he can see our discussion on it here, and will suggest poking the ML or joining the meeting
[21:36] <teward> RoyK: mishighlight
[21:36] <ianorlin> I think the alternate for 32 bit makes more sense for lubuntu though on really old machines
[21:36] <RoyK> stevef: then possibly a kernel argument may help
[21:36] <RoyK> teward: sorry
[21:36] <teward> RoyK: no harm done :)
[21:37] <ianorlin> yeah even if you were say runninng a virtual machine of a server it is a lot easier to get hardware virtualization extensions needed for 64 bit and it will be orders of magnitudes faster
[21:38] <arcsky> in resolv.conf there is search domain.test . is that dns suffix ? or what dhcp option is that ?
[21:38] <bekks> arcsky: that option is most likely provided by your DHCP server.
[21:39] <sarnold> arcsky: that means when you try to resolve e.g. "google.com" your resolver will first try to resolve "google.com.domain.test." before trying "google.com."
[21:39] <arcsky> bekks: yeah but which option is that ?
[21:40] <arcsky> i think its option 119 or 15
[21:40] <teward> matsubara: any objection to me adding it to the schedule for discussion anyways, even if only briefly?
[21:41] <teward> to bring attention to the fact it was brought up to a server team member
[21:41] <bekks> arcsky: Just take a look at your DHCP server, which option is being used.
[21:41] <matsubara> teward, no objection at all
[21:41] <teward> matsubara: then i'll add it under the QA section, on the tracker.  thanks again.
=== Lcawte|Away is now known as Lcawte
=== _thumper_ is now known as thumper
[22:04] <stevef> royk: i have managed to get it connected by doing [sudo ifconfig enp0s24 up] and changing its name in interfaces... but how do i get it to do "up" automatically when computer starts? otherwise it will never connect :S
[22:05] <stevef> i will then try and figure out the wifi part, but first step is to get it to enable automatically upon startup :S
[22:05] <sarnold> add 'auto' to the /etc/network/interfaces stanza
[22:06] <stevef> it's already at auto... but i'll verify that it wasn't because of the new name system thank you sarnold
[22:06] <sarnold> ahh
[22:15] <stevef> i also keep getting disconnected from here so i do not see all responses :S but lshw always tells me they are disabled when i start the computer; interfaces is set to auto.
=== Lcawte is now known as Lcawte|Away
[22:26] <stevef> cannot bypass "interface not configured" in ifdown
[22:27] <bekks> stevef: because an unconfigured interface cant be downed.
[22:27] <bekks> stevef: can you pastebin your /etc/network/interfaces again please?
[22:29] <stevef> i cannot pastebin it's a native install in terminal; i have: auto lo / iface lo inet loopback // auto wlp3s0 / iface wp3s0 inet dhcp / wpa-ssid xxxxx / wpa-psk xxxxx
[22:32] <genii> !pastebinit
[22:32] <ubottu> pastebinit is the command-line equivalent of !pastebin - Command output, or other text can be redirected to pastebinit, which then reports an URL containing the output - To use pastebinit, install the « pastebinit » package from a package manager - Simple usage: command | pastebinit -b http://paste.ubuntu.com
[22:32] <stevef> right, but it's not connected to the net
[22:32] <stevef> which is the main issue
[22:37] <stevef> and also, problematic, to get it connected, via my laptop and a bridge, i need to modify the network/interfaces and do ifconfig xxxx up ...
[22:41] <stevef> http://paste.ubuntu.com/14491402/
[22:41] <stevef> bekks: http://paste.ubuntu.com/14491402/
[23:00] <stevef> still there?
[23:02] <TJ-> stevef: syntax error: "allo-hotplug"
[23:02] <TJ-> stevef: and again "iface wp3s0"
[23:04] <stevef> yes, it's on
[23:04] <stevef> ...? i'm not sure i understand what you recommend me to add/modify!?
[23:04] <TJ-> stevef: it should be "allow-hotplug ..." and "wp3s0" should be "wlp3s0"
[23:06] <TJ-> stevef: you can use "ifquery --all" to check the configuration
[23:11] <stevef> HS!!!!!! a typo i was unnable to notice.. O.O
[23:11] <stevef> i've spent 5hours on this, because of a typo!!!! O.O ..... anyone know why they changed the default wlan0 etc.... to these new names? :S
[23:12] <stevef> btw THANK YOU tj thank you very much... with the small font i don't know how long it would have taken me, thank you so much
[23:14] <TJ-> stevef: the init system changed the interface naming for more machine-consistent naming to avoid the arbitrary mess there was previously for discovery/hot-plug
[23:14] <Schalla> For KVM, there is any recommended hdd type?
[23:14] <Schalla> Or is the qcow2 default reasonable?
[23:14] <TJ-> Schalla: I use qcow2 since it supports overlays
[23:15] <TJ-> Schalla: it depends on your use-case; LVMs are also a good option
[23:17] <Schalla> TJ-: Setting up KVM the first time, so many options... ^^
[23:17] <TJ-> Schalla: yes, it is very configurable :)
[23:17] <Schalla> Considered to get the Ubuntu Server Guide
[23:17] <Schalla> *Book
[23:17] <TJ-> although techically KVM isn't; it's QEMU that is
[23:17] <Schalla> True
[23:31] <RoyK> stevenroose|BNC: add "up blbla" after the iface line somewhere in the interfaces file
=== JanC_ is now known as JanC
[23:36] <Schalla> RoyK: I found the reason for the issue I had yesterday before I had to go, I got the hint in another channel to blank out the superblock with dd
[23:37] <Schalla> and it worked after that. Didn't expect that^^
[23:49] <RoyK> Schalla: it usually works if things are messed up
[23:52] <Schalla> RoyK: Yeah, I just start to worry when there is not even a error message^^
[23:59]  * RoyK worries if temperatures will drop under -20 tomorrow