[01:03] <Benl90> hello. I have problem. I done something stupid, really stupid, I do chown -R root:root .* on /root and it change all permission on the OS, now I can't start mysql service and other things. Is there anyway to fix it? Thanks
[01:04] <sarnold> Benl90: /root or / ?
[01:04] <Benl90> on folder root, but it impact the /var/lib/ also
[01:04] <Benl90> I need to make sure mysql server back online, but now I can't
[01:05] <sarnold> Benl90: if you mean / then you are indeed in trouble
[01:05] <Benl90> sarnold, I did it on /root and /var/lib only
[01:06] <Benl90> Any suggestion?
[01:07] <sarnold> Benl90: you can ignore /root because everything in there should be root:root
[01:07] <Benl90> nah how about /var/lib?
[01:08] <sarnold> Benl90: http://paste.ubuntu.com/p/23K6XQ4ZMr/  http://paste.ubuntu.com/p/WTTnfP5BQF/  -- this is two machines I've got easy access to
[01:17] <Benl90> I've fix the whole permission but still mysql won't run. also there's error on journalctl -xe like this https://paste.ubuntu.com/p/3k9yJ4bpFc/
[01:21] <sarnold> try restarting rsyslog and see if you get error messages there
[01:27] <Benl90> sarnold, I tried, and nothing error log help https://paste.ubuntu.com/p/dr2J9qTyN6/. Any suggestion?
[01:28] <sarnold> Benl90: are there more detailed logs in a /var/log/mysql* or /var/log/syslog?
[01:31] <Benl90> no help from mysql/error.log, but some clue maybe on syslog https://paste.ubuntu.com/p/86hcKfVggV/
[01:32] <Benl90> apparmor denied operation open
[01:34] <sarnold> Benl90: [ERROR] Could not open file '/var/log/mysql/error.log' for error logging: Permission denied
[01:34] <sarnold> Benl90: you'll have to fix this one first
[01:34] <Benl90> sarnold, how to fix it? Ehmm..
[01:34] <sarnold> the apparmor denial is on name="/sys/devices/system/node/" -- which is probably just mysql trying to figure out what NUMA nodes the system has
[01:35] <sarnold> Benl90: ls -l /var/log/mysql/error.log /var/log/mysql/ /var/log/ /var/  -- and make sure those are correct
[01:35] <Benl90> sarnold, to mysql user?
[01:35] <sarnold> Benl90: probably
[01:35] <sarnold> double-check against a good mysql install somewhere
[01:39] <Benl90> sarnold, Ah it's running now. Thank God. Thank you sarnold. But I still worry about the rest of the permission. chmod -R is really dangerous :'(
[01:39] <Benl90> I can't think more :'(.
[01:41] <sarnold> Benl90: indeed, there's probably a lot more wrong on this system if you've not yet fixed up the permissions on subdirectories and subsubdirectories etc
[01:41] <Benl90> sarnold, Then I must recheck it one by one?
[01:42] <sarnold> Benl90: yup
[01:42] <Benl90> sarnold, :'(
[01:54] <Benl90> sarnold, Do you ever handle ms sql server on ubuntu?
[01:54] <Benl90> The ms sql server also down. maybe with the same reason
[01:55] <sarnold> Benl90: not often, someone seems to ask about it every six months or so..
[01:55] <sarnold> Benl90: do the same thing -- find its logs. if it's not logging, find out why. fix that. iterate. :)
[01:59] <Benl90> The log for database 'master' is not available. Check the operating system error log for related error messages. Resolve any errors and restart the database. I can't guess the permission of the ms sql log. Ugh
[02:08] <Benl90> sarnold, Thank you. It's running now. Seems the problem really only because of permission. Thank god!
[02:08] <sarnold> Benl90: good news :)
[03:07] <Benl90> sarnold, Anyway, is there anyway to fix the permission automatically?
[03:08] <sarnold> Benl90: no; you can try something like a loop over all pacakges and apt install --reinstall -- but I'd like to make clear that I don't know how well that will work out
[03:09] <sarnold> Benl90: that won't fix anything that's created at runtime by programs; it can only fix up whatever might be packaged
[03:11] <Benl90> oh so the reinstall is a parameter on the command. Seems the sudo also affected. I really curious. When I did "chown -R root:root .*" on folder /root, why it recursively done to the whole system?
[03:15] <sarnold> /root/../
[03:15] <sarnold> it climbed back up and kept going..
[03:15] <Benl90> sarnold, ouch..
[03:15] <sarnold> yeah. everyone learns this one the hard way.
[03:15] <sarnold> yours is probably more frustrating than most
[03:16] <Benl90> sarnold, anyway why if I use  "chown -R root:root *", it won't touch .git directory or hidden folder I mean.
[03:16] <Benl90> sarnold, Does it mean I need to reinstall the OS?
[03:16] <sarnold> /root/.???* is the usual fixz
[03:16] <Benl90> sarnold, what's .???*
[03:17] <sarnold> Benl90: depends upon how much was changed.. a reinstall might be the easiest way forward, but if you were able to ^C it very quickly, maybe it's more work..
[03:17] <Benl90> sarnold, I left it there, at least the OS run for now.
[03:17] <sarnold> hthat limits the expanded files and directories to starting with a period, several chars, and then any number of other chars; it ought to match all the dot files and directories excepting . and ..
[03:18] <Benl90> oh the ?? mean minimum character?
[03:18] <sarnold> .a or .b or whatever won't match that
[03:19] <sarnold> sortof.. try echo /etc/rc?.d to get a quick idea..
[03:19] <sarnold> or echo /etc/sub?id*
[03:20] <Benl90> ah. I see. echo /b??, shows bin
[03:20] <Benl90> learn the hard way :'(
[03:22] <sarnold> yup. like I said, everyone does this one sooner or later.
[03:22] <sarnold> you're lukcy if you do it early on a system that doesn't matter to anyone else..
[03:23] <sarnold> unlucky if your job depends onthe correct working of the machine
[03:24] <Benl90> sarnold, The 2nd one :'(
[03:24] <sarnold> :(
[03:24] <Benl90> Because for long time on /var/www/* It never done something harm, and just stop on the /var/www
[03:25] <Benl90> at least my boss can present the app to client for now.
[03:26] <Benl90> sarnold, does "action 'action 0' resumed (module 'builtin:omfile')" is also an error?
[03:27] <sarnold> Benl90: almost certainly that's rsyslog doing its best to report an error
[06:34] <lordievader> Good morning
[09:35] <miu5> hi, where can i find out what kernel ubuntu-16.04.4-server-amd64.iso ships with by default?
[10:53] <Benl90> 4.14should be
[15:06] <dreugeworst> Hi all, I have a machine with Ubuntu Server 18.04 installed, and am trying to replace systemd-resolved. I've installed resolvconf, network-manager and dnsmasq. It seems to delegate to dnsmasq just fine, and it seems in turn to call to resolvconf, but resolvconf doesn't work. systemd-resolved found the network dns server fine, but resolvconf only works if I add, say, 8.8.8.8 to resolv.conf.d/head. anyone know what
[15:06] <dreugeworst> might be up?
[15:10] <Ussat> I would first ask, why ?
[15:15] <dreugeworst> I've had systemd-resolved crash and then it gets in a loop trying to restart but unable to.
[15:17] <tomreyn> that's bad, and i've never heard of it. did you report a bug?
[15:18] <dreugeworst> did not report one, no, was too preoccupied trying to get the server working again
[15:18] <tomreyn> was your system fully updated when it happened? is this amd64?
[15:18] <dreugeworst> I updated it a couple of times hoping it would fix the error, it's amd64 yes
[15:20] <tomreyn> the crash log should still be present in /var/crash
[15:22] <tomreyn> hmm, i just looked at previously reported crashes of systemd-resolve on 18.04, and there are none. maybe it's something specific to your system?
[15:22] <dreugeworst> no, it seems to be empty. I do have an old syslog with me, it wasn't quite a crash. It starts with 'systemd-resolved.service: watchdog timeout (limit 3min)!
[15:23] <dreugeworst> then it starts killing systemd-resolve processes with signal SIGABRT
[15:23] <tomreyn> these looks more like follow-up issues
[15:23] <dreugeworst> then the same happens with systemd-networkd
[15:25] <dreugeworst> the only other problems I see in the log are with snapd
[15:25] <tomreyn> is this bare metal or a VM?
[15:25] <dreugeworst> bare metal
[15:25] <tomreyn> was this system upgraded from earlier ubuntu releases?
[15:25] <dreugeworst> no, new install
[15:26] <tomreyn> can you share a full journalctl -b ?
[15:26] <dreugeworst> hmm
[15:26] <tomreyn> (ideally of a fresh boot, if you'll do.)
[15:27] <tomreyn> it's not strictly neccessary, just wondering
[15:27] <dreugeworst> I'll have a look if it's an option
[15:29] <tomreyn> interestingly i find only a single hit for "systemd-resolved.service: watchdog timeout" on the web.
[15:29] <tomreyn> maybe there's an issue with the network environment which triggers this.
[15:30] <Ussat> I have never had something like that happen
[15:31] <tomreyn> actually google has more hits on this search.
[15:31] <dreugeworst> there's a lot of ssh login attempts happening, looks like a dictionary attack
[15:31] <tomreyn> welcome to the internet
[15:31] <dreugeworst> yeah, I installed sshguard, didn't think it would be the issue
[15:32] <krintax56> Guys, I'm installing Ubuntu 18.04 LTS on HP DL380 G6 using ethernet. During setup when I go to Network connections and configure to use DHCP it says timed out. Now I configured DHCP IPv4 to be manual but I can only "Continue without network". Help! https://imgur.com/a/RoWKQdl https://imgur.com/a/3tCUYGW
[15:32] <dreugeworst> well, I'll continue with a manually configured dns server for now
[15:34] <tomreyn> dreugeworst: maybe just look at     dmesg --level=err,warn    and see if you have any serious issues which occur before it.
[15:35] <tomreyn> krintax56: which ubuntu 18.04 server edition (the default, or alternative) and which exact version (18.04(.0), 18.04.0.1, 18.04.1, 18.04.2, 18.04.3) are you installing?
[15:35] <krintax56> ubuntu-18.04.3-live-server-amd64
[15:37] <tomreyn> krintax56: can you select the enp2s0f0 device and select "info"?
[15:38] <krintax56> https://imgur.com/a/hc1Nb18
[15:38] <krintax56> Sorry for the bad quality picture.
[15:38] <tomreyn> works for me.
[15:39] <tomreyn> so somehow it failed to configure, i guess. are you able to configure it properly if you reboot and then don't try dhcp but immediately configure it statically=?
[15:40] <tomreyn> also can you say which values you entered during static configuration?
[15:41] <tomreyn> krintax56: i assume you have verified this NIC actuall yhas a link?
[15:42] <krintax56> What is NIC? Noob to linux and server stuff?
[15:42] <tomreyn> network interface card
[15:42] <krintax56> Ah yes it has. I actually installed CentOS 7 and it worked fine. Now I need Ubuntu and I get this.
[15:43] <tomreyn> actually "network interface controller"
[15:43] <krintax56> Yes it has.
[15:44] <tomreyn> please consider the other approaches i discussed above, too:
 so somehow it failed to configure, i guess. are you able to configure it properly if you reboot and then don't try dhcp but immediately configure it statically=?
 also can you say which values you entered during static configuration?
[15:44] <krintax56> https://imgur.com/a/3tCUYGW here is the static config: https://imgur.com/a/3tCUYGW
[15:45] <krintax56> i actually haven't setup the IPv4 because I don't know what values to use.
[15:46] <krintax56> I mean IPv6*
[15:48] <tomreyn> krintax56: okay, i don't think you made any mistakes there, or none that i can see.
[15:48] <tomreyn> krintax56: i suggest you try rebooting and reconfiguring it.
[15:48] <tomreyn> in the meantime i'll see if i can reproduce
[15:49] <krintax56> I just did that, still I can only see the Continue without network button.
[15:49] <krintax56> Maybe I should setup the IPv6 too?
[15:49] <tomreyn> it should not be neccessary, i think
[15:50] <tomreyn> if you have another network interface connected, maybe try configuring that instead.
[15:50] <krintax56> I don't have.
[15:51] <tomreyn> then i'm afraid i can only suggest you try the alternative server installer at this time.
[15:51] <tomreyn> or install offline
[15:51] <krintax56> What is install offline, like continue without network then try to connect?
[15:52] <tomreyn> you would then need to configure dhcp in your environment, or configure the ip address statically on the server after reboot.
[15:53] <krintax56> Okay, I will continue without network from here.
[15:53] <tomreyn> alternate server installer https://ubuntu.com/download/alternative-downloads#alternate-ubuntu-server-installer
[16:12] <tomreyn> krintax56: i'm trying to reproduce this here (in a VM), but am not having much luck. once i finish manual configuration of the network interface the "continue without network" option on the bottom of the screen always switches to "done", i.e. network configuration succeeded. but, differently to yours, my 'info' screen also has all the details i entered. yours is basically empty, suggesting network interface configuration did not succeed.
[16:12] <tomreyn> it'd be great if you could report this as a bug (run "ubuntu-bug subiquity" after installation, from the rebooted system, after configuring the network manually).
[16:13] <tomreyn> bug reporting requires a one-time registration with the ubuntu SSO which also enables you to use the ubuntu kernel livepatch and other services.
[16:14] <tomreyn> reporting a bug guides you through this rather quick process