Basic fam Troubleshooting

Can't connect to fam 

1. Check to see if fam is running with the command:

   ps -ef | grep fam

2. If fam is not running, verify the following things:

   • Verify that /usr/etc/fam exists and is executable with the following command:

     ls -l /usr/etc/fam

     If the file is not found, you must reinstall the software package eoe1.sw.unix. If it is found, the permissions should be:

     -rwxr-xr-x 1 root sys 156484 Jan 24 18:34 /usr/etc/fam

     The date and size may vary.

   • Verify that fam is listed in the /etc/inetd.conf file. The fam daemon is invoked when the system starts up the network. Even if the system is not connected using the network to other systems, the network software must be started. A line similar to the following should be found in /etc/inetd.conf:

     sgi_fam/1 stream rpc/tcp wait root ?/usr/etc/fam famd -t 6

   • Verify that inetd is running with the command:

     ps -ef | grep inetd

     You should see a response similar to:

     root 214 1 0 Oct 24 ? 0:01 /usr/etc/inetd

     If the message

     portmapper failure

     is displayed, it is also a sign that the network is not active. Start the network according to the steps outlined in the IRIX Admin: Networking and Mail guide.

   • Verify that fam is registered with portmapper with the command:

     rpcinfo -p | grep fam

     You should see output similar to the following:

     391002 1 tcp 1033 sgi_fam

     If you are using a foreign NIS master system, see the section titled "If You Are Using a Foreign NIS Master".

3. If fam is running, turn on debugging mode by by adding a -d flag to the entry in /etc/inetd.conf. The finished line should be similar to the following:

   sgi_fam/1 stream rpc/tcp wait root ?/usr/etc/fam famd -t 6 -d

   Reboot your system for the debugging to take effect. The debugging information is written in the file /var/adm/SYSLOG. This can be conveniently viewed with the sysmon tool, described in "Viewing Your System Log With sysmon".