[01:04] <smoser> jtv, if/when you see this, you can ssh to<EMAIL_ADDRESS>(bounce through chinstrap). I've imported your launchpad ssh keys there.
[01:05] <smoser> you can poke around and see the issue, but basically, the following "should work" to get enlist the kvm node:
[01:05] <smoser>  xkvm --netdev maasbr0,macaddr=:01 --    -drive file=system-01.img,if=virtio -curses
[01:09] <roaksoax> smoser: you should made that availoable on a wikipage :)
[01:09] <smoser> ?
[01:10] <roaksoax> smoser: how you got MAAS working on canonicastack for it to enlist, dpeloy, etc
[01:11] <smoser> http://bazaar.launchpad.net/~smoser/maas/maas-pkg-test/view/head:/maas-ephemeral-test-quantal.txt
[01:11] <smoser> that is clsoe.
[01:11] <smoser> thats basically what i'm doing
[01:11] <smoser> and that has the maas server on the instance not in any sort of container.
[01:11] <smoser> i'd like to make it so that the maas server is in a lxc container.
[01:12] <smoser> i'll improve on that a bit more tomorrow.
[01:12] <roaksoax> awesome!
[01:14] <smoser> its pretty close.
[01:14] <smoser> and i hope to hvae some quantal images at least available that would work
[01:15] <smoser> the biggest hting i'm waiting on now for quantal is bug 643289
[01:15] <smoser> i have all the fixes i need collected at https://launchpad.net/~smoser/+archive/ephermal-fixes
[01:15] <smoser> but the mountall i'm wwaiting on slangasek for
[01:16] <smoser> and either getting that is required or i have to hack around it in cloud-init (i have that ready, but i'd rather have the moutnall fix)
[01:16] <smoser> good night.
[01:17] <roaksoax> ack
[01:17] <roaksoax> night scoot
[02:17] <jtv> smoser: got no access to <IP_ADDRESS>.
[13:07] <mgz> so, what I was doing before lunch,
[13:08] <mgz> when testing out schema migrations, is there an easy way to either trigger a rollback, or blow away the db, to go from scratch again?
[13:08] <mgz> the overhead of reverting a change, creating a new migration, applying that, then removing both is a bit pointless for test data
[13:09] <rvba> mgz: you can always rm -rf db && make sampledata
[13:10] <mgz> rvba: thanks, just what I was after
[13:10] <rvba> np
[13:28] <smoser> what daemon runs the tftp server?
[13:28] <roaksoax> smoser: pserv
[13:28] <roaksoax> maas-pserv
[13:30] <smoser> do you know what interfaces it binds to?
[13:31] <roaksoax> smoser: i think is the one with the address of MAAS_DEFAULT_URL
[13:31] <roaksoax> allenap: ^^
[13:32] <smoser> what is 'maas-dhcp/maas-dhcp-ip:' result in ?
[13:32] <smoser> the debconf value (that i added) ?
[13:34]  * allenap thinks
[13:34] <roaksoax> smoser: you mean maas-dhcp-addr?
[13:34] <roaksoax> smoser: tftp is different from dhcp
[13:35] <jtv> ¾ different in fact!
[13:35] <allenap> smoser, roaksoax: It listens on all interfaces, afaict.
[13:35] <roaksoax> smoser: thought maas-dhcp-addr should be the same as MAAS_DEFAULT_URL address IMHO since it is the same address that clients will contact, say for cloud-init meta-data server
[13:35] <jtv> dhcp currently listens on all, but is being fixed not to; dns didn't, but is being or has been fixed to listen on all interfaces.
[13:36] <roaksoax> jtv: the usage of series is because bigjools requested it instead of release, beside the fact of course that there's a release() function
[13:36] <jtv> I see.  Wish I'd known!
[13:37] <roaksoax> rvba: idk if you saw but I uploaded the branch that adds the distro_series support. So we can start adding tests :)
[13:37] <smoser> jtv, https://bugs.launchpad.net/maas/+bug/1047061
[13:37] <jtv> smoser: is that the one you were talking about?
[13:37] <jtv> The configuration problem you ran into?
[13:37] <smoser> see comment 1 there. that is what i was running into in https://bugs.launchpad.net/maas/+bug/1051626
[13:38] <smoser> right.
[13:38] <rvba> roaksoax: I've seen that indeed :).  As promised I'll give you a hand with the tests.
[13:38] <smoser> i'm not sure what '--ip' is supposed to mean to 'maas config_master_dhcp', but a.) i had thought it meant next-server b.) one way or another next-server is wrong.
[13:38] <jtv> roaksoax: Also, I was wondering: since recently, the master worker sends the list of downloaded installable images to the server.  Maybe that should ultimately become the source of the “choices” list for OS releases.
[13:39] <jtv> smoser: yeah, I thought that was a little unclear too.  The trick is to read it within the context of “dhcp”: “the IP address that serves DHCP.”
[13:39] <smoser> roaksoax, shoot. i did mean addr, but i was preseeding ip.
[13:39] <smoser> hm.. one way or another that is busted, but it should have done better.
[13:40] <smoser> jtv, but who cares what serves dhcp?
[13:40] <smoser> other than next server.
[13:40] <smoser> it seems broken that you're requiring both interface to listen too and ip address.
[13:40] <jtv> Good question.  I'm about as confused about this as you are.
[13:41] <roaksoax> jtv: right makes sense
[13:41] <jtv> roaksoax: not saying it has to be that way right now — in fact people might not even like it because it means you don't get offered any operating systems to install until you have some.  But something to keep in mind as an answer to one of my points.
[13:41] <roaksoax> smoser: liston to would be basically on what interfaces to listen DHCP requests, and ip address is the "next-server" isn't it?
[13:42] <jtv> No
[13:42] <jtv> Ah
[13:42] <smoser> roaksoax, i thought the same thing as you.
[13:42] <jtv> I think maybe it should be, but isn't yet.
[13:42] <rvba> next_server = get_maas_facing_server_address()
[13:42] <roaksoax> jtv: yeah, bigjools mentioned that he would like that to become data driven, but something to do in the future as it would require lots of changes
[13:42] <rvba> I don't see where that 'ip' is used in the code really… so I'm confused as well.
[13:42] <jtv> Maybe the ip is just the nodes-facing IP address of the cluster — which will _also_ be the tftp download address once we have proxies set up.
[13:43] <smoser> can i suggest that people actually try to use code they write?
[13:43] <smoser> rather than just assuming that if tests pass it works?
[13:43] <jtv> In which case, yes it would also be the next-server, but wouldn't actually function as one yet until we have tftp proxies.
[13:43] <rvba> jtv: that's what Julian had in mind indeed… but where is this used?
[13:43] <jtv> Scott knows the details.
[13:44] <jtv> smoser: feel free to send hardware.  :)
[13:44] <smoser> jtv, canonistack works fine.
[13:44] <smoser> and a single system is all you need to test the vast majority of this.
[13:44] <jtv> Then maybe I should try that.  The address you told me to ssh into this weekend didn't let me in for some reason.  :(
[13:45] <smoser> you have to bounce thorugh chinstrap
[13:45] <smoser> (i did say that)
[13:45] <jtv> What a coincidence.
[13:45] <jtv> Because when you said that I actually did that.
[13:45] <jtv> Did I mention that it didn't work?
[13:46] <smoser> i dont have the instance any more , but i assume that your credentials weren't geting through.
[13:46] <smoser> i 'ssh-import-id jtv'
[13:46] <jtv> Well… maybe this was after you let the instance go.
[13:46] <jtv> Or it was taken from you, or whatever happened.
[13:47] <smoser> nah. that was this morning. maybe 30 minutes ago.
[13:47] <smoser> https://wiki.canonical.com/InformationInfrastructure/IS/CanonicalOpenstack?action=show&redirect=CanoniStack
[13:47] <jtv> Or evening, as we like to call it.  ;)
[13:47] <smoser> that is an *extremely* useful resource.
[13:47] <jtv> Thanks.  Maybe I'll play with it tomorrow.
[13:47] <smoser> you should set it up.
[13:47] <smoser> note, even EC2 or HP cloud can also test this tuff.
[13:47] <smoser> the real value of canonistack is that you can get nested virtualization.
[13:48] <jtv> That is nice, yes.
[13:48] <smoser> there are no public clouds to my knowledge that have nested virt support.
[13:49] <jtv> I dared not run the script you pointed to the other day — it did an apt-get dist-upgrade without confirmation, and if I lose this system, I have nothing.
[13:51] <jtv> Good thing I spotted it!
[13:52] <smoser> this is why we have instances.
[13:53] <smoser> and virtualization
[13:54] <smoser> ok. i re-purposed bug 1051626
[13:54] <smoser> i did'nt follow all of what you all were saying above
[14:07] <smoser> what do we need to do to make dhcp actually funciton.
[14:14] <smoser> rvba, how can i ask maas what its server ip is?
[14:14] <smoser> the one it is listening to
[14:14] <smoser> (and is currently getting written aas 'next-server')
[14:15] <rvba> smoser: get_maas_facing_server_address()
[14:15] <smoser> anyway other htan python?
[14:16] <rvba> smoser: get_maas_facing_server_address extracts it from settings.DEFAULT_MAAS_URL.
[14:21] <smoser> $ echo 'from maasserver.server_address import get_maas_facing_server_address; print "\n%s" % get_maas_facing_server_address()' | sudo maas shell 2>/dev/null | grep -v "^>>>"
[14:21] <smoser> <IP_ADDRESS>
[14:25] <roaksoax> Daviey: so you want me to ditch ipmitool in favor of freeipmi within MAAS right?
[14:27] <roaksoax> allenap: can you point me to the package and upstream of the package you wanted me to upload?
[14:28] <allenap> roaksoax: The delay has served you well: it looks like it's not suitable after all. It wasn't suitable for the kind of thing that Francis and Scott had in mind last week, so I've switched to argparse.
[14:28] <roaksoax> cool
[14:41] <Daviey> roaksoax: I think it should be considered
[14:41] <Daviey> :)
[14:42] <roaksoax> Daviey: i don't mind changing it if necessary
[14:43] <roaksoax> Daviey: it will require a few changes but it is possible
[14:48] <Daviey> roaksoax: ideally, we'd support both IMO
[14:48] <roaksoax> Daviey: do we want to MIR ipmitool and freeipmi ?
[14:49] <roaksoax> Daviey: not that is is simply to power on/off machines nothing else
[14:49] <roaksoax> s/not/note
[14:49] <Daviey> roaksoax: JUST MIR'ing freeipmi seems more sensible IMO.
[14:49] <Daviey> It's a more active and safer project IMO.
[14:50] <Daviey> roaksoax: Yeah, so we don't have to worry about kernel integration
[14:50] <roaksoax> k
[14:52] <roaksoax> Daviey: we don't need kernel integration when we use ipmitool either, since we are only using to send a command over the network
[14:53] <Daviey> roaksoax: For the MIR?
[14:53] <roaksoax> Daviey: worry about kernel integration --> we only need 1 binary
[14:53] <roaksoax> Daviey: but either way, i'll look into it
[14:54] <Daviey> roaksoax: right,i mean we are MIR'ing the whole shebang
[14:58] <roaksoax> indeed
[16:43] <roaksoax> Daviey: bug #1052056 could you please ack?
[17:47] <guimaluf> I would like to make maas node more sofisticated default settings. the most convinient way is going through cobbler and kickstart files?:
[17:49] <smoser> guimaluf, well, the going forward way is to basically allow cloud-init to handle that for you.
[17:50] <smoser> but currently, you'd have to write your own api tool to launch an instance with user-data.
[17:50] <guimaluf> smoser, is cloud-init a script?
[17:50] <smoser> https://help.ubuntu.com/community/CloudInit
[17:51] <guimaluf> smoser, exactly, i'm trying to cutomize via maas.pressed file and maybe puppet. but isn't enough
[17:51] <smoser> why "isnt enough?"
[17:51] <smoser> s/?"/"?/
[17:54] <guimaluf> not isnt enough. but I'm having difficult to find what I want. like partitioning many disks on my nodes. the default partitioning made trought partman is OK, but I can do nothing with the other disks. i'm on this many days and nothing happens...
[17:54] <smoser> ah. yeah. i remmber. the only way you can accomplish that is via customization of the preseed.
[17:54] <guimaluf> I know puppet and preseed is enough. I just can find the way...
[17:55] <guimaluf> smoser, I'm using a for-loop inside preseed file in the early-command, as you said, but this make the installation process freak out!
[17:56] <guimaluf> and my maas set-up could never give the correct ssh-keys with the cloud-init. I'd to put a echo "ssh-key" >> /root/.ssh/auth_keys in the late command :/
[17:58] <guimaluf> I dont know how can I use snnipets on the preseed file. On cobbler doc seems so easy. but when I put SNIPPET("asdf"); the installations get broken
[17:58] <smoser> you're using maas on 12.04 ?
[17:58] <guimaluf> I would like to know how maas deal with that...
[17:58] <guimaluf> yep
[17:59] <guimaluf> I thought the clock syncronization issue would be the only problem getting ssh-keys, but isnt the only one.
[18:03] <smoser> well, the clock issue will most deifnitely block you
[18:03] <smoser> b
[18:03] <smoser> ut there are other issues potentially to
[18:03] <smoser> for some reason your installed node is not able to reach the maas metadata service
[18:03] <smoser> possibly routing
[18:04] <guimaluf> hmmmm make sense... the metadata service is <IP_ADDRESS>? may I should create a iptables rule for that...
[18:06] <guimaluf> I'm also using openstack, and this is the metadata server and it points to IP:80. which route should maas metadata points to?
[18:10] <smoser> maas has its own metadata service. <IP_ADDRESS> is the openstack metadata service.
[18:12] <guimaluf> and how can I know wich is the address?
[18:12] <guimaluf> I think this is happening cause my dhcp-server isnt the maas server
[18:13] <guimaluf> so I need to put a rule on firewall to redirect metadata server to my maas server right?
[18:14] <roaksoax> guimaluf: check that MAAS_DEFAULT_URL has the correct address in /etc/maas/maas_local_settings.py
[18:15] <Daviey> roaksoax: Forwarded to jdstrand
[18:16] <roaksoax> Daviey: k thanks!
[18:16] <guimaluf> roaksoax, is correct
[18:40] <smoser> guimaluf, and the nodes need to be able to get to the MAAS_DEFAULT_URL
[18:40] <guimaluf> they are.
[18:40] <guimaluf> they can do the PXE boot, ping, ssh, etc.
[18:52] <smoser> well, then the next thing is to get into a node and run the cloud-init maas datasource
[18:54] <smoser> there is a file in /etc/cloud/cloud.cfg.d/ with content in it for the acl.
[18:54] <smoser> you can run that and it should show errors also.
[18:55] <guimaluf> do you mean run this command? # cloud-init maas datasource
[18:55] <guimaluf> root@node-782bcb77e1d4:~# cloud-init maas datasource
[18:55] <guimaluf> bad command maas. use one of ('start', 'start-local')
[18:56] <smoser> no. sorry.
[18:57] <smoser> python /usr/share/pyshared/cloudinit/sources/DataSourceMAAS.py
[19:01] <roaksoax> smoser: will you make quantal images available for commissioning/enlistment?
[19:02] <smoser> working on that right now. they dont work
[19:02] <smoser> :)
[19:02] <smoser> biggest thing i'm waiting on is mountall
[19:02] <roaksoax> smoser: hehe ok, I can make available a package that has quantal support for you to test if you dont want to manually apply the patches
[19:02] <smoser> https://launchpad.net/~smoser/+archive/ephermal-fixes
[19:03] <smoser> maas is actually ok.
[19:03] <roaksoax> k ;)
[19:03] <smoser> i'll upload openiscsi today
[19:04] <roaksoax> Daviey: sill around?
[19:04] <roaksoax> smoser: ok cool!
[19:04] <Daviey> roaksoax: i am
[19:04] <roaksoax> Daviey: where did you published the squashfs image? :)
[19:05] <roaksoax> publish*
[19:06] <Daviey> roaksoax: I haven't.. i manually exposed it via cp'ing it to a place on cdimage
[19:06] <roaksoax> Daviey: is it still exposed? Are we going to keep exposing it?
[19:07] <roaksoax> Daviey: or should I just use the mini.iso?
[19:07] <Daviey> mini.iso doesn't ship the squashfs :)
[19:07] <roaksoax> ah i thought it did
[19:08] <roaksoax> Daviey: in that case, I think it would make sense to make the iamge available somewhere in cdimage
[19:08] <roaksoax> Daviey: that way we wont have to download the whole ISO
[19:11] <Daviey> hmm
[19:12] <Daviey> http://cdimage.ubuntu.com/ubuntu-server/daily/current/quantal-server-amd64.squashfs
[19:12] <Daviey> It's only 61M
[19:12] <Daviey> roaksoax: That is temp' do not expect it to be there tomorrow
[19:12] <roaksoax> Daviey: ok cool thanks
[19:23] <roaksoax> smoser: do you think it would be a good idea to change wget on maas-import-pxe-files to rsync instead?
[19:27] <smoser> roaksoax, no.
[19:27] <smoser> for what, specifically?
[19:27] <roaksoax> maas-import-pxe-files
[19:27] <smoser> what files
[19:27] <roaksoax> to donwload the required files
[19:27] <roaksoax> initrd.gz
[19:27] <roaksoax> linux
[19:27] <roaksoax> etc
[19:27] <roaksoax> etc
[19:27] <smoser> url? example?
[19:27] <smoser> why would that be superior to wget
[19:28] <roaksoax> smoser: http://paste.ubuntu.com/1211666/
[19:28] <roaksoax> smoser: not just superior, but if a download process is broken or if we already have the latests image, then it wont download from 0% or re-download
[19:30] <smoser> is that stuff available via rsync ?
[19:30] <smoser> i dont think its really that big of a deal.
[19:30] <roaksoax> smoser: yeah
[19:31] <smoser> you're looking at, what, 100M there?
[19:31] <smoser> at max.
[19:31] <smoser> actually.
[19:31] <smoser> no.
[19:31] <smoser> we do not want rsync
[19:31] <smoser> due to it being less proxyable
[19:31] <roaksoax> ok
[19:32] <smoser> ie, you get the resume for all practicle purposes for free if you set http_proxy
[19:33] <smoser> now, for the lcoud-images, we coudl/should make those resume better.
[19:34] <roaksoax> right
[19:34] <roaksoax> i'm also trying to avoid the fact of having to download those files each time
[19:34] <smoser> use a proxy, silly.
[19:35] <roaksoax> lol will have to
[19:50] <roaksoax> smoser: did you make any change to the boot process to display the kernel parameters on enlistment/commissioning?
[19:52] <smoser> yes.
[19:53] <roaksoax> smoser: now, however, I don't see any ouput been displayed on the image itself whicle provisioning (as in I no longer see how it downloads maas-enlist, etc etc)
[19:53] <roaksoax> nor during commissioning
[19:53] <smoser> its going to ttyS0
[19:54] <smoser> which i think is actually more correct in this environment.
[19:55] <smoser> roaksoax, do you agree?
[19:55] <roaksoax> smoser: i have no say on this, It doesn't really matter to me
[19:55] <roaksoax> smoser: so yes, whichever you think is best, I agree
[19:55] <smoser> well, console is almost certainly not being logged as text in any reasonable manner
[19:56] <smoser> console as in 'tty1' (video console)
[19:56] <smoser> ttyS0 might be.
[19:57] <roaksoax> yeah i agree that's probably the best place
[20:01] <smoser> roaksoax, i just built a quantal image
[20:01] <smoser> using my ppa i pointed at
[20:01] <smoser> and have enlisted 3 systems
[20:01] <smoser> whoowhoo!
[20:02] <smoser> using the daily ppa of maas from this morning.
[20:02] <roaksoax> smoser: awesome!
[20:03]  * roaksoax brb
[20:06] <smoser> roaksoax, hm.
[20:06] <smoser> can't i somehow deploy a node from the ui?
[20:07] <roaksoax> smoser yes you can
[20:07] <smoser> hm..
[20:07] <roaksoax> smoser not quantal though
[20:07] <smoser> oh. ok.
[20:07] <smoser> wait
[20:08] <roaksoax> smoser but you wont be able to release it nir delete it if you do so
[20:08] <smoser> roaksoax: ssh -L 10080:localhost:80 <IP_ADDRESS>
[20:09] <smoser> tell me if what you see on http://localhost:10080/MAAS for 'node-525400123403' is other than expected
[20:13] <roaksoax>   smoser brb xhsnging locstiond
[20:14] <smoser> k
[20:46] <roaksoax> smoser: sorry about that
[20:47] <smoser> no worries
[20:48] <roaksoax> smoser: what is it that you wanted me to look at?
[20:48] <smoser> well, one of those nodes is commissedon
[20:48] <smoser> how would you push a button to install it?
[20:49] <roaksoax> smoser: you can't start it? or it can't commission? or you need it to commission?
[20:49] <roaksoax> smoser: or the button is there but it is greyed out?
[20:50] <roaksoax> smoser: if you add a node from the WebUI there's no start button IIRC
[20:51] <smoser> the start button is greyed out
[20:52] <smoser> (you can look at the ui with the ssh above)
[20:52] <roaksoax> smoser: did you add an SSH key?
[20:54] <roaksoax> smoser: i think you need to add an ssh key in order for it to allow you to start the machine
[20:54] <smoser> roaksoax, no i did not add ssh key
[21:17] <nov503> hi, when i bootstrap juju, i forget to put the public key in maas. Now the system is installed but the key is not pushed to the system and I can't login into it.  Is there any way I can redo this?
[21:35] <matsubara> smoser, hi there
[21:36] <matsubara> smoser, I'm enlisting a node in the Lenovo lab but once it boots the image from the MAAS server it gets stuck waiting for eth1 to become ready. Did something change recently in the image that might cause that?
[21:37] <roaksoax> smoser: so I guess you figured by now that you need to add an ssh key in order to start them
[23:59] <smoser> matsubara, nothing should be waiting on eth1. and the image hasn't changed (unless you're using 'daily', which would have taken configuration).
[23:59] <smoser> you could be hitting a bug i supposed could exist.


[02:20] <richd> hi...Ubuntu 20.04.6 LTS with Xen can't start any xen guests after updates.  Is there a way to get something more meaningful than "xen.service: Failed with result 'exit-code'" out of systemd? or any other log files?
[02:22] <richd> "xl list" reports "(null)" instead of "Domain-0", and nothing else will start
[02:54] <mybalzitch> do you still have a xen domU or whatever kernel?
[03:31] <THE_HF> boa noite galera.
[03:31] <THE_HF> hello.
[04:04] <richd> mybalzitch: never mind.  I tried rebooting it, and it hasn't come back.  It'll have to wait until I get there.
[04:07] <richd> one of the updates broke all of the network connectivity.  I don't know at all why, but for some reason, after one of the updates, the network interfaces (em1 - em4) were ever so helpfully renamed to eth0 - eth3.  Openvswitch was not at all happy with that change.
[04:08] <richd> I thought I had all that fixed, but perhaps not
[04:08] <richd> or perhaps a subsequent update decided to rename them all again.
[13:36] <athos> Just came across LP: #2024291 and we indeed are missing dbg symbols for some of the security updates there (although, from checking LP, I see that the dbg-sym packages were indeed built)
[13:36] -ubottu:#ubuntu-server- Launchpad bug 2024291 in tmux (Ubuntu) "missing debug symbol for 3.0a-2ubuntu0.4" [Undecided, New] https://launchpad.net/bugs/2024291
[13:36] <athos> am I missing sth here or is this indeed a (possibly known) issue?
[13:36] <athos> Cc sergiodj


[03:24] <OvermindDL1> So I upgraded from Kubuntu 18.04 to Kubuntu 20.04 and now all my personal storage has vanished, so I'm in a new root user on this install now.  The drives holding all my data are an LVM mirrored set of drives and I'm getting some... interesting messages from vgck that google is being entirely not helpful with:
[03:24] <OvermindDL1> LV storage0 invalid: visible raid meta LV for raid1 segment
[03:24] <OvermindDL1> `storage0` being the name of the LV and `storage` being the name of the vg
[03:25] <OvermindDL1> Literally only a single google result for that, and it was someone with the same issue as I and no followup at all
[04:30] <viewer|79> Hello guys.
[04:32] <viewer|79> I used Ubuntu 20.04, I have Intel Ivy Bridge graphics card and I have Brightness issues in Linux. So I have to use acpi_backlight=video to fix it. But this fix is not working Kubuntu. Anyway I can fix this issue?
 @viewer|79, I had issues on a Laptop with an AMD graphic card. An upgrade to 20.10 fixed the issue because the Kernel 5.8 has a better support for newer graphic cards.
[05:18] <OvermindDL1> So, if anyone hits this problem again with LVM and RAID, I frankencoded up my own version of the `lvm` tool that bypasses that check, and very carefully called `lvchange --setactivationskip y <mystoragename>` and that fixed it.  I could have just, say, put a bootable old copy of kubuntu on a usb drive and done it that way, but I would have had to wait to tomorrow for that, and this worked!
[05:21] <OvermindDL1> What happened basically is that my RAID had a metadata inconsistency (which was fine for my specific use case, but I guess to be truthful isn't "safe") and the newer LVM's have a test for that to prevent loading up such broken metadata
[05:22]  * OvermindDL1 is documenting this in case these logs appear online sometime for some possible future person
[07:22] <lordievader> Good morning
[08:12] <boby> hello
[08:12] <boby> anyone online?
[08:12] <boby> i need help
[08:12] <boby> my laptop keyboard and trackpad not working
[08:12] <boby> but external mouse and keyboard do work
[08:12] <boby> right from the beginning when i installed it from usb drive
[08:12] <boby> it dint work even in the liveusb
 I have an issue regarding my touchpad
 Some funtionalities are not working in 20.04 LTS
 like tap to click
 two finger right click etc.
 Any Fix?
 Hello
[12:58] <BluesKaj> Hi folks
[16:05] <Crell> Hi folks. I'm trying to install 20.10 on a Thinkpad X1 Yoga. It boots to the USB key fine. The installer keeps getting tripped up on the EUFI, though.  I've tried disabling the EUFI or not in the hardware setup, but it still can't install onto the disk.
[16:06] <Crell> Right now, the disk has an EFI System Partition (NTFS) partition, and a sinle large ext4 partition. (Remnants of previous install attempts.)  Should I remove the ntfs partition?  I've never had this issue before with other laptops.
[16:18] <k_sze> Is kubuntu 20.04 supposed to support screen autobrightness?
[16:18] <k_sze> I have ubuntu converted to kubuntu by installing kubuntu-desktop
[16:21] <Crell> "The attempt to mount a file system with type vfat in SCSI2, partition #1 (sda) at /boot/efi failed." - That's the error I get early in the installer, after I pick the disk configuration.  I get it no matter what disk setup I try to use.
 Good morning
 Good Night from India 🇮🇳 ! 😴
[17:33] <k_sze> erm, I get this when I `dpkg -i` a deb file: Error in file "/usr/share/applications/org.kde.kdeconnect_open.desktop": "*/*" is an invalid MIME type ("*" is an unregistered media type)
[17:33] <k_sze> that file is clearly not recently modified, the date is still 2019-12-08.
 @ri5h46h, How r u
 Hey people! I just did a dualboot install of kubutu(alongside manjaro)  … There's no audio tho! … It's not even registering the laptop speakers. What to do?
 (Photo, 1280x960) https://irc-attachments.kde.org/cs0oUUnk/file_39526.jpg also, these errors are there whenever I boot in
 nvm. it works after a reboot


[08:40] <smartboyhw> Hello zequence
[09:26] <smartboyhw_> Hello DarkEra:)
[09:26] <DarkEra> good morning smartboyhw_  :)
[09:27] <DarkEra> yaaawn....
[09:27]  * DarkEra needs coffee
[09:27]  * smartboyhw_ gives DarkEra a cup of super-strong espersso:P
[09:29] <DarkEra> Thanks smartboyhw_ In a super large cup i hope ? :D
[09:32] <smartboyhw_> DarkEra: Tjat
[09:32] <smartboyhw_> That cup is a 50 Litre one
[09:34] <DarkEra> O_o
[09:34] <smartboyhw_> DarkEra: LOL:P
[09:34] <DarkEra> ok, now that is too much. I still want to live :D
[09:35] <smartboyhw_> DarkEra: OK. Let me give you 1 Litre of zequence special blend coffee with a Ubuntu Studio mug designed by madeinkobaia:P
[09:36] <smartboyhw_> sold by ttoine
[09:36] <DarkEra> that'll do it :D
[09:36] <DarkEra> members get it free i hope :P
[09:37] <smartboyhw_> DarkEra: Gifted by smartboyhw_
[09:37] <DarkEra> well thank you :)
[09:38] <DarkEra> DarkEra , how do you wake up and feel great?
[09:38] <DarkEra> well, just jump in on IRC and have a chat with smartboyhw_  in the morning
[09:39] <DarkEra> while drinking coffee from a Ubuntu Studio mug
[09:39] <smartboyhw_> DarkEra: self-chatting is not a good thing…
[09:39] <DarkEra> smartboyhw_, it's ok
[09:39] <DarkEra> i know i'm nuts
[09:41] <smartboyhw_> DarkEra: :O
[09:41]  * smartboyhw_ hides from nutty DarkEra
[09:43] <DarkEra> lol
[09:45]  * zequence sighs of relief, as another test was passed: network+
[09:46] <zequence> Means I can focus on other things more for a little while
[09:46] <zequence> linux+ is next, so that's more close to home
[09:47] <smartboyhw_> zequence: Congratulations!
[09:47] <zequence> smartboyhw_: Thanks
[09:48] <zequence> So, let the planning start!
[09:48] <smartboyhw_> zequence: \o/
[09:49] <smartboyhw_> So what things we have on the whiteboard? linux-rt, DE support, ubuntustudio-controls...
[09:51] <DarkEra> zequence, congrats :)
[09:53] <smartboyhw_> zequence: What test it is? Is it paper-written? How much does the exam cost?
[09:57] <zequence> smartboyhw_: It's done on a dumb client, and the test is a collection of 80 random questions, so each test is unique
[09:58] <zequence> Don't know the cost. I'm not paying for it myself (the unemployment office is), but I estimate it to be somehwere between 250-700$
[09:59] <zequence> First, I will start looking at what we didn't complete for raring, and move over + reorganize those workitems
[10:00] <zequence> Then I'll make sure everything we've planned but not yet written down is documented
[10:00] <zequence> Lastly, we need to discuss further planning on the mail list
[10:27] <DarkEra> http://distrowatch.com/table.php?distribution=extix ---> anyone knows this?
[10:29] <DarkEra> by the way i also noticed that there are no screenshots shown on distrowatch of Ubuntu Studio in the Weekly/released last week part and on some other reviews/blogs. :/
[10:30] <smartboyhw_> DarkEra: :/
[10:32] <smartboyhw_> Hmm that Extix thing should effectively be killed since it violates our trademarj
[10:32] <smartboyhw_> zequence: It does come from Sweden though…
[10:34] <DarkEra> smartboyhw_, seems to be a older guy who 'made' this distro
[10:34] <DarkEra> just looking on facebook
[10:34] <smartboyhw_> DarkEra: What do you mean by "an older guy"?
[10:34] <DarkEra> smartboyhw_, https://www.facebook.com/pages/Exton-Linux/125357627524343
[10:35] <smartboyhw_> DarkEra: I can't view the link (I don't have Facebook)
[10:35]  * smartboyhw_ has parents that are anti-Facebooks
[10:36] <DarkEra> i could write a comment but want to know what zequence thinks of all this
[10:36] <DarkEra> smartboyhw_, oh, i see
[10:36] <DarkEra> didn't know that
[10:36] <smartboyhw_> DarkEra: I think zequence is the one to file a trademark infringement…
[10:37] <DarkEra> using a Ubuntu Studio wallpaper with that logo can be confusing to people out there
[10:38] <smartboyhw_> DarkEra: Or maybe Canonical is the one to file infringements…
[10:39] <DarkEra> smartboyhw_, from what i can see that man is just remastering distro's and puts them out in the world. There's also a exGENT (Gentoo) of the same guy
[10:40] <DarkEra> anyhoo, something must be done about the wallpaper though
[10:41] <smartboyhw_> DarkEra: OK. But they shouldn't be using our wallpaper (albeit an old one)
[10:41] <DarkEra> that's what i mean :)
[10:41] <DarkEra> and is the reason i put it in here
[10:42] <smartboyhw_> zequence: Can you have a look at http://linux.exton.net/node/1171 ?
[10:43] <DarkEra> http://www.extix.se/
[10:43] <DarkEra> does he have multiple sites?
[10:44] <smartboyhw_> lol
[10:45]  * DarkEra is getting even more confused
[10:45]  * smartboyhw_ is infuriated
[10:46] <DarkEra> *eye twitching*
[10:56] <zequence> I wouldn't pay too much notice to that
[10:57] <zequence> It's one guy, doing a sort of Ubuntu Gnome, with some custom addons (some which might not be legal)
[10:57] <zequence> (he mentions codecs)
[10:57] <zequence> At least for redistribution
[10:57] <smartboyhw_> zequence: OK then
[10:58] <smartboyhw_> zequence: You know how to install bzr in Android? (LOL)
[10:58] <DarkEra> ok but still i don't agree on using a wallpaper of our project for his remaster
[10:59] <zequence> I don't know much about reuising trademarks in wallpapers. Maybe he was unaware of that the CEF is a symbol for Ubuntu Studio
[10:59] <zequence> Also, I'm not sure about the legal status of that symbol
[11:00] <smartboyhw_> zequence: OK
[11:00] <DarkEra> need another coffee and hope my wife get's back soon, need to pick up something later on
[11:00] <zequence> I'll send him an email about it
[11:01] <smartboyhw_> zequence: Thanks!
[11:01] <DarkEra> zequence, uhm... ubuntu studio is a registered trademark of Canonical Ltd. thus so is the logo from my point of view
[11:01] <DarkEra> :)
[11:02] <smartboyhw_> DarkEra, zequence eee that will involve Canonical in it:O
[11:03] <DarkEra> :P
[11:04]  * smartboyhw_ is now wondering will that alarm the CC (shan't)
[11:06] <smartboyhw_> Back…
[11:13] <zequence> DarkEra: The logo is a different story
[11:13] <smartboyhw_> zequence: Meh https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuStudio says three years while the main website says 5
[11:13] <zequence> DarkEra: Only the name is Canical, AFAIK
[11:14] <zequence> smartboyhw_: You are welcome to double check the actual support time
[11:14] <smartboyhw_> zequence: Oh
[11:14] <smartboyhw_> zequence: Should be 5 I think.
[11:15] <zequence> I sent him an email about it, so let's see what he says
[11:16] <smartboyhw_> zequence: \o/
[11:21] <DarkEra> zequence, oh ok. And thanks for sending the mail. Let's see what his answer will be.
[11:21] <DarkEra> about the LTS time... i was confused... is it 5 or 3 years of support?
[11:22] <smartboyhw_> DarkEra: Starting from 12.04 LTS all LTS releases are supposed to be supported for 5 years, no matter desktop or server.
[11:22] <DarkEra> i know Ubuntu itself has 5 years but i read that xubuntu and ubu studio only had 3 years with 12.04
[11:23] <smartboyhw_> DarkEra: Oh
[11:23] <zequence> The support is equal to all. I can't think of why it wouldn't be
[11:23] <DarkEra> http://xubuntu.org/getxubuntu/
[11:24] <DarkEra> The 12.04 release, codenamed Precise Pangolin, is a Long Term Support release, which means it has support for 3 years
[11:24] <zequence> I think perhaps the release period was made longer after the release. Deserves some investigation perhaps
[11:24] <zequence> I think those release notes are wrong
[11:25] <smartboyhw_> DarkEra: zequence: Xubuntu IS three years
[11:25] <DarkEra> i wonder why
[11:25] <smartboyhw_> http://xubuntu.org/news/12-04-release/
[11:26] <zequence> Again, I believe the period was made longer
[11:26] <zequence> Please do not look at news or statements from just around the release
[11:26] <smartboyhw_> zequence: https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/Xubuntu
[11:26] <smartboyhw_> Even the release NOTES says that:O
[11:26] <DarkEra> i could ask in the xubuntu channel to make sure.
[11:27] <smartboyhw_> zequence: Please ask for us in #xubuntu-devel :)
[11:27] <DarkEra> smartboyhw_, i dropped the question in their channel
[11:28] <smartboyhw_> DarkEra: Which?
[11:28]  * smartboyhw_ never joined #xubuntu
 !lts
 LTS means Long Term Support. LTS versions of Xubuntu will be supported for 3 years. The current LTS version is !Precise (Precise Pangolin 12.04)
[11:29] <smartboyhw_> …
[11:29] <zequence> Seems like Xubuntu have decided among themselves to only support the LTS for three years
[11:29] <zequence> But, that's Xubuntu
[11:29] <zequence> DarkEra: Nowadays, it means 5 years
[11:29] <zequence> https://wiki.ubuntu.com/LTS
[11:29] <smartboyhw_> zequence: Hmm that's strange
[11:30] <zequence> Kubuntu will be supporting the LTS for 5 years
[11:30] <zequence> So, 5 years it is
[11:30] <DarkEra> yep and since we base on Xubuntu Scott took it over with 12.04 i guess
[11:30] <DarkEra> we need to change it and make it clear for once :)
[11:31] <smartboyhw_> zequence: DarkEra: Then can you guys change it? Thx!
[11:32]  * smartboyhw_ likes https://wiki.ubuntu.com/Xubuntu/StrategyDocument very detailed
[11:33] <zequence> smartboyhw_: Why not you, since you brought it up?
[11:33] <smartboyhw_> zequence: Can't, I'm in mobile.
[11:34] <smartboyhw_> If not I would've done it already.
[11:34] <zequence> "will be supported for three years per the Xubuntu LTS plan."
[11:34] <smartboyhw_> zequence: What sort of plan is that?:O
[11:34] <zequence> That's from the Xubuntu release notes
[11:34] <zequence> Their plan
[11:35] <smartboyhw_> zequence: Grrrr
[11:35]  * smartboyhw_ does think the Xubuntu team is rather conservative
[11:35] <smartboyhw_> Fortunately knome isn't here:P
[11:39] <zequence> I'm unable to login to the wiki. Some new SSO problem
[11:40] <smartboyhw_> zequence: :O
[11:41] <smartboyhw_> zequence: Are you in https://launchpad.net/~xubuntu-users ? Xubuntu is going to have a Project Lead election and people in it can vote (which is rather interesting)
[11:41] <zequence> ok, now I'm in
[11:42] <zequence> smartboyhw_: No, I'm not involved in that
[11:42] <smartboyhw_> zequence: \o/
[11:42] <smartboyhw_> zequence: It's rather one-sided though, the XPL election
[11:42] <smartboyhw_> ttoine: Greetings!
[11:44]  * smartboyhw_ now doesn't know who to vote for Kubuntu Council grrr
[12:11] <ttoine> hey
[12:17] <DarkEra> ok guys, i'll be back later again, got some things to do
[14:03] <smartboyhw> zequence: For Saucy, are we planning for 1 Beta as originally planned for Raring or 2 Betas like what we finally did for Raring or what?
[14:13] <smartboyhw> Wb DarkEra
[14:13] <DarkEra> thanks :)
[14:19] <zequence> smartboyhw: Either we do structured testing before the final beta, or we do both betas. I think the former would do. Testing is one of those subjects that still needs to be developed
[14:20] <zequence> This cycle I will put more energy on the testing bit too. We need to test new packages, and make sure all of our multimedia software is functional well before any beta releases
[14:29] <smartboyhw> zequence: OK
[14:32] <DarkEra> looks like i'm missing out too much chat here :)
[14:34] <smartboyhw> DarkEra: No. The only thing you missed was my question.
[14:34] <DarkEra> ah, ok
[15:09] <DarkEra> why would someone still have songbird packaged when they dropped linux support
[15:17] <DarkEra> bleh... i read that wrong i guess... lol
[15:18] <smartboyhw> DarkEra: lol
[18:06] <madeinkobaia> Hi all : )
[18:10] <DarkEra> aloha madeinkobaia
[18:13] <madeinkobaia> Hi darkera : ) How are you ?
[18:14] <DarkEra> besides a cold i caught i'm doing fine. :) how are you?
[18:19] <madeinkobaia> Fine : )
[20:01] <zequence> I'm building ardour3 in my testing ppa now, just for the sake of practicing. Updated 4 of its dependencies, hoping that will be enough to build it.
[20:02] <zequence> Or, rather, I'm still building the dependencies
[20:19] <DarkEra> speaking of ... i'm playing around with ardour2, busy with a new track after all these years
[20:20] <DarkEra> looking forward to ardour 3
[20:22] <zequence> I was actually mixing an album for a friend just now, but got tired of some problems I had with ardour2, or rather mixbus
[20:23] <zequence> Going to give ardour3 a go now
[20:26] <DarkEra> cool stuff :)
[20:27] <zequence> DarkEra: I'm building it at ppa:zequence/testing
[20:27] <zequence> damn, one build failed
[20:27] <zequence> Ah, no
[20:27] <DarkEra> zequence, thanks. might have a look later on :)
[20:27] <zequence> Just LP being hard to decipher
[20:28] <zequence> If the build works (which seems likely), it should be ready by tomorrow
[20:28] <DarkEra> i tried ardour 3 on dreamstudio once before i switched over here :)
[20:28] <DarkEra> hey cool
[20:28] <zequence> Apparently the build servers aren't particularly busy atm, since they start building at once
[20:29] <zequence> Everyone's on holiday
[20:29] <zequence> https://launchpad.net/~zequence/+archive/testing/+packages
[20:29] <DarkEra> lol, guess they are after the hard work on the release
[20:29] <DarkEra> brb
[21:20] <DarkEra> bookmarked the ppa ;)
[21:30] <zequence> Seems like there are some missing dependencies in the original Debian source. Should be fixed now
[21:39] <DarkEra> cool :)
[21:41] <DarkEra> bah... steel need to catch up on some sleep and get a more focussed brain if i want to get into the dev thing
[21:41] <DarkEra> steel/still*
[21:44] <zequence> hmm "Missing libs/ardour/revision.cc.  Blame the packager."
[21:46] <DarkEra> zequence, i have Gnome 3 installed on another partition and added the Gnome 3 ppa to get 3.8. Looks nice to me so far. Much better and smoother than 3.4 was
[21:47] <DarkEra> as long as you don't blame me^^
[21:47] <DarkEra> i didn't package it :P
[21:47] <zequence> DarkEra: I had some problems with it myself. The OS totally crashed
[21:47] <zequence> I need to reinstall
[21:48] <DarkEra> oops
[21:48] <DarkEra> borked it yourself?
[21:49] <zequence> I just did an update, and then it didn't boot anymore
[21:58] <DarkEra> well, that kinda sucks.
[22:10] <zequence> Well, I think I fixed it with a patch that falktx had added to his build ;)
[22:11] <falktx> hm?
[22:11]  * falktx is missing context
[22:11] <zequence> falktx: I was just practicing debian packaging by getting ardour3 prepped for a PPA
[22:12] <falktx> ah cool
[22:12] <zequence> got the four dependencies built first, that were not available yet in raring, added a couple of build dependencies, but wscript was giving me problems still
[22:13] <zequence> so, I had a look at your build
[22:14] <falktx> ah yes,
[22:14] <falktx> ardour3 build is broken on purpose
[22:14] <falktx> afaik the ardour devs are against packaging it
[22:14] <falktx> but that is no fair for a studio distro, we need ardour3
[22:16] <len-1304> If there was a reasonable way to download from their site on install I would be happy (er)
[22:16] <zequence> I suppose ardour devs would prefer a different way of distributing packages for distros, one where they have more control
[22:17] <len-1304> When they offer the src they have given that control up.
[22:18] <zequence> Of course, the license doesn't give them the right to decide on how it's distributed, but I think they would prefer another kind of culture around package distribution
[22:18] <zequence> There are other ways to do things than the way Debian does it
[22:18] <len-1304> The way to do that is to provide a package distros can use
[22:20] <zequence> Debian doesn't use ready binaries, unless it's non-free. Everything is built from source
[22:20] <len-1304> yup, This allows changing libs as needed
[22:21] <zequence> And everything is adapted to the Debian policy
[22:21] <zequence> Don't know what possibilities there would be using the Ubuntu Software Center thing
[22:22] <zequence> Ardour could add a package there, and even charge for it
[22:22] <len-1304> A live ISO without ardour would not be as nice.
[22:22] <zequence> I'm not suggesting we follow Ardours wishes
[22:22] <len-1304> USC would want a defined price
[22:23] <zequence> Well, maybe USC should be more flexible
[22:23] <zequence> Just saying there are many ways to do things
[22:23] <len-1304> Yes.
[22:24] <zequence> Some people think the current model is not for the future
[22:24] <zequence> dependency hell
[22:24] <len-1304> I am not sure what the best route is.
[22:25] <zequence> providing the source is a fundamental must
[22:25] <len-1304> Jack is looking at including the opus lib because the one debian ships is not usable.
[22:26] <zequence> But, it would be nice to have a system where you can use any version of software just by doing one command, and also, being able to use many different versions on the same system
[22:27] <len-1304> many? One per user might work, but two system wide (maybe three) are about it.
[22:27] <zequence> There's no reason to have restrictions on that
[22:28] <zequence> If I want to be able to run 10 different version of an application on my system, that is what I should be able to do
[22:28] <zequence> Simple as that
[22:28] <zequence> there's much more reason to have many different versions of libraries, than applications of course
[22:28] <len-1304> So long as they are in different directories it can be done. Ardour does this and can work.
[22:29] <len-1304> Many libs can be used... often two or more are.
[22:30] <zequence> Also, static releases is not for the future either
[22:30] <len-1304> But they work better now and future than in the past :)
[22:32] <zequence> Either the file system hierachy needs to add a name system that uses versioning, to keep track of multiple libraries and applications, all simultaniously installed on the system, or, packages should include them all in on package, or both
[22:33] <zequence> I mean, about the package, the way the offical Ardour3 is packaged
[22:34] <len-1304> I think in that case there needs to be a division between "added" SW and what comes with the OS or distro
[22:34] <len-1304> Not sure where the line would be drawn though.
[22:35] <zequence> I think Windows does something of the sort, where if you remove some applications, if there are system libraries that no other application is using, it's supposed to be removed
[22:36] <zequence> And say you have old versions of libraries. The packaging system on the OS should be able to keep track of when an older version of a library becomes redundant, and can be removed
[22:36] <len-1304> deb/ub sort of do that too... It would be nice if older kernels were removed once in a while though.
[22:36] <zequence> debian only keeps one version at the time, not many
[22:37] <zequence> not talking about kernels
[22:37] <len-1304> more than one version of tcl/tk, more than one version of the major gnome libs.
[22:38] <len-1304> not more than one package version of the same lib version though.
[22:39] <zequence> Some libs do have version naming, yes, you are right
[22:39] <zequence> But, not all
[22:39] <zequence> it's just <library>
[22:44] <len-1304> That is left up to the SW author or the packager. I would think any package could be built versioned
[22:44] <zequence> I'm not talking about individual packages. I'm talking about the policy of the entire system
[22:44] <len-1304> most src allows the base dir to be spec-ed at build time
[22:45] <zequence> anyway, seems like ardour3 got built finally
[22:45] <len-1304> Yes, but what I am saying is that if an org (like debian) decided to impose that, the src would not stop it from being done.
[22:49] <zequence> well, of course not, as long as you have access to the source. Also, it is quite possible to suggest policy changes upstream to SW authors, if nothing else, then in the form of "if" defitions
[23:26] <DarkEra> i'm off to catch up on some sleep, chat you later guys :)


[12:58] <hwpplayer1> Hi do you talk about high performance computing ?
[12:59] <tomreyn> hwpplayer1: i guess there's no reason not to
[13:00] <tomreyn> ...as long as it's based on ubuntu-server
[13:03] <hwpplayer1> tomreyn : run that command on your Ubuntu OS -->  sudo apt-cache search quantum | more > quantum.ubuntu.txt on your playground folder ofcourse
[13:04] <tomreyn> hwpplayer1: why?
[13:05] <hwpplayer1> tomreyn : i just want to talk about these packages and their sources , it is related with science , machine learning and high performance computing
[13:07] <tomreyn> hwpplayer1: okay, what's your goal?
[13:07] <hwpplayer1> tomreyn : to deploy them in a more comfortable environment
[13:08] <hwpplayer1> there is a channel for that #ubuntu-science
[13:09] <tomreyn> hwpplayer1: yes i guess it's best discussed there.
[13:09] <tomreyn> see also https://help.ubuntu.com/community/UbuntuScience
[13:10] <hwpplayer1> But no one is there , hope Canonical didnt left there
[13:12] <tomreyn> if you are trying to improve on the packaging of these softwares you'd best read up on ubuntu package development (see also #ubuntu-devel and it's channel topic)
[13:12] <hwpplayer1> tomreyn : not only packaging but development and service contiunity
[13:13] <tomreyn> if you'd like to get involved with software development you'd best contact the developers of the existing softwares directly (i.e. outside of ubuntu).
[13:14] <hwpplayer1> i'll make it up to you , a platform may be
[15:33] <hwpplayer1> I want to make an IRC Meeting on #ubuntu-science at UTC+3 19:00 Istanbul who wants to join are welcome
[19:53] <gunix> guys, i need some help :(
[19:53] <gunix> when using mariadb on lxd containers, mariadb won't start the nodes when using galera
[19:54] <gunix> i can start the first node with new glaera cluster
[19:54] <gunix> aand i can start any db as long as i disable the galera conf
[19:55] <gunix> hmm ... i think this might be related to the fact that connections between containers default to ipv6. i have to test this.
[20:18] <gunix> well, i disabled ipv6 on all nodes, AND i also rebooted the hypervizor and it seems to work now
[21:53] <tafa2> can anyone recommend a dnsbl other than bl.spamcop.net, zen.spamhaus.org and cbl.abuseat.org ?
[23:36] <keithzg[m]> tafa2: I also use truncate.gbudb.net, although in my postfix conf it's after the three you mentioned, heh.
[23:37] <keithzg[m]> IIRC it does catch some things the others don't from time to time
[23:44] <tafa2> thanks keithzg[m]
[23:44] <tafa2> added it looks good
[23:44] <keithzg[m]> No problem :)