18.3 Cluster precheck failed due to avahi-daemon is running
we need to stop daemon to proceed further
Verifying Daemon "avahi-daemon" not configured and
running ...
Node Name Configured Status
------------ ------------------------ ------------------------
host2 no passed
host1 no passed
Node Name Running? Status
------------ ------------------------ ------------------------
host2 yes failed
host1 yes failed
Verifying Daemon "avahi-daemon" not configured and
running ...FAILED (PRVG-1360)
#systemctl status avahi-daemon
● avahi-daemon.service - Avahi mDNS/DNS-SD
Stack
Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled;
vendor preset: enabled)
Active: active (running) since Tue 2019-02-05 13:23:55 PST; 9h ago
Main
PID: 10183 (avahi-daemon)
Status: "avahi-daemon 0.6.31 starting up."
CGroup: /system.slice/avahi-daemon.service
├─10183 avahi-daemon: running [host1.local]
└─10187 avahi-daemon: chroot helper
Feb 05 13:24:00 host1.com
avahi-daemon[10183]: Joining mDNS multicast group on interface eth0.IPv4 with
add....41.
Feb 05 13:24:00 host1.com
avahi-daemon[10183]: New relevant interface eth0.IPv4 for mDNS.
Feb 05 13:24:00 host1.com
avahi-daemon[10183]: Registering new address record for on
eth0.IPv4.
Feb 05 13:24:02 host1.com
avahi-daemon[10183]: Registering new address record for fe80::225:b5ff:fe00:45e
o...1.*.
Feb 05 13:24:04 host1.com
avahi-daemon[10183]: Joining mDNS multicast group on interface eth1.IPv4 with
add....41.
Feb 05 13:24:04 host1.com
avahi-daemon[10183]: New relevant interface eth1.IPv4 for mDNS.
Feb 05 13:24:04 host1.com
avahi-daemon[10183]: Registering new address record for on
eth1.IPv4.
Feb 05 13:24:07 host1.com
avahi-daemon[10183]: Joining mDNS multicast group on interface virbr0.IPv4 with
a...2.1.
Feb 05 13:24:07 host1.com
avahi-daemon[10183]: New relevant interface virbr0.IPv4 for mDNS.
Feb 05 13:24:07 host1.com
avahi-daemon[10183]: Registering new address record for on
virbr0.IPv4.
Hint: Some lines were ellipsized, use -l to
show in full.
root@host1:# systemctl stop avahi-daemon
Warning: Stopping avahi-daemon.service, but
it can still be activated by:
avahi-daemon.socket
root@host1:# systemctl disable
avahi-daemon
Removed symlink
/etc/systemd/system/sockets.target.wants/avahi-daemon.socket.
Removed symlink
/etc/systemd/system/dbus-org.freedesktop.Avahi.service.
Removed symlink
/etc/systemd/system/multi-user.target.wants/avahi-daemon.service.
runcluvfy will pass after stopping daemon:
Verifying
Daemon "avahi-daemon" not configured and running ...
Node Name
Configured Status
------------
------------------------
------------------------
host2
no passed
host1
no passed
Node Name
Running? Status
------------
------------------------
------------------------
host2
no passed
host1
no passed
Verifying
Daemon "avahi-daemon" not configured and running ...PASSED
No comments:
Post a Comment