[14:37] <orenii> Hey everyone, I've got some issue with Ubuntu Server 18.04 LTS running on a Windows Server 2012 R2 (on Hyper-V). I indeed set a static ipv4 in `/etc/netplan/01-netcfg.yaml` and can ping my LAN network but I can't ping `8.8.8.8`.
[14:48] <supaman> orenii: sounds more like a problem with the network configuration in the hyper-v
[14:49] <mybalzitch> do you have a default route set?
[14:51] <orenii> supaman, I have other linux vms running (debian 9) and they work perfectly (static IP set)
[14:52] <orenii> mybalzitch, ```
[14:52] <orenii> mybalzitch, `
[14:52] <orenii> Kernel IP routing table
[14:52] <orenii> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
[14:52] <orenii> 0.0.0.0         192.168.8.200   0.0.0.0         UG    0      0        0 eth0
[14:52] <orenii> 192.168.8.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
[14:52] <orenii> `
[14:52] <orenii> (sorry for the duplicate message, thought I could edit it)
[14:52] <supaman> please use a paste service for pastes like that
[14:54] <orenii> Yes sorry, you're right. But well, I found my mistake because I didn't check it twice -> gateway is `192.168.8.200` which is the DNS server whereas the gateway should be `192.168.8.254` and what's funny is that I did the mistake twice (I reinstalled the server)
[14:54] <supaman> ah, good :-)
[14:55] <orenii> Now it's just a DNS issue, it should be easily fixed I guess, thanks a lot guys
[15:14] <jiffe> 19.10 server installer seems to have issues, its crashed on me 3 times in different places now
[15:16] <supaman> virtual or bare metal?
[15:17] <jiffe> bare metal
[15:18] <supaman> faulty memory?
[15:18] <jiffe> I can test but I don't think so, its been running fine up to this point and I've been doing a lot of memory intensive work
[15:20] <supaman> or a broken iso file ... checked the md5 sum of the download file?
[15:43] <jiffe> memory is good, md5 checks out, I'm going to reflash the usb stick
[15:44] <compdoc> jiffe, use memtest86+, and check the SMART info in the hard drive
=== tds3 is now known as tds
[16:35] <aberrant> morning
[16:35] <aberrant> is anyone else seeing frequent clock drift messages in their syslogs?
[16:41] <teward> aberrant: not on my systems, no.  Sounds like your system clock keeps drifting and needs reset by NTP / chrony / time sync
[16:47] <aberrant> teward: yeah. Why do you think that is?
[16:47] <aberrant> teward: it started happening after a reboot yesterday
[16:50] <aberrant> (after I did a purge of a bunch of software)
[16:53] <teward> not sure.  normally drift is caused by hardware clocks constantly drifting, I don't know why you'd suddenly start seeing a LOT of thsoe messages at once
[16:53] <teward> and clock drift can come from a number of different sources of issues
[16:58] <compdoc> those batteries for the cos clock only last a few years. if the battery measures below 3v, then it needs replaced. there are commands to test reading and writing to the motherboards cmos clock.
[16:59] <compdoc> *for the cmos clock
[16:59] <aberrant> compdoc: this is a brand-new mobo. Let's see if I can find some of those diagnostics
[17:00] <aberrant> seth@elemental:~$ cat /proc/driver/rtc | grep batt
[17:00] <aberrant> batt_status     : okay
[17:00] <compdoc> theres also a bios setting in some boards that prevent writing
[17:02] <compdoc> anyway, BF4 is calling me. theres a bullet with my name on it
[17:07] <aberrant> could someone paste /proc/driver/rtc from their system?
[17:22] <compdoc> https://pastebin.com/VsuwjfQb
[17:47] <aberrant> thanks
[17:48] <aberrant> mine looks identical
[17:48] <aberrant> ok, shutting down to see if it's a battery issue. brb