Collecting Logs From a Failed Node Install or Imaging

Logs required for debugging issues from a failed node installation or imaging process can be collected and transferred using an NFS/CIFS mount after network configuration is completed on the node.

Procedure

1. Configure the network on the node using the following steps:

   • In environments with DHCP, assign an IP address to the public interface by running the following command:

     # dhclient $[intx]
     

   • In non-DHCP environments, assign a static IP address to the public interface using the following commands:

     # ifconfig $[intx] $[IPaddress] netmask $[nmask]
     # route add default gw $[gateway] $[intx]
     

2. Mount the NFS/CIFS export on the node.

   • To mount an NFS export, run the following command:

     # mount -o nolock $[NFSServerIP]:$[ExportPath] $[mountpath]
     

     Without the -o nolock option, the following error occurs:

     mount.nfs: rpc.statd is not running but is required for remote locking.
     mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
     mount.nfs: mounting $[server:path] failed, reason given by server: No such file or directory
     

   • To mount a CIFS export, run the following command:

     # mount.cifs $[WindowsExportPath] $[mountpath] -o user=$[username]
     

     When prompted, enter the password for the specified username.

3. Collect the logs by copying the following files and directories to the NFS/CIFS mount. You can use tar to compress directories, if required.

   • Directory /var/log/

   • All .xml and .map files present at /

   • Output of the dmesg command

   • Output of the LVM commands vgscan, lvscan, and pvscan