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.
If the installation procedure fails:
Locate the UNIX file /tmp/d3.install.errs which contains information to help resolve the problem.
View the contents of the file.
Enter:
more /tmp/d3.install.errs |
Press ENTER to continue viewing until the message <EOF> displays.
Communicate its content to a Rocket support representative.
Review the list of error messages and conditions below if you encounter an error.
Unlike other UNIX systems, the ipcs command in Linux does not show the KEY or ID field to identify who owns a given semaphore, shared memory segment, or message queue. Because of this, it is difficult to identify which of these ipcs lines belong to D3 or any other specific UNIX process. The following errors reported by the system require working with:
Cannot create semaphore set: permission denied |
Global MPCB attachment failed |
WARNING: Buffer attachment failed. Error: Not enough memory. Only 0K were allocated |
At this time, it is up to the system administrator to learn the patterns of the ipcs allocation for each individual system. When ipcs entries need to be killed, be sure to kill only those entries for D3; otherwise, other system functionality may be affected. When in doubt, the best solution is to attempt a shutdown of D3, then reboot Linux itself.
If the virtual machine has been started by another UNIX user or by root, it may become inaccessible to any other user.
Check the permissions; log on as root and enter:
ipcs -s |
A similar screen displays:
-----Semaphore Arrays----- semid owner perms nsems status 21 root 660 5 |
If the system fails to attach memory, follow the procedure outlined in Global MPCB attachment failed below.
If the virtual machine has been booted by another UNIX user or by root, it becomes inaccessible to any other user.
Check the permissions; log on as root and enter:
ipcs -m |
A similar screen displays:
------ Shared Memory Segments -------- key shmid owner perms bytes nattch status 0x00000000 0 nobody 600 46084 11 dest 0x80000010 1 root 660 157520 12 0xc0000010 2 root 660 6880256 12 0x00000010 3 root 660 16777216 12 0x00000011 4 root 660 15661056 12 0xa0000010 5 root 777 3686400 12 |
Note the IDs (1,2, 3, 4, and 5) in this example.
For each ID enter:
ipcrm shm ID |
where ID is the shared memory ID from above.
If the virtual machine has been started with some memory size, and if this memory is increased (by changing the statement core in the configuration file), the system fails while trying to allocate more memory with the same key.
Remove the existing segments as indicated for Global MPCB attachment failed above.
When Linux is installed, the permissions are set to 660 for the 3 1/2" 1.44 floppy device /dev/fd0H1440 and for the tape device /dev/nst0. Because the user pick is not a root user, the permissions are not sufficient for D3. As a result, when a D3 process attempts to write to the floppy, a message displays indicating that the drive is write-protected. To write to the device from D3 execute the command:
If using floppy:
chmod 666 /dev/fd0H1440 |
If using tape:
chmod 666 /dev/nst0 |
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/fd0 |
If using CD-ROM:
chmod 666 /cdrom |
This should start the restore. If not, verify that the device is correctly set.
Follow the same procedure as the Buffer attachment failed message.
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.
Make sure the message override protection setting 06755 for d3 did not occur, as shown elsewhere in this section. The UNIX file /tmp/d3.install.errs contains a trace of the errors. Display this file and communicate its content to the Rocket support representative.
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 -auwx | grep d3 ps -auwx | grep ap ps -auwx | grep pick |
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.
Reboot D3.
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.
See Also
D3 Installation Guide Overview
Upgrading with a File-Save Tape
Upgrading with Data Files in Place