This section provides information about identifying and resolving problems that may occur during installation. The following topics are discussed:
Resolving Installation Problems
Problems may be encountered during the installation process. Follow these steps to resolve them.
Review the error messages and conditions descriptions, and their resolutions below.
Re-install the product.
Review the list of error messages and conditions below if you encounter an error.
This message is a result of an AIX logical volume manager problem. Contact Rocket Customer Service.
If the virtual machine has been started by another UNIX user or root, it may become inaccessible to any other user.
Check the permissions; log in as root and enter:
|
ipcs -s |
A similar screen displays:
|
IPC status from /dev/kmem as of Tue MMM DD hh:mm:ss YYYY T ID KEY MODE OWNER GROUP Semaphores: s 21 0x80000010 --ra-ra-r-- root other |
The last two digits of the KEY are the virtual machine unique key as specified in the configuration file /usr/lib/pick/pick0 by the core statement.
Note the ID (21 in this example).
Remove the existing semaphore.
Enter:
|
ipcrm -s ID |
If the system fails while trying to attach memory, follow the procedure outlined in Global MPCB attachment failed.
The UNIX permissions may not be properly set for the D3 process to use the disk or tape device. On another terminal, log on as root and enter:
If using floppy:
|
chmod 666 /dev/rfd* |
If using tape:
|
chmod 666 /dev/rmt* |
This should start the restore. If not, verify that the device is correctly set.
Follow the same procedure as the Buffer attachment failed message.
D3 was not in single user mode during installation. Kill all D3 processes, enter single user mode, and restart installation.
If the file restore aborts, the virtual machine must be stopped before a new attempt to load the files is made.
If the file restore process is aborted in the virtual debugger, proceed to step 2.
If not, enter the D3 virtual debugger by pressing CTRL+].
When the virtual debugger prompt (!) displays, enter a colon (:), then press ENTER to push a level.
This action returns to TCL and displays a double colon prompt (::).
Enter:
|
shutdown |
If this fails, press CTRL+] to re-enter the virtual debugger.
Enter the monitor debugger from the virtual debugger. Enter:
|
md |
At the B! prompt enter:
|
kf q |
The following message displays:
|
sure? |
Enter y.
The system returns to the UNIX Shell prompt and terminates D3.
If the virtual machine has been booted by another UNIX user or by root, it may become inaccessible to any other user.
Check the permissions; log in as root and enter:
|
ipcs -m |
A similar screen displays:
|
IPC status from /dev/kmem as of Tue MMM DD hh:mm:ss YYYY T ID KEY MODE OWNER GROUP Shared Memory: m 202 0x80000010 --rw-rw-r-- root other m 303 0x00000010 --rw-rw-r-- root other |
The last two digits of the KEY are the virtual machine unique key as specified in the configuration file by the core statement.
Note the two IDs (202 and 303 in this example).
Remove the existing memory segment(s).
Enter:
|
ipcrm -m ID1 |
where ID1 is 202 in this example.
|
ipcrm -m ID2 |
where ID2 is 303 in this example.
If there is not enough space in /usr or the root file systems this error message displays.
|
D3_setup: INSTALLATION ERROR There may not be enough space in the root or /usr file system to install D3. D3_setup can attempt to compensate by re-executing the install with an option to automatically allocate more space from a pool of free space. Alternatively, you can examine the /tmp/ap.installerr file to determine which file system needs more space and remove or relocate as necessary. Do you want to automatically allocate space? |
D3_setup attempts to compensate by re-executing the installation with an option to automatically allocate more space from a pool of free space.
Enter y to automatically allocate space.
If there is not enough free space, this message displays:
|
D3_setup: INSTALLATION ERROR The installation has failed. To retry the installation when the problem has been resolved, run the D3_setup script again. The first part of the /tmp/ap.installerr file will print below: [message from ap.installerr] |
View the ap.installerr file to resolve the problem.
If you are unable to resolve the problem as described in the ap.installerr file contact your reseller for assistance.
There is less than 32 MB left on the volume group rootvg. If there is no space on the hard disk, AIX must be re-installed. If there is space on the hard disk, a separate volume group must be created. Create the volume group using smit and restart the installation procedure.
This message can occur during the installation procedure when trying to re-install D3 on a system where D3 processes are active. When the procedure is executed in single-user mode as indicated, all D3 processes are terminated. However, in some cases a process cannot be terminated (usually due to a problem with a tape device that a D3 process is trying to access).
Set the system to single-user mode to ensure no D3 process is active.
At the shell prompt, enter these commands to check for existing processes and proceed with steps 3 to 7 for each:
|
ps -ef | grep d3 ps -ef | grep ap |
This may display a screen similar to:
|
root 1640 1 06:03:42 90/0 0:00 d3 - 58 tty90 |
which indicates there is one process (PID 1640) still running D3.
Attempt to kill it. Type:
|
kill pid.number |
Retry the ps command to make sure the process is gone.
If the kill fails, attempt the command:
|
kill -9 pid.number |
Retry the ps command again.
If the kill still fails, UNIX must be shut down to remove the process.
After UNIX is rebooted, restart the D3 installation procedure with UNIX in single-user mode.
Contact Rocket Customer Service. Make sure the message override protection setting 06755 for ap did not occur, as shown earlier in this section. The AIX file /tmp/ap.linkerr contains a trace of the errors. Display this file and communicate its content to the Rocket Support Representative.
If this error message displays:
|
ld: 0706-006 Cannot find or open library file: -l m ld:open () : A file or directory in the path name does not exist. |
This indicates that you do not have the minimum software requirements installed. See Minimum Recommendations and Requirements.
When the virtual machine is started, messages are displayed as D3 processes are started. For example, after starting background processes, messages indicating a process has failed to start may appear. For example, if the above message occurs, log on as dm and enter start.ss. which restarts the scheduler and the spooler. If no error messages occur, the system processes were started successfully. Check that all processes have started with the d3 -q command. If the error message occurs again, contact Rocket Customer Service for assistance.
Reboot D3 AIX.
The following message displays:
|
Options: F)ile only, A)BS only, X)eXecute. Q)uit = _ |
Select the A option, load the ABS, and select the device corresponding to /usr/lib/pick/ab.
If the virtual machine has been started with a given memory size, and if this memory is increased by changing the core statement in the configuration file, the system fails while trying to allocate more memory with the same key.
Check the permissions; log in as root and enter:
|
ipcs -m |
A similar screen displays:
|
IPC status from /dev/kmem as of Tue MMM DD hh:mm:ss YYYY T ID KEY Mode OWNER GROUP Shared Memory: M 202 0x80000010 --rw-rw-r-- root other M 303 0x00000010 --rw-rw-r-- root other IPC statusfrom /dev/kmem as of Tue MMM DD hh:mm:ss YYYY T ID KEY MODE OWNER GROUP Shared Memory: m 202 0x80000010 --rw-rw-r-- root other m 202 0x00000010 --rw-rw-r-- root other |
The last two digits of the KEY are the virtual machine unique key as specified in the configuration file by the statement core.
Note the two IDs (202 and 303 in this example).
Remove the existing memory segment(s). Enter:
|
ipcrm -m ID1 |
(where ID1 is 202 in this example.
|
ipcrm -m ID2 |
(where ID2 is 303 in this example.
See Also
D3 Installation Guide Overview
Upgrading with a File-Save Tape
Upgrading with Data Files in Place