Error messages and conditions

Errors and working with ipcs

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 might be affected. When in doubt, the best solution is to attempt a shutdown of D3, then reboot Linux itself.

Cannot create semaphore set: permission denied

If the virtual machine has been started by another UNIX user or by root, it might become inaccessible to any other user.

• Check the permissions.
• Log on as root and enter:

  ipcs -s

  You will see a screen similar to:

  -----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 section.

Global MPCB attachment failed

If the virtual machine has been booted by another UNIX user or by root, it becomes inaccessible to any other user.

1. Check the permissions: Log on as root and enter:

   ipcs -m

   You will see a screen similar to:

   ------ 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

2. Note the IDs (1,2, 3, 4, and 5) in this example.
3. For each ID enter:

   ipcrm shm ID

   where ID is the shared memory ID from above.

WARNING: Buffer attachment failed. Error: Not enough memory. Only 0K were allocated

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.

Device is write-protected

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, you will see a message 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

Device light does not go on when restoring the files

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/fd0

If using CD-ROM:

chmod 666 /cdrom

This should start the restore. If not, verify that the device is correctly set.

Error: Not enough memory. Only 0K were allocated

Follow the same procedure as the WARNING: Buffer attachment failed. Error: Not enough memory. Only 0K were allocated message.

File restore aborts

If the file restore aborts, the virtual machine must be stopped before a new attempt to load the files is made.

1. 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+].

2. At the virtual debugger prompt (!), enter a colon (:) and press Enter to push a level.

   This action returns to TCL and displays a double colon prompt (::).

3. Enter:

   shutdown

4. If this fails, press CTRL+] to re-enter the virtual debugger.
5. Enter the monitor debugger from the virtual debugger.
6. Enter:

   md

7. At the B! prompt, enter:

   kf
   q

   You will see the following message:

   sure?

8. Enter y.

   The system returns to the UNIX Shell prompt and terminates D3.

Monitor link failed

Ensure that 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.

Override protection setting 06755 for d3 or d3 is busy

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).

1. Set the system to single-user mode to ensure no D3 process is active.
2. Complete the following steps:
   1. At the shell prompt, enter these commands to check for existing processes:

      ps -auwx | grep d3 
      ps -auwx | grep ap 
      ps -auwx | grep pick

      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.

   2. Proceed with Steps 3 through Step 7 for each.
3. Attempt to kill existing processes. Type:

   kill pid.number

4. Retry the ps command to ensure the process is gone.
5. If the kill fails, attempt the command:

   kill -9 pid.number

6. Retry the ps command again.
7. If the kill still fails, UNIX must be shut down to remove the process.
8. After UNIX is rebooted, restart the D3 installation procedure with UNIX in single-user mode.

Virtual ABS not valid

1. Reboot D3.

   You will see the following message:

   Options: F)ile only, A)BS only, X)eXecute. Q)uit = _

2. Select the A option, load the ABS, and select the device corresponding to /usr/lib/pick/ab.