Avahi package does not survive a config restore on pfsense 2.6.0 due to missing avahi-daemon package

NollipfSense

@SteveITS said in Avahi package does not survive a config restore on pfsense 2.6.0 due to missing avahi-daemon package:

Trying to remember if installing the package before restoring alleviates this…?

Occasionally, restoring a backup configuration will sometimes have package hiccups, especially if the Internet is been trottled with dips in speed right at the time the system makes the request.

When that happens, just reinstall the package...the configuration will be there...no need to create a post...there is nothing anyone can do.

SteveITS

@SteveITS said in Avahi package does not survive a config restore on pfsense 2.6.0 due to missing avahi-daemon package:

Trying to remember if installing the package before restoring alleviates this…?

Rereading what I wrote, what I was thinking of was a restore on a new install/router where the package didn't exist yet.

OP, I think, is talking about restoring over top of an existing router, correct @StadaanZee?

A Former User

@SteveITS

The same problem and error message happens on these 3 scenarios :

an existing pfsense router with a working config with a number of packages, including Avahi, where I need to restore a previous configuration (when I mess up a planned change)
after a fresh re-install where I have a /conf/config.xml file on the installation media
on a freshly installed pfsense box without any configuration, where I then manually restore the last config.xml file

Before using the Avahi package, I have never had issues with restoring a configuration in that way.

It can be that the first package that is restored is Avahi, if packages are indeed restored in alfabetical order.

dennypage

@StadaanZee said in Avahi package does not survive a config restore on pfsense 2.6.0 due to missing avahi-daemon package:

It can be that the first package that is restored is Avahi, if packages are indeed restored in alfabetical order.

I don't know if it is in alphabetical order or something else. But it's not uncommon. Nothing to worry about. As previously noted, you can just re-install the package after the restore or upgrade is done.

DBMandrake

@dennypage I've always had this issue as well - if I do a configuration restore the Avahi package fails to reinstall automatically claiming the package doesn't exist, but you can manually reinstall it afterwards.

I haven't seen the issue with any other packages, and I have many installed.

dennypage

A google search for

"Package" "does not exist in current pfSense version and it has been removed"

will show folk posting about the issue with many commonly used packages, including acme, avahi, iperf, named, nmap, pfBlockerNG, radiusd, squid, etc.

There are a some notable packages absent from this list, including apcupsd, ntopng, NUT, snort and suricata. Of course, the fact that no one has posted about a given package doesn't mean that it doesn't happen, but people tend to be vocal about these issues.

I don't know what triggers it. Something about the dependencies maybe?

DBMandrake

@dennypage Not sure.

Of your list I have had avahi, iperf, nmap, pfBlockerNG-Devel, squid all installed at the time of a restore, along with many other packages and the only one that ever exhibited the issue is avahi.

I started to look into it some time ago and I think it was a mistake in the package name that it was trying to install - the package is in the repository but under a slightly different name.

A Former User

@DBMandrake
@dennypage

Referring to my original post "Package avahi-daemon does not exist in current pfSense version and it has been removed.", it's something specific with the Avahi package.

Looking into my backup config.xml file I see a few sections:


<package>
			<name>Avahi</name>
			<internal_name>avahi-daemon</internal_name>
			<pkginfolink>https://forum.netgate.com/topic/134339</pkginfolink>
			<website>http://www.avahi.org/</website>
			<descr><![CDATA[Avahi is a system which facilitates host and service discovery in local networks via mDNS (Multicast DNS) and DNS-SD (DNS Service Discovery).]]></descr>
			<version>2.2_1</version>
			<configurationfile>avahi.xml</configurationfile>
			<include_file>/usr/local/pkg/avahi/avahi.inc</include_file>
			<plugins>
				<item>
					<type>plugin_carp</type>
				</item>
			</plugins>
</package>

and


<service>
			<name>avahi</name>
			<rcfile>avahi-daemon.sh</rcfile>
			<executable>avahi-daemon</executable>
			<description><![CDATA[Avahi mDNS/DNS-SD daemon]]></description>
			<starts_on_sync></starts_on_sync>
</service>

I believe the restore process tries to restore the package "avahi-daemon" based on the <internal name>, which does not exist.

A manually re-install of the Avahi package does work, probably because it's tries to install the right package "Avahi".

dennypage

@StadaanZee said in Avahi package does not survive a config restore on pfsense 2.6.0 due to missing avahi-daemon package:

I believe the restore process tries to restore the package "avahi-daemon" based on the <internal name>, which does not exist.

A manually re-install of the Avahi package does work, probably because it's tries to install the right package "Avahi".

Neither is the actual name of the package. The "name", "Avahi", is the display name shown in the UI. The "internal_name", "avahi-daemon", is how the installed package is tracked. The actual name of the package is "pfSense-pkg-Avahi".

I wrote the current avahi package (5 years ago now), replacing a very old package that had been around for a very long time. I used the same values for name and internal_name as the old version had used for backward compatibility, allowing users to upgrade to the new package rather than having to remove an old orphaned package and install a completely new one.

It may very well be that the issue arrises from the fact that name and internal_name are different. I did a quick check on a few of the others: some don't declare an internal_name at all; some use a different value for name and internal_name; most have name and internal name set to the same value. Determining if this actually the cause of the restore failure is a research project.

A Former User

@dennypage Meanwhile I upgraded the same hardware box to pfsense 2.7.0 CE and restoring a backup config.xml now also restores the avahi package without any errors.
Same box, same configuration, just running 2.7.0 CE instead of 2.6.

I upgraded via the CLI and did not even uninstall the packages (as is recommended before the upgrade process)

So 2.7.0 fixes my problem.

SteveITS

@StadaanZee sounds like
https://docs.netgate.com/pfsense/en/latest/releases/2-7-0.html#package-system
Fixed: Packages are not automatically reinstalled when restoring configuration using the installer #12105
Fixed: Packages with custom internal_name values do not reinstall properly when restoring a backup #12766

A Former User

@SteveITS 2.7.0 CE fixed the restore issue with Avahi for me. However, I can only confirm it as "fixed" on a single pfsense box with a maximum of 2-3 restores.
My pfsense has only been updated a few days ago. Early days, without another user also confirming it as fixed I would say.