7 Replies Latest reply on Aug 26, 2010 5:23 PM by 807559

    Console login service(s) fail to run..

    807559
      Hello,

      I've searched the forums, but I do not see any answer to my problem. When I reboot my system under milestone:multi-user-server, I get the following error, and enter maintenance mode:

      rebooting...

      SC Alert: Host System has Reset
      Probing system devices
      Probing memory
      Probing I/O buses

      Sun Fire V240, No Keyboard
      Copyright 1998-2004 Sun Microsystems, Inc. All rights reserved.
      OpenBoot 4.16.2, 2048 MB memory installed, Serial #65114435.
      Ethernet address 0:3:ba:e1:91:43, Host ID: 83e19143.



      Rebooting with command: boot
      Boot device: /pci@1c,600000/scsi@2/disk@0,0:a File and args:
      SunOS Release 5.10 Version Generic 64-bit
      Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
      Use is subject to license terms.
      Hardware watchdog enabled
      Booting to milestone "svc:/milestone/multi-user-server:default".
      Requesting System Maintenance Mode
      (See /lib/svc/share/README for more information.)
      Console login service(s) cannot run

      Root password for system maintenance (control-d to bypass):

      [root@dark (~)]# svcs -l console-login
      fmri svc:/system/console-login:default
      name Console login
      enabled false (temporary)
      state disabled
      next_state none
      state_time Wed Dec 07 15:34:41 2005
      restarter svc:/system/svc/restarter:default
      dependency require_all/none svc:/system/filesystem/minimal (online)
      dependency require_all/none svc:/system/identity:node (online)
      dependency require_all/none svc:/system/utmp:default (online)
      dependency require_all/none svc:/milestone/sysconfig (online)


      [root@dark (~)]# svcs -x console-login
      svc:/system/console-login:default (Console login)
      State: disabled since Wed Dec 07 15:34:41 2005
      Reason: Temporarily disabled by an administrator.
      See: http://sun.com/msg/SMF-8000-1S
      See: ttymon(1M)
      Impact: This service is not running.


      [root@dark (~)]# svcadm enable console-login
      [root@dark (~)]#
      [root@dark (~)]# svcs -x console-login
      svc:/system/console-login:default (Console login)
      State: offline since Wed Dec 07 15:43:18 2005
      Reason: Unknown.
      See: http://sun.com/msg/SMF-8000-AR
      See: ttymon(1M)
      Impact: This service is not running.

      [root@dark (~)]# svcs -xv console-login
      svc:/system/console-login:default (Console login)
      State: offline since Wed Dec 07 15:43:18 2005
      Reason: Unknown.
      See: http://sun.com/msg/SMF-8000-AR
      See: man -M /usr/share/man -s 1M ttymon


      [root@dark (~)]# ps -ef | grep svc
      root 459 72 0 15:44:35 console 0:00 grep svc
      root 7 1 0 15:34:40 ? 0:01 /lib/svc/bin/svc.startd
      root 9 1 0 15:34:40 ? 0:05 /lib/svc/bin/svc.configd
      [root@dark (~)]# gcore 7
      gcore: core.7 dumped

      I am not sure how to upload my core, if anyone can assist me I would greatly appreciate it.
        • 1. Re: Console login service(s) fail to run..
          807559
          It almost looks as if someone has been messing around in the manifest file, or you didn't paste the full output because:
          [root@dark (~)]# svcs -l console-login
          fmri svc:/system/console-login:default
          name Console login
          enabled false (temporary)
          state disabled
          next_state none
          state_time Wed Dec 07 15:34:41 2005
          restarter svc:/system/svc/restarter:default
          dependency require_all/none
          svc:/system/filesystem/minimal (online)
          dependency require_all/none
          svc:/system/identity:node (online)
          dependency require_all/none
          svc:/system/utmp:default (online)
          dependency require_all/none
          svc:/milestone/sysconfig (online)
          This is what I have:

          magi:/home/peter/bin $ svcs -l console-login
          fmri svc:/system/console-login:default
          name Console login
          enabled true
          state online
          next_state none
          state_time Fri Oct 28 00:39:33 2005
          logfile /var/svc/log/system-console-login:default.log
          restarter svc:/system/svc/restarter:default
          contract_id 1245
          dependency require_all/none svc:/system/filesystem/minimal (online)
          dependency require_all/none svc:/system/identity:node (online)
          dependency require_all/none svc:/system/utmp:default (online)
          dependency require_all/none svc:/milestone/sysconfig (online)


          Logical question: where's the logfile entry ? That would be the first place you need to start looking in order to determine what is going wrong here. Apart from that you should also consult the syslog and messages logfiles.
          • 2. Re: Console login service(s) fail to run..
            807559
            Unfortunatley I didn't cut anything out, that is what the output looks like...

            [root@dark (~)]# svcs -l console-login
            fmri svc:/system/console-login:default
            name Console login
            enabled true
            state offline
            next_state none
            state_time Wed Dec 07 16:54:58 2005
            restarter svc:/system/svc/restarter:default
            dependency require_all/none svc:/system/filesystem/minimal (online)
            dependency require_all/none svc:/system/identity:node (online)
            dependency require_all/none svc:/system/utmp:default (online)
            dependency require_all/none svc:/milestone/sysconfig (online)
            [root@dark (~)]#

            I have also referred to the logfile in /var/svc/log/

            -rw-r--r-- 1 root root 2409 Dec 7 16:54 system-console-login:default.log

            [ Dec  7 10:45:01 Rereading configuration. ]
            [ Dec  7 10:49:12 Disabled. ]
            [ Dec  7 11:05:24 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 11:05:25 Rereading configuration. ]
            [ Dec  7 11:05:25 No 'refresh' method defined.  Treating as :true. ]
            [ Dec  7 11:06:28 Stopping because all processes in service exited. ]
            [ Dec  7 11:06:28 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 11:10:51 Stopping because all processes in service exited. ]
            [ Dec  7 11:10:51 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 11:11:08 Stopping because all processes in service exited. ]
            [ Dec  7 11:11:08 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 11:11:46 Stopping because all processes in service exited. ]
            [ Dec  7 11:11:46 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 11:11:53 Stopping because all processes in service exited. ]
            [ Dec  7 11:11:53 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 11:13:36 Stopping because all processes in service exited. ]
            [ Dec  7 11:13:36 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 12:03:05 Stopping because all processes in service exited. ]
            [ Dec  7 12:03:05 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 12:37:55 Stopping because all processes in service exited. ]
            [ Dec  7 12:37:55 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 12:39:13 Stopping because all processes in service exited. ]
            [ Dec  7 12:39:13 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 13:05:30 Stopping because all processes in service exited. ]
            [ Dec  7 13:05:30 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 13:08:51 Stopping because all processes in service exited. ]
            [ Dec  7 13:08:51 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 14:35:22 Stopping because service disabled. ]
            [ Dec  7 14:35:22 Executing stop method (:kill) ]
            [ Dec  7 14:36:21 Enabled. ]
            [ Dec  7 15:04:15 Enabled. ]
            [ Dec  7 15:06:24 Rereading configuration. ]
            [ Dec  7 15:08:37 Enabled. ]
            [ Dec  7 15:43:18 Enabled. ]
            [ Dec  7 16:23:36 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 16:48:31 Executing start method ("/lib/svc/method/console-login") ]
            [ Dec  7 16:54:58 Enabled. ]

            Here are some logs from messages:

            messages:Dec 7 11:06:28 dark svc.startd[7]: [ID 694882 daemon.notice] instance svc:/system/console-login:default exited with status 1
            messages:Dec 7 11:11:08 dark svc.startd[7]: [ID 694882 daemon.notice] instance svc:/system/console-login:default exited with status 2
            messages:Dec 7 12:03:05 dark svc.startd[7]: [ID 694882 daemon.notice] instance svc:/system/console-login:default exited with status 127

            Any ideas on how I can troubleshoot this would be helpful..
            • 3. Re: Console login service(s) fail to run..
              807559
              Well, the logfile looks normal even though you might think it doesn't at first (I compared with mine, and considering that my box runs fine...).

              Next I'd do is check the restarter, located at /lib/svc/method/console-login and see what commands its trying to run and if all of those commands are available.

              I also noticed that this service can get enabled/disabled on its own (rather; by the system itself) which could be a next lead to a possible cause for problems.
              • 4. Re: Console login service(s) fail to run..
                807559
                Hello,

                I've searched the forums, but I do not see any answer
                to my problem. When I reboot my system under
                milestone:multi-user-server, I get the following
                error, and enter maintenance mode:

                rebooting...

                SC Alert: Host System has Reset
                Probing system devices
                Probing memory
                Probing I/O buses

                Sun Fire V240, No Keyboard
                Copyright 1998-2004 Sun Microsystems, Inc. All
                rights reserved.
                OpenBoot 4.16.2, 2048 MB memory installed, Serial
                #65114435.
                Ethernet address 0:3:ba:e1:91:43, Host ID: 83e19143.



                Rebooting with command: boot

                Boot device: /pci@1c,600000/scsi@2/disk@0,0:a File
                and args:
                SunOS Release 5.10 Version Generic 64-bit
                Copyright 1983-2005 Sun Microsystems, Inc. All
                rights reserved.
                Use is subject to license terms.
                Hardware watchdog enabled
                Booting to milestone
                "svc:/milestone/multi-user-server:default".
                Requesting System Maintenance Mode
                (See /lib/svc/share/README for more information.)
                Console login service(s) cannot run

                Root password for system maintenance (control-d to
                bypass):

                [root@dark (~)]# svcs -l console-login
                fmri svc:/system/console-login:default
                name Console login
                enabled false (temporary)
                state disabled
                next_state none
                state_time Wed Dec 07 15:34:41 2005
                restarter svc:/system/svc/restarter:default
                dependency require_all/none
                svc:/system/filesystem/minimal (online)
                dependency require_all/none
                svc:/system/identity:node (online)
                dependency require_all/none
                svc:/system/utmp:default (online)
                dependency require_all/none
                svc:/milestone/sysconfig (online)


                [root@dark (~)]# svcs -x console-login

                svc:/system/console-login:default (Console login)
                State: disabled since Wed Dec 07 15:34:41 2005
                Reason: Temporarily disabled by an administrator.
                See: http://sun.com/msg/SMF-8000-1S
                See: ttymon(1M)
                Impact: This service is not running.


                [root@dark (~)]# svcadm enable console-login
                [root@dark (~)]#











                [root@dark (~)]# svcs -x console-login
                svc:/system/console-login:default (Console login)
                State: offline since Wed Dec 07 15:43:18 2005
                Reason: Unknown.
                See: http://sun.com/msg/SMF-8000-AR
                See: ttymon(1M)
                Impact: This service is not running.

                [root@dark (~)]# svcs -xv console-login
                svc:/system/console-login:default (Console login)
                State: offline since Wed Dec 07 15:43:18 2005
                Reason: Unknown.
                See: http://sun.com/msg/SMF-8000-AR
                See: man -M /usr/share/man -s 1M ttymon


                [root@dark (~)]# ps -ef | grep svc

                root 459 72 0 15:44:35 console 0:00
                0:00 grep svc
                root 7 1 0 15:34:40 ? 0:01
                0:01 /lib/svc/bin/svc.startd
                root 9 1 0 15:34:40 ? 0:05
                0:05 /lib/svc/bin/svc.configd
                [root@dark (~)]# gcore 7



                gcore: core.7 dumped

                I am not sure how to upload my core, if anyone can
                assist me I would greatly appreciate it.
                Did have a similar problem.
                In my case, the problem occurred after I issued the following command:

                # svcadm milestone -d milestone/single-user:default


                The -d option made milestone/single-user:default the default milestone.
                So, everytime that I was booting the server, the server was going to milestone/single-user

                Cleared the situation with

                # svcadm milestone -d all
                # init 0
                ok boot

                My understanding is that milestone all is the default milestone when Solaris 10 is installed out of box.
                • 5. Re: Console login service(s) fail to run..
                  807559
                  Yep it should be all.
                  • 6. Re: Console login service(s) fail to run..
                    abrante
                    I found this thread useful, but would like to add one thing to the solution:

                    To check which milestone which is the default one, run:

                    svccfg -s svc:/system/svc/restarter:default listprop |grep "options/milestone"


                    If the command above returns nothing, then the default (i.e. 'all') is used.

                    .7/M.
                    • 7. Re: Console login service(s) fail to run..
                      807559
                      You posted:

                      [root@dark (~)]# svcs -x console-login
                      svc:/system/console-login:default (Console login)
                      State: offline since Wed Dec 07 15:43:18 2005
                      Reason: Unknown.
                      See: http://sun.com/msg/SMF-8000-AR
                      See: ttymon(1M)
                      Impact: This service is not running.
                      -------

                      ttymon is not running. This is a problem for the system console according to the ttymon man page:

                      System Console Invocation
                      The invocation of ttymon on the system console is managed under smf(5) by the service svc:/system/console-login.

                      you can see the interaction further when you look at the /var/svc/manifest/system/console-login and /lib/svc/method/console-login scripts.

                      you need sacadm -l to come back clean:

                      # sacadm -l
                      PMTAG PMTYPE FLGS RCNT STATUS COMMAND
                      zsmon ttymon - 0 ENABLED /usr/lib/saf/ttymon #

                      while you may have other config problems, ttymon is clearly yelling for attention. Check and verify that the /etc/saf and var/saf directories for zsmon are intact (check against a working system). There is a log file in /var/saf/zsmon that will sometimes give you the smoking gun or enough clues to figure out the problem.