On 6/29/25 12:55 AM, David C Rankin wrote:
I went ahead and updated to current (pacman -Syu) and the problem
persists. So the easiest workaround at this point is to write a short
script that runs after boot to bring the interface back up, add the
default route and start dhcpd4, e.g.
<snip>
Could this be something new with netctl? systemd is showing the profile
failed due to "resolvconf: signature mismatch: /etc/resolv.conf". I
don't not use systemd-resolvconf and never have. The unit file failure
shows the following:
# systemctl --no-pager --full status
'netctl@ethernet\x2dstatis\x2dvalkyrie.service'
× netctl@ethernet\x2dstatis\x2dvalkyrie.service - A basic static
ethernet connection
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; enabled;
preset: 5:185mdisabled)
Drop-In:
/etc/systemd/system/netctl@ethernet\x2dstatis\x2dvalkyrie.service.d
└─profile.conf
Active: failed (Result: exit-code) since Sun 2025-06-29 00:44:59
CDT; 2h 6min ago
Duration: 1.157s
Invocation: 07b4efd73c69447db4d62112dccf3ce3
Docs: man:netctl.profile(5)
Process: 779 ExecStart=/usr/lib/netctl/network start
ethernet-statis-valkyrie (code=exited, status=1/FAILURE)
Main PID: 779 (code=exited, status=1/FAILURE)
Mem peak: 7.3M
CPU: 213ms
Jun 29 00:44:55 valkyrie systemd[1]: Starting A basic static ethernet
connection...
Jun 29 00:44:55 valkyrie network[779]: Starting network profile
'ethernet-statis-valkyrie'...
Jun 29 00:44:57 valkyrie systemd[1]: Started A basic static ethernet
connection.
Jun 29 00:44:58 valkyrie network[847]: resolvconf: signature mismatch:
/etc/resolv.conf
Jun 29 00:44:58 valkyrie network[847]: resolvconf: run `resolvconf -u`
to update
Jun 29 00:44:59 valkyrie systemd[1]:
netctl@ethernet\x2dstatis\x2dvalkyrie.service: Main process exited,
code=exited, status=1/FAILURE
Jun 29 00:44:59 valkyrie network[779]: Failed to bring the network up
for profile 'ethernet-statis-valkyrie'
Jun 29 00:44:59 valkyrie systemd[1]:
5:185m5:185mnetctl@ethernet\x2dstatis\x2dvalkyrie.service: Failed with
result 'exit-code'.
This failure is new since the Jun 28 update. The resolve.conf file
hasn't changed since 2022 (the way I set it and it provides the backup
nameserver as well), e.g.
$ l /etc/resolv.conf
-rw-r--r-- 1 root root 313 Dec 10 2022 /etc/resolv.conf
$ cat /etc/resolv.conf
## Generated by dcr
# set 1 sec timeout to use alternate NS and prevent parallel requests
options timeout:1
options single-request
# all lookup using hostnames rather than FQDN
domain 3111skyline.com
search 3111skyline.com
# nameservers to use
nameserver 127.0.0.1
nameserver 192.168.6.14
nameserver 192.168.6.17
The netctl config (based on the /example for static) hasn't changed
Nov 6 2022:
$ cat cat ethernet-statis-valkyrie
Description='A basic static ethernet connection'
Interface=enp5s0
Connection=ethernet
IP=static
Address=('192.168.6.14/24')
#Routes=('192.168.0.0/24 via 192.168.1.2')
Gateway='192.168.6.11'
DNS=('192.168.6.14')
## For IPv6 autoconfiguration
#IP6=stateless
## For IPv6 static address configuration
#IP6=static
#Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#Routes6=('abcd::1234')
#Gateway6='1234:0:123::abcd'
The profile hasn't changed since that same date:
$ l /etc/systemd/system/netctl@ethernet\\x2dstatis\\x2dvalkyrie.service.d/
total 12
drwxr-xr-x 2 root root 4096 Nov 6 2022 .
drwxr-xr-x 10 root root 4096 May 6 14:01 ..
-rw-r--r-- 1 root root 148 Nov 6 2022 profile.conf
$ cat
/etc/systemd/system/netctl@ethernet\\x2dstatis\\x2dvalkyrie.service.d/profile.conf
[Unit]
Description=A basic static ethernet connection
BindsTo=sys-subsystem-net-devices-enp5s0.device
After=sys-subsystem-net-devices-enp5s0.device
Why would this netctl unit suddenly start failing? Is the
'resolvconf: signature mismatch: /etc/resolv.conf' now something that
causes the unit to fail? That is the only thing shown for the unit and
then systemd seems to be taking the interface down after that?
If it is systemd and netctl - why didn't downgrading systemd fix it?
netctl hasn't changed in almost a year:
[2024-07-06T18:27:27-0500] [ALPM] upgraded netctl (1.29-1 -> 1.29-2)
I have got to get this sorted out. The network being taken down
causes havoc in the journal with named and the repeated restart
attempts. Not to mention not being able to reboot into a running
configuration. Manually bringing the interface up and restoring the
default route is a quick work-around and not a solution.
What package would a bug even be written against here? systemd?
netctl? Any/all thoughts welcome. I've been through 1000s lines of
dmesg, the journal, the network configs, and my eyes are starting to
cross. I'm done for the night and will check back tomorrow. Frustrating...
--
David C. Rankin, J.D.,P.E.
