On 6/29/25 4:27 AM, David C Rankin wrote:
Ironically (and also hiding the problem) when the interface is
brought up manually with "ip set enp5s0 up" there must be no check of
resolv.conf. Otherwise, if that is what is causing the issue, I would
expect bringing the interface up to result in the same error and it to
go back down. But it doesn't. After being brought up, the server is
running perfectly, just as it did before the Jun 28 update.
Hah! we may have just found it. openresolv was updated in the Jun 28
update. That may be the culprit. I'll downgrade reboot and report.
I'll be damned!
It's openresolv and the update on 6/28 broke the netctl unit startup:
[2025-06-28T01:54:53-0500] [ALPM] upgraded openresolv (3.16.5-1 -> 3.17.0-1)
I downgraded openresolv, rebooted and BINGO, server comes up
perfectly, network is up, all it good in the world.
# pmu openresolv-3.16.5-1-any.pkg.tar.zst
loading packages...
warning: downgrading package openresolv (3.17.0-1 => 3.16.5-1)
resolving dependencies...
looking for conflicting packages...
Packages (1) openresolv-3.16.5-1
Total Installed Size: 0.08 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring
[########################################] 100%
(1/1) checking package integrity
[########################################] 100%
(1/1) loading package files
[########################################] 100%
(1/1) checking for file conflicts
[########################################] 100%
(1/1) checking available disk space
[########################################] 100%
:: Processing package changes...
(1/1) downgrading openresolv
[########################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
(reboot)
We have a winner! openresolv gets the bug. One hell of a process of
elimination :) Thanks to all for suggestions that got this identified.
I'm going to bed...
--
David C. Rankin, J.D.,P.E.
