Verifying Daemon “Avahi-Daemon” Not Configured And Running …FAILED (PRVG-1360)

 


Execute "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" as root user on nodes "shsebs7idb1" to perform the fix up operations manually


Press ENTER key to continue after execution of "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" has completed on nodes "shsebs7idb1"


Fix: Daemon "avahi-daemon" not configured and running


  Node Name                             Status

  ------------------------------------  ------------------------

  shsebs7idb1                           failed


ERROR:

shsebs7idb1: PRVG-9023 : Manual fix up command "/tmp/CVU_19.0.0.0.0_grid/runfixup.sh" was not issued by root user on node "shsebs7idb1"


Result:

"Daemon "avahi-daemon" not configured and running" could not be fixed on nodes "shsebs7idb1"


SOLUTION:

To fix this error, stop and disable avahi-daemon service.

1. Check avahi-daemon status:


[root@shsebs7idb1 ~]# ls -l /bin/systemctl

-rwxr-xr-x. 1 root root 717696 Sep  7  2018 /bin/systemctl

[root@shsebs7idb1 ~]# cd /bin

[root@shsebs7idb1 bin]# chmod 755 systemctl

[root@shsebs7idb1 bin]# ls -l /bin/systemctl

-rwxr-xr-x. 1 root root 717696 Sep  7  2018 /bin/systemctl

[root@shsebs7idb1 bin]# 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 Wed 2024-07-03 10:58:48 IST; 6h ago

 Main PID: 10063 (avahi-daemon)

   Status: "avahi-daemon 0.6.31 starting up."

    Tasks: 2

   CGroup: /system.slice/avahi-daemon.service

           ├─10063 avahi-daemon: running [shsebs7idb1.local]

           └─10070 avahi-daemon: chroot helper


Jul 03 11:02:29 shsebs7idb1.appsolworld.com avahi-daemon[10063]: Received response from host 192.168.1.3 with invalid source port 5819...32.0'

Jul 03 11:02:29 shsebs7idb1.appsolworld.com avahi-daemon[10063]: Invalid legacy unicast query packet.

Jul 03 11:02:29 shsebs7idb1.appsolworld.com avahi-daemon[10063]: Received response from host 192.168.1.3 with invalid source port 5819...32.0'

Jul 03 11:02:30 shsebs7idb1.appsolworld.com avahi-daemon[10063]: Invalid legacy unicast query packet.

Jul 03 11:02:30 shsebs7idb1.appsolworld.com avahi-daemon[10063]: Invalid legacy unicast query packet.

Jul 03 11:02:30 shsebs7idb1.appsolworld.com avahi-daemon[10063]: Received response from host 192.168.1.3 with invalid source port 5819...32.0'

Jul 03 11:02:31 shsebs7idb1.appsolworld.com avahi-daemon[10063]: Received response from host 192.168.1.3 with invalid source port 5819...32.0'

Jul 03 11:02:31 shsebs7idb1.appsolworld.com avahi-daemon[10063]: Received response from host 192.168.1.3 with invalid source port 5819...32.0'

Jul 03 11:02:31 shsebs7idb1.appsolworld.com avahi-daemon[10063]: Received response from host 192.168.1.3 with invalid source port 5819...32.0'

Jul 03 11:02:33 shsebs7idb1.appsolworld.com avahi-daemon[10063]: Received response from host 192.168.1.3 with invalid source port 5819...32.0'

Hint: Some lines were ellipsized, use -l to show in full.


2. Stop avahi-daemon service:

[root@shsebs7idb1 bin]# systemctl stop avahi-daemon
Warning: Stopping avahi-daemon.service, but it can still be activated by:
  avahi-daemon.socket

3. Disable avahi-daemon service:

[root@shsebs7idb1 bin]# systemctl disable avahi-daemon
Removed symlink /etc/systemd/system/multi-user.target.wants/avahi-daemon.service.
Removed symlink /etc/systemd/system/sockets.target.wants/avahi-daemon.socket.
Removed symlink /etc/systemd/system/dbus-org.freedesktop.Avahi.service.


Now run the cluvfy again to validate.

Comments

Post a Comment

Popular posts from this blog

How to fix Oracle SQL Developer connection issue "Got minus one from a read call"

Image
 During connection from SQL Developer to EBS database got below error message: Status : Failure - Test failed: IO Error: Got minus one from a read call Following solution can be done : 1. Go to directory $ORACLE_HOME / network / admin 2. Modify sqlnet.ora file with following parameter : tcp.validnode_checking = no 3. If you don 't want to disable this, you can put the machine names as follows: tcp.invited_nodes=(machine1, machine2) 3. Bounce the listener. Due to security enhancements it is not good to put tcp.validnode_checking = no or comment out will through error when we start listener like below: Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=shsebs7idb1.appsolworld.com)(PORT=1522))) TNS-00584: Valid node checking configuration error TNS-12560: TNS:protocol adapter error Better plan is to add localhost or IP address of client (Local Computer) in the sqlnet.ora file That will solve the problem NAMES.DIRECTORY_PATH=(TNSNAMES, ONAMES, HOSTNAME) SQLNET.EXPI
Read more

How to troubleshoot Long Running Concurrent Request in EBS 12.2

 The following points need to answer before jumping into troubleshooting: Are there any recent code changes done in the concurrent program?           Check long_running_sid and verify the recent code change of last_ddl_timestamp after a             discussion with the developer. Was this running long in the last few run as well, or was this time only?            ==> Check the program history. How much time does it take to complete?           Once again program history can give us some idea. Are these jobs fetching higher data compared to the last run           ===> Confirm on data change . Query Plan change will indicate this issue. Does this job runs at any specific time or it can be run anytime           ===> The nature of the job can help to understand the job's nature. Does this job fetch data using DB Link          ====> Check whether the DB link is involved or not. The below-given approach would help to conclude the gray areas. Check the load of the server using t
Read more

Few Important steps of Oracle Database Clone

 Make Sure oraInst.loc location is correct and accessble. [demantra@dsiddem ~]$ cat /etc/oraInst.loc inventory_loc=/orastage/oraInventory inst_group=dba [demantra@dsiddem ~]$ cd /orastage/oraInventory [demantra@dsiddem oraInventory]$ ls -ltr total 16 drwxrwx---. 5 demantra dba 4096 Jul 22 19:37 backup drwxrwx---. 2 demantra dba 4096 Jul 22 19:37 ContentsXML drwxrwx---. 2 demantra dba 4096 Jul 22 19:37 locks drwxrwx---. 3 demantra dba 4096 Jul 23 10:08 logs Remove Oracle Home from Inventory [demantra@dsiddem oraInventory]$ cd $ORACLE_HOME/oui/bin [demantra@dsiddem bin]$ ./runInstaller -detachHome ORACLE_HOME=$ORACLE_HOME Starting Oracle Universal Installer... Checking swap space: must be greater than 500 MB.   Actual 3039 MB    Passed The inventory pointer is located at /etc/oraInst.loc Run Clone.pl [demantra@dsiddem bin]$ echo $ORACLE_HOME /dnbsid/demantra/oracle/19.0.0 [demantra@dsiddem bin]$ echo $ORACLE_BASE /dnbsid/demantra [demantra@dsiddem bin]$ E01=ORACLE_HOME=$ORACLE_HOME [dema
Read more