Error Messages for Component ID 0513

0513-001 The System Resource Controller daemon is not active

Possible Causes

• The System Resource Controller (SRC) master daemon record in the /etc/inittab file is either missing or damaged.

Procedures for Recovery

• Use the mkitab command to create a record of the SRC master daemon in the /etc/inittab file:

  mkitab -i fbcheck srcmstr:2:respawn:/etc/srcmstr

• Reprocess the /etc/inittab file by entering:

  telinit q

0513-021 The subserver is not on file or subserver is not currently active. Check your subserver entries and try again

Possible Causes

You attempted to access a subserver that either does not exist or is not currently active.

Procedures for Recovery

• Include the subserver or make the subserver active.
  1. To check the status of your subservers, enter:

     lssrc -a

  2. If it is not active, select the SMIT Processes and Subsystems->Subservers->Start a Subserver menu option. Select the subsystem you want to start.

0513-053 The System Resource Controller is experiencing problems with its socket communications

Possible Causes

• You ran a System Resource Controller (SRC) command that tried unsuccessfully to access a remote host.
• You ran a command that tried to access the /dev/SRC file, but that file is either damaged or no longer available.
• The root (/) file system was full, and an SRC command cannot be completed.
• There is a loose network cable connection.

Procedures for Recovery

• Reconfigure the Internet socket.
  1. Check if you are able to contact the remote hosts through the network. Use the ping command to see if you can access the host files.
  2. If you suspect that your system is having problems with the network, enter smit tcpip at the command line to reconfigure your system.
  3. If you suspect that the host is having communication problems, try to attach it to the network.
• Check if the /dev/SRC file or the /dev/.SRC-unix directory exists.
  1. Change to the /dev directory by using the cd command and run the ls command.
  2. If the /dev/SRC file or the /dev/.SRC-unix directory does not exist, reboot your system by running the shutdown -Fr command. The shutdown -Fr command automatically creates the /dev/SRC file when the system comes up.
• If the /dev/SRC file or the /dev/.SRC-unix directory does exist, your file or directory may be damaged.
  1. Rename the file and directory by using the mv command to the /dev/SRC file or the/dev/.SRC-unix file, respectively.
  2. Reboot your system by running the shutdown -Fr command, which automatically creates the /dev/SRC file and the/dev/.SRC-unix directory when the system comes up.
  3. Reissue your command.
• Run the df command to check the file system capacity. Remove the unnecessary files if the file system is full, and rerun the SRC command.
• Check to see that the network cables are correctly attached. Run the errpt -a command to check for network or cabling errors.

0513-056 Timeout waiting for command response

If you specified a foreign host, see the /etc/inittab file on that foreign host. By viewing the file you are able to verify that the SRC daemon (srcmstr) was started with the -r flag to accept remote requests.

Possible Causes

• You ran the /usr/bin/refresh command or another SRC command with the -h (host-name) to access the System Resource Controller on another system, but the system was not physically attached to the network.
• You ran the /usr/bin/refresh command or another SRC command with the -h (host-name) parameter to access the System Resource Controller on another system , but the srcmstr daemon does not accept remote requests.

  Note: By default the srcmstr daemon does not accept remote requests.

• You ran the /usr/bin/refresh command or another SRC command to access the System Resource Controller on the local system, but the srcmstr process was not responding.

Procedures for Recovery

• If you were trying to access the System Resource Controller on a foreign host:
  1. Verify that the System Resource Controller on the foreign host is accepting remote requests.
     1. Use the ping command to verify that you can access the foreign host.
     2. Check the /etc/inittab file on the foreign host. The srcmstr entry must include the -r flag on the srcmstr command to allow srcmstr to accept remote requests.

        Note: From a security perspective this is not recommended.

     3. See the srcmstr command for the required /etc/hosts.equiv or /.rhosts configuration.
     4. If you require remote SRC support, add the -r flag to the srcmstr /etc/inittab entry, and restart the foreign host.
     5. Issue your command again to complete this procedure.
  2. If you cannot ping the foreign host, reconfigure the Internet socket. If you suspect that your system is having problems with the network, enter smit tcpip at the command line to reconfigure your system, then run your command again.
  3. Check your physical network cable connections.
     1. Check your cables and adapters, ensuring they are correctly attached.
     2. Run diagnostics by using the diag command.
     3. Ensure that the cable is attached and is switched on.
  4. Reboot your system by running the shutdown -Fr command.
  5. Issue your command again.
• If your were trying to access the System Resource Controller on the local system, run the ps -ef | grep srcmstr command to verify that the srcmstr daemon is running.

  To start the srcmstr daemon requires access to the file /etc/objrepos/SRCsubsys and a minimum amount of space in the root file system to create local sockets. To communicate, the srcmstr daemon requires AF_UNIX local socket support. See the netstat command.