Sun N1 System Manager 1.3.1 Troubleshooting Guide

Chapter 2 Installation and Configuration Problems

This chapter lists Sun N1 System Manager problems that can occur during installation and configuration, their causes, and the solution for each problem. The following topics are discussed:

Checkinstall Script Did Not Complete Successfully

If you use the command su instead of su - root to log in to the management server to run N1 System Manager installation, the checkinstall process will fail. The following message is displayed:

/tmp/bm122834/installm1a4XN/checkinstallp1a4XN: /tmp/bm122834/installm1a4XN/checkinstallp1a4XN: cannot open
pkgadd: ERROR: checkinstall script did not complete successfully

Always use the command su - root when instructed to log in as root. The su command does not provide the full system root account environment, path, and privileges.

Command failed for target `Makefile'

If the management server system date is incorrect, N1 System Manager installation will fail. The following message is written to the installation log file /var/tmp/installer.log.lates:

Writing Makefile for Locale::gettext
Makefile out-of-date with respect to
/usr/perl5/5.8.4/lib/i86pc-solaris-64int/Config.pm
/usr/perl5/5.8.4/lib/i86pc-solaris-64
int/CORE/config.h
Cleaning current config before rebuilding Makefile...
make -f Makefile.old clean > /dev/null 2>&1 || /bin/sh -c true
/usr/bin/perl Makefile.PL
Writing Makefile for Locale::gettext ==> Your Makefile has been rebuilt. <== 
==> Please rerun the make command.  <== false
*** Error code 255 make: Fatal error: Command failed for target `Makefile'

Set the management server system date and rerun the N1 System Manager install.

DHCP Startup Failed

If N1 System Manager has not been configured, DHCP will not start. The error message Starting dhcpd: [Failed] is displayed during management server reboot.

Configure the N1 System Manager system as described in Configuring the N1 System Manager in Sun N1 System Manager 1.3 Installation and Configuration Guide.

Error Waiting for `Component` To Start

If the management server /etc/hosts file does not contain a domain name for the management server, or contains an incorrect domain name, then N1 System Manager components will fail to start. The following message is displayed:

Error waiting for component to start

where component is the name of the N1 System Manager component that failed to start.

Update the /etc/hosts file as described in To Update the /etc/hosts File.

HTTPD Cannot Determine Server's Domain Name

If the management server /etc/resolve.conf file is not configured correctly, then N1 System Manager cannot start HTTPD services. The following message is displayed:

[alert] httpd: Could not determine the server's fully
 qualified domain name, using 129.123.111.12 for ServerName 
 scs-httpd: Fri Nov 19 12:47:34 PST 2004 : Daemon started (pid=1473 1485 1486..

Update the /etc/resolv.conf file as described in To Update the /etc/resolv.conf File.

HTTPS Connection to the Management Server Is Refused

If the management server file /etc/resolve.conf is not configured correctly, any attempt to connect to themanagement server web server using the URL format https://management-server-name will fail and display the following error message.

Connect to management server url:443 failed (Connection refused)