Solaris 11 zone is not coming online Post: 303040789

Sponsored Content

Operating Systems Solaris Solaris 11 zone is not coming online Post 303040789 by ron323232 on Wednesday 6th of November 2019 11:22:26 PM

11-07-2019

Registered User

This is on Solaris-11 with shared IP.
zlogin -C bring me inside zone without issue.
No file-system is full inside zone or on global zone

Code:

root@tdr-db:~# zoneadm list -icv
  ID NAME             STATUS      PATH                         BRAND      IP
   0 global           running     /                            solaris    shared
   2 tdr-db2        running     /zones/tdr-db2_root        solaris    shared
   5 tdr-db2-3      running     /zones/tdr-db2-3_root      solaris    shared
root@tdr-db:~#
root@tdr-db:~# svcs -xv
root@tdr-db:~# zlogin tdr-db2-3
[Connected to zone 'tdr-db2-3' pts/5]
Oracle Corporation      SunOS 5.11      11.2    June 2014
You have mail.
root@tdr-db2-3:~# svcs -xv
svc:/network/rpc/smserver:default (removable media management)
 State: uninitialized since November  1, 2019 11:24:51 AM PDT
Reason: Restarter svc:/network/inetd:default has not initialized service state.
   See: http://support.oracle.com/msg/SMF-8000-4D
   See: man -M /usr/share/man -s 1M rpc.smserverd
Impact: 2 dependent services are not running:
        svc:/milestone/multi-user-server:default
        svc:/application/texinfo-update:default

svc:/network/sendmail-client:default (sendmail SMTP client queue runner)
 State: disabled since November  1, 2019 11:24:51 AM PDT
Reason: Disabled by an administrator.
   See: http://support.oracle.com/msg/SMF-8000-05
   See: man -M /usr/share/man -s 1M sendmail
Impact: 1 dependent service is not running:
        svc:/system/fm/smtp-notify:default

svc:/application/cups/scheduler:default (CUPS Print Spooler)
 State: maintenance since November  1, 2019 11:30:09 AM PDT
Reason: Start method died on Killed (9).
   See: http://support.oracle.com/msg/SMF-8000-KS
   See: man -M /usr/share/man -s 8 cupsd
   See: /var/svc/log/application-cups-scheduler:default.log
Impact: This service is not running.
root@tdr-db2-3:~#

ron323232

View Public Profile for ron323232

Find all posts by ron323232

7 More Discussions You Might Find Interesting

1. News, Links, Events and Announcements

Sun says Open Source Solaris is coming

Sun confirms plans to open source Solaris Jonathan Schwartz (Sun CEO): "I don't want to say when that will happen. But make no mistake, we will open source Solaris."

2. Solaris

Solaris Zone : Non global Zone check failed

Hi All , I try to install some packages in my global zone... On the execution of the installion of the script it quits by saying the error "Non global zone check failed" Kindly help me in this regard Thanks in advance, jeganr

3. Solaris

Solaris 10 local zone on Solaris 11 global zone

Hi, A quick question: Can Solaris 10 local zones be moved to a Solaris 11 global zone and work well? Thank you in advance!

4. UNIX for Advanced & Expert Users

Solaris 10: I forgot to detach a zone before zpool export. Uninstall zone?

Dear all, recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes. I did the following: host1: $ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed $ zpool export zone1 host2: $ zpool...

5. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently...

6. Solaris

Solaris 11 Global zone patching having Solaris 10 branded zone

I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10...

7. Solaris

Solaris 11 zone has no external network access (except to Global Zone)

Hi, hoping someone can help, its been a while since I used Solaris. After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin) However, the NGZ cannot access any other netwqork devices, it can't even see the default router ...

LEARN ABOUT OSF1

named-xfer

named-xfer(8)						      System Manager's Manual						     named-xfer(8)

NAME

       named-xfer - Pulls BIND zones from another server

SYNOPSIS

       /usr/sbin/named-xfer  -z  zone_to_transfer  -f  db_file	-s  serial_no  [-d debug_level] [-l debug_log_file] [-t trace_file] [-p port] [-S]
       servers...

OPTIONS

       Specifies the name of the BIND zone for the named-xfer daemon to transfer, for example, dec.com. This option is required to  pull  a  zone.
       Specifies  the  name  of the file into which the pulled zone information is placed. This option is  required to pull a zone.  Specifies the
       current serial number of the SOA record for the zone zone_to_transfer.  If serial_no is set to 0, the zone is always pulled. This option is
       required  to  pull  a  zone.  Sets the debug level and determines the amount of debug information to be displayed.  Specifies the file that
       will contain any debug messages from the zone pull.  Specifies the file that will contain a trace from the zone pull.  Specifies  the  port
       that  will  be  used  instead  of the default name server port listed in /etc/services.	Performs a restricted transfer of only the SOA, NS
       records and glue A records for the zone. The SOA record is not loaded by named, but is used to determine when to  verify  the  NS  records.
       See named(8) for more information.  Specifies a list of Internet addresses, in dotted-quad format, from which to pull a zone.  If the first
       host cannot be reached, the named transfer daemon tries to pull the zone from the next host listed.

DESCRIPTION

       The named transfer daemon, /usr/sbin/named-xfer, is a server that is usually run by the named daemon, /usr/sbin/named, but it can  also	be
       run  manually  with  the  given	arguments.   The named transfer daemon runs on a BIND secondary server and pulls BIND zones from a primary
       server. This daemon is not run by default, nor can it be started up from inetd(8).

SEE ALSO

       Commands: named(8)

       Files: resolver(4), services(4)

																     named-xfer(8)