A Troubleshooting

This appendix suggests solutions to issues that you may encounter when provisioning Linux.

I cannot see my stage, boot server in the UI to configure them with the provisioning application?

Either Management Agents have not been installed on the Stage/Boot Server machine or its not uploading data to the OMS. Refer to Agent Deployment Best Practices for troubleshooting information and known issues.

"Cannot create under the software library, please contact your administrator" error comes up while creating default image.

This may happen because the Software Library is not configured. Refer to Configuring Software Library. If it is configured and the error still occurs, then check if the library directory is accessible from the OMS server. The software library location should be accessible from the OMS and should have enough space.

Default Image or OS component creation fails with a '404' status while copying the header.info.

This may happen because of the RPM Repository URL being incorrect or because the RPM Repository has not been configured properly. Please refer to Setting Up RPM Repository and Configuring RPM Repository.

Default Image or OS component creation fails with an error message "Following RPMs are not found in Repository".

Reference machine has additional RPMs that are not available in the RPM repository. One of the following alternatives can be selected:

Choose a different reference machine.
Add extra RPMs in RPM repository (Make sure the RPMs are added in the repository as per Redhat specifications. Header files should be updated with the new RPM).
If the rpms are not required on the provisioned machine mention them in the custom_rpm.properties file. Refer to Appendix C.

Default Image or OS component creation job is suspended.

This may happen if the Preferred Credentials are not set for Reference machine. Please set the Preferred Credentials.

Default Image or OS component creation fails "Sudo error".

This may happen if

Sudo is not installed on the reference machine
The user mentioned for the Reference Machine is not in the sudoers list. Edit /etc/sudoers file and add the user in the list.

Default Image staging fails "cannot stage default image".

This happens if there is already a default image staged for the same IP address range as the current one. Remove the staged image by clicking on the Remove button in the Default Image section on the Administration tab.

Default Image or OS component staging/provision fails with "Sudo error".

This may happen if

Sudo is not installed on the reference machine.
The user mentioned for the Reference Machine is not in the sudoers list. Edit /etc/sudoers file and add the user in the list.

Default Image or OS component staging/provision job is suspended.

This may happen if the Preferred Credentials are not set for Reference machine. Please set the Preferred Credentials.

Default Image or OS component staging/provision job fails "with directory permission error".

This error happens because of insufficient user privileges on the stage server machine. STAGE_TOP_LEVEL_DIRECTORY should have the write permission for the Stage user. In case of NAS, the NAS directory should be mounted on the staging server. If the error is while writing to the '/tftpboot directory then it has to have the write permission for the Stage user.

Bare metal machine is not coming up since it cannot locate the Boot file.

Verify the dhcp settings (/etc/dhcpd.conf) & tftp settings for the target machine. Check whether the services (dhcpd, xinted, portmap) are running. Make the necessary setting changes if required or start the required services if they are down.

Even though the environment is correctly setup, bare metal box is not getting booted over network

Dhcp server does not get a DHCPDISCOVER message for the MAC address of the bare metal machine.

Even if your environment is setup properly and default image is staged properly you might face this issue if there is some problem with the NIC card. Because of this boot requests do not reach the boot server. Please verify the NIC and network connections.

Provisioning Default image on the bare metal box fails with "reverse name lookup failed" error.

One needs enter IP address of the Stage/NAS server if you have issue with 'reverse lookup'. Do the following:

Go to the Administration tab.
Click Edit button after selecting the existing Stage server entry.
Replace the Stage/NAS server hostname with its IP address.

Agent Installation fails after operating system has been provisioned on the bare metal box?

No host name is assigned to the bare metal box after provisioning the OS?

This might happen if the "get-lease-hostnames" entry in the dhcpd.conf file is set to true. Edit the dhcpd.conf file to set get-lease-hostnames entry to false.

Bare metal machine hangs after initial boot up (tftp error/kernel error).

This may happen if the tftp service is not running. Enable the tftp service. Go to the '/etc/xinetd.d/tftp' file and change the 'disable' flag to 'no' (disable=no). Also verify the dhcp settings.

Kernel panic occurs when the Bare Metal machine boots up.

Verify the dhcp settings and tftp settings for the target machine and make the necessary changes as required. In a rare case, the intird and vmlinuz copied may be corrupted. Copying them from RPM repository again would fix the problem.

Bare metal machine hangs after loading the initial kernel image.

This may happen if the network is half duplex. Half duplex network is not directly supported but following steps below would fix the problem:

On the Reference Machine modify 'ethtool -s eth0 duplex half' entry to 'ethtool -s eth0 duplex full' in the kickstart file.
Once done recreate the Default Image.

Bare metal machine cannot locate the kickstart file (Redhat screen appears for manually entering the values such as 'language', 'keyboard' etc).

This happens if STAGE_TOP_LEVEL_DIRECTORY is not mountable or not accessible. Make sure the stage top level is network accessible to the target machine. Though very rare but this might also happen because of any problem in resolving the stage server hostname. Enter the IP address of the stage/NAS server instead of hostname on which they are located and try the provisioning operation again.

Bare metal machine does not go ahead with the silent installation (Redhat screen appears for manually entering the network details).

Verify the DHCP settings for the target machine. Also verify that Network profile attached with the provisioning operation is proper. Though very rare but this might also happen because of any problem in resolving the stage server hostname. Enter the IP address of the stage/NAS server instead of hostname and try the provisioning operation again.

After provisioning, the machine is not registered in EM.

This happens if the EM Agent is not placed in the STAGE_TOP_LEVEL_DIRECTORY before provisioning operation. Place the EM agent in this directory and try the operation again. It might also happen if the OMS registration password provided for securing the agents is incorrect. Go to the agent oracle home on the target machine and run the emctl secure agent command supplying the correct OMS registration password.

Component creation fails with "Cannot create under the software library, please contact your administrator".

This may happen if the Software Library is not configured with the Enterprise Manager. Refer Configuring Software Library. Create the components once the software library is configured.

"Cannot create under the software library, please contact your administrator" error comes up while creating default image.