I made a post about 2 months ago regarding an archlinux-keyring package update ( link here ), that threw out a bunch of messages I wasn’t familiar with, but at the time @joekamprad assured me it was okay since it was happening for other users too. Now fast forward to now, I’ve come across a new message from the result of a recent archlinux-keyring package update. Now granted, this is not an issue, nothing is broken, and I don’t think anything has gone haywire, so hopefully nothing to fix here!
But if anyone can fill me in on what exactly this message all means, I’d appreciate that.
I don’t believe I need to do anything since there were no errors, but since I’m not sure if I need to possibly refresh a database or if I need to do something else please let me know, thanks very much.
:: Processing package changes...
(1/2) upgrading archlinux-keyring [-----------------------] 100%
==> Appending keys from archlinux.gpg...
gpg: public key DB323392796CA067 is 3037 days newer than the signature
==> Updating trust database...
gpg: next trustdb check due at 2022-01-20
==> Updating trust database...
gpg: next trustdb check due at 2022-01-20
Here’s the full output from yay for anyone that’s curious:
[scott@endeavourOS ~]$ yay
[sudo] password for scott:
:: Synchronizing package databases...
core 138.8 KiB 252 KiB/s 00:01 [-----------------------] 100%
extra 1572.2 KiB 398 KiB/s 00:04 [-----------------------] 100%
community 5.8 MiB 1053 KiB/s 00:06 [-----------------------] 100%
multilib is up to date
endeavouros is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Package (2) Old Version New Version Net Change Download Size
core/archlinux-keyring 20210902-1 20211028-1 0.00 MiB 0.96 MiB
extra/opencv 4.5.4-4 4.5.4-5 0.00 MiB 26.03 MiB
Total Download Size: 26.99 MiB
Total Installed Size: 97.46 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
archlinux-keyrin... 979.1 KiB 72.3 KiB/s 00:14 [-----------------------] 100%
opencv-4.5.4-5-x... 26.0 MiB 1100 KiB/s 00:24 [-----------------------] 100%
Total (2/2) 27.0 MiB 1137 KiB/s 00:24 [-----------------------] 100%
(2/2) checking keys in keyring [-----------------------] 100%
(2/2) checking package integrity [-----------------------] 100%
(2/2) loading package files [-----------------------] 100%
(2/2) checking for file conflicts [-----------------------] 100%
(2/2) checking available disk space [-----------------------] 100%
:: Processing package changes...
(1/2) upgrading archlinux-keyring [-----------------------] 100%
==> Appending keys from archlinux.gpg...
gpg: public key DB323392796CA067 is 3037 days newer than the signature
==> Updating trust database...
gpg: next trustdb check due at 2022-01-20
==> Updating trust database...
gpg: next trustdb check due at 2022-01-20
(2/2) upgrading opencv [-----------------------] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Checking which packages need to be rebuilt
:: Searching databases for updates...
:: Searching AUR for updates...
-> Flagged Out Of Date AUR Packages: gdm-prime libgdm-prime
there is nothing to do
[scott@endeavourOS ~]$
To the moderators: I wasn’t sure if I should’ve posted this in the original post I linked in the beginning or if I should’ve created a new thread like this. Feel free to merge the two if need be, thank you.
Hmm, is there a way to know if I already have systemd-timesyncd enabled? I did install EndeavourOS in July so I used the April iso, so maybe it’s a default on the most recent iso, but perhaps wasn’t a default then for the April iso?
This is what I get, I’d say it looks normal to me, but feel free to let me know otherwise:
[scott@endeavourOS ~]$ systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled;>
Active: active (running) since Fri 2021-10-29 11:36:13 EDT; 1 day 1h ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 363 (systemd-timesyn)
Status: "Initial synchronization to time server 157.245.125.229:123 (3.arch>
Tasks: 2 (limit: 18984)
Memory: 1.9M
CPU: 359ms
CGroup: /system.slice/systemd-timesyncd.service
└─363 /usr/lib/systemd/systemd-timesyncd
Oct 29 11:41:14 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply >
Oct 29 11:41:24 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply >
Oct 29 11:41:34 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply >
Oct 29 11:41:44 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply >
Oct 29 11:41:55 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply >
Oct 29 11:42:05 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply >
Oct 29 11:42:15 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply >
Oct 29 11:42:25 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply >
Oct 29 11:42:36 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply >
Oct 29 11:42:36 endeavourOS systemd-timesyncd[363]: Initial synchronization to t>
lines 1-22/22 (END)
I just realized I didn’t fully copy the output from before. If I maximize my Tilix terminal, I can see the bigger picture of the output in full detail:
[scott@endeavourOS ~]$ systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2021-10-29 11:36:13 EDT; 1 day 3h ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 363 (systemd-timesyn)
Status: "Initial synchronization to time server 157.245.125.229:123 (3.arch.pool.ntp.org)."
Tasks: 2 (limit: 18984)
Memory: 1.9M
CPU: 379ms
CGroup: /system.slice/systemd-timesyncd.service
└─363 /usr/lib/systemd/systemd-timesyncd
Oct 29 11:41:14 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply from [2400:6180:0:d1::745:6001]:123 (2.arch.pool.ntp.org).
Oct 29 11:41:24 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply from [2001:41d0:8:8759::1]:123 (2.arch.pool.ntp.org).
Oct 29 11:41:34 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply from [2a02:2b88:2:382::1]:123 (2.arch.pool.ntp.org).
Oct 29 11:41:44 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply from [2a03:b0c0:2:d0::16:7001]:123 (2.arch.pool.ntp.org).
Oct 29 11:41:55 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply from 50.205.244.114:123 (2.arch.pool.ntp.org).
Oct 29 11:42:05 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply from 209.58.140.18:123 (2.arch.pool.ntp.org).
Oct 29 11:42:15 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply from 129.250.35.251:123 (2.arch.pool.ntp.org).
Oct 29 11:42:25 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply from 64.142.54.12:123 (2.arch.pool.ntp.org).
Oct 29 11:42:36 endeavourOS systemd-timesyncd[363]: Timed out waiting for reply from 204.2.134.162:123 (3.arch.pool.ntp.org).
Oct 29 11:42:36 endeavourOS systemd-timesyncd[363]: Initial synchronization to time server 157.245.125.229:123 (3.arch.pool.ntp.org).
[scott@endeavourOS ~]$
We can see that for whatever reason 3.arch.pool.ntp.org is giving me the timeouts. It looks like I’m using 3.arch.xxx and you’re using 2.arch.xxx so maybe I need to reset or switch servers perhaps.
Not sure if the timeout is due to any issue on my end specifically, but if there’s anything I need to do to possibly correct this, feel free to let me know, thanks. I’m not sure why it timeouts on my end, but I’m more than happy to tinker around with some guidance of course
