This section lists, in alphabetical order, common error messages you might encounter on a CMS server. Each message is accompanied by its probable cause and the likely solution.

• Error in creating UNIX login for user ’username’. The user may have already had UNIX log...

  - Cause: The user already has a Linux system login in CMS.

  - Resolution: If the user username already has a Linux system login, ignore this message. Otherwise, verify that this user can log on and report any problems to Services.

• ERROR: Password aging cannot be implemented on systems using LDAP.

  - Cause: The system is using LDAP.

  - Resolution: Contact your network administrator. The passwords will have to be aged from the server running the directory service.

• Insufficient number of free blocks (#-of-blocks) in system name for temporary database tables.

  - Cause: The file system does not contain enough free blocks for CMS to create the temporary tables needed for the migration.

  - Resolution: Call services to resolve this situation.

• *** INTERNAL ERROR: contact services (error#, timestamp) ***

  - Cause: An internal error occurred during processing of the table listed above this message.

  - Resolution: Contact services immediately. Do not remove the log file. Services needs the errornum and time stamp to find more information in their error log.

• Request failed. See /cms/install/logdir/backup.log for more information.

  - Cause: The tape is improperly seated in the drive, or was removed from the drive during the backup, or is write protected, or the medium is corrupted.

  - Resolution: Check the console terminal. If you see a message like WARNING: ST01: HA 0 TC 3 LU 0: Err 60503005 CMD 0000000A Sense Key 00000004 Ext Sense 00000000, the tape is corrupted. Discard it and replace it with a new tape. Otherwise, remove the tape from the drive and make sure it is not write protected (the black arrow in the upper left corner should be pointing away from “safe”).

  Finally, reinsert the tape into the drive, making certain it is properly seated, and restart the backup.

• UNRECOVERABLE ERROR READING TAPE, errno= Failed to open tape: no entry in the device directory. Make sure the Maintenance: Backup/Restore Devices screen has the correct Path.

  - Cause: The program could not open the tape drive to read the CMS data.

  - Resolution: Check that the specified tape drive is set up with the correct path in the Maintenance: Backup/Restore Devices window. If you cannot resolve this problem, contact services for additional help. You may have a tape drive hardware problem or need a corrected tape device path.

• ** WARNING:** Only one user may run age_pw at one time.

  - Cause: More than one person is attempting to use the passwd_age option in the CMSADM menu.

  - Resolution: Attempt to run the command after a few minutes have passed. If you still receive the warning message, contact Avaya services.

• You must be root in order to run this command.

  - Cause: Superuser privileges are necessary to run this script because most of the commands are related to system administration.

  - Resolution: Log in as the root user and rerun the command.

• stale databases

  - Cause: The state database contains old information.

  - Resolution: Recreate the database.

• syntax error

  - Cause: The syntax and usage of the command may be incorrect.

  - Resolution: Reenter the command, correcting syntax errors you have made.

• The /cms filesystem needs to be mounted

  - Cause: /cms must be mounted for the command to work.

  - Resolution: Mount /cms with the command:

  mount /cms

• touch: /cms/db/unix_start cannot create

  - Cause: A CMSADM backup was done when CMS was still running. An attempt is made to restart CMS, but CMS files are not yet available.

  - Resolution: No response required. The message will disappear after you have restored and migrated CMS.

• Warning: inode blocks/cyl group (230 >= data blocks (135) in lost cylinder group. This implies 2160 sector(s) cannot be allocated.

  - Resolution: Some sectors will not be used by the filesystem. This is just a warning; the filesystem should be fine.

• logtime[xxx]: Failed to list SAVECORE dir contents. ERROR 0

  - Resolution: No action required, this is an informational message only indicating that no coredump files currently exist.