AIX

AIX

Connect with fellow AIX users and experts to gain knowledge, share insights, and solve problems.

 View Only
  • 1.  AIX Console Loop After Upgrade to 6.1 TL02 from 5.3 TL05

    Posted Tue July 21, 2009 09:45 AM

    Originally posted by: ca1cu1on


    Greetings,

    I have migrated 3 Servers all from 5.3 TL 05 to 6.1 TL 02:
    9115-505 - Test migration
    9131-52A - Database Server
    9113-550 - Application Server

    The first two migrated to AIX 6.1 TL02 with no issue. The third machine boots, however, no console log in appears. I can, though, telnet and rsh into the machine no problem using an emulator (exceed), and remote mount filesystems...I just can't log in to the machine through the console OR through the emulator (exceed).

    I ran a ps -ef | grep console, where I see /usr/bin/X11/aixconsole
    so I ps -ef | grep the PID of /usr/bin/X11/aixconsole and I see:
    1. sleep 2 process tied to PID of /usr/bin/X11/aixconsole that keeps respawning
    2. another process tied to PID of /usr/bin/X11/aixconsole for /usr/sbin/rc.bootx

    In the rc.bootx file I see the loop under:
    #wait boot sequence to end
    which apparently is never ending...

    Can someone explain why the loop is occurring and how to pass through the loop so that a console log in can be made?
    Thanks in advance!


  • 2.  Re: AIX Console Loop After Upgrade to 6.1 TL02 from 5.3 TL05

    Posted Tue July 21, 2009 03:53 PM

    Originally posted by: ca1cu1on


    The inittab seems to be hanging:

    init:2:initdefault:
    brc::sysinit:/sbin/rc.boot 3 >/dev/console 2>&1 # Phase 3 of system boot
    powerfail::powerfail:/etc/rc.powerfail 2>&1 | alog -tboot > /dev/console # Power Failure Detection
    mkatmpvc:2:once:/usr/sbin/mkatmpvc >/dev/console 2>&1
    atmsvcd:2:once:/usr/sbin/atmsvcd >/dev/console 2>&1
    tunables:23456789:wait:/usr/sbin/tunrestore -R > /dev/console 2>&1 # Set tunables
    rc:23456789:wait:/etc/rc 2>&1 | alog -tboot > /dev/console # Multi-User checks
    rcemgr:23456789:once:/usr/sbin/emgr -B > /dev/null 2>&1
    fbcheck:23456789:wait:/usr/sbin/fbcheck 2>&1 | alog -tboot > /dev/console # run /etc/firstboot
    srcmstr:23456789:respawn:/usr/sbin/srcmstr # System Resource Controller
    rctcpip:23456789:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP daemons
    rcnfs:23456789:wait:/etc/rc.nfs > /dev/console 2>&1 # Start NFS Daemons
    rcitm1:2:wait:/etc/rc.itm1 > /dev/console 2>&1
    mkcifs_fs:2:wait:/etc/mkcifs_fs > /dev/console 2>&1 <- This is the last thing that I can prove loads

    One of these may be the cause:
    sniinst:2:wait:/var/adm/sni/sniprei > /dev/console 2>&1
    cron:23456789:respawn:/usr/sbin/cron

    This never occurs:
    install_assist:2:wait:/usr/sbin/install_assist </dev/console >/dev/console 2>&1 <- Is this the post installation configuration setup (TCP/IP, root pw, etc? It doesn't appear in inittab of other 2 successfully started servers...If so, this never happens, is it required after install, or can I rem it??
    Rest of inittab:
    piobe:2:wait:/usr/lib/lpd/pioinit_cp >/dev/null 2>&1 # pb cleanup
    qdaemon:23456789:wait:/usr/bin/startsrc -sqdaemon
    writesrv:23456789:wait:/usr/bin/startsrc -swritesrv
    uprintfd:23456789:respawn:/usr/sbin/uprintfd
    shdaemon:2:off:/usr/sbin/shdaemon >/dev/console 2>&1 # High availability daemon
    l2:2:wait:/etc/rc.d/rc 2
    l3:3:wait:/etc/rc.d/rc 3
    l4:4:wait:/etc/rc.d/rc 4
    l5:5:wait:/etc/rc.d/rc 5
    l6:6:wait:/etc/rc.d/rc 6
    l7:7:wait:/etc/rc.d/rc 7
    l8:8:wait:/etc/rc.d/rc 8
    l9:9:wait:/etc/rc.d/rc 9
    naudio::boot:/usr/sbin/naudio > /dev/null
    ntbl_reset:2:once:/usr/bin/ntbl_reset_datafiles
    rcml:2:once:/usr/ml/aix61/rc.ml > /dev/console 2>&1
    logsymp:2:once:/usr/lib/ras/logsymptom # for system dumps
    perfstat:2:once:/usr/lib/perf/libperfstat_updt_dictionary >/dev/console 2>&1
    diagd:2:once:/usr/lpp/diagnostics/bin/diagd >/dev/console 2>&1
    ctrmc:2:once:/usr/bin/startsrc -s ctrmc > /dev/console 2>&1
    dt:2:wait:/etc/rc.dt
    cons:0123456789:respawn:/usr/sbin/getty /dev/console
    ha_star:h2:once:/etc/rc.ha_star >/dev/console 2>&1
    vty1:2:off:/usr/sbin/getty /dev/vty1
    vty0:2:off:/usr/sbin/getty /dev/vty0
    rcpkcs11:2:wait:/etc/rc.pkcs11 > /dev/console
    rcnetwlm:23456789:wait:/etc/rc.netwlm start> /dev/console 2>&1 # Start netwlm
    lpd:2:once:/usr/bin/startsrc -s lpd
    ibmdir:2:once:/usr/ldap/sbin/rc.ibmdir > /dev/null 2>&1
    xmdaily:2:once:/usr/bin/topasrec -L -s 300 -R 1 -r 6 -o /etc/perf/daily/ -ypersistent=1 2>&1 >/dev/null #Start local binary recording


  • 3.  Re: AIX Console Loop After Upgrade to 6.1 TL02 from 5.3 TL05

    Posted Tue July 21, 2009 04:08 PM

    Originally posted by: The_Doctor


    I've seen similar symptoms before. Our problems may not be identical but removing the line ->

    install_assist:2:wait:/usr/sbin/install_assist </dev/console >/dev/console 2>&1

    fixed my issue. Notice the "wait" on this item. Your system startup will wait for this to complete & in your case, I'd hazard a guess, it never completes.

    I'd suggest dropping this line from inittab & see if this doesn't clear things up for you.


  • 4.  Re: AIX Console Loop After Upgrade to 6.1 TL02 from 5.3 TL05

    Posted Tue July 21, 2009 05:33 PM

    Originally posted by: shargus


    install_assist is a GUI program that finishes up the initial install (see the man page).
    It's supposed to put up a menu on the console to guide you through setting up terminal type, initial hostname and IP, etc.
    It could be that it's confused as to where the console is, and is waiting for input from the wrong place.


  • 5.  Re: AIX Console Loop After Upgrade to 6.1 TL02 from 5.3 TL05

    Posted Wed July 22, 2009 08:58 AM

    Originally posted by: ca1cu1on


    I commented out the following line, as you suggested:

    install_assist:2:wait:/usr/sbin/install_assist </dev/console >/dev/console 2>&1

    and it booted correctly. Thanks!
    Any ideas as to why this option causes the inittab to hang on some servers and not others?


  • 6.  Re: AIX Console Loop After Upgrade to 6.1 TL02 from 5.3 TL05

    Posted Wed July 22, 2009 09:07 AM

    Originally posted by: tony.evans


    As described above, it's either waiting for you to choose a console (i.e. it's sent output to all attached terminals asking you to press 1 or 2 or whatever to use as your active console) or the defined console has something on it which it's expecting you to interact with.

    Because the inittab entry says 'wait', init will do nothing until that process exits.