Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
unable to get login prompt.
- Thread starter ranjank
- Start date
Hi RK
If you wants to login to CDE(common desktop environment)
Your $HOME/.dtprofile will be read.
Please ensure that last line of this file is uncommented such as :
DTRESOURCEPROFILE=true
If u are looking for command line login prompt
Please check $HOME/.profile or $HOME/.login files for accurate entries.
sushveer
IBM certified specialist-p-series AIX5L System Administration
AIX/SOLARIS/WEBSPHERE-MQ/TIVOLI Administrator
If you wants to login to CDE(common desktop environment)
Your $HOME/.dtprofile will be read.
Please ensure that last line of this file is uncommented such as :
DTRESOURCEPROFILE=true
If u are looking for command line login prompt
Please check $HOME/.profile or $HOME/.login files for accurate entries.
sushveer
IBM certified specialist-p-series AIX5L System Administration
AIX/SOLARIS/WEBSPHERE-MQ/TIVOLI Administrator
Check to see if the terminal is defined for login:
Assuming that console is listed in the output. Run:
If the system has a graphics terminal it would normally list the console as /dev/lft0. Generally an ascii console is on /dev/tty0 or /dev/tty1.
Finally check to make sure getty is running for the terminal you are trying to login from (eg. ps -ef | grep getty). If getty's not running you might have entries missing in you inittab.
Hope some of these suggesions help you out.
Code:
penable
Code:
lsconsFinally check to make sure getty is running for the terminal you are trying to login from (eg. ps -ef | grep getty). If getty's not running you might have entries missing in you inittab.
Hope some of these suggesions help you out.
- Thread starter
- #4
Hi ALL
Thanks for the reply,but i am still facing the problem.after making DTSOURCEFILE=true and checking gettty and /dev/tty0 which were there on the server settings,i am still not getting the login prompt on the console....does anyone can give any clues.
Regards,
RK.
Thanks for the reply,but i am still facing the problem.after making DTSOURCEFILE=true and checking gettty and /dev/tty0 which were there on the server settings,i am still not getting the login prompt on the console....does anyone can give any clues.
Regards,
RK.
I guess the first question would be is the console a serial ascii terminal (i.e. ibm 3151, ibm 3153, etc)?
If it is a serial terminal are you sure you are using a null modem cable? Are the baud rates for the port and terminal the same? Have you tried the terminal in a different serial port (one that's configured).
You can also quickly try:
If it's not showing up where you think it should you have either a config problem or a hardware setup problem.
If it is a serial terminal are you sure you are using a null modem cable? Are the baud rates for the port and terminal the same? Have you tried the terminal in a different serial port (one that's configured).
You can also quickly try:
Code:
echo "Where's my stinkin' console" > /dev/console
CrystalWizard
Technical User
sounds like maybe someone set your machine up for a different graphics console at some point and the systems trying to configure a monitor you no longer have. Boot to SMS and make sure your server is configured to use the console you actualy have plugged in.
You can also turn the machine off, take the video card out. turn it on, let it boot, turn it off, put the video card back IN and boot it. The first time through it'll discover you dont have a video card and delete it's console definition then when you put the card back in, it'll find a new adapter, and ask you to hit <somenumber> to use the console. (only asks you to hit that the first time the box is booted with a new graphics adapter)
SMS is eaiser.
You can also turn the machine off, take the video card out. turn it on, let it boot, turn it off, put the video card back IN and boot it. The first time through it'll discover you dont have a video card and delete it's console definition then when you put the card back in, it'll find a new adapter, and ask you to hit <somenumber> to use the console. (only asks you to hit that the first time the box is booted with a new graphics adapter)
SMS is eaiser.
If your console is directed to /dev/tty0, then check:
# lsattr -El tty0 -a login
You should get:
login enable Enable LOGIN True
If you get that login is disabled, change config by
# smit chgtty
If you have ascii terminal (not a monitor) connected directly to your RS/6000, then check baud rate/parity/bits per character/ num. of stop bits parameters for tty0. It is usually set to 9600/none/8/1.
Check graphical/console boot settings by
# smit dtconfig
wappet
Check initab with lsitab -a. Do you have a line which reads like
cons:0123456789:respawn:/usr/sbin/getty /dev/console
If you have a serial terminal ( e.g. IBM3151 ) console, then you need this. This is the entry that initiates the console login prompt
If you do, then check what entries are in inittab before it. You might have an entry which is of type 'wait' which is not completing and so inittab entries are not all being processed. Try moving this entry further up inittab and seeing if it works; this may help narrow down where the problem lies
If you are using CDE, check whether there is a line
dt:2:wait:/etc/rc.dt to start the desktop login
Dave
cons:0123456789:respawn:/usr/sbin/getty /dev/console
If you have a serial terminal ( e.g. IBM3151 ) console, then you need this. This is the entry that initiates the console login prompt
If you do, then check what entries are in inittab before it. You might have an entry which is of type 'wait' which is not completing and so inittab entries are not all being processed. Try moving this entry further up inittab and seeing if it works; this may help narrow down where the problem lies
If you are using CDE, check whether there is a line
dt:2:wait:/etc/rc.dt to start the desktop login
Dave
- Thread starter
- #9
Hi All
Sorry for the late reply.I tried all the suggestions but still i am not getting the success.I am still not getting the login prompt.Can anyone infuse some fresh suggestions.Waiting eagerly for the replies.Thanks in advance.
Regards,
RK.
Sorry for the late reply.I tried all the suggestions but still i am not getting the success.I am still not getting the login prompt.Can anyone infuse some fresh suggestions.Waiting eagerly for the replies.Thanks in advance.
Regards,
RK.
CrystalWizard
Technical User
Since you can login through telnet, please do this:
login through telnet and type errpt. Paste the output between your last reboot and right now up here so we can see it please.
login through telnet and type errpt. Paste the output between your last reboot and right now up here so we can see it please.
why can't try like this.
1. #lscons -a
current = <device>
find the console. verify the same.
2. if you are using CDE,(may be CDE not coming up properly)
#ps -ef|grep dtlogin
kill the pid or
#stopsrc -s dtsrc
if you don't succeed , post errpt details.
aixnag
IBM Certified Specialist - P-series AIX 5L Administration
IBM Certified Specialist - AIX V4 HACMP
1. #lscons -a
current = <device>
find the console. verify the same.
2. if you are using CDE,(may be CDE not coming up properly)
#ps -ef|grep dtlogin
kill the pid or
#stopsrc -s dtsrc
if you don't succeed , post errpt details.
aixnag
IBM Certified Specialist - P-series AIX 5L Administration
IBM Certified Specialist - AIX V4 HACMP
- Thread starter
- #13
HI
Here is my errpt result.
---------------------------------------------------------------------------
LABEL: CONSOLE
IDENTIFIER: 7F88E76D
Date/Time: Thu Jun 26 19:29:56 IST
Sequence Number: 317
Machine Id: 005119224C00
Node Id: cambridge
Class: S
Type: PERM
Resource Name: console
Description
SOFTWARE PROGRAM ERROR
Probable Causes
SOFTWARE PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
REVIEW DETAILED DATA
Detail Data
USER'S PROCESS ID:
4434
DETECTING MODULE
conwrite
FAILING MODULE
UIO_WRITE
RETURN CODE
5
ERROR CODE
0
---------------------------------------------------------------------------
LABEL: CONSOLE
IDENTIFIER: 7F88E76D
Date/Time: Thu Jun 26 19:29:55 IST
Sequence Number: 316
Machine Id: 005119224C00
Node Id: cambridge
Class: S
Type: PERM
Resource Name: console
Description
SOFTWARE PROGRAM ERROR
Probable Causes
SOFTWARE PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
REVIEW DETAILED DATA
Detail Data
USER'S PROCESS ID:
4434
DETECTING MODULE
conwrite
FAILING MODULE
UIO_WRITE
RETURN CODE
5
ERROR CODE
0
Duplicates
Number of duplicates
2
Time of first duplicate
Thu Jun 26 19:29:55 IST
Time of last duplicate
Thu Jun 26 19:29:55 IST
---------------------------------------------------------------------------
LABEL: CONSOLE
IDENTIFIER: 7F88E76D
Date/Time: Thu Jun 26 19:29:53 IST
Sequence Number: 315
Machine Id: 005119224C00
Node Id: cambridge
Class: S
Type: PERM
Resource Name: console
Description
SOFTWARE PROGRAM ERROR
Probable Causes
SOFTWARE PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
REVIEW DETAILED DATA
Detail Data
USER'S PROCESS ID:
4434
DETECTING MODULE
conwrite
FAILING MODULE
UIO_WRITE
RETURN CODE
5
ERROR CODE
0
---------------------------------------------------------------------------
LABEL: CONSOLE
IDENTIFIER: 7F88E76D
Date/Time: Thu Jun 26 19:29:53 IST
Sequence Number: 314
Machine Id: 005119224C00
Node Id: cambridge
Class: S
Type: PERM
Resource Name: console
Description
SOFTWARE PROGRAM ERROR
Probable Causes
SOFTWARE PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
REVIEW DETAILED DATA
Detail Data
USER'S PROCESS ID:
4434
DETECTING MODULE
conwrite
FAILING MODULE
UIO_WRITE
RETURN CODE
5
ERROR CODE
0
---------------------------------------------------------------------------
LABEL: CONSOLE
IDENTIFIER: 7F88E76D
Date/Time: Thu Jun 26 19:29:52 IST
Sequence Number: 313
Machine Id: 005119224C00
Node Id: cambridge
Class: S
Type: PERM
Resource Name: console
Description
SOFTWARE PROGRAM ERROR
Probable Causes
SOFTWARE PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
REVIEW DETAILED DATA
Detail Data
USER'S PROCESS ID:
4434
DETECTING MODULE
conwrite
FAILING MODULE
UIO_WRITE
RETURN CODE
5
ERROR CODE
0
---------------------------------------------------------------------------
LABEL: CONSOLE
IDENTIFIER: 7F88E76D
Date/Time: Thu Jun 26 19:29:52 IST
Sequence Number: 312
Machine Id: 005119224C00
Node Id: cambridge
Class: S
Type: PERM
Resource Name: console
Description
SOFTWARE PROGRAM ERROR
Probable Causes
SOFTWARE PROGRAM
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
REVIEW DETAILED DATA
Detail Data
USER'S PROCESS ID:
4434
DETECTING MODULE
conwrite
FAILING MODULE
UIO_WRITE
RETURN CODE
5
ERROR CODE
0
---------------------------------------------------------------------------
LABEL: REBOOT_ID
IDENTIFIER: 2BFA76F6
Date/Time: Thu Jun 26 19:27:10 IST
Sequence Number: 310
Machine Id: 005119224C00
Node Id: cambridge
Class: S
Type: TEMP
Resource Name: SYSPROC
Description
SYSTEM SHUTDOWN BY USER
Probable Causes
SYSTEM SHUTDOWN
Detail Data
USER ID
0
0=SOFT IPL 1=HALT 2=TIME REBOOT
0
TIME TO REBOOT (FOR TIMED REBOOT ONLY)
0
---------------------------------------------------------------------------
LABEL: ERRLOG_ON
IDENTIFIER: 9DBCFDEE
Date/Time: Thu Jun 26 19:29:52 IST
Sequence Number: 309
Machine Id: 005119224C00
Node Id: cambridge
Class: O
Type: TEMP
Resource Name: errdemon
Description
ERROR LOGGING TURNED ON
Probable Causes
ERRDEMON STARTED AUTOMATICALLY
User Causes
/USR/LIB/ERRDEMON COMMAND
Recommended Actions
NONE
---------------------------------------------------------------------------
LABEL: ERRLOG_OFF
IDENTIFIER: 192AC071
Date/Time: Thu Jun 26 19:26:30 IST
Sequence Number: 308
Machine Id: 005119224C00
Node Id: cambridge
Class: O
Type: TEMP
Resource Name: errdemon
Description
ERROR LOGGING TURNED OFF
Probable Causes
ERRSTOP COMMAND
User Causes
ERRSTOP COMMAND
Recommended Actions
RUN ERRDEAD COMMAND
TURN ERROR LOGGING ON
$
Thks
Ranjan
theycallmetim
Technical User
Try using a null-modem adapter on your console line (assuming it's a serial line).
aixmurderer
IS-IT--Management
Did you at some or other time perhaps redirect the console to another port? It seems like the system cannot find the console, look at your console settings. (smitty console)
It may be a cable issue too, see if the "clocal" setting is included in your TTY port setting (smitty tty), entry below:
STTY attributes for LOGIN [other,...,clocal]
IBM Certified Confused - MQSeries
IBM Certified Flabbergasted - AIX 5 pSeries System Administration
MS Certified Windblows Rebooter
It may be a cable issue too, see if the "clocal" setting is included in your TTY port setting (smitty tty), entry below:
STTY attributes for LOGIN [other,...,clocal]
IBM Certified Confused - MQSeries
IBM Certified Flabbergasted - AIX 5 pSeries System Administration
MS Certified Windblows Rebooter
CrystalWizard
Technical User
I agree with aixmurderer, make sure you aren't redirecting the console to something invalid. A search on uio_write errors on the ibm website returned an interesting result. If you're not on an SP2 node, it doesnt' exactly apply but read it over, it might give you a better idea of what's causing your problem.
Abstract
CONSOLE ERRORS AT BOOTTIME FROM MODULE UIO_WRITE ON SP2
Error Description
error report fills up with console errors from module
uio_write.
this is because the nodes get their console output
redirected to a file way through the rc.sp script way
too late. everything started before tries to write to
a nonvalid console, what creates those console errors.
Additional keywords: Fixed by IX49512
Local Fix
you can circumvent this by putting a line into inittab
directly after the "powerfail" line, like this :
swcons:2:wait:/etc/swcons /tmp/cons.out > /dev/console 2>&1
this will redirect everything to a file, and therefore
circumvent the errorlog messages.
Abstract
CONSOLE ERRORS AT BOOTTIME FROM MODULE UIO_WRITE ON SP2
Error Description
error report fills up with console errors from module
uio_write.
this is because the nodes get their console output
redirected to a file way through the rc.sp script way
too late. everything started before tries to write to
a nonvalid console, what creates those console errors.
Additional keywords: Fixed by IX49512
Local Fix
you can circumvent this by putting a line into inittab
directly after the "powerfail" line, like this :
swcons:2:wait:/etc/swcons /tmp/cons.out > /dev/console 2>&1
this will redirect everything to a file, and therefore
circumvent the errorlog messages.
- Status