Problems registering Logical Hostname resource

I�m trying to mount a HA Oracle.
I installed SC 3.1, with Volume Manager I configurated the logical devices.
I install Oracle 9i in the local HD of the cluster nodes.
I have 2 280R in the cluster.
I installed HA for Oracle from SC 3.1 Cd.
I configure in /etc/hosts in both nodes:
node 0:
/etc/hosts
<IP> bbddtlatam
node 1:
/etc/hosts
<same IP> bbddtlatam
I configure a IPMP for each interface (both machines)
# ifconfig qfe0 group iptest
and
#scrgadm -a -t SUNW.oracle_server
#scrgadm -a -t SUNW.oracle_listener
#scrgadm -a -g resource_name_group
but
when i try to register the logical hostname:
#scrgadm -a -L -g resource_name_group -l bbddtlata
Call to rpc.fed failed for resource bbddtlatam, method hafoip_validate.
Validation of resource bbddtlatam in resource group bbdd-ora-rg on node latamint-9 failed.
In /var/adm/messages
Jun 15 10:31:46 latamint-9 Cluster.RGM.fed: [ID 115461 daemon.error] in libsecurity __rpc_get
localuid failed
Jun 15 10:31:46 latamint-9 Cluster.RGM.fed: [ID 991800 daemon.error] in libsecurity transport
tcp is not a loopback transport
Jun 15 10:31:46 latamint-9 Cluster.RGM.fed: [ID 299417 daemon.error] in libsecurity strong Un
ix authorization failed
Jun 15 10:31:46 latamint-9 Cluster.RGM.rgmd: [ID 217093 daemon.error] Call failed: FE_RUN: RP
C: Authentication error; why = Client credential too weak
Jun 15 10:31:46 latamint-9 Cluster.RGM.rgmd: [ID 581180 daemon.error] launch_validate: call t
o rpc.fed failed for resource <bbddtlatam>, method <hafoip_validate>
Any idea????
Thanks.....

looking at your error
this all comes and looks like error with rpc
see if rpc deamon is running fine

Similar Messages

  • Problem in creating logical hostname resource

    Hi all,
    I have a cluster configured on 10.112.10.206 and 10.112.10.208
    i have a resource group testrg
    I want to create a logical hostname resource testhost
    I have given a ip 10.112.10.245 in /etc/hosts file for testhost
    I am creating a logical hostname resource by below command -
    clrslh create -g testrg testhost
    I am doing this on 206
    As I do, the other node 208 becomes unreachable....I m not able to ping 208 but ssh is done from 206 to 208.
    I am also not able to ping 10.112.10.245
    Please help.

    So, the physical IP addresses of your two nodes are:
    10.112.10.206 node1
    10.112.10.208 node2
    And your logical host is:
    10.112.10.245 testhost
    Have you got a netmask set for this network? Is it 255.255.255.0 and is it set in /etc/netmasks?
    It's most likely that this is the cause of the problem if you have different netmasks on the interfaces.
    Tim
    ---

  • Restrict HA-NFS to logical hostname resource

    I have a 2 node cluster running 2 HA-NFS pools (one active on each node at a time). The two nodes each have a connection to our storage network (a private network, but not the same as the cluster interconnect networks). They also each have connections to the public network.
    I have everything working fine from a clustering standpoint. However, when I try to connect to the logical hostname of one of either of the NFS resource groups from FreeBSD, things fail. When I did a snoop, I saw the FreeBSD box talking to the address defined by my logical hostname for that resource group, then all of a sudden, the cluster node responding with its non-cluster address from that interface. As a result, the FreeBSD machine apparently rejects the packet, since it came from a differing source (despite it being UDP). Is it possible to restrict the NFS traffic to just the logical hostname for the resource group?
    For example:
    dfshares <clusternode> would return nothing, as the cluster node has no shares specifically listed.
    But
    dfshares <resourcegroup-lh-rs> would return the shares for that resource group.
    Basically, can we bind SUNW.HA-NFS to a specific interface/address like we can with samba?

    Hi,
    1. Have a look at http://blogs.sun.com/SC/entry/why_a_logical_ip_is , which should explain part of the problem. I doubt that you can configure the NFS server to listen on a specific interface or address only.
    2. I am not sure why your NFS client refuses the response from the NFS server. Or is it some firewall on your system that does this?
    3. If you switch NFS to TCP, this "problem" should not occur.
    Regards
    Hartmut

  • Creating Logical Hostname Resource - Resource contains invalid hostnames

    I am desperately trying to create a shared ip address that my two-node zone cluster will utilize for a failover application. I have added the hostname/ip address pair to /etc/hosts and /etc/inet/ipnodes on both global nodes as well as within each zone cluster node. I then attempt to run the following:
    # clrslh create -Z test -g test-rg -h foo.bar.com test-hostname-rs
    which yields the following:
    clrslh: host1.example.com:test - The hostname foo.bar.com is not authorized to be used in this zone cluster test.
    clrslh: host1.example.com:test - Resource contains invalid hostnames.
    clrslh: (C189917) VALIDATE on resource test-hostname-rs, resource group test-rg, exited with non-zero exit status.
    clrslh: (C720144) Validation of resource test-hostname-rs in resource group test-rg on node host1 failed.
    clrslh: (C891200) Failed to create resource "test:test-hostname-rs".
    I have searched high and low. The only thing I found was the following:
    http://docs.sun.com/app/docs/doc/820-4681/m6069?a=view
    Which states: User the clzonecluster(1M) command to configure the hostnames to be used for this zone cluster and then rerun this command to create the resource.
    I do not understand what it is saying. My guess is that I need to apply a hostname to the zone cluster. Granted, I don't know how to accomplish this. Halp?

    The procedure to authorize the hostnames for the zone cluster is below:
    clzc configure <zonecluster> (this will bring you under the zone cluster scope like below)
    clzc:<zonecluster> add net
    clzc:<zonecluster>:net> set address=<hostname>
    clzc:<zonecluster>:net> end
    clzc:<zonecluster> commit
    clzc:<zonecluster>info (to verify the hostname)
    After this operation, run the clrslh command to create the logical host resource
    and the command should pass.
    Thanks,
    Prasanna Kunisetty

  • Creating Logical hostname in sun cluster

    Can someone tell me, what exactly logical hostname in sun cluster mean?
    For registering logical hostname resource in failoover group, what exactly i need to specify
    for example, i have two nodes in sun cluster , How to create or configure a logical hostanme and it should point to which IP Address ( Whether it should point to IP addresses of nodes in sun cluster). Can i get clarification on this?

    Thanks Thorsten for ur continue help...
    The output of clrs status abc_lg
    === Cluster Resources ===
    Resource Name Node Name State Status Message
    abc_lg node1 Offline Offline
    node2 Offline Offline
    The status is offline...
    the output of clresourcegroup status
    === Cluster Resource Groups ===
    Group Name Node Name Suspended Status
    abc_rg node1 No Unmanaged
    node2 No Unmanaged
    You say that the resource should de enabled after creating the resource.. I am using GDS and i am just following the steps he provided to acheive high availabilty (in developers guide...)
    I have 1) Logical hostname resorce.
    2) Application resource in my failover resource group
    When i bring online the failover resource group , what should my failover resource group status and the status of resource in my resource group

  • Including Logical Hostname as a Resource Dependency

    Hi Folks,
    We're setting up a Calendar Server. we assign a Logical Hostname resource on which the Calendar Clients connect to.
    These are the steps that are used:
    I created a Fail Over Resource Group called MS_RG_BUDDY and bring it online
    scrgadm -a -g MS_RG_BUDDY -h mars,venus
    I created a Logical Hostname resource EVERGREEN for this Fail Over resource group
    scrgadm -a -L -g MS_RG_BUDDY -l EVERGREEN
    scrgadm -c -j EVERGREEN -y R_description="LogicalHostname resource for evergreen"
    Bring the Resource Group Online
    scswitch -Z -g MS_RG_BUDDY
    I create a HAStoragePlus Resources called disk-evergreen with two cluster file systems ( /var/opt/xyz and /var/opt/abc )
    scrgadm -a -j disk-evergreen -g MS_RG_BUDDY -t SUNW.HAStoragePlus -x FileSystemMountPoints="/var/opt/xyz,/var/opt/abc" -x AffinityOn=TRUE
    Enable the HAStoragePlus resource
    scswitch -e -j disk-evergreen
    Create a resource with a dependency on the HAStoragePlus resource
    scrgadm -a -j core-rs -t SUNW.iws -g MS_RG_BUDDY -x IWS_serverroot=/opt/SUNWiws -y Resource_dependencies=disk-evergreen
    I have a question. In the above command, we created a Resource_Dependency on the HAstoragePlus resource, should we also create dependency on the Logical hostname i.e should the Resource_dependency look like
    Resource_dependencies=evergreen,disk-evergreen
    Is this correct ?. Should we bother. Are there any other factors we might want to consder

    Hartmut,
    Thanks for your response, I think i wil use the explicit dependency :) since all our clients connect to the custer via this LogicalHostname.
    Are you referring to this property ?
    (CAL-RED-RG) Res Group network dependencies: True
    Gotten from running the following command:
    # ./scrgadm -pvv -g CAL-RED-RG
    Res Group name: CAL-RED-RG
    (CAL-RED-RG) Res Group RG_description: <NULL>
    (CAL-RED-RG) Res Group mode: Failover
    (CAL-RED-RG) Res Group management state: Managed
    (CAL-RED-RG) Res Group RG_project_name: default
    (CAL-RED-RG) Res Group RG_SLM_type: manual
    (CAL-RED-RG) Res Group RG_affinities: <NULL>
    (CAL-RED-RG) Res Group Auto_start_on_new_cluster: True
    (CAL-RED-RG) Res Group Failback: False
    (CAL-RED-RG) Res Group Nodelist: shaw telstra
    (CAL-RED-RG) Res Group Maximum_primaries: 1
    (CAL-RED-RG) Res Group Desired_primaries: 1
    (CAL-RED-RG) Res Group RG_dependencies: <NULL>
    (CAL-RED-RG) Res Group network dependencies: True
    (CAL-RED-RG) Res Group Global_resources_used: <All>
    (CAL-RED-RG) Res Group Pingpong_interval: 3600
    (CAL-RED-RG) Res Group Pathprefix: <NULL>
    (CAL-RED-RG) Res Group system: False
    (CAL-RED-RG) Res Group Suspend_automatic_recovery: False
    (CAL-RED-RG) Res name: redmeadows
    (CAL-RED-RG:redmeadows) Res R_description: LogicalHostname resource for
    redmeadows
    (CAL-RED-RG:redmeadows) Res resource type: SUNW.LogicalHostname:2
    (CAL-RED-RG:redmeadows) Res type version: 2
    (CAL-RED-RG:redmeadows) Res resource group name: CAL-RED-RG
    (CAL-RED-RG:redmeadows) Res resource project name: default
    (CAL-RED-RG:redmeadows{shaw}) Res enabled: True
    (CAL-RED-RG:redmeadows{telstra}) Res enabled: True
    (CAL-RED-RG:redmeadows{shaw}) Res monitor enabled: True
    (CAL-RED-RG:redmeadows{telstra}) Res monitor enabled: True
    (CAL-RED-RG:redmeadows) Res strong dependencies: <NULL>
    (CAL-RED-RG:redmeadows) Res weak dependencies: <NULL>
    (CAL-RED-RG:redmeadows) Res restart dependencies: <NULL>
    (CAL-RED-RG:redmeadows) Res offline restart dependencies: <NULL>
    (CAL-RED-RG:redmeadows) Res property name: Retry_interval
    (CAL-RED-RG:redmeadows:Retry_interval) Res property class: standard
    (CAL-RED-RG:redmeadows:Retry_interval) Res property description: Time in w
    hich monitor attempts to restart a failed resource Retry_count times.
    (CAL-RED-RG:redmeadows:Retry_interval) Res property type: int
    (CAL-RED-RG:redmeadows:Retry_interval) Res property value: 300
    (CAL-RED-RG:redmeadows) Res property name: Retry_count
    (CAL-RED-RG:redmeadows:Retry_count) Res property class: standard
    (CAL-RED-RG:redmeadows:Retry_count) Res property description: Indicates th
    e number of times a monitor restarts the resource if it fails.
    (CAL-RED-RG:redmeadows:Retry_count) Res property type: int
    (CAL-RED-RG:redmeadows:Retry_count) Res property value: 2
    (CAL-RED-RG:redmeadows) Res property name: Thorough_probe_interval
    (CAL-RED-RG:redmeadows:Thorough_probe_interval) Res property class: standa
    rd
    (CAL-RED-RG:redmeadows:Thorough_probe_interval) Res property description:
    Time between invocations of a high-overhead fault probe of the resource.
    (CAL-RED-RG:redmeadows:Thorough_probe_interval) Res property type: int
    (CAL-RED-RG:redmeadows:Thorough_probe_interval) Res property value: 60
    (CAL-RED-RG:redmeadows) Res property name: Cheap_probe_interval
    (CAL-RED-RG:redmeadows:Cheap_probe_interval) Res property class: standard
    (CAL-RED-RG:redmeadows:Cheap_probe_interval) Res property description: Tim
    e between invocations of a quick fault probe of the resource.
    (CAL-RED-RG:redmeadows:Cheap_probe_interval) Res property type: int
    (CAL-RED-RG:redmeadows:Cheap_probe_interval) Res property value: 60
    (CAL-RED-RG:redmeadows) Res property name: Failover_mode
    (CAL-RED-RG:redmeadows:Failover_mode) Res property class: standard
    (CAL-RED-RG:redmeadows:Failover_mode) Res property description: Modifies r
    ecovery actions taken when the resource fails.
    (CAL-RED-RG:redmeadows:Failover_mode) Res property type: enum
    (CAL-RED-RG:redmeadows:Failover_mode) Res property value: HARD
    (CAL-RED-RG:redmeadows) Res property name: PRENET_START_TIMEOUT
    (CAL-RED-RG:redmeadows:PRENET_START_TIMEOUT) Res property class: standard
    (CAL-RED-RG:redmeadows:PRENET_START_TIMEOUT) Res property description: Max
    imum execution time allowed for Prenet_Start method.
    (CAL-RED-RG:redmeadows:PRENET_START_TIMEOUT) Res property type: int
    (CAL-RED-RG:redmeadows:PRENET_START_TIMEOUT) Res property value: 300
    (CAL-RED-RG:redmeadows) Res property name: MONITOR_CHECK_TIMEOUT
    (CAL-RED-RG:redmeadows:MONITOR_CHECK_TIMEOUT) Res property class: standard
    (CAL-RED-RG:redmeadows:MONITOR_CHECK_TIMEOUT) Res property description: Ma
    ximum execution time allowed for Monitor_Check method.
    (CAL-RED-RG:redmeadows:MONITOR_CHECK_TIMEOUT) Res property type: int
    (CAL-RED-RG:redmeadows:MONITOR_CHECK_TIMEOUT) Res property value: 300
    (CAL-RED-RG:redmeadows) Res property name: MONITOR_STOP_TIMEOUT
    (CAL-RED-RG:redmeadows:MONITOR_STOP_TIMEOUT) Res property class: standard
    (CAL-RED-RG:redmeadows:MONITOR_STOP_TIMEOUT) Res property description: Max
    imum execution time allowed for Monitor_Stop method.
    (CAL-RED-RG:redmeadows:MONITOR_STOP_TIMEOUT) Res property type: int
    (CAL-RED-RG:redmeadows:MONITOR_STOP_TIMEOUT) Res property value: 300
    (CAL-RED-RG:redmeadows) Res property name: MONITOR_START_TIMEOUT
    (CAL-RED-RG:redmeadows:MONITOR_START_TIMEOUT) Res property class: standard
    (CAL-RED-RG:redmeadows:MONITOR_START_TIMEOUT) Res property description: Ma
    ximum execution time allowed for Monitor_Start method.
    (CAL-RED-RG:redmeadows:MONITOR_START_TIMEOUT) Res property type: int
    (CAL-RED-RG:redmeadows:MONITOR_START_TIMEOUT) Res property value: 300
    (CAL-RED-RG:redmeadows) Res property name: UPDATE_TIMEOUT
    (CAL-RED-RG:redmeadows:UPDATE_TIMEOUT) Res property class: standard
    (CAL-RED-RG:redmeadows:UPDATE_TIMEOUT) Res property description: Maximum e
    xecution time allowed for Update method.
    (CAL-RED-RG:redmeadows:UPDATE_TIMEOUT) Res property type: int
    (CAL-RED-RG:redmeadows:UPDATE_TIMEOUT) Res property value: 300
    (CAL-RED-RG:redmeadows) Res property name: VALIDATE_TIMEOUT
    (CAL-RED-RG:redmeadows:VALIDATE_TIMEOUT) Res property class: standard
    (CAL-RED-RG:redmeadows:VALIDATE_TIMEOUT) Res property description: Maximum
    execution time allowed for Validate method.
    (CAL-RED-RG:redmeadows:VALIDATE_TIMEOUT) Res property type: int
    (CAL-RED-RG:redmeadows:VALIDATE_TIMEOUT) Res property value: 300
    (CAL-RED-RG:redmeadows) Res property name: STOP_TIMEOUT
    (CAL-RED-RG:redmeadows:STOP_TIMEOUT) Res property class: standard
    (CAL-RED-RG:redmeadows:STOP_TIMEOUT) Res property description: Maximum exe
    cution time allowed for Stop method.
    (CAL-RED-RG:redmeadows:STOP_TIMEOUT) Res property type: int
    (CAL-RED-RG:redmeadows:STOP_TIMEOUT) Res property value: 300
    (CAL-RED-RG:redmeadows) Res property name: START_TIMEOUT
    (CAL-RED-RG:redmeadows:START_TIMEOUT) Res property class: standard
    (CAL-RED-RG:redmeadows:START_TIMEOUT) Res property description: Maximum ex
    ecution time allowed for Start method.
    (CAL-RED-RG:redmeadows:START_TIMEOUT) Res property type: int
    (CAL-RED-RG:redmeadows:START_TIMEOUT) Res property value: 500
    (CAL-RED-RG:redmeadows) Res property name: CheckNameService
    (CAL-RED-RG:redmeadows:CheckNameService) Res property class: extension
    (CAL-RED-RG:redmeadows:CheckNameService) Res property description: Name se
    rvice check flag
    (CAL-RED-RG:redmeadows:CheckNameService) Res property pernode: False
    (CAL-RED-RG:redmeadows:CheckNameService) Res property type: boolean
    (CAL-RED-RG:redmeadows:CheckNameService) Res property value: TRUE
    (CAL-RED-RG:redmeadows) Res property name: NetIfList
    (CAL-RED-RG:redmeadows:NetIfList) Res property class: extension
    (CAL-RED-RG:redmeadows:NetIfList) Res property description: List of IPMP g
    roups on each node
    (CAL-RED-RG:redmeadows:NetIfList) Res property pernode: False
    (CAL-RED-RG:redmeadows:NetIfList) Res property type: stringarray
    (CAL-RED-RG:redmeadows:NetIfList) Res property value: sc_ipmp0@1 sc_ipmp0@
    2
    (CAL-RED-RG:redmeadows) Res property name: HostnameList
    (CAL-RED-RG:redmeadows:HostnameList) Res property class: extension
    (CAL-RED-RG:redmeadows:HostnameList) Res property description: List of hos
    tnames this resource manages
    (CAL-RED-RG:redmeadows:HostnameList) Res property pernode: False
    (CAL-RED-RG:redmeadows:HostnameList) Res property type: stringarray
    (CAL-RED-RG:redmeadows:HostnameList) Res property value: redmeadows
    (CAL-RED-RG) Res name: disk-red-rs
    (CAL-RED-RG:disk-red-rs) Res R_description: Failover data service resourc
    e for SUNW.HAStoragePlus:4
    (CAL-RED-RG:disk-red-rs) Res resource type: SUNW.HAStoragePlus:4
    (CAL-RED-RG:disk-red-rs) Res type version: 4
    (CAL-RED-RG:disk-red-rs) Res resource group name: CAL-RED-RG
    (CAL-RED-RG:disk-red-rs) Res resource project name: default
    (CAL-RED-RG:disk-red-rs{shaw}) Res enabled: True
    (CAL-RED-RG:disk-red-rs{telstra}) Res enabled: True
    (CAL-RED-RG:disk-red-rs{shaw}) Res monitor enabled: True
    (CAL-RED-RG:disk-red-rs{telstra}) Res monitor enabled: True
    (CAL-RED-RG:disk-red-rs) Res strong dependencies: <NULL>
    (CAL-RED-RG:disk-red-rs) Res weak dependencies: <NULL>
    (CAL-RED-RG:disk-red-rs) Res restart dependencies: <NULL>
    (CAL-RED-RG:disk-red-rs) Res offline restart dependencies: <NULL>
    (CAL-RED-RG:disk-red-rs) Res property name: Retry_interval
    (CAL-RED-RG:disk-red-rs:Retry_interval) Res property class: standard
    (CAL-RED-RG:disk-red-rs:Retry_interval) Res property description: Time in
    which monitor attempts to restart a failed resource Retry_count times.
    (CAL-RED-RG:disk-red-rs:Retry_interval) Res property type: int
    (CAL-RED-RG:disk-red-rs:Retry_interval) Res property value: 300
    (CAL-RED-RG:disk-red-rs) Res property name: Retry_count
    (CAL-RED-RG:disk-red-rs:Retry_count) Res property class: standard
    (CAL-RED-RG:disk-red-rs:Retry_count) Res property description: Indicates t
    he number of times a monitor restarts the resource if it fails.
    (CAL-RED-RG:disk-red-rs:Retry_count) Res property type: int
    (CAL-RED-RG:disk-red-rs:Retry_count) Res property value: 2
    (CAL-RED-RG:disk-red-rs) Res property name: Failover_mode
    (CAL-RED-RG:disk-red-rs:Failover_mode) Res property class: standard
    (CAL-RED-RG:disk-red-rs:Failover_mode) Res property description: Modifies
    recovery actions taken when the resource fails.
    (CAL-RED-RG:disk-red-rs:Failover_mode) Res property type: enum
    (CAL-RED-RG:disk-red-rs:Failover_mode) Res property value: SOFT
    (CAL-RED-RG:disk-red-rs) Res property name: POSTNET_STOP_TIMEOUT
    (CAL-RED-RG:disk-red-rs:POSTNET_STOP_TIMEOUT) Res property class: standard
    (CAL-RED-RG:disk-red-rs:POSTNET_STOP_TIMEOUT) Res property description: Ma
    ximum execution time allowed for Postnet_stop method.
    (CAL-RED-RG:disk-red-rs:POSTNET_STOP_TIMEOUT) Res property type: int
    (CAL-RED-RG:disk-red-rs:POSTNET_STOP_TIMEOUT) Res property value: 1800
    (CAL-RED-RG:disk-red-rs) Res property name: PRENET_START_TIMEOUT
    (CAL-RED-RG:disk-red-rs:PRENET_START_TIMEOUT) Res property class: standard
    (CAL-RED-RG:disk-red-rs:PRENET_START_TIMEOUT) Res property description: Ma
    ximum execution time allowed for Prenet_Start method.
    (CAL-RED-RG:disk-red-rs:PRENET_START_TIMEOUT) Res property type: int
    (CAL-RED-RG:disk-red-rs:PRENET_START_TIMEOUT) Res property value: 1800
    (CAL-RED-RG:disk-red-rs) Res property name: MONITOR_CHECK_TIMEOUT
    (CAL-RED-RG:disk-red-rs:MONITOR_CHECK_TIMEOUT) Res property class: standar
    d
    (CAL-RED-RG:disk-red-rs:MONITOR_CHECK_TIMEOUT) Res property description: M
    aximum execution time allowed for Monitor_Check method.
    (CAL-RED-RG:disk-red-rs:MONITOR_CHECK_TIMEOUT) Res property type: int
    (CAL-RED-RG:disk-red-rs:MONITOR_CHECK_TIMEOUT) Res property value: 90
    (CAL-RED-RG:disk-red-rs) Res property name: MONITOR_STOP_TIMEOUT
    (CAL-RED-RG:disk-red-rs:MONITOR_STOP_TIMEOUT) Res property class: standard
    (CAL-RED-RG:disk-red-rs:MONITOR_STOP_TIMEOUT) Res property description: Ma
    ximum execution time allowed for Monitor_Stop method.
    (CAL-RED-RG:disk-red-rs:MONITOR_STOP_TIMEOUT) Res property type: int
    (CAL-RED-RG:disk-red-rs:MONITOR_STOP_TIMEOUT) Res property value: 90
    (CAL-RED-RG:disk-red-rs) Res property name: MONITOR_START_TIMEOUT
    (CAL-RED-RG:disk-red-rs:MONITOR_START_TIMEOUT) Res property class: standar
    d
    (CAL-RED-RG:disk-red-rs:MONITOR_START_TIMEOUT) Res property description: M
    aximum execution time allowed for Monitor_Start method.
    (CAL-RED-RG:disk-red-rs:MONITOR_START_TIMEOUT) Res property type: int
    (CAL-RED-RG:disk-red-rs:MONITOR_START_TIMEOUT) Res property value: 90
    (CAL-RED-RG:disk-red-rs) Res property name: INIT_TIMEOUT
    (CAL-RED-RG:disk-red-rs:INIT_TIMEOUT) Res property class: standard
    (CAL-RED-RG:disk-red-rs:INIT_TIMEOUT) Res property description: Maximum ex
    ecution time allowed for Init method.
    (CAL-RED-RG:disk-red-rs:INIT_TIMEOUT) Res property type: int
    (CAL-RED-RG:disk-red-rs:INIT_TIMEOUT) Res property value: 1800
    (CAL-RED-RG:disk-red-rs) Res property name: UPDATE_TIMEOUT
    (CAL-RED-RG:disk-red-rs:UPDATE_TIMEOUT) Res property class: standard
    (CAL-RED-RG:disk-red-rs:UPDATE_TIMEOUT) Res property description: Maximum
    execution time allowed for Update method.
    (CAL-RED-RG:disk-red-rs:UPDATE_TIMEOUT) Res property type: int
    (CAL-RED-RG:disk-red-rs:UPDATE_TIMEOUT) Res property value: 1800
    (CAL-RED-RG:disk-red-rs) Res property name: VALIDATE_TIMEOUT
    (CAL-RED-RG:disk-red-rs:VALIDATE_TIMEOUT) Res property class: standard
    (CAL-RED-RG:disk-red-rs:VALIDATE_TIMEOUT) Res property description: Maximu
    m execution time allowed for Validate method.
    (CAL-RED-RG:disk-red-rs:VALIDATE_TIMEOUT) Res property type: int
    (CAL-RED-RG:disk-red-rs:VALIDATE_TIMEOUT) Res property value: 1800
    (CAL-RED-RG:disk-red-rs) Res property name: STOP_TIMEOUT
    (CAL-RED-RG:disk-red-rs:STOP_TIMEOUT) Res property class: standard
    (CAL-RED-RG:disk-red-rs:STOP_TIMEOUT) Res property description: Maximum ex
    ecution time allowed for Stop method.
    (CAL-RED-RG:disk-red-rs:STOP_TIMEOUT) Res property type: int
    (CAL-RED-RG:disk-red-rs:STOP_TIMEOUT) Res property value: 1800
    (CAL-RED-RG:disk-red-rs) Res property name: START_TIMEOUT
    (CAL-RED-RG:disk-red-rs:START_TIMEOUT) Res property class: standard
    (CAL-RED-RG:disk-red-rs:START_TIMEOUT) Res property description: Maximum e
    xecution time allowed for Start method.
    (CAL-RED-RG:disk-red-rs:START_TIMEOUT) Res property type: int
    (CAL-RED-RG:disk-red-rs:START_TIMEOUT) Res property value: 90
    (CAL-RED-RG:disk-red-rs) Res property name: Zpools
    (CAL-RED-RG:disk-red-rs:Zpools) Res property class: extension
    (CAL-RED-RG:disk-red-rs:Zpools) Res property description: The list of zpoo
    ls
    (CAL-RED-RG:disk-red-rs:Zpools) Res property pernode: False
    (CAL-RED-RG:disk-red-rs:Zpools) Res property type: stringarray
    (CAL-RED-RG:disk-red-rs:Zpools) Res property value: <NULL>
    (CAL-RED-RG:disk-red-rs) Res property name: FilesystemCheckCommand
    (CAL-RED-RG:disk-red-rs:FilesystemCheckCommand) Res property class: extens
    ion
    (CAL-RED-RG:disk-red-rs:FilesystemCheckCommand) Res property description:
    Command string to be executed for file system checks
    (CAL-RED-RG:disk-red-rs:FilesystemCheckCommand) Res property pernode: False
    (CAL-RED-RG:disk-red-rs:FilesystemCheckCommand) Res property type: stringa
    rray
    (CAL-RED-RG:disk-red-rs:FilesystemCheckCommand) Res property value: <NULL>
    (CAL-RED-RG:disk-red-rs) Res property name: AffinityOn
    (CAL-RED-RG:disk-red-rs:AffinityOn) Res property class: extension
    (CAL-RED-RG:disk-red-rs:AffinityOn) Res property description: For specifyi
    ng affinity switchover
    (CAL-RED-RG:disk-red-rs:AffinityOn) Res property pernode: False
    (CAL-RED-RG:disk-red-rs:AffinityOn) Res property type: boolean
    (CAL-RED-RG:disk-red-rs:AffinityOn) Res property value: TRUE
    (CAL-RED-RG:disk-red-rs) Res property name: GlobalDevicePaths
    (CAL-RED-RG:disk-red-rs:GlobalDevicePaths) Res property class: extension
    (CAL-RED-RG:disk-red-rs:GlobalDevicePaths) Res property description: The l
    ist of HA global device paths
    (CAL-RED-RG:disk-red-rs:GlobalDevicePaths) Res property pernode: False
    (CAL-RED-RG:disk-red-rs:GlobalDevicePaths) Res property type: stringarray
    (CAL-RED-RG:disk-red-rs:GlobalDevicePaths) Res property value: <NULL>
    (CAL-RED-RG:disk-red-rs) Res property name: FilesystemMountPoints
    (CAL-RED-RG:disk-red-rs:FilesystemMountPoints) Res property class: extensi
    on
    (CAL-RED-RG:disk-red-rs:FilesystemMountPoints) Res property description: T
    he list of file system mountpoints
    (CAL-RED-RG:disk-red-rs:FilesystemMountPoints) Res property pernode: False
    (CAL-RED-RG:disk-red-rs:FilesystemMountPoints) Res property type: stringar
    ray
    (CAL-RED-RG:disk-red-rs:FilesystemMountPoints) Res property value: /opt/sh
    aw /cal/shaw

  • SC 3.2 - logical hostname create rpoblem

    Hello
    I am running with Sun Cluster 3.2 in two node cluster with IPMP. And we are using IBM Storage and metaset (Solaris Volume Manager) in the cluster.
    While trying to create Sun Cluster resource logical hostname, I get this error. I was able to successfully create the data resource but the logical hostname resource is giving this error.
    Command executed: /usr/cluster/bin/clreslogicalhostname create -g test-rg -p Resource_project_name=default -p R_description=Failover\ network\ resource\ for\ SUNW.LogicalHostname:3 -N group1@1:node1,group1@2:node22 -h test-rs test-rs
    Error message:
    clreslogicalhostname: <test-rs> cannot be mapped to an IP address
    Please advise.

    Hi,
    The value you specified with -h option is the logical hostname that should be mapped to an IP address and is not
    the resource name. The address mapping is possible if you have an entry for this hostname either in the /etc/hosts file or an entry in the name service
    that you are using. Make sure that you have an entry in the /etc/hosts file for "test-rs" and retry the create operation.
    BTW, You need not specify the -h option if your hostname
    is same as the resource name, and resource name is resolvable.
    From man page of clrslh command:
    -h lhost[,…]
    --logicalhost lhost[,…]
    Specifies the list of logical hostnames that this resource represents. You must use the -h option either when more than one logical hostname is to be associated with the new logical hostname resource or when the logical hostname does not have the same name as the resource itself. All logical hostnames in the list must be on the same subnet. If you do not specify the -h option, the resource represents a single logical hostname whose name is the name of the resource itself.
    You can use -h instead of setting the HostnameList property with -p. However, you cannot use -h and explicitly set HostnameList in the same command.
    Thanks,
    Prasanna Kunisetty

  • Logical Hostname

    Hi All ,
    Below is my requirement
    1)  Two - Node Cluster
    2)  To Create Failover NFS resource group
    I want to create a logica hostname resource, what is procedure and requirements for configuring the logical hostname.  
    I am very much confused in creating a logical hostname resource.
    Please help to create a logical hostname.
    Regards,
    R. Rajesh Kannan.

    Have you looked att he example in http://docs.sun.com/app/docs/doc/819-2979/z4000275997776?a=view
    I would have thought that was fairly clear. If not, which specific bit do you need explaining?
    Thanks,
    Tim
    ---

  • Difference betwn shared address and logical hostname

    Hello,
    For cluster 3.2, could someone explain the diff betwn "clreslogicalhostname create" and "clressharedaddress create"? I thought the former was to share a logical hostname (depending on DNS to resolve to the ip address) betwn nodes, and the latter to share ip address (don't need to rely ip address resolution). But examples of the latter use a hostname and not an ip address, which leads to my confusion.
    Thank you for clarifying this!

    You've got things a little bit confused.
    A logical hostname resource is an IP address (and associated hostname) that is placed in a fail-over resource group and used by the application(s) in that resource group. Such a resource group is resident on one node only and thus the IP address only exists, i.e. is plumbed in, on that cluster node too.
    An example of such a service would be, say, an NFS service, with the IP address being the one you mount shares from. Alternatively, it could be an HA-Oracle database with the IP address being that of the listener that clients connect to.
    A shared address resource is an IP address (and associated hostname) that is placed in a fail-over resource group but is used by applications in a scalable resource group. The shared address IP/hostname becomes a global IP address, such that it is physically plumbed in, e.g. on bge0:1, on the cluster node where the fail-over resource group is mastered and also plumbed in on the loopback interface, e.g. lo:2, of the cluster nodes that run the scalable services that depend on it.
    An example of such a service would be a scalable web server, e.g. Apache or Sun Java Web Server, that is run on multiple cluster nodes at once and has requests load-balanced to them directly by the cluster. The scalable IP address would provide a single address that clients could use, yet the requests can be serviced by one of several nodes.
    Hope that helps,
    Tim
    ---

  • Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING

    hello colleagues,
    In the phase Connect Diagnostics dont show the Agent available in SLD, but when go to SLD i have the agents,
    Error,
    Connect Diagnostics Agent
    The table does not contain any data
    Agent availables in all SLD
    SOAP:1.007 SRT: Unupported xstream found: ("HTTP Code 401 : Unauthorized")
    Web service invocation problem on host hostname and port 8000 protocol : http logical port name : LP_WS_SMDAGENT_MONITORING
    Thanks

    OK, then pls follow below steps;
    - Go to step 'Create Users' in solman_setup System Preparation scenario and make sure the user SM_INTERN_WS has a green status. Use the 'Test Login' button to make sure the user is not locked and has correct credentials maintained in solman_setup
    - Immediately after checking the user status, navigate to Configure Connectivity->Enable Web Services and execute again the 'Create Logical Ports' automatic activity, in order to propagate the correct credentials to the Logical Port definitions.
    - If the above operation is not successful, repeat the two steps above, providing a different user Id in 'Create Users' step, eg SM_INTERN_W1. This will prevent situations where the user gets locked by Logical Ports using an obsolete password.
    Let me know the results.
    Regards,
    Vivek

  • Sun Cluster 3.1 Failover Resource without Logical Hostname

    Maybe it could sound strange, but I'd need to create a failover service without any network resource in use (or at least with a dependency on a logical hostname created in a different resource-group).
    Does anybody know how to do that?

    Well, you don't really NEED a LogicalHostname in a RG. So, i guess i am not understanding
    the question.
    Is there an application agent which demands to have a network resource in the RG? Sometimes
    the VALIDATE method of such agents refuses to work if there is no network resource in
    the RG.
    If so, tell us a bit more about the application. Is this GDS based and generated by
    Sun Cluster Agent Builder? The Agent Builder has a option of "non Network Aware", if you
    select that while building you app, it ought to work without a network resource in the RG.
    But maybe i should back up and ask the more basic question of exactly what is REQUIRING
    you to create a LogicalHostname?
    HTH,
    -ashu

  • Logical Hostname fail to create

    Hi,
    I have installed Sun Cluster 3.2 on Solaris 10 10/08 with Kernel patch 138888-01
    The cluster is a test cluster running on one node.
    I have create 2 Local Zones with Exclusive IP
    1. clrg create -n HOST:zone1,HOST:zone2 test-rg
    2. I have add test-ip in /etc/hosts on the 2 zones
    3. when I am trying to run the clrslh command to create the logical hostname I get the following errors
    ( I am using the GUI for the creation of the logical hostname)
    clrslh (C189917) VALIDATE on resource OP-rs resource group test-rg exited with non-zero exit status
    clrslh (C720144) validation on resource IP-rs in resource group test-rg on node HOST;ZONE failed
    clrslh (C891200) Failed to create resource IP-rs
    Can any one help to resolve this problem?
    Thanks
    Yacov

    Hi
    I have some information regarding this problem.
    The /var/adm/messages* content regarding the problem
    May 28 09:26:23 za-dr-it-sp1 Cluster.RGM.global.rgmd: [ID 224900 daemon.notice] launching method <hafoip_validate> for resource <test-ip>, resource group <test-rg>, node <za-dr-it-sp1:uat-mozambique2>, timeout <300> seconds
    May 28 09:26:23 za-dr-it-sp1 Cluster.RGM.global.rgmd: [ID 896918 daemon.notice] 10 fe_rpc_command: cmd_type(enum):<1>:cmd=</usr/cluster/lib/rgm/rt/hafoip/hafoip_validate>:tag=<uat-mozambique2.test-rg.test-ip.2>: Calling security_clnt_connect(..., host=<za-dr-it-sp1>, sec_type {0:WEAK, 1:STRONG, 2:DES} =<1>, ...)
    May 28 09:26:24 za-dr-it-sp1 Cluster.RGM.global.rgmd: [ID 699104 daemon.error] VALIDATE failed on resource <test-ip>, resource group <test-rg>, time used: 0% of timeout <300, seconds>
    When creating the logical hostname*
    Command executed: /usr/cluster/bin/clreslogicalhostname create -g test-rg -p Resource_project_name= -p Failover_mode=NONE -p R_description=Failover\ network\ resource\ for\ SUNW.LogicalHostname:3 -h test-ip test-ip
    Error message:
    clreslogicalhostname: (C189917) VALIDATE on resource test-ip, resource group test-rg, exited with non-zero exit status.
    clreslogicalhostname: (C720144) Validation of resource test-ip in resource group test-rg on node za-dr-it-sp1:uat-mozambique2 failed.
    clreslogicalhostname: (C891200) Failed to create resource "test-ip".

  • How many iMacs can i register Logic Pro on?

    How many iMacs can i register Logic Pro on?
    We use Logic Pro at our work.  We are using using 6 macs at the moment, i would like to have logic on all 6

    Hi
    Technically this is NOT the 'legal' case:
    https://discussions.apple.com/message/18228781#18228781
    CCTM wrote:
    Hi
    According to the details in this:
    http://www.apple.com/legal/itunes/uk/terms.html#SALE
    You could well be out of luck....
    MAC APP STORE PRODUCT USAGE RULES
    Except as otherwise set forth herein,
    If you are an individual acting in your personal capacity, you may download and use an application from the Mac App Store (“Mac App Store Product”) for personal, non-commercial use on any Apple-branded products running Mac OS X (“Mac Computer”) that you own or control.
    (ii) If you are a commercial enterprise or educational institution, you may download a Mac App Store Product for use by either (a) a single individual on each of the Mac Computer(s) used by that individual that you own or control, or (b) multiple individuals on a single shared Mac Computer that you own or control. For example, a single employee may use a Mac App Store Product on both the employee’s desktop Mac Computer and laptop Mac Computer, or multiple students may serially use the Mac App Store Product on a single Mac Computer located at a resource centre or library. For the sake of clarity, each Mac Computer used serially by multiple users requires a separate licence.
    (iii) Use of Mac App Store Products may require sign-in with the Apple ID used to download the Mac App Store Product from the Mac App Store. Mac App Store Products can be updated through the Mac App Store only."
    HTH???
    CCT

  • Problem starting logical host on eGate 5.1.0

    I'm having problem starting logical host for eGate 5.1.0 on Linux platform, and I cant see where is the problem lies. Is there anybody here that can give me some hint or guide?
    Below is the error message from the log.
    [#|2006-08-22T17:57:28.506+0800|WARNING|IS5.1|javax.enterprise.resource.jms|_ThreadID=11; ThreadName=STCMS process monitoring;|STCMS process ended unexpectedly with exit code 1; initiating application server restart|#]
    [#|2006-08-22T17:57:28.567+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=11; ThreadName=STCMS process monitoring;|sending restart notification to server...server|#]
    [#|2006-08-22T17:57:28.721+0800|WARNING|IS5.1|javax.enterprise.system.tools.admin|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|core.tmp_folder_deletion_failed|#]
    [#|2006-08-22T17:57:28.722+0800|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|stcms.alert_shutting_down|#]
    [#|2006-08-22T17:57:28.722+0800|INFO|IS5.1|javax.enterprise.resource.jms|_ThreadID=12; ThreadName=RMI TCP Connection(1)-127.0.0.1;|stcms.broker_shutting_down|#]
    [#|2006-08-22T17:57:31.020+0800|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Creating virtual server server|#]
    [#|2006-08-22T17:57:31.039+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|IS AVK Instrumentation disabled|#]
    [#|2006-08-22T17:57:31.045+0800|INFO|IS5.1|javax.enterprise.system.core.security|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
    [#|2006-08-22T17:57:31.117+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC JTS Extension] The last agent commit optimization is enabled.|#]
    [#|2006-08-22T17:57:32.315+0800|INFO|IS5.1|com.stc.corba.any.UtilDelegate|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC CORBA Extension]EE/SE Corba Util delegate loaded|#]
    [#|2006-08-22T17:57:33.730+0800|INFO|IS5.1|com.stc.corba.any.UtilDelegate|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|[STC CORBA Extension]Enabling SE Corba support|#]
    [#|2006-08-22T17:57:34.007+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5082: Exception running j2ee services: [java.lang.RuntimeException: java.lang.ExceptionInInitializerError]|#]
    [#|2006-08-22T17:57:34.008+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=0;|CORE5091: Error executing J2EE server ...
    java.lang.RuntimeException: java.lang.ExceptionInInitializerError
         at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
         at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
         at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
         at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:374)
         at com.sun.enterprise.iiop.ORBMonitoring.<init>(ORBMonitoring.java:48)
         at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:236)
         ... 9 more
    Caused by: java.lang.ExceptionInInitializerError
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:164)
         at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:368)
         ... 11 more
    Caused by: java.lang.NullPointerException: No MBeanServer was returned by the MBeanServerFactory
         at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.getMBeanServer(MonitoringRegistrationHelper.java:83)
         at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<init>(MonitoringRegistrationHelper.java:60)
         at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<clinit>(MonitoringRegistrationHelper.java:55)
         ... 14 more
    |#]
    [#|2006-08-22T17:57:34.012+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5092: J2EE server reported following error: [java.lang.ExceptionInInitializerError] |#]
    [#|2006-08-22T17:57:34.012+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|CORE5093: Error executing J2EE server |#]
    [#|2006-08-22T17:57:34.013+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=1;|CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: com.sun.appserv.server.ServerLifecycleException: java.lang.ExceptionInInitializerError
         at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:235)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:222)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: com.sun.appserv.server.ServerLifecycleException: java.lang.ExceptionInInitializerError
         at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:763)
         at com.sun.enterprise.server.ApplicationServer.onInitialization(ApplicationServer.java:233)
         ... 7 more
    Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
         at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:351)
         at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:754)
         ... 8 more
    Caused by: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
         at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:374)
         at com.sun.enterprise.iiop.ORBMonitoring.<init>(ORBMonitoring.java:48)
         at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:236)
         ... 9 more
    Caused by: java.lang.ExceptionInInitializerError
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:164)
         at com.sun.enterprise.server.ServerContextImpl.getMonitoringRegistry(ServerContextImpl.java:368)
         ... 11 more
    Caused by: java.lang.NullPointerException: No MBeanServer was returned by the MBeanServerFactory
         at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.getMBeanServer(MonitoringRegistrationHelper.java:83)
         at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<init>(MonitoringRegistrationHelper.java:60)
         at com.sun.enterprise.admin.monitor.registry.spi.MonitoringRegistrationHelper.<clinit>(MonitoringRegistrationHelper.java:55)
         ... 14 more
    |#]
    [#|2006-08-22T17:57:34.023+0800|SEVERE|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server Startup failed. Exiting...|#]
    [#|2006-08-22T17:57:34.023+0800|INFO|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|Server shutdown in progress...|#]
    [#|2006-08-22T17:57:34.024+0800|INFO|IS5.1|javax.enterprise.system.container.web|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;|WEB0303: Stopping Tomcat.|#]
    [#|2006-08-22T17:57:34.025+0800|WARNING|IS5.1|javax.enterprise.system.core|_ThreadID=10; ThreadName=org.apache.commons.launcher.ChildMain;stacktrace-id=2;|CORE5061: Exception :
    com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
         at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:536)
         at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:65)
         at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:255)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:186)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: LifecycleException: WEB0103: This web container has not yet been started
         at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:529)
         at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:528)
         ... 9 more
    |#]
    Hopefully somebody can help me as I'm stuck with it for few days already. Thank you.

    This is what I got when I try to start the server from the directory logicalhost/is/domains/domain1/bin/
    ./startservAug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger <init>
    INFO: Setting URL to http://localhost:18000
    Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
    INFO: Opening connection to http://localhost:18000
    Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
    INFO: Connection to http://localhost:18000 opened successfully.
    Aug 23, 2006 7:23:55 PM com.stc.is.util.pinger.HttpOKPinger isAlive
    SEVERE: Connection refused
    java.net.ConnectException: Connection refused
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    at java.net.Socket.connect(Socket.java:507)
    at java.net.Socket.connect(Socket.java:457)
    at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
    at sun.net.www.http.HttpClient.<init>(HttpClient.java:214)
    at sun.net.www.http.HttpClient.New(HttpClient.java:287)
    at sun.net.www.http.HttpClient.New(HttpClient.java:299)
    at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:792)
    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:744)
    at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:669)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:913)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
    at com.stc.is.util.pinger.HttpOKPinger.isAlive(Unknown Source)
    at com.stc.is.util.Ping.main(Unknown Source)
    Aug 23, 2006 7:23:55 PM com.stc.is.util.Ping main
    INFO: IS is not alive.
    Startup failed.
    any clue what is it about?

  • How to add network information for failover zones with logical hostname?

    Hello!
    As stated in [http://docs.sun.com/app/docs/doc/819-3069/ds_template-21?a=view] I must not configure network addresses for a zone when I manage these with a logical hostname:
    If you require the SUNW.LogicalHostName resource type to manage all the zone's addresses, configure a SUNW.LogicalHostName resource with a list of the zone`s addresses and do not configure them by using the zonecfg utility.But when I start the zone for the first time using "zlogin -C" it does not ask me any questions about the network. Of course, there is no adapter configured. But how do I add information like routes or nameservers to the system when using a logical hostname?
    TIA
    Stephan

    Hi Stephan,
    I can only assume that when the zone was configured via zonecfg without any network interfaces that sysidcfg did not ask you for the default route or name service, as such you will need to setup those parts up manually.
    Please take a look at the FAQs for zones, i.e. http://opensolaris.org/os/community/zones/faq/ in particular
    http://opensolaris.org/os/community/zones/faq/#u5
    http://opensolaris.org/os/community/zones/faq/#cfg_defroute
    Finally, if you require a NIS client then please see http://docs.sun.com/app/docs/doc/816-5166/ypinit-1m?a=view
    Regards
    Neil

Maybe you are looking for