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

Possible Causes

• You ran the /bin/refresh command or another SRC command to access the System Resource Controller, but the system was not physically attached to the network.
• The console was either switched off or not attached when the system was restarted. This caused two srcmstr processes to start.

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 determine 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, then run your command again.
• Check your physical network cable connections.
  1. Check your cables and adapters to make sure that they are correctly attached.
  2. Run diagnostics by using the diag command.
• Run the ps -ef | grep srcmstr command to check if more than one scrmstr daemon is running.
• Ensure that the cable is attached and is switched on.
• Reboot your system by running the shutdown -Fr command.
• Issue your command again.