Review the list of error messages and conditions provided 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 might become inaccessible to any other user.
ipcs -s
You will see a screen similar to:
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.
ipcrm -s ID
If the system fails while trying to attach memory, follow the procedure outlined in the Global MPCB attachment failed section.
The UNIX permissions might 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 WARNING: Buffer attachment failed. Error: Not enough memory. Only 0K were allocated message.
If the file restore aborts, the virtual machine must be stopped before a new attempt to load the files is made.
If not, enter the D3 virtual debugger by pressing CTRL+].
This action returns to TCL and displays a double colon prompt (::).
shutdown
md
kf q
You will see the following message:
sure?
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 might become inaccessible to any other user.
ipcs -m
You will see a screen similar to:
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.
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, you will see this error message:
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/d3.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.
If there is not enough free space, you will see this message:
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/d3.installerr file will print below: [message from d3.installerr]
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).
ps -ef | grep d3 ps -ef | grep ap
You might see information 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.
kill pid.number
kill -9 pid.number
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/d3.linkerr contains a trace of the errors. Display this file and communicate its content to the Rocket Support Representative.
If you see this error message:
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.
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 might appear. If this occurs, log on as dm and enter start.ss., which restarts the scheduler and the spooler.
You will see the following message:
Options: F)ile only, A)BS only, X)eXecute. Q)uit = _
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.
ipcs -m
You will see a message similar to:
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).
ipcrm -m ID1
(where ID1 is 202 in this example.
ipcrm -m ID2
(where ID2 is 303 in this example.