=== genii is now known as genii-core === Bebef9 is now known as Bebef === cpaelzer_ is now known as cpaelzer [10:57] icey: hey [10:57] what's the rationale for adding the version suffix to the luarocks rocks- subdirectory in your patch? [10:58] the conditional that's wrapped in lacks the -5.1 [10:59] jamespage: ah - should have added it to the conditional as well; the version suffix is because that's what's added to the `--tree` path [11:45] icey: https://paste.ubuntu.com/p/SbMR3tBSBF/ [11:46] jamespage: lgtm [13:06] jamespage: I'm seeing errors like https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1827415.html on ceph as well [14:05] icey: uploaded [14:05] (luarocks) [14:05] jamespage: \o/ [14:27] icey: pls can you submit those changes back to debian as well :) [14:38] jamespage: did a report2debian :-D === genii-core is now known as genii === Kamilion|ZNC is now known as Kamilion [18:55] rbasak: swtpm import please ? [19:01] and libtpms === paride4 is now known as paride [22:13] Somehow one of my server's time is not NTP syncronized and the time has drifted enough that TOTP doesn't work anymore [22:13] How do I force a time sync from the terminal? [22:16] Oddly the RTC clock is the correct time === Voeid8 is now known as Voeid [22:18] Zaliek: sudo apt-get update ; sudo apt-get -y install ntpdate ; sudo ntpdate pool.ntp.org [22:18] It seems systemd-timesyncd is supposed to be doing this [22:18] I tried restarting the service but it still won't update the time [22:19] Zaliek: system status systemd-timesyncd ; journalctl -u systemd-timesyncd.service -f [22:20] Nothing in there, just the service started/stopped messages [22:21] Zaliek, what does "timedatectl timesync-status" say? [22:22] Not a valid command [22:22] status says NTP syncronized: no [22:23] Network time on: yes [22:23] it might not change time if the difference is too large [22:24] ntpdate should do that though [22:27] it's 2 minutes [22:28] i think there are some commented out options in the timesyncd configuration file you can use to get more verbose info. [22:28] that's /etc/systemd/timesyncd.conf [22:29] hmm no, nothing about verbosity [22:29] This system is 16.04 if that makes a difference [22:30] Honestly surprised it took this long for the clock to drift by 2 mins [22:30] oh 16.04, do you have ESM then? [22:30] Yeah, but no actual support [22:30] Just the free ESM [22:31] hmm, i think 16.04 only used a smaller subset of sytemd services [22:31] It's being replaced soon but I can't login to the app it's hosting because the clock has drifted [22:31] i don't remember whether it already did timesyncd [22:31] Yeah it's using the systemd service [22:32] All of the old ntp tools are not installed [22:32] you could override the ntp server it's synching to in the configuration file, then restart the service, wait 5 minutes and see whether it caught up. [22:33] if not, i'd disable timesyncd and use a different ntp client, such as chrony [22:36] also, for a quick workaround you can set the time manually, of course... [22:36] I figured it out... [22:36] I never allowed NTP through the firewall [22:36] :facepalm" [22:36] hehe [22:38] Thanks for your help. Gonna need to do the same for my other servers [22:38] Luckily I never setup TOTP with SSH on this one [22:38] you just lost an excuse to not upgrade just yet ;-P [22:39] Well it still needs to because I need a newer version of PHP [22:41] I have the other problem: I need a 16.04 system because I need an older PHP version... :-/ [22:45] i assume you know about https://deb.sury.org/ [22:47] I did not [22:47] that's debian developer ondřej surý providing co-installable php versions for several debian + ubuntu releases [22:47] could be useful, I guess :) [22:48] those can break release upgrades, of course, so be careful about that [22:49] I want to get rid of that website though, so maybe not going to use it for this [22:51] this, too, can't prevent the inevitable or provide full security support for bugs in software long EOL'd upstream. [22:52] supposedly PHP 5.x is still supported upstream? [22:53] apparently not, although that repository says it only has supported versions? [22:55] (it clearly does have EOL versions) [22:56] i think he means to say he does provide support for them [22:56] """Only Supported Versions of PHP (http://php.net/supported-versions.php) for Supported Ubuntu Releases (https://wiki.ubuntu.com/Releases) are provided.""" [22:56] oh, that seems to be misleading, yes [22:59] https://www.patreon.com/posts/may-2021-update-50798437 [23:07] Odd, apparently LXD containers keep their time in sync with the host via some other mechanism than NTP [23:16] cat /sys/devices/system/clocksource/*/current_clocksource # https://www.kernel.org/doc/Documentation/timers/timekeeping.txt [23:22] perhaps by the expedient of not having virtualized clocks? [23:23] LXD containers (as oppsed to LXD VMs) use the host kernel instance, no? So it's lierally the same clock [23:25] Which is why systemd-timesyncd.service has "ConditionVirtualization=!container" === rfm_ is now known as rfm