Error Messages for Component ID 3004

AIX Version 4.3 Messages Guide and Reference

Error Messages for Component ID 3004

3004-004 You must "exec" login from the lowest login shell

Possible Causes

You attempted to log off the system while processes are still running in another shell.

Procedures for Recovery

Notes:

Verify that all processes have stopped.

Log off from the lowest login shell.

3004-007 You entered an invalid login name or password

Possible Causes

You tried to log in to a system that does not recognize your login or password.

Procedures for Recovery

Add your user ID to the system
1. Log in to your system as the root user. Check to see if your system has the user ID you want to add by running the lsuser command.
2. Run the mkuser command to create a user ID.
3. Change the password by running the passwd command.
4. Try logging in again.
Change the password on that particular user ID.
1. Log in to your system as the root user.
2. Check to see if your system has the user ID you want by running the lsuser command.
3. Change the password by running the passwd command.
4. Try logging in again.
Make sure that you have a shell open in the Initial PROGRAM attribute on your user ID.
1. Log in to your system as the root user.
2. Open the System Management Interface Tool (SMIT) by entering smit user from the command line.
3. Go to the Change / Show Characteristics of a User option and enter in the user ID you want to check at the User NAME prompt.
4. If you do not have a shell opened in the Initial PROGRAM attribute, enter in the login shell you want to use. For example:
```
/bin/ksh
```
5. Reenter and log in again.
If you cannot log in as the root user, then reboot your system as a single user mode and change the root password.
1. Shut down your system and turn the key mode switch to Service.
2. Reboot your system using the boot media.
3. Select the Maintenance option from the Installation and Maintenance menu, then select Access a Root Volume Group.
4. After identifying the correct volume group, select Access this Volume Group and Start a Shell.
5. Change the directory to the /etc/security directory by running the cd command.
6. Copy the passwd file to the passwd.sav file by running the cp command.
7. Edit the passwd file and change the passwd = entry blank, then turn your key mode switch to Normal.
8. Reboot your system and log in to your system as the root user.
9. Force the changes you have made to be written to disk by the using the sync command:
```
sync;sync
```
10. Change your password with the passwd command.
If you do not have either the /etc/passwd or /etc/security/passwd file on your system, try replacing the file.
1. Copy either the /etc/passwd or the /etc/security file from another system that has the same release level as your current system. Do this either through the network by running the ftp command or through a diskette by using the backup and restore commands.
2. When you restore the file, make sure that it preserves the permission code, ownership, and location of your previous file.
3. Edit the /etc/security/passwd file and delete all unnecessary user IDs, then blank out the passwd = entry.
4. Reboot and log in as the root user.
If you suspect that the /usr/sbin/tsm file is damaged, perform the following steps:
If you can log in as the root user, check the /usr/sbin/tsm file:
1. Make sure the file has the correct permission and ownership. The permission should be set to -r-sr-xr-x and ownership of root security. You can change permission by using the chmod command. Use the chown command for setting the correct ownership.
2. If you still have problems, replace the file from another system that has the same release level as your current system, either through the network by running the ftp command, or through a diskette by using the backup and restore commands.
3. When you restore the file, make sure that it preserves the permission code, ownership, and location of your previous file.
4. Turn the key mode switch to Normal and reboot the system by using the shutdown -Fr command.
If you cannot log in as the root user, start your system as single mode user and recreate the port.

3004-008 Failed setting credentials

Possible Cause

Procedures for Recovery

Check the permissions on the root directory (/). They should be 755. You can change permission by using the chmod command. Use the chown command for setting the correct ownership.
If a service fix has recently been applied, it may be necessary to reboot the system.

3004-009 Failed running login shell

Possible Causes

You tried to log in to a system that has a damaged login shell.
The login shell does not exist.

Procedures for Recovery

If you can log in as the root user, use the System Management Interface Tool (SMIT) to check the Initial PROGRAM attribute for that particular user ID.
1. Log in to your system as the root user.
2. Enter smit user at the command line, go to the Change / Show Characteristics of a User option, and enter in the user ID you want to check at the User NAME prompt.
3. On the next menu, check the Initial PROGRAM attribute to see which login shell the user is in. For example:
```
/bin/ksh
```
4. Either change the Initial PROGRAM that the user is in to another login shell or replace the existing login shell file from another system that has the same release level as your system. Do this either through the network by running the ftp command, or through a diskette by using the backup and restore commands.
5. When you restore the file, make sure that it preserves the permission code, the ownership, and the location of your previous file.
If you cannot log in as the root user, then reboot your system as single user mode and change the login shell.
1. First see "Accessing a System That Does Not Boot" , and perform the steps described to access a system that does not boot from the hard disk. After completing the procedure, return here and continue with the following steps.
2. Run the cd /bin command, then run the ls -l command.
3. If you know what your login shell name is, rename it with the mv command. For example:
```
mv ksh ksh.sav
```
4. Create a link to another of the login shells by using the ln command. For example:
```
ln -s sh ksh
```
5. Turn your key mode switch to the Normal position.
6. Reboot your system login to your system as the root user and try replacing the damaged or missing shell from another system that has the same release level as your system, either through the network by running the ftp command or through a diskette by using the backup and restore commands.
7. When you restore the file, make sure that it preserves the permission code, the ownership, and the location of your previous file.

3004-010 Failed setting terminal ownership and mode

Possible Causes

You tried to log in to a system that does not recognize your user group ID.
Your settings on the limit file are incorrect.

Procedures for Recovery

Log in as the root user and use the System Management Interface Tool (SMIT) to do the following:
1. Enter smit user at the command line and go to the Change / Show Characteristics of a User option and enter in the user name at the User NAME prompt.
2. Change the group ID of the user on the PRIMARY Group attribute.
3. Try logging in again.
If you cannot log in as the root user, reboot your system as single user mode and change the root password.
1. Shut down your system and turn the key mode switch to the Service position.
2. Reboot your system using the boot media.
3. Select the Maintenance option from the Installation and Maintenance menu, then select Access a Root Volume Group.
4. After identifying the correct volume group, select Access this Volume Group and Start a Shell.
5. Run the cd command and change the directory to the /etc file.
6. Add the following line to the group file:
```
system:!:0:root
```
7. Enter smit user and go to the Change / Show Characteristics of a User option and enter in root at the PRIMARY Group attribute; press Enter.
8. Turn the key mode switch to the Normal position.
9. Reboot your system and log in as the root user.
Check the /etc/security/limits file and increase the default setting of your login ID.

3004-015 TSM was unable to open port PathName

Possible Causes

You tried to log in to a system in which the /etc/getty command could not find the port (dev/tty#), or the port is damaged.

Procedures for Recovery

Log in as the root user and check if the port in the path name exists.
1. If the port exists, rename the port by using the mv command.
2. Create the new port name by using the mknod command or by rebooting the system.
3. If the port name does not exist, create a new port name by using the mknod command or by rebooting the system with the shutdown -Fr command.
If you cannot log in as the root user, reboot your system as a single user mode and re-create the port.
1. Shut down your system and turn the key mode switch to the Service position.
2. Reboot your system using the boot media.
3. Select the Maintenance option from the Installation and Maintenance menu, then select Access a Root Volume Group.
4. After identifying the correct volume group, select Access this Volume Group and Start a Shell.
5. If the port in the path name exists, rename the port by using the mv command.
6. Turn the key mode switch to the Normal position and reboot the system with the shutdown -Fr command.

3004-017 TSM was invoked with an illegal baud rate

Possible Causes

The baud rate specified in the Object Data Management (ODM) database was invalid for the terminal type.

Procedures for Recovery

Make sure that your system has access to the PdAt ODM file located in the /usr/lib/objrepos directory.
Make sure that there is a link file /etc/objrepos/PdAt pointing to the /usr/lib/objrepos/PdAt file.
If you suspect that the file is damaged or is missing, you can replace the file from another system that has the same release level as your system. Do this either through the network by running the ftp command or through a diskette by using the backup and restore commands.

When you restore the file, make sure that it preserves the permission code, the ownership, and the location of your previous file.

Verify that the Speedparameter for the tty has the correct value for the terminal type.

3004-019 TSM encountered an error on terminal /dev/Name

Possible Causes

This error message is always preceded by another error message and is to let you know that the condition needs to be corrected.

Procedures for Recovery

Check the previous message for more specific information in order to recover.

3004-024 ioctl failed errno Number

Possible Causes

You tried to log in to a system in which the tty configuration is damaged.
The cable attached to the terminal is damaged.
You tried to log in to a system that has a damaged /usr/sbin/tsm file.

Procedures for Recovery

Using the System Management Interface Tool (SMIT), select the Devices option, then remove and re-add the tty configuration.
Run the errpt-a command to check for cabling or other hardware problems.
If you suspect that the /usr/sbin/tsm file is damaged and you can log in as the root user, check the /usr/sbin/tsm file.
1. Make sure that the /usr/sbin/tsm file has the correct permission and ownership. The permission should be set to -r-sr-xr-x and ownership of root security.
2. You can change the permission by using the chmod command.
3. Use the chown command to set the correct ownership.
4. If you still have problems, replace the file from another system that has the same release level as your system, either through the network by running the ftp command or through a diskette by using the backup and restore commands.
5. When you restore the file, make sure that it preserves the permission code, ownership, and location of your previous file.
If you cannot log in as the root user, start your system as single user mode and recreate the port.
1. Shut down your system and turn the key mode switch to the Service position.
2. Reboot your system using the boot media.
3. Select the Maintenance option from the Installation and Maintenance menu, then select Access a Root Volume Group.
4. After identifying the correct volume group, select Access this Volume Group and Start a Shell.
5. Check if the /usr/sbin/tsm file has the correct permission and ownership. The permission should be set to -r-sr-xr-x and ownership of root security.
6. You can change the permission by using the chmod command.
7. Use the chown command to set the correct ownership.
8. If you still have problems, replace the file from another system that has the same release level as your system. Do this either through the network by running the ftp command or through a diskette by using the backup and restore commands.
9. When you restore the file, make sure that it preserves the permission code, the ownership, and the location of your previous file.

3004-026 tcsetattr failed errno Number

Possible Causes

You used the tsm, getty, rlogin, or telnet command to access a communications port that is locked, disabled, or nonexistent.

Procedures for Recovery

Check port definitions using the System Management Interface Tool (SMIT) to verify that the port you are attempting to access is properly defined.
If you are attempting to access a /dev/tty# device, use SMIT and from the command line enter the following to check the tty port definition:
```
smit tty
```
1. Select the Change/Show Characteristics option from the menu. Pay particular attention to the Number of BSD STYLE symbolic links field.
2. Ensure that this setting is greater than the number of connections expected on the computer.
3. Verify that the STATE field of the pty device is set to available.
Use the lsdev -c command to check the availability of the tty and pty devices.
If you are attempting to access a pseudo-terminal directly by means of the /dev/pts/# or /dev/ptc/# device, try using a different port number than the one you are using. The port number you use cannot be greater than the Number of BSD STYLE symbolic links defined for the pty device in SMIT.

3004-030 You logged in using all uppercase characters

Possible Causes

You attempted to log in with Caps Lock on.

Procedures for Recovery

Take Caps Lock off and try again.

3004-031 Password read timed out--possible noise on port

Possible Causes

You logged in but did not enter your password within a specified amount of time.
Your password wasn't validated within a specified amount of time due to a weak port connection.

Procedures for Recovery

Log in again and enter your password within approximately 90 seconds.
Verify your port connections.

3004-312 All available login sessions are in use

Possible Causes

You tried to log in to a system that had all present sessions in use.

Procedures for Recovery

Change the number of license users in your system.
1. Log in to your system as the root user.
2. List the number of license users by running the lslicense command.
3. Increase the number of license users by running the chlicense command.
4. Restart your system in order for this change to take effect.

3004-501 Cannot su to root: Authentication is denied - or Account has expired?

Possible Causes

You entered the su command but typed the password incorrectly.
The expiration date on the ID has expired.

Procedures for Recovery

Vefiry the password and entere the su command again.
Using the System Management Interface Tool (SMIT), remove the expiration date from that ID, or change the date to a new expiration date.

3004-686 Group Name does not exist

Possible Causes

Using the System Management Interface Tool (SMIT), you specified an invalid group name.
From the command line, you specified an invalid group name with the lsgroup command, the chgroup command, the chuser command, or the rmgroup command.

Procedures for Recovery

Use SMIT to specify a valid group name.
1. Return to the SMIT menu where the error occurred.
2. Select List to display valid group names.
3. Select the desired group name from the list.
4. Select Do to cause the desired action to take place.
Locate and specify a valid group name.
1. List valid group names in two ways:
  - Enter the lsgroup -a ALL command to list all valid group names.
    OR
  - Enter the cat /etc/group command to list all valid group names at the command line. This command shows the /etc/group file.
2. Enter the desired command with a valid group name.

3004-687 User does not exist

Possible Causes

Using the System Management Interface Tool (SMIT), you specified an invalid user name.
From the command line, you specified an invalid user name with the lsuser command, the chuser command, the rmuser command, or the passwd command.

Procedures for Recovery

Use SMIT to specify a valid user name.
1. Return to the SMIT menu where the error occurred.
2. Select List to display all valid users.
3. Select the desired user name from the list.
4. Select Do to cause the desired action to take place.
Locate and specify a valid user name.
1. List valid user names in one of two ways:
  - Enter the lsuser -a ALL command to list all valid user names. In the list, the first word of each line is the user name.
    OR
  - Enter the cat /etc/passwd command to list all valid user names. This command shows the /etc/passwd file. The first word on each line is the user name.
2. Enter the desired command with a valid user name.

3004-692 Error changing String to String : Value is invalid

Possible Causes

You assigned an invalid group name to the pgrp attribute using the mkuser or the chuser command, or with the System Management Interface Tool (SMIT) Security and Users—> Add a User menu option.
You assigned an invalid shell name to the shell attribute with the chuser command.
You assigned an invalid attribute with the chuser command or with the SMIT Security and Users—> Users—> Change / Show Characteristics of a User menu option.
You assigned an invalid attribute to the id or admin attributes with the chgroup command.
You assigned an invalid value to the flags attribute with the pwdadm -f command.

Procedures for Recovery

Ensure that the group name is valid.
When using the mkuser or chuser command to change the pgrp attribute, or when using SMIT to add a new user, verify that the group name exists with the lsgroup command, as follows:
```
lsgroup ALL | awk '{print $1}'
```
Ensure that the shell exists.
When using the chuser command to change the shell attribute, verify that the shell exists by doing one of the following:
- Check the shell entry in the /etc/security/login.cfg file.
- List the available shells with the chsh command.
Ensure that the attribute value is valid.
When using the chuser command to change attribute values, or specifying user attributes with SMIT, verify that the attribute value is valid.
- See the /etc/security/user file for a listing of valid values for the following attributes:
```
login         su              rlogin
telnet        daemon          admin
sugroups      tpath           ttys
expires       auth1           auth2
umask
```
- See the /etc/security/limits file for a listing of valid values for the following attributes:
```
fsize          cpu              data
stack          core             rss
```
Ensure that the id and admin attribute values are valid.
When using the chgroup command, ensure that the id attribute is an integer, and the admin attribute is one of the following:
```
yes    no
true   false
always
```
Ensure that valid values are specified.
When using the pwdadm -f command, ensure that the value following the flag is one or more of the following:
```
NOCHECK
ADMIN
ADMCHG
```