Routing: radvd: exiting, failed to read config file

drewsaur

I was running through logs and found this.

Everything with my IPv6 seems to be working, and the last radvd log entry reporting "exiting, failed to read config file" was several days ago, but this seems to be an ongoing entry. Is there anything I should be concerned about, or is this simple log noise?

Gertjan

@drewsaur

Is there a message in the logs that says :

"Error: cannot open radvd.conf in services_radvd_configure()."

The file is auto generated here : https://github.com/pfsense/pfsense/blob/75dfcf4ac7d703a618a050af8ac880d900a87b8f/src/etc/inc/services.inc#L468

When dhcpd DHCP server(s) LAN based are started, and there is also at least one LAN interface with "all" or "inet6" set, services_radvd_configure() is called and thus radvd.conf is created.

The radvd deamon is started after the radvd.conf is created so ... the file couldn't be created ?
Disk full ? File system bad (check it !) ?

drewsaur

@Gertjan

No such other error messages. Disk is only 9% full, and filesystem is OK (running ZFS).

I did a:

more /var/etc/radvd.conf

And got (IPv6 address obfuscated for this post):

# Automatically Generated, do not edit
# Generated for DHCPv6 Server lan
interface igb1 {
	AdvSendAdvert on;
	MinRtrAdvInterval 200;
	MaxRtrAdvInterval 600;
	AdvDefaultLifetime 1800;
	AdvLinkMTU 1500;
	AdvDefaultPreference medium;
	prefix XXXX:XXXX:XXXX:XXXX::/64 {
		DeprecatePrefix on;
		AdvOnLink on;
		AdvAutonomous on;
		AdvValidLifetime 86400;
		AdvPreferredLifetime 14400;
	};
	route ::/0 {
		AdvRoutePreference medium;
		RemoveRoute on;
	};
};

Is this the right file? This seems to be the file that it should be referencing. Is the error message a red herring?

Gertjan

@drewsaur

Ok, great, the file exists.
In your image, I can see that every line has another radvd process ID.

radvd getting restarted, so DHCP servers are getting restarted, any many mores, quiet (imho : way to) often. Your pfSense has interfaces that are going down and up that often ?

I'm out of suggestion why radvd can't read a file that was created just moment before, and exists.

These is just one instance running :

[24.11-RELEASE][root@pfSense.bhf.tld]/root: ps aux | grep 'radvd'
root    58063   0.0  0.1  13024   2832  -  Is   Wed11      0:01.76 /usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog

right ,

drewsaur

@Gertjan

Oh - good observation - you know, my ISP had many issues recently, and my modem had to be restarted.

Also, I added some new devices and reconfigured my DHCP server (new static mappings) several times recently.

It seems like it might correspond to those events. Could it simply be a remnant of that? Since it hasn't happened in several days, might everything be OK?

FYI:

root 69058 0.0 0.1 13024 2796 - Ss 24Jan25 1:10.52 /usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog

Yes, just one instance, dating back.