parnassus
April 18, 2014, 7:23am
1
Regarding to this and considering a FreePBX Distro 5.211.65-11 system (*) which doesn’t use any Digium phone (GrandStream only), is it safe to remove (with a good yum erase) both the avahi-deamon and the avahi-libs associated library?
After a power failure (UPS went down unexpectedly yesterday after a prolonged uncontrolled main power outage) I noticed the FreePBX Distro system started to log a lot of system messages regarding specifically the avahi-deamon, as example:
Apr 18 08:31:49 freepbx avahi-daemon[1110]: Invalid query packet.
Apr 18 08:31:50 freepbx avahi-daemon[1110]: Invalid query packet.
Apr 18 08:31:50 freepbx avahi-daemon[1110]: Invalid query packet.
Apr 18 08:31:50 freepbx avahi-daemon[1110]: Invalid query packet.
Apr 18 08:31:52 freepbx avahi-daemon[1110]: Invalid query packet.
Apr 18 08:31:53 freepbx avahi-daemon[1110]: Invalid query packet.
Apr 18 08:31:53 freepbx avahi-daemon[1110]: Invalid query packet.
Apr 18 08:31:56 freepbx avahi-daemon[1110]: Invalid query packet.
Apr 18 08:32:02 freepbx avahi-daemon[1110]: Invalid query packet.
Apr 18 08:32:29 freepbx avahi-daemon[1110]: Invalid query packet.
(*) actually the system:
is fully up to date (with April, 17th 2014 latest updates).
has Digium Addon module locally available but disabled (I installed it months ago when was released but then I disabled it because wasn’t necessary).
hasn’t Digium Phones Config module installed.
You can disable it if you want. It wont hurt anything.
parnassus
April 18, 2014, 2:35pm
3
If I desire more…like removing it?
Here the dependencies on removing it:
[root@freepbx ~]# yum erase avahi avahi-libs
Loaded plugins: changelog, fastestmirror, kmod, security
Setting up Remove Process
Resolving Dependencies
--> Running transaction check
---> Package avahi.x86_64 0:0.6.25-12.el6 will be erased
---> Package avahi-libs.x86_64 0:0.6.25-12.el6 will be erased
--> Processing Dependency: libavahi-client.so.3()(64bit) for package: 1:cups-libs-1.4.2-50.el6_4.5.x86_64
--> Processing Dependency: libavahi-client.so.3()(64bit) for package: asterisk11-res_digium_phone-1.0.1_centos6-47.x86_64
--> Processing Dependency: libavahi-common.so.3()(64bit) for package: 1:cups-libs-1.4.2-50.el6_4.5.x86_64
--> Running transaction check
---> Package asterisk11-res_digium_phone.x86_64 0:1.0.1_centos6-47 will be erased
---> Package cups-libs.x86_64 1:1.4.2-50.el6_4.5 will be erased
--> Processing Dependency: libcups.so.2()(64bit) for package: gtk2-2.20.1-4.el6.x86_64
--> Processing Dependency: libcups.so.2()(64bit) for package: ghostscript-8.70-19.el6.x86_64
--> Processing Dependency: libcupsimage.so.2()(64bit) for package: ghostscript-8.70-19.el6.x86_64
--> Running transaction check
---> Package ghostscript.x86_64 0:8.70-19.el6 will be erased
--> Processing Dependency: libgs.so.8()(64bit) for package: ImageMagick-6.5.4.7-7.el6_5.x86_64
---> Package gtk2.x86_64 0:2.20.1-4.el6 will be erased
--> Processing Dependency: libgdk-x11-2.0.so.0()(64bit) for package: librsvg2-2.26.0-6.el6_5.3.x86_64
--> Processing Dependency: libgdk_pixbuf-2.0.so.0()(64bit) for package: librsvg2-2.26.0-6.el6_5.3.x86_64
--> Processing Dependency: libgtk-x11-2.0.so.0()(64bit) for package: librsvg2-2.26.0-6.el6_5.3.x86_64
--> Processing Dependency: gtk2 >= 2.9.0 for package: librsvg2-2.26.0-6.el6_5.3.x86_64
--> Processing Dependency: gtk2 >= 2.9.0 for package: librsvg2-2.26.0-6.el6_5.3.x86_64
--> Processing Dependency: gtk2 >= 2.9.0 for package: librsvg2-2.26.0-6.el6_5.3.x86_64
--> Running transaction check
---> Package ImageMagick.x86_64 0:6.5.4.7-7.el6_5 will be erased
---> Package librsvg2.x86_64 0:2.26.0-6.el6_5.3 will be erased
--> Finished Dependency Resolution
...
Dependencies Resolved
...
Transaction Summary
...
Remove 8 Package(s)
Installed size: 42 M
I can disable it on all run levels but, you know, disabling something isn’t like removing it.
May I answer “Yes” without causing any side issue to the system? mumble mumble…
Anyway…by now to stop the log I did a:
chkconfig --level 345 avahi-daemon off