=== miguel is now known as Guest43488 === jhebden is now known as jhebden-afk === jhebden-afk is now known as jhebden [03:07] Hello everyone. I have an LXD server (18.04) with five containers running on it. The containers have very low usage, it's more of a test server for me to play with than it is a production system. My issue is that it runs VERY slow. For example, if I run: apt dist-upgrade (for example) it takes a very long time, it seems that it can take 30-60 seconds to install any app (the packages seem to download fast though). I was hoping someone [03:07] can provide documentation links to what I can do to tune it, I wasn't able to find anything [03:08] Also, it's installed via snap, if that matters === Aztec03 is now known as Panoptes [05:59] Good morning [06:00] jlacroix: I'd try to pinpoint what the problem actually is. Is it disk related, ram, cpu, etc. === stgraber_ is now known as stgraber [12:18] who know whether my server is properly work? [12:18] here is test result [12:18] https://ssl-tools.net/mailservers/mail.kselax.ru [12:19] What shall I do for correct those all? [12:27] Neo4: You don't want to use a self-signed certificate. [12:30] lordievader: see, there weak ciphers, do you know how I could forbid weak ciphers? [12:30] and should I forbid them? [12:30] I try to stay away from mail servers, so no. Read the documentation of your mail server. [12:31] lordievader: how TLS works? [12:31] there ssl3 [12:31] But weak ciphers is less of a problem than a self signed certificate. [12:31] lordievader: no [12:31] Self signed cert is no less secure then a signed cert. [12:32] Fair enough. [13:15] not bad? :) [13:15] https://ssl-tools.net/mailservers/kselax.ru [13:15] I have to get certificate from let's encrypt for mail.kselax.ru, how fast get it? [13:17] see here, How to correct that all errors? [13:17] https://mxtoolbox.com/domain/mail.kselax.ru/ [13:28] Neo4: blacklisted by Spamhaus? you're better off getting a new IP. Preferably with a reputable hosting provider that is not blacklisted. [13:34] and stop what ya doin to get blacklisted [13:36] blackflow: can I write them and ask kick me from black list I won't more? [13:56] Neo4: you could try, but that's Spamhaus. Chances are they'll just laugh at you. [13:57] You are probably there for a reason [13:57] and they have a process for being removed [14:30] nice :) [14:30] https://ssl-tools.net/mailservers/kselax.ru [14:31] left overcome 5 errors and everything will work perfectly [15:32] ok I've added byobu to my ubuntu server, and I want to try and start a second shell session but none of the commands I've googled seem to be working. is there a default key combo? I didn't customize anything [15:32] ctrl-a [15:32] then it will ask you [15:33] ah, thanks! [16:07] Hi, anyone has experience with conjure-up? is it compatible wit 18.04? [16:46] gaughen: yes [16:46] and yes [16:46] dpb1, what? [16:47] dpb1: did you mean gabboman, who left? === Panoptes is now known as Aztec03 [16:55] nacc: yes [16:55] :) [16:55] gaughen: sorry === FalconMillennium is now known as FalconMillenniu === FalconMillenniu is now known as FalconMillennium [20:49] hey, I'm having issues with setting static IP with netplan [20:49] I use the following YAML: https://codebeautify.org/yaml-validator/cbd763fb [20:49] which is valid [20:49] but netplan apply gives an error [20:49] Error in network definition //etc/netplan/01-netcfg.yaml line 4 column 13: expected mapping [20:49] enoch85: oh, sorry, i think your indentation is wrong maybe [20:49] enoch85: you should be indented below the ens32: line, no? [20:50] enoch85: yaml is sensitive to the layout [20:51] nacc, yeah I know yaml is sesetive, and I really don't like the fact the ifupdown is depcrecated in 18.04, but yeah... why does a valid yaml gives an error [20:51] hwo should I intendent exacly? [20:51] how* [20:51] enoch85: well 'valid' just means it parses [20:51] not that it's well-formed [20:51] ok, hmm [20:52] enoch85: you are defining ethernets, which means the first entry is the key into that dictionary (that's how i think o fit) [20:52] so is it 2 spaces between every intended line? [20:52] so everything for ens32 should be under ens32: indentend [20:52] *indented [20:52] otherwise, it thinks you are defining an empty (or invalid) ens32 entry, then a dhcp4: entry (also invalid), etc. [20:52] also take a look at: https://netplan.io/examples#dhcp-and-static-addressing [20:52] powersj: thanks! [20:53] enoch85: i say this knowing next to nothing about netplan syntax, just based upon judicious use of parsing :) [20:53] ok, so it works now :) [20:54] https://codebeautify.org/yaml-validator/cb8a1a24 [20:54] thanks ncc [20:54] nacc, powersj [20:55] enoch85: yw [20:55] enoch85: it helps to translate the yaml into a dictionary [20:55] enoch85: to see how it's actually going to be used [20:58] nacc, I know what dictionary is, but what do you mean in relation to netplan? [21:02] enoch85: the yaml is being transformed into a dictionary [21:02] nacc, aah ok [21:02] enoch85: so if you had read your original, as a dictionary, i think you would have seen the error immediately [21:02] I have code in progress that should improve the error reporting [21:04] cyphermox: nice [21:04] cyphermox: yeah there seem to be 'classes' of errors [21:04] from parse failures to structural issues === Epx998- is now known as Epx998