[03:12] so, I think there's a problem with bog-standard postfix... [03:13] i'll have to dig into it, but it's odd that a postfix server with no firewall rules at all and a base "local site" instance cannot receive connections on port 25... [04:43] teward: "local site" only listens locally IIRC? [06:06] Good morning [07:16] good morning lordievader [07:17] Hey cpaelzer [07:17] How are you doing? [07:18] good, just too busy on most mornings to remember saying hi :-) [07:19] and 4 hours after I start or so it feels wrong to then say good mornign :-) [07:20] Good afternoon is a thing too 😋 [07:22] but I feel bad already for forgetting the community :-) [07:22] so I better stay silent [07:23] Hihihi [08:39] how it could be 43 000 dislikes and 26 734 views? :) [08:39] https://www.youtube.com/watch?v=DfNjAYilrFc [08:39] many Kremlin bots in ru-net [08:39] Neo4: a view is only caluclated after a specific % of the clip or time viewed. But you can dislike right away. [08:40] OpenTokix: no, here army of kremlin bots, they barely touch USA ellection, but here in local ru, they harder work, here factory of bots [08:41] OpenTokix: promotion, in runet better do video that support power, more chance that it will promoted by kremlin bots [08:43] about power say only good, or nothing ) [10:13] is PTR record for server correctly customized? [10:13] https://paste.ubuntu.com/p/68k4tv5NHw/ === Neo5 is now known as Neo4 [12:02] hello everyone, So i believe i have a compromised ubuntu server, alot of [sync_supers] processes grinding the CPU, this server hosts many wordpress sites which seems to be the root of the cause. I found alot of malicious file removed those did a fresh ubuntu install reattached the drive and about a week later they appeared again.. is there any way outside of using wordpress plugins to identify where and how and what is go [12:02] ing on? === miguel is now known as Guest73785 [12:03] thank you for any help in advance [12:19] Well, for now, take it off the network. They will reappear again unless you can figure out how the keep getting in. You need to start reading log files unfortunately [12:19] On web servers, outdated stuff are usually the culprit [12:20] You should never just rebuild and redeploy unless you have found and mitigated the issue [12:33] cpaelzer: I'm struggling whether to mark #1767886 as invalid or wontfix, see comment #3. tl;dr some settings changed their default values between 1.13 and 1.14. I updated the bionic release notes [12:33] in terms of packaging fixes, I guess we could detect upgrades from < 1.14, check the config file, and adjust settings, but I'm not comfortable messing with config files on upgrades, not even sure we can [12:33] any opinions? [12:34] https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes#SSSD my release notes update [12:54] ahasenack: only seeing your ping now [12:54] * cpaelzer is reading [12:56] ahasenack: we can mess with config files, but I certainly would not recommend it [12:56] the release not entry is great [12:57] ahasenack: I'd think you can do a few things to make people realize, but not mess with the config [12:57] ahasenack: e.g. you could have a news entry on this that would pop up in some environments [12:57] OTOH I only see people immediately-close those :-/ [12:57] so I'm not sure how useful that would be [12:58] if you think they actually watch the console you could detect your former version and warn there [12:58] but again - will it be read at all [12:58] ahasenack: you release notes entry is already great [12:58] hello, can anyone help me? [12:59] !asktoask [12:59] pedroj: if you just need somebody answering you - yes, otherwise one would need the actual question :-) [13:01] haha, how can I do a incremental backup without change the folders and docs to one archive? [13:05] cpaelzer: I think not many people are affected, or the other ones that were just figured it out themselvez [13:05] themselves [13:05] since this change was introduced in 1.14.0, and the first ubuntu release that had >= 1.14 was zesty [13:06] cpaelzer: about console warnings, I think that's not applicable because people would hit this in release upgrades, not regular upgrades [13:07] what seems to be the problem? [13:07] ahasenack: then I think you have done all you can [13:07] the bug is just another piece that will direct to the release notes [13:08] can somebody file me in regards to bug you guys are talking about? [13:08] cpaelzer_: ok, so "wontfix" or "invalid"? :) [13:08] I always find "invalid" so rude [13:08] TheEagerPadawan: bug 1767886 [13:08] bug 1767886 in sssd (Ubuntu) "sssd-ldap breaks automount on bionic" [Medium,Incomplete] https://launchpad.net/bugs/1767886 [13:08] if there were a release notes task, I would add it to the bug [13:08] and mark that task as fix released [13:09] ah had issues my self with cryptsetup during my 17.10 -> 18.04 updated. Had to use a liveusb, decrypt the luks partition, decrypt the private desktop [13:09] ahasenack: I thought there is such a task [13:09] backup up everything :p [13:09] tbh, I haven't searched [13:10] wow, found ubuntu-release-notes [13:10] cpaelzer_: ^ sounds good? === rmk` is now known as rmk === Kamilion|ZNC is now known as Kamilion === markus_e92_ is now known as markus_e92 === Redfoxmoon_ is now known as Redfoxmoon === StathisA_ is now known as StathisA === slashd- is now known as slashd [13:17] hello, how can I do a incremental backup without change the folders and docs a one archive? ^^ thanks [13:22] pedroj: What do you mean with 'without change the folder and docs a one archive'? Just a simple A -> B sync? [13:24] lordievader: I am trying to do the incremental backup with TAR but TAR change the files into .tar [13:27] Yes, that is what tar does. You might be interested in dirvish. Makes incremental backups using hardlinks. [13:30] ^^ nice, I'll try dirvish now, thanks [13:39] blackflow: if you have issues with netplan, I invite you to please file bugs in Launchpad so we can address them... [13:39] cyphermox: my issue with netplan is the existence of it. I doubt you'd address that, but thanks. :) [13:43] JanC: i mistyped, i meant "internet site" [13:43] it was late when I posted :P [13:43] JanC: core issue is a POstfix listening on port 25, 587 wasn't accepting connections on this one system [13:43] but i've since ruled out Postfix and pointed at a networking issue where the server sits, so I have some tickets pending to upstream. [13:43] at the DataCenter [13:43] blackflow: alrighty then. what would you prefer, we keep ifupdown? [13:43] 25 is indeed often filtered upstream. [13:44] cyphermox: is it broken? [13:44] yes [13:44] (thank you spammers) [13:44] so why not networkd directly? [13:44] or NetworkManager for desktop installations. [13:44] because you also have NM [13:44] and that makes it hard for everyone having to deal with different setups [13:45] (for one, with netplan you can copy settings across systems trivially) [13:45] or switch the renderer to NM if you also need, say, some random wifi feature in extra [13:46] my example is my own setup here: https://paste.ubuntu.com/p/5sMkW4S5DH/ [13:46] ^ this works with NM because I also want NM to deal with wifis when I travel, give conferences, etc. [13:47] and this works the same on my server, with the renderer changed to networkd [13:48] I wonder what percentage of deployments are switching between networkd and NM so frequently that a third layer and increase in complexity is needed. [13:48] it's not about switching [13:48] it's about being able to have one single config file you can comprehend [13:48] the 15th standard? :) [13:49] meh [13:49] https://xkcd.com/927/ in case the reference is unclear :) [13:49] I know that reference. [13:49] the funny thing about that comic is how true it is. [13:50] so that's my problem with netplan. addition of new complexity that does not solve any actual real world problems. [13:55] really this Canonical's invention of Canonical specific things is only being harmful to the community. creates more fragmentation and does not solve any problems. Systemd was supposed to be the one ring to rule them all, among distros, and what happened in reality is that different distros deploy different versions, with different features, and different abstractions atop of it. 15th standard all [13:55] over again. ;) Was snappy really needed? couldn't take flatpak and evolve it? now we have vendors who AGAIN have to figure out which of the 15 standards to support. [13:55] /rant. [14:02] any idea why OS build comes up with em1 instead of eth1 for some HP servers? [14:03] axisys: your system has embedded devices, they are detected as such so they are named that way to make sure things don't change name across reboot (there used to be issues where it might be eth0 or eth1 depending on scan order) [14:05] cyphermox: how do I find out how ubuntu decides it? [14:06] cyphermox: good to know .. thank you === cpaelzer_ is now known as cpaelzer [14:12] axisys: it's systemd work [14:12] axisys: there's a list somewhere I think [14:13] looking for it.. not in /etc/systemd or /usr/lib/systemd [14:14] that https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_id.c#L20 ? [14:17] trying to see which file in the system [14:17] is the OS* [14:18] there shouldn't be one, but I could be wrong === kees_ is now known as kees === cnewcomer_ is now known as cnewcomer === shadoxx_ is now known as shadoxx [17:54] nacc: hi, should I unassign you from https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1644057 ? [17:54] Launchpad bug 1644057 in logwatch (Ubuntu) "Excessive Disconnect unmatched entries from sshd" [Undecided,Triaged] [19:28] frickler: if you get a minute, can you take a look at our testing results for 1750121? [20:46] ahasenack: yeah probably :/ === popey_ is now known as popey === rsalveti_ is now known as rsalveti === fidothe_ is now known as fidothe === soahccc_ is now known as soahccc === odc_ is now known as odc [20:54] nacc: thx, not a problem :) === tomreyn_ is now known as tomreyn [21:11] with the live 18.04 iso, i'm getting boot holds on a "Holds Snappy daemon refresh," after it finishes, it just seems to be sitting at the boot log (nothing else is happening) [21:11] hm [21:13] i see, about 5 minutes after, it did continue. [21:16] shouldnt pause tho, although ive only tried the minimal install [21:23] how do i opt out of cloud-init? [21:25] am i missing a minimal iso http://releases.ubuntu.com/18.04/ ? [21:54] kevr: the traditional d-i based installer is available here right now http://cdimage.ubuntu.com/ubuntu-server/bionic/daily/current/ [21:55] although I'm confused as to why it is a "daily" [21:55] and the minimal is available here https://help.ubuntu.com/community/Installation/MinimalCD [21:56] powersj: AHA, thank you! [22:13] kevr, powersj: i think http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04-server-amd64.iso is a better link btw [22:14] ah yes it is [22:14] thanks! [22:16] okay [22:16] thanks [22:16] what does the -live- mean? [22:16] a nightly build? [22:17] live is using our new installer based on subiquity [22:18] oh.. i see