=== thumper-bjj is now known as thumper [01:24] hi [01:25] Who are there? [02:33] what? [11:55] Good afternoon. === n00p is now known as naise [12:43] good afternoon [12:57] o/ [13:04] Where can i learn about the stuff in ifconfig? [13:04] E.g. what is utun, what is ethernet etc. [13:05] different device file types, you may want to look at the bridge-utils documentation [13:07] ikonia: Is there a place that generally gives an introduction in terms and concepts? [13:07] sth like https://www.digitalocean.com/community/tutorials/an-introduction-to-dns-terminology-components-and-concepts for dns [13:07] shredding: no idea [13:08] ok === Error404NotFound is now known as E404NF === E404NF is now known as Error404NotFound === Error404NotFound is now known as E404NF === E404NF is now known as Error404NotFound === rbanffy_ is now known as rbanffy [14:56] How can I list all processes that are running? when I run top some PIDs come in an out of the list, but they aren't there constantly [14:57] ps aux [14:57] for example mysqld will show up running over 3 GB but then dissapear [14:57] "ps auxww" shows you even more info, if that is desired [14:57] jayjo: you can also scroll in top, but I find htop much easier to use. [15:04] ps aux and top seem to be showing me different things. top says I have 8GB memory (and I actually don't know how much I have, can I find tha from the command line... I dont have access to the AWS dashboard) but in ps aux it says the same memory is being consumed but it is 10% of memory [15:04] under %MEM [15:04] See free -m [15:05] Pici: these are MBs? [15:05] Yes. [15:05] The -m means MB [15:05] ah OK, so the %MEM is not accurate I think in ps aux [15:15] ddellav, coreycb: any reason where holding back on the swift 2.6.0 upload? [15:16] jamespage, nope not that I know of [15:16] coreycb, let me take a look - I'll sponsor it... [15:16] jamespage, thanks [15:32] coreycb, I'll try to unpick the python-django-compressor merge I've had on my list for a while now today as well but might be tomorrow [15:33] jamespage, ok [15:33] jamespage, I've started on the b3 core packages, and so far just blocked on the new paramiko release [15:34] coreycb, urgh [15:34] jamespage, which seems fairly important: https://review.openstack.org/#/c/268197/ [15:46] im trying to install ubuntu 12.04 but at downloading installer component i just get a purple screen and then nothing happens what could this be [15:47] coreycb, ~ well yes it important but generally rather than openstack specifically [15:57] im trying to install ubuntu 12.04 but at downloading installer component i just get a purple screen and then nothing happens what could this be [15:59] i also tryed other mirrors but all mirrors seems to have this issue [16:59] rbasak, hello =) would you like to be on the Developer Membership Board? [16:59] jamespage, hello =) would you like to be on the Developer Membership Board? [16:59] xnox, +1 on rbasak on the DMB [17:00] Daviey, hello =) would you like to be on the Developer Membership Board? [17:00] xnox, lol [17:00] jamespage, excellent. Do you have rbasak's gpg key to sign and send in nomination? =) [17:01] xnox, yes [17:01] coreycb, hey - looking a python-django-compressor - will need a MIR for three new packages to go to 2.0 [17:01] two are pull-outs of existing vendored code in 1.6 [17:02] and the other is new [17:05] ddellav, take a look at python-pika-pool for an example of running tests as autopkgtests [17:07] Howdy, folks. So I have a bit of a confusion that maybe someone here could help me work out... why is it that there is so little interest in pulp in the .deb world? [17:07] jamespage, need a hand with those MIRs? [17:07] I mean, it's been over two years since the basic framework for .deb support was published to the pulp github, and it's *still* nonfunctional. [17:07] coreycb, I'll need a ffe first - you focus on the rest of the stuff... [17:07] jamespage, ok [17:11] What's pulp? [17:11] Pulp is a repository synchronization/publication engine [17:11] Why does the .deb world need this? [17:11] http://www.pulpproject.org/ [17:12] rbasak: Well for one it would enable the use of products like Katello === conan141- is now known as conan1415 [17:12] What's Katello? Why does the .deb world need that? [17:13] It is a significant gain over apt-mirror in that it enables administrators to create repositories interanally and associate them with specific servers in order to more readily manage what packages are accessible to what servers (up to and including recency of mirror, to enable package lifecycles for promotion paths from nonprod to prod, etc., etc..) [17:14] Katello is the opensource upstream of the Red Hat Network Satellite (version 6.x) ( http://www.katello.org/ ) [17:14] It ... does a great deal of things, including bundling foreman, puppet, pulp, and candlepin [17:14] Gives you recency, inventorying, ownership tracking, config management, etc., in a bundled manner. [17:15] I don't see a benefit here. You need to frame this in terms of the benefits it brings, not in terms of other things whose benefit you have also not explained. [17:15] O_o [17:16] IM(personal)HO, apt repositories outside the distro are fundamentally broken anyway. PPAs are about as far as they'll stretch. [17:16] apt wasn't designed for this, and it shows. [17:16] I suspect RPMs are the same. [17:16] rbasak: You can do PPAs as well with this, but it's primary function is in handling the core distro channels. [17:16] It's a repository mirroring engine. [17:17] coreycb, for reference: [17:17] https://bugs.launchpad.net/ubuntu/+source/python-django-compressor/+bug/1554134 [17:17] Launchpad bug 1554134 in python-django-compressor (Ubuntu) "[FFe] python-django-compressor 2.0" [High,New] [17:17] It lets you do things like expose the current packageset to your dev environment, a week old version of that to your acceptance/staging/testing environments, and a month old to your production [17:18] That sounds handy. [17:18] So you can just let packages autoupgrade and still have that assurance of burn-in on all packages. [17:18] This is what I mean by "recency" [17:18] Make it do that easily for Ubuntu users and perhaps they'll take it up. [17:18] It *ALSO* lets you do things like track which DSAs (or the Ubuntu equivalent) are applicable to which of your servers. [17:18] rbasak: ... That's exactly what I'm asking about. [17:18] Add a million layers of abstraction in the middle, and I suspect that nobody will bother. [17:19] Why isn't this there already? It just needs plugin development. [17:19] Apparently the answer is nobody in the .deb world has heard of it. Which seems surreal to me. [17:19] Someone needs to champion it for Ubuntu I guess. [17:19] You're familiar with Ubuntu Landscape? [17:19] Yes. [17:19] jamespage, thanks [17:19] Katello is a free and opensource "competitor" in a sense to it. [17:20] (You can also use pulp for pip, cpan, gems, or puppetforge) [17:20] So be competitive :) [17:20] I'm not a developer. [17:20] Ah. [17:20] I'm just trying to understand why it seems like nobody in the .deb world seems to give a crap about it. [17:20] What you're really asking is why nobody is spending money on developing it. [17:20] I've been asking this for years. I never get a good answer beyond "I've never heard of it" [17:20] Which is just ... bizarre. [17:21] There's a big difference between those questions. [17:21] Nobody has heard of it because nobody else is spending resources on developing it for this world. [17:21] Simple answer I think. [17:22] * Logos01 shrugs [17:22] It's not even like it would take a great deal of manhours to do. [17:22] https://github.com/pulp/pulp_deb [17:22] Give somebody a good reason to spend those manhours, and perhaps they will. [17:24] That is ... a surreal answer, to me. [17:24] That is exactly how the Free Software ecosystem works. I don't understand why it's surreal. [17:25] Because the benefits of the thing are rather extensive; knowledge of the project in and of itself should comprise sufficient reason for at least *someone* to want to make that development. [17:25] Especially considering it is developing a plugin, not overhauling the engine itself, that is all that's called for. [17:25] That's not how it works. [17:25] And yet no matter how many times I've brought this up over the years nobody has ever seemed to ever say anything other than "Why should we care?" [17:26] And I can explain and reexplain the benefits of having repository management and all the ancillary benefits therein and it just doesn't sink in. [17:26] You can wish for developers to magically appear all you want. Actually everyone only does stuff because of some reason to motivate them. This applies to everything, not just this project. [17:28] There's a difference between wishing for something to have happened, and trying to understand why there seems to be significant resistance to something that has obvious and imminent gains for the community. [17:28] The latter is what I'm trying to figure out here. [17:28] I don't see any resistance. [17:28] You say resistance, I say lack of motivation. [17:29] That is; not merely, "Why hasn't someone done what *I* want" but rather "Why has no one done this despite how painfully obvious the benefits of it are?" [17:29] And to be clear; they *are* [17:29] Which is why I find answers like yours surreal. [17:29] Because this is far from the first time I've brough this topic up. [17:29] I suspect most people in a position to need this find it easier to just pay for Landscape. [17:29] Yet that is *always* the answer: "Why should we care?" "Do it yourself", etc.. [17:30] s/need/develop/ maybe. [17:30] Again, that's how the ecosystem works. [17:30] Or, more commonly, as you did, "Never heard of it" [17:30] And it's that last part that is the most perplexing. [17:31] Oh well. [17:31] It seems the answer hasn't changed from the last dozen times I've asked this question (in here, no less) [17:31] Thanks for your time. [17:31] * Logos01 walks away in utter astonishment [17:31] That's because the motivation for the existence of the Free Software ecosystem hasn't changed, either. [17:32] How can you still be astonished, if others have given you the same answer previously? [17:32] well, it seems like pulp explicitly lists only RH-family distros, no? and the diagram is all yum ... http://www.pulpproject.org/ [17:32] matsubara, rbasak: did you guys make progress on the dlm merge from debian? [17:32] or is that the point of this discussion? [17:33] jamespage: I don't recall any movement on that. [17:33] jgrimm: do you know the status of the dlm merge? [17:33] "There is also a community-contributed plugin for Debian packages." [17:33] Logos01: --^ ? [17:33] Logos01: why isn't that "good enough"? [17:34] nacc: It's a skeleton that is non-functional and has been in that state since it was first created over two years ago. [17:34] It wouldn't take much work to finalize but nobody in the .deb world ever seems to care. [17:35] It sounds to me that it's a RH world product that claims to be "cross platform" in order to make it more appealing to users to lock themselves in, because in reality they're only paying lip service to that claimed portability. [17:35] Logos01: i have to agree with rbasak; what you've described above is a generic argument for why pulp is good. But not why I should care to contribute. And tbh, it doesn't solve a gap for me, as a user. The gap seems to be deploying pulp in a place that wants to host Debian [17:35] or Ubuntu [17:36] nacc: I'm not agitating for it to be done. [17:36] I'm not *asking* for it to be done. [17:36] I'm trying to understand why nobody in the .deb world already *wants* it to be done. [17:38] Logos01: why would anyone in the .deb world particularly care to make a RH/rpm-based product integrate with deb-based? why is it so much better than what already exists? (and if it is, i think it would naturally be supplanting it in the ecosystem ... the best tools, ime, exist & thrive in FOSS) [17:39] rbasak, I'll deal with it - clearing my merge backlog... [17:39] nacc: The closest analogue to it is apt-mirror, and pulp is a significant gain over that in terms of the raw functionality it provides, to the point where I don't even know where to begin to describe how much so this is true. [17:40] And you're asking exactly the question I'm asking with the latter parts there. Which is why I am constantly amazed by the lack of penetration or care/concern it has here. [17:40] The people who might want that functionality probably use Landscape. So you need to be comparing against Landscape, not apt-mirror. [17:40] rbasak: Pulp is best compared against apt-mirror. [17:41] Katello, which uses pulp as a component, is what is best compared against Landscape. [17:41] If you say so. I doubt users care. [17:41] You can use Pulp without anything else. Many do. [17:42] Also, and this is a major consideration point; Individuals who want to learn how to manage the closed-source product from Red Hat (RHN Satellite) can deploy their own Katello instances in the lab, and take exactly those skills across without having to license anything. [17:42] Makes for a much easier entry path into competence. [17:44] I use aptly snapshots to do what sounds like the same things [17:44] same things being alpha/beta/prod snapshots on a local mirror plus personal repos [17:47] rattking: From the description (on the page as well) it seems very similar, yes. [18:55] jamespage: i just noticed something else about commons-vfs that I missed before, I apologize! there's a bindep from libcommons-vfs-java-doc -> libcommons-net-java-doc but the latter is in universe. It looks like historically (it hasn't been packaged in ubuntu since oneiric?) it was in main. Should it be MIR'd? the package does build & test successfully without either of libjackrabbit or [18:55] libcommons-net-java-doc, but i'm guessing maybe some documentation linking won't work? [19:45] Hi. Does someone know a tutorial (that works) for running at least 1 application over a vpn, but the rest of the server over the normal ethernet connection === alexisb is now known as alexisb-afk === Pici is now known as Guest19584 === Pici` is now known as Guest1760 [20:17] jancoow: VPN's usually work on a basis of routes, not applications. [20:24] jancoow: lordievader: https://schnouki.net//schnouki.net/posts/2014/12/12/openvpn-for-a-single-application-on-linux/ [20:25] bekks: 'That page doesn't exist!'? [20:26] Ah, double schnouki.net [20:26] indeed - no clue how I copied that :D === alexisb-afk is now known as alexisb [20:27] This forces a program to use a different default gateway? [20:27] Yes. Which basically what a VPN does, as well. [20:27] well i tried that [20:28] the virtual interface is kinda working but it lost connection after x seconds [20:28] like i could ping , but when i try 10 seconds later: nope no connection [20:28] Nice though. [20:28] (and that's without vpn running) [20:28] jancoow: So, the underlying network connection has problems? [20:29] jancoow: that solution requires a vpn. [20:31] bekks: i also tried a vpn. If i do it in "the first 10 seconds" the vpn could communicate with the vpn server. But this also timed out after 15 seconds or so [20:31] lordievader: i do think so! [20:32] i simply runned this https://gist.github.com/Schnouki/fd171bcb2d8c556e8fdf with ""up" [20:32] and changed the fping to ping (because i doesn't have fping installed) :) [20:33] and eventually started openvpn (with another config, ofcourse) [20:33] jancoow: So fix your network first ;) [20:33] lordievader: well the normal ethernet connection is just fine (the one on eth0) === Monthrect is now known as Piper-Off [20:34] < jancoow> lordievader: i do think so! <- /me is confused [20:34] wut ;p [20:35] I asked if the underlaying network connection has problems, you said yes. And later you said it didn't. === Piper-Off is now known as Monthrect [20:36] lordievader: oh wel. The "Yes" was more on the underlaying network connections UNDER the vpn :). So actually the bridge between the virtual interface and the realinterface [20:36] Ah, the regular network is fine? [20:37] yes! [20:37] server is already up for 200 days and never had problems :) [20:39] Ah, I misunderstood. So after some time the vpn connection, and only the vpn connection, dies? [20:40] not only the vpn connection. Even when i doesn't start the vpn on it, and i'm trying to use ping it doesnt work [20:41] jancoow: Was the "ip netns exec frootvpn ping www.google.com" from the guide set? [20:41] yes [20:41] this is for example the output after i imdetialy run the script: https://jancokock.me/f/b566a [20:42] Does ping work after removing that setting? [20:42] how can i test that without running that command? [20:43] You cant. :) [20:43] You cant remove those settings? [20:44] well it isn't a setting, right? It exec's a program, and that programm is ping [20:44] No. The exec program is frootvpn [20:44] and that executes ping. [20:44] ah! [20:45] * lordievader fears his understanding of the Linux network stack is too little [20:45] actually that frootvpn is a network namespace which you execute ping in. [20:46] So it is vital to use "ip netns frootvpn ..." [20:46] but why does it stops working after some seconds :/ [20:46] that's the question ; [20:46] ;p [20:47] do you know if there are somewhere logs ?? [20:47] Look at the logs? :) [20:47] ?* [20:47] Logs are in /var/log/ e.g. [20:47] yeah [20:48] there are a lot of logs there :D [20:48] Thats why the directory is names /var/log :P [20:48] the only thing i can see in dmesg is [16873278.337995] IPv6: ADDRCONF(NETDEV_UP): vpn0: link is not ready [20:48] [16873278.360117] IPv6: ADDRCONF(NETDEV_CHANGE): vpn0: link becomes ready === _thumper_ is now known as thumper [21:03] bekks: any idea? :D [21:29] btw [21:29] is it bad that i didn't rebooted my server for already 200 days [21:30] If you did security updates in that time and didn't reboot yet, then yes [21:30] just regual updates in apt update/upgrade [21:31] during the past 200 days there was the glic patch, which suggests you should reboot [21:33] (not all ubuntu versions / platforms were affected by it, though). while i have not checked, it is somewhat likely that kernel security patches were also made available during this time. which, unless you use live kerbel patching, would also requiore a reboot to apply. [21:33] s/ kerbal / kernel / [21:33] ubuntu doesn't have the ability for live kernal patching right? [21:34] only redhat right? [21:34] linux has the ability [21:34] in some versions or other [21:37] Ubuntu does, but it gets convoluted [21:37] !info ksplice [21:37] ksplice (source: ksplice): Patching live kernel without having to reboot. In component universe, is optional. Version 0.9.9-5 (wily), package size 527 kB, installed size 3525 kB (Only available for i386; amd64; arm; armel; armhf) [21:38] and how safe is it to do? [21:38] or is it stable [21:39] ksplice itself is stable, but the updates then work differently than normal === ^King is now known as King === King is now known as KingRodriguez === KingRodriguez is now known as King === King is now known as King` [22:01] ddellav, can you update the (build-)dependencies for heat? [22:01] ddellav, looks ok other than that [22:01] coreycb ok [22:06] jancoow: If you're worried about live kernel patching then you might want to look into LXD [22:06] And then containerize all of your services. === King` is now known as King [22:06] Probably a safer/easier path [22:35] i'm not woried [22:35] just asking :) [22:35] still didn't fix my vpn [22:50] Hey all. If this is not yet on-topic I'll go elsewhere, but Xenial installs with the server ISO that set up LUKS root seem to all time out on shutdown, as systemd can't dispense with the LUKS container or the MD-RAID (in some cases) underneath it. Is there a known workaround [22:50] ? === thumper is now known as thumper-dogwalk [22:59] Hello! i have a question! === King is now known as King` === King` is now known as King [23:22] !ask [23:22] Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience [23:25] ChibaPet: probably best to file a bug against systemd, sounds like something that might require attention from someone in foundations [23:26] sarnold: Yeah, I suspect that's the thing to do. I'll also read a bit about this shutdown-initrd concept. [23:26] I wish I'd noticed this sooner, as we're somewhat close to release. [23:27] Anyway, commuting, and I'll file a bug report when I am connected via wires again. [23:27] yeah, I'm surprised just how soon we are.. [23:27] mm wires === jgrimm is now known as jgrimm-afk