Configuring rcd to contact you Zenworks Linux Management server

I am new to Zenworks and am installing version 6.6. Under installing the
client on a single machine in step 6 it says to run the following command
rug service-add https://youZLMserver/data
If I use the above server I get the following message
ERROR: Unable to mount service for 'https://yourZLMserver/data': Unable to
download service info: IO error - Soup error: Cannot resolve hostname (2)
When I run this command i get the following message subsituting my server
address
ERROR: Unable to mount service for 'https://136.174.209.92/data': Unable to
down
Nowhere do I find a directory called /data or remember one being created.
Any help in getting past this point would be greatly apprecieated.
Kevin

I better try things before asking :) The problem is that the ssl cert ain't
trusted. you can turn it of with. Or trust the cert
rug set require-verified-certificates false
Johan Blom wrote:
> I have the same problem
>
> Anyone solved this?
>
>
> [email protected] wrote:
>
>
>
>> I am new to Zenworks and am installing version 6.6. Under installing the
>> client on a single machine in step 6 it says to run the following command
>>
>> rug service-add https://youZLMserver/data
>>
>> If I use the above server I get the following message
>>
>> ERROR: Unable to mount service for 'https://yourZLMserver/data': Unable
>> to download service info: IO error - Soup error: Cannot resolve hostname
>> (2)
>>
>> When I run this command i get the following message subsituting my server
>> address
>>
>> ERROR: Unable to mount service for 'https://136.174.209.92/data': Unable
>> to down
>>
>> Nowhere do I find a directory called /data or remember one being created.
>> Any help in getting past this point would be greatly apprecieated.
>>
>> Kevin

Similar Messages

  • Zenworks Linux Management Device Registration Issue

    All,
    Below is a detailed description of a resistration issue using Zenworks
    Linux Management 7.
    Hardware Configuration:
    1- DSL Modem (Westell Model 2200)
    1- DI 614+ 2.4 GHz Broadband Wireless Router (includes 4-5 ethernet
    ports) with a IP address of 192.168.0.1
    1- PC Server running Redhat SUSE Linux Enterprise Server 9 (has a static
    IP address of 192.168.0.103). This machine is running the Zenworks 7
    Linux Management Software and is able to sucessfully launch the Zenworks
    7 Control Panel.
    1- Redhat Linux Enterprise Server 3 on a completely different network
    with a static IP address (207.44.142.56). This machine is running the
    Zenworks Linux Management Agent install using the ./zlm-install -a
    command.
    Network Configuration:
    The broadband DSL modem is connected directly to the WAN ethernet port on
    the wireless router
    The primary PC server running Redhat SUSE Linux Enterprise Server 9 has a
    direct connection to one of the ethernet ports on the wireless broadboard
    router with a private static IP address of 192.168.0.103 and has a public
    IP of 70.22.107.168.
    The DSL modem is has a direct connection to the telephone line.
    The Redhat Linux Enterprise Server 3 is on a completely different network
    with a IP of 207.44.142.56.
    No firewalls are configured on the primary server and the wireless router
    Port Forwarders are configured on the broadband wireless router as
    follows:
    zlm1
    192.168.0.103
    TCP 80/80
    always
    zlm2
    192.168.0.103
    TCP 443/443
    always
    zlm3
    192.168.0.103
    TCP 524/524
    always
    zlm4
    192.168.0.103
    TCP 1299/1299
    always
    zlm5
    192.168.0.103
    TCP 2544/2544
    always
    zlm6
    192.168.0.103
    TCP 5506/5506
    always
    zlm7
    192.168.0.103
    TCP 10389/10389
    always
    zlm8
    192.168.0.103
    TCP 10636/10636
    always
    Goal:
    To successfully register the Redhat Linux Enterprise 3 server (i.e. the
    managed device with IP 207.44.142.56) with the primary server
    (192.168.0.103 SUSE Redhat Enterprise Server 9 machine) so it can be
    viewed and managed from the Zenworks 7 Control panel.
    Nature of Problem:
    When attempting to register the managed device (207.44.142.56) with the
    primary server (192.168.0.103) which resides inside of my Wireless Local
    Area Network (WLAN) via the following command, it appears to fail. I'm
    unable to view or configure this managed device inside of the Zenworks 7
    Linux Management Control Panel. The following are 2 manual approaches
    that I take to register the managed device and the results for each.
    Register using private IP approach:
    /opt/novell/zenworks/bin/rug sa https://192.168.0.103
    Results: ERROR: Could not add 'https://192.168.0.103': Download failed:
    (https://192.168.0.103/zenworks-registration/service.xml) Error:
    ConnectFailure
    Register using public IP approach:
    /opt/novell/zenworks/bin/rug sa https://70.22.107.168
    Results: ERROR: Could not add 'https://70.22.107.168': Download failed:
    (https://70.22.107.168/zenworks-registration/service.xml) Error:
    ConnectFailure
    Regards,
    Darrick Addison
    Sr. Software Engineer/Consultant
    ASC Technologies, LLC
    Ph: 443.257.9116
    Fax: 410.360.5570
    E-mail: [email protected]
    Web: www.asctllc.com

    On Tue, 08 Nov 2005 02:40:58 GMT, [email protected] wrote:
    > Below is a detailed description of a resistration issue using Zenworks
    > Linux Management 7.
    duplicate question - can I gently mention a point? Whilst we naturally
    understand that you may need information/help in a hurry, asking the
    same question in multiple forums dilutes the answers you get, and makes
    more work for those of us who have to read them; it would help if you
    could avoid this in future.
    Many thanks
    (c) Shaun Pond, stolen without permission ;-)
    Marcus Breiden
    Please change -- to - to mail me.
    The content of this mail is my private and personal opinion.
    http://www.edu-magic.net

  • Zenworks Linux Management 7

    I have installed the ZLM 7 Client on a NLD 9 computer. Since then I have
    not been able to run the Red Carpet Update Manager nor have I been able
    to run RPMS by clicking on them and it running in Red Carpet. I get a
    Zenworks 7 Linux Management Update Manager login with Connect to this
    system selected I click Connect. Once I do this the login window locks
    and I am unable to get to the Management Window. Please Help! My ZLM 7
    server is running on SUSE Enterprise server 9.

    you'll get quicker answers I think if you ask this in the 7x forum
    instead of 6x...
    Shaun Pond

  • Zenworks 7 Linux Management Device Registration Issue

    All,
    Below is a detailed description of a resistration issue using Zenworks
    Linux Management 7.
    Hardware Configuration:
    1- DSL Modem (Westell Model 2200)
    1- DI 614+ 2.4 GHz Broadband Wireless Router (includes 4-5 ethernet
    ports) with a IP address of 192.168.0.1
    1- PC Server running Redhat SUSE Linux Enterprise Server 9 (has a static
    IP address of 192.168.0.103). This machine is running the Zenworks 7
    Linux Management Software and is able to sucessfully launch the Zenworks
    7 Control Panel.
    1- Redhat Linux Enterprise Server 3 on a completely different network
    with a static IP address (207.44.142.56). This machine is running the
    Zenworks Linux Management Agent install using the ./zlm-install -a
    command.
    Network Configuration:
    The broadband DSL modem is connected directly to the WAN ethernet port on
    the wireless router
    The primary PC server running Redhat SUSE Linux Enterprise Server 9 has a
    direct connection to one of the ethernet ports on the wireless broadboard
    router with a private static IP address of 192.168.0.103 and has a public
    IP of 70.22.107.168.
    The DSL modem is has a direct connection to the telephone line.
    The Redhat Linux Enterprise Server 3 is on a completely different network
    with a IP of 207.44.142.56.
    No firewalls are configured on the primary server and the wireless router
    Port Forwarders are configured on the broadband wireless router as
    follows:
    zlm1
    192.168.0.103
    TCP 80/80
    always
    zlm2
    192.168.0.103
    TCP 443/443
    always
    zlm3
    192.168.0.103
    TCP 524/524
    always
    zlm4
    192.168.0.103
    TCP 1299/1299
    always
    zlm5
    192.168.0.103
    TCP 2544/2544
    always
    zlm6
    192.168.0.103
    TCP 5506/5506
    always
    zlm7
    192.168.0.103
    TCP 10389/10389
    always
    zlm8
    192.168.0.103
    TCP 10636/10636
    always
    Goal:
    To successfully register the Redhat Linux Enterprise 3 server (i.e. the
    managed device with IP 207.44.142.56) with the primary server
    (192.168.0.103 SUSE Redhat Enterprise Server 9 machine) so it can be
    viewed and managed from the Zenworks 7 Control panel.
    Nature of Problem:
    When attempting to register the managed device (207.44.142.56) with the
    primary server (192.168.0.103) which resides inside of my Wireless Local
    Area Network (WLAN) via the following command, it appears to fail. I'm
    unable to view or configure this managed device inside of the Zenworks 7
    Linux Management Control Panel. The following are 2 manual approaches
    that I take to register the managed device and the results for each.
    Register using private IP approach:
    /opt/novell/zenworks/bin/rug sa https://192.168.0.103
    Results: ERROR: Could not add 'https://192.168.0.103': Download failed:
    (https://192.168.0.103/zenworks-registration/service.xml) Error:
    ConnectFailure
    Register using public IP approach:
    /opt/novell/zenworks/bin/rug sa https://70.22.107.168
    Results: ERROR: Could not add 'https://70.22.107.168': Download failed:
    (https://70.22.107.168/zenworks-registration/service.xml) Error:
    ConnectFailure
    Regards,
    Darrick Addison
    Sr. Software Engineer/Consultant
    ASC Technologies, LLC
    Ph: 443.257.9116
    Fax: 410.360.5570
    E-mail: [email protected]
    Web: www.asctllc.com

    On Tue, 08 Nov 2005 02:37:16 GMT, [email protected] wrote:
    > Below is a detailed description of a resistration issue using Zenworks
    > Linux Management 7.
    duplicate question - can I gently mention a point? Whilst we naturally
    understand that you may need information/help in a hurry, asking the
    same question in multiple forums dilutes the answers you get, and makes
    more work for those of us who have to read them; it would help if you
    could avoid this in future.
    Many thanks
    (c) Shaun Pond, stolen without permission ;-)
    Marcus Breiden
    Please change -- to - to mail me.
    The content of this mail is my private and personal opinion.
    http://www.edu-magic.net

  • Re: Zenworks 7 Linux Management Device Registration Issue

    On Tue, 08 Nov 2005 02:35:13 GMT, [email protected] wrote:
    > All,
    >
    > Below is a detailed description of a resistration issue using Zenworks
    > Linux Management 7.
    duplicate question - can I gently mention a point? Whilst we naturally
    understand that you may need information/help in a hurry, asking the
    same question in multiple forums dilutes the answers you get, and makes
    more work for those of us who have to read them; it would help if you
    could avoid this in future.
    Many thanks
    (c) Shaun Pond, stolen without permission ;-)
    Marcus Breiden
    Please change -- to - to mail me.
    The content of this mail is my private and personal opinion.
    http://www.edu-magic.net

    On Tue, 08 Nov 2005 02:39:10 GMT, [email protected] wrote:
    > Below is a detailed description of a resistration issue using Zenworks
    > Linux Management 7
    duplicate question - can I gently mention a point? Whilst we naturally
    understand that you may need information/help in a hurry, asking the
    same question in multiple forums dilutes the answers you get, and makes
    more work for those of us who have to read them; it would help if you
    could avoid this in future.
    Many thanks
    (c) Shaun Pond, stolen without permission ;-)
    Marcus Breiden
    Please change -- to - to mail me.
    The content of this mail is my private and personal opinion.
    http://www.edu-magic.net

  • Configuring Listen Address for a machine / node manager

    Hi,
    If I give the localhost as value for the Listen Address for the machine (and this the Node Manager), I can start/stop any managed server belonging to the domain
    and related machine.
    When I change this address to the value of the IP address I get from "ping hostname" (that is to be found in /etc/hosts), or the corresponding host name found in /etc/hosts,
    I get the following Warning from the Console:
    - For server <managed server>, the Node Manager associated with machine MyMachine02 is not reachable.
    - All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
    Can someone explain me how can a machine and the node manager be configured with another value than localhost for the Listen Address?
    Is there maybe a configuration that must be done at physical server level?
    Having this functionality will be a necessity for a cluster.
    Thanks by advance for sharing your experience.

    Actually the cert is coming from your Dev machine but it is sending the Prod cert.
    What cert is used by your admin server ? It should match the host name.
    So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
    The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
    In your nodemanager.properties, are you explicitly accessing keystores, such as with:
    KeyStores=CustomIdentityAndJavaStandardTrust
    CustomIdentityAlias=some_alias
    CustomIdentityKeyStoreFileName=some_path_to_keystore
    CustomIdentityKeyStorePassPhrase={3DES}...
    CustomIdentityKeyStoreType=jks
    CustomIdentityPrivateKeyPassPhrase={3DES}
    In my multi-machine clusters, I have multiple certificates such as:
    admin machine1:
    has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
    has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
    all other machines:
    has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
    has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

  • Zenworks mobile management activesync with datasynchronizer

    Can I point zenworks mobile management server at the datasynchronizer as an activesync for auto enrolment?

    Georg,
    Option A seems to work reliably today with Exchange 2007 so as long as the DataSync team properly implements the settings request for email address provided in the ActiveSync 12.1 protocol then it should work reliably. As for B today if the device doesn't support 12.1 or the server doesn't support 12.1 as is the case right now the only approach we currently have is to strip off the domain from the email address and attempt authentication as the user specified in the email. We are working to see if there is some other approach we can take once we provide additional LDAP enhancements in the next version of the product. But for now the two options you identified in our long term solution are the knowns. I'll forward this thread on to both the DataSync team and the ZMM development team and see if we can all come up with some better ideas.
    Thanks,
    Jason
    >>> Georg Fritsch<[email protected]> 8/9/2012 1:24 PM >>>
    Hi Jason,
    Thanx again for the detailed and competent anwser.
    All this restrictions unfortunately mean that hands-off enrollment is going
    to fail for many setups. (including us)
    A requirement that the local-part of an email address has to match the
    username is ridiculous. (Yes, we all know that Exchange 2003 and ActiveSync
    2.5 are ****...)
    I am not sure if understand the long term solution:
    A) If a user gives just a username, the device must get the corresponding
    email address from the ActiveSync system. Available with protocol version
    12.1. Fine. (As long as the device uses protocol version 12.1)
    B) A user gives an email-address, the username must be derived from the
    local-part. Where/How?, local-part == username is an invalid assumptionand
    the device does the parsing and just returns the local-part as username to
    the ActiveSync system. (And this information is IMO not enough to find the
    real username)
    Or is B) not allowed (or a really bad idea/design decision) as A) does
    reliably work?
    Georg
    >>> Jason Blackett<[email protected]> schrieb am 09.08.2012 um 05:35 in
    Nachricht <[email protected]>:
    > The problem with 1.2.3 is that when you authenticate to the domain with
    > the following credentials:
    >
    > user : bob
    > domain : m.comp.com
    > server : zmm.comp.com
    >
    > That the ZMM product currently relies on the activesync provider to tell
    > it Bob's email address. If it doesn't receive one then the iOS active
    > sync account it creates ends up with an email address of
    > m.comp.com\[email protected] which seems to work fine for getting
    > email/calendar but not for sending email. This only occurs if you do
    > hands-off enrollment because as TASNovell points out the email address
    > attribute doesn't get populated in the user, but is a required field when
    > creating a user.
    >
    > The ActiveSync way to fix this is that ActiveSync has to allow the user
    > to authenticate with their email address [email protected] for instance. And
    > then when it parses that it sends back the username as bob and uses the
    > full email address. This is the same capability provided by Microsoft
    > Exchange 2003 which implements the same version of ActiveSync as DataSync
    > currently. There definitely will be issues if the username portion of the
    > email address is not the ActiveSync user account name. In that case hands
    > off enrollment will fail and you will have to manually create the account
    > or import it from the directory and set the email address attribute.
    >
    > The long term solution is that DataSync will move to the 12.1 version of
    > the ActiveSync protocol which provides a settings call that the agent can
    > make to retreive the email address from the ActiveSync system if the user
    > didn't provide one. However this is going to take some time. So in the
    > short term the datasync team implemented the Exchange 2003 like
    > capability allowing user authentiction with email address and then
    > parsing the username. This capability will be part of 1.2.4. This issue
    > is documented in the ZMM Server Release notes
    > (http://www.novell.com/documentation/.../zen_mobile_se
    > rver_relnote.pdf) as follows:
    >
    > "12. Systems where iOS users are interfacing with a Novell GroupWise
    > DataSync server must use
    > DataSync Update 4 (Mobility 1.2.4) to fully utilize the hands-off
    > enrollment functionality. Users need to
    > enroll using their entire email address in lieu of their username if
    > they are enrolling by the hands-off
    > method. Similar processes must be followed to use hands-off enrollment
    > when users interface with
    > Exchange 2003 or any other mail server running ActiveSync 2.5 protocol.
    > A user's username and the
    > string of characters to the left of the @ sign in their email address
    > must be the same."
    >
    > Jason
    >
    >>>> TASNovell<[email protected]> 8/9/2012 8:26 AM >>>
    >
    > feeling a bit silly not reading the version number. We are running
    > datasync v1.2.3.3xxx. ZMM seems to connect fine. Email flows correctly
    > to the ios devices through the delivered profile. The only thing that is
    > not imported is the email address into the newly created user in ZMM. I
    > assume this should be pulled through from LDAP as you have to set the
    > attribute up during install.

  • Starting a managed server session and keeping the session when you exit

    I created a managed server named "xxx_mgd" with the create managed server wizard in the admin console
    when I start the managed server it produces a prompt for the username and password, whcih is the same username
    and password entered when i was created. The issue I have is that when I exit the session, the process dies.
    In comparison to the starting of the admin server, which is started with custom scripts which calls the standard wl startup scripts and it runs in background using nohup....
    Is there away to start my managed server the same way, so that it stays running when you exit. I have tried running it as the admin server, using an option where the password if fed, but it dies and never startup
    If you have any clue let me know
    Joseph

    Assuming that you are running WebLogic version 9.x and above.
    Copy the "security" folder inside DOMAIN_HOME/servers/AdminServer directory to DOMAIN_HOME/servers/ManagedServer directory.
    This security folder will have boot.properties file which contains encrypted username and password which is used when starting the server.
    You can run Admin Server in background using nohup command as below from DOMAIN_DIRECTORY. This command will redirect stdout to AdminServer.out file.
    nohup ./startWebLogic>>AdminServer.out &
    You can run Managed Server in background using nohup command as below from DOMAIN_DIRECTORY/bin folder. This command will redirect stdout to ManagedServer.out file.
    nohup ./startManagedWebLogic.sh <Managed Server Name> t3://<AdminServerListenAddress>:<PortNo> >>ManagedServer.out &
    Hope this helps.
    - Tarun
    Edited by: Tarun Boyella on Feb 3, 2011 2:09 PM

  • Deployment of Web Application when the managed Server is down .....

    Part of our installation, we want to deploy our web application on to a managed server.
    So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
    But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
    We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
    Can anyone help to deploy web application on to a managed server when the managed server is down ?
    Thanks,
    Selva-
    [att1.html]

    This is currently being fixed in 7.0 line, contact [email protected] and reference
    CR110687
    Cheers
    mbg
    "Selvamohan Neethiraj" <[email protected]> wrote in message news:[email protected]..
    Part of our installation, we want to deploy our web application on to a managed server.
    So, we use the JMX API calls to deploy the web application. But, at the time of this deployment the managed server is not brought up. So, our expectation was that when the managed server is brought up later, it will automatically STAGE the web application from Admin Server and then, deploy it in the managed server.
    But, what is happending is that the web application is not being deployed to the managed server (even though the web application is configured to be deployed in the specified managed server in the config.xml and it is set as the default application of the managed server application).
    We are using WebLogic 7.0 SP2 on RedHat Linux 7.2.
    Can anyone help to deploy web application on to a managed server when the managed server is down ?
    Thanks,
    Selva-
    [att1.html]

  • OBIEE 11.1.1.7.0 failing during starting managed server : bi_server1

    Hi All,
          I am trying to install OBIEE 11.1.1.7.1 un a Linux box, but during the Configuration Progress, OBIEE got error at Start Managed server; bi_server1.
         Looking into install log I've found the following :
    Done
    Stopping Derby Server...
    Starting AdminServer
    Starting the domain ...
    progress in calculate progress1
    Executing Task: Starting Managed Server: bi_server1
    oracle.as.install.bi.wls.ServerLifeCycleException: Failed to achieve state RUNNING in 3600seconds. The server is currently in state ADMIN
    at oracle.as.install.bi.wls.ServerLifeCycle.waitForManagedWLSServerState(ServerLifeCycle.java:119)
    at oracle.as.install.bi.wls.ServerLifeCycle.startServerSynchronous(ServerLifeCycle.java:59)
    at oracle.as.install.bi.biconfig.standard.StartStopManagedServer.doExecute(StartStopManagedServer.java:55)
    at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
    at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:66)
    at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
    at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:375)
    at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
    at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
    at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
    at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:96)
    at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:186)
    at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
    at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
    at java.lang.Thread.run(Thread.java:662)
         What could be caussing this failure ?
    Thanks

    I had similar issue in windows 7 [64 bit].
    It is found that the nodemanger windows service was not present and I had to create it by executing installNodeMgrSvc.cmd present in wls server location say, 'C:\Oracle\Middleware\wlserver_10.3\server\bin'  in my case and then come to bi wls console and 'Resume' the bi_server1 managed server. You would see progress in the installer once the managed server bi_server1 is 'Running' state.
    Hope this helps.

  • AuditLogFileException while starting a managed server

    Hi all,
    I implemented custom JAAS authentication for WLS 7.0 server and console. There
    are no issues with a standalone or single server in the domain. When testing an
    AdminServer with a managed server, I could still start the Admin Server without
    any problem after configuring the security realm. I got the following errors while
    starting the managed server. I tested with both servers on the same machine.
    Any help would be appreciated.
    <Server failed during initialization. Exception:weblogic.security.service.AuditLogFileException:
    Couldn't rename C:\bea7\user_projects\deletedomain\.\DefaultAuditRecorder.log
    to C:\bea7\user_projects\deletedomain\.\DefaultAuditRecorder.log2598.old
    weblogic.security.service.AuditLogFileException: Couldn't rename C:\bea7\user_pr
    ojects\deletedomain\.\DefaultAuditRecorder.log to C:\bea7\user_projects\deletedo
    main\.\DefaultAuditRecorder.log2598.old
    at weblogic.security.service.AuditLogFile.<init>(AuditLogFile.java:98)
    at weblogic.security.providers.audit.DefaultAuditProviderImpl.createLogF
    ile(DefaultAuditProviderImpl.java:106)
    at weblogic.security.providers.audit.DefaultAuditProviderImpl.initialize
    (DefaultAuditProviderImpl.java:89)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvid
    er(SecurityServiceManager.java:1752)

    Hi,
    Please remember to mark the answers accordingly... Helpful or correct... You will be helping the forum community by doing that.
    First thing to fix is the Admin_URL, there should be something like:
    -Dweblogic.management.server=http://localhost:7001How are you starting this managed server? Node manager or command line? Try both options and see if they bring up the same error.
    Cheers,
    Vlad

  • Managed server is getting crashed with Unexpected Signal : 11 occurred

    Hi All,
    I have installed weblogic 8.1 in production environment which has 4 manged servers configured on it.
    One of my managed server is getting down on daily basis with JVM crash leaving the below error:
    Unexpected Signal : 11 occurred at PC=0xFEDCBCAC
    Function=[Unknown. Nearest: JVM_FillInStackTrace+0x4CE4]
    Library=/Prod/bea/jdk142_05/jre/lib/sparc/server/libjvm.so
    Current Java thread:
    Dynamic libraries:
    0x10000      /Prod/bea/jdk142_05/bin/java
    0xff380000      /usr/lib/libthread.so.1
    0xff370000      /usr/lib/libdl.so.1
    0xff280000      /usr/lib/libc.so.1
    0xff3b0000      /usr/platform/SUNW,Sun-Fire-V890/lib/libc_psr.so.1
    0xfec00000      /Prod/bea/jdk142_05/jre/lib/sparc/server/libjvm.so
    0xff230000      /usr/lib/libCrun.so.1
    0xff210000      /usr/lib/libsocket.so.1
    0xfeb00000      /usr/lib/libnsl.so.1
    0xfeab0000      /usr/lib/libm.so.1
    0xff1f0000      /usr/lib/libsched.so.1
    0xfebd0000      /usr/lib/libmp.so.2
    0xfea80000      /Prod/bea/jdk142_05/jre/lib/sparc/native_threads/libhpi.so
    0xfea50000      /Prod/bea/jdk142_05/jre/lib/sparc/libverify.so
    0xfea10000      /Prod/bea/jdk142_05/jre/lib/sparc/libjava.so
    0xfe9e0000      /Prod/bea/jdk142_05/jre/lib/sparc/libzip.so
    0xfe860000      /usr/lib/locale/en_GB.ISO8859-1/en_GB.ISO8859-1.so.2
    0xf98d0000      /Prod/bea/jdk142_05/jre/lib/sparc/libnet.so
    0xf9a90000      /Prod/bea/weblogic81/server/lib/solaris/libweblogicunix1.so
    0xf9890000      /Prod/bea/weblogic81/server/lib/solaris/libstackdump.so
    0x59560000      /Prod/bea/jdk142_05/jre/lib/sparc/libnio.so
    0x59540000      /usr/lib/librt.so.1
    0x59520000      /usr/lib/libaio.so.1
    0x58fe0000      /usr/lib/libmd5.so.1
    0x58fc0000      /usr/lib/libsendfile.so.1
    0x58fa0000      /Prod/bea/jdk142_05/jre/lib/sparc/libioser12.so
    0x49300000      /Prod/bea/jdk142_05/jre/lib/sparc/libawt.so
    0x4ca00000      /Prod/bea/jdk142_05/jre/lib/sparc/libmlib_image.so
    0x51e60000      /Prod/bea/jdk142_05/jre/lib/sparc/headless/libmawt.so
    0x49200000      /Prod/bea/jdk142_05/jre/lib/sparc/libfontmanager.so
    Heap at VM Abort:
    Heap
    def new generation total 678464K, used 239751K [0x59800000, 0x842a0000, 0x842a0000)
    eden space 657920K, 35% used [0x59800000, 0x67e59228, 0x81a80000)
    from space 20544K, 18% used [0x82e90000, 0x83258bc0, 0x842a0000)
    to space 20544K, 0% used [0x81a80000, 0x81a80000, 0x82e90000)
    tenured generation total 1398144K, used 91656K [0x842a0000, 0xd9800000, 0xd9800000)
    the space 1398144K, 6% used [0x842a0000, 0x89c22090, 0x89c22200, 0xd9800000)
    compacting perm gen total 74496K, used 74281K [0xd9800000, 0xde0c0000, 0xf9800000)
    the space 74496K, 99% used [0xd9800000, 0xde08a7c8, 0xde08a800, 0xde0c0000)
    Local Time = Tue Sep 22 12:17:26 2009
    Elapsed Time = 94624
    # HotSpot Virtual Machine Error : 11
    # Error ID : 4F530E43505002EF 01
    # Please report this error at
    # http://java.sun.com/cgi-bin/bugreport.cgi
    # Java VM: Java HotSpot(TM) Server VM (1.4.2_05-b04 mixed mode)
    Kindly help me out to solve above problem ......
    Thanks,
    Karthik.

    The kinds of issues are usually bugs in the JVM, I would check your 8.1 Service Pack / Operating System combination on this page:
    http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/configs81/81_over/overview.html#1146895
    Make sure you're using the latest supported version of the JVM available for your platform.
    So if you're using 8.1 SP6 on Solaris SPARC, then you could be using Sun Java 2 SDK 1.4.2_11.
    You should also open a support request.

  • Disaster Recovery Scripts for Managed Server MSI Startup

    I am trying to get some custom start scripts created for each of my managed servers in the event the admin console is down or server gets hosed. We use nodemanager to start the managed servers in a Windows environment. I have about 8 managed servers and they all use the same nodemanager classpath but all have different server start arguments (different memory settings, etc....) so I need to make different custom scripts for each.
    Verbose Garbage Collection to Determine Heap Size .....this thread by Jay has been very helpful but so far I am just getting kicked back to the syntax screen like something is wrong in my script. Attached is the script and the output when I run it. Any help would be appreciated...thanks.
    startManagedFPCE1.cmd contents
    java.exe -Xms400m -Xmx400m -classpath $CLASSPATH -Dweblogic.Name=FPCE1 -Dbea.home="C:\Oracle\Middleware" -Dweblogic.management.username=beaadmin -Dweblogic.management.password=beaadminxxx -Dweblogic.management.server=http://sitportal1:8098 -Djava.library.path=c:\Oracle\Middleware\wlserver_10.3\server\bin -Dweblogic.ext.dirs=C:\Oracle\Middleware\patch_wls1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_wlp1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_oepe1111\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\wlportal_10.3\p13n\lib\system;C:\Oracle\Middleware\wlportal_10.3\light-portal\lib\system;C:\Oracle\Middleware\wlportal_10.3\portal\lib\system;C:\Oracle\Middleware\wlportal_10.3\info-mgmt\lib\system;C:\Oracle\Middleware\wlportal_10.3\analytics\lib\system;C:\Oracle\Middleware\wlportal_10.3\apps\lib\system;C:\Oracle\Middleware\wlportal_10.3\info-mgmt\deprecated\lib\system;C:\Oracle\Middleware\wlportal_10.3\content-mgmt\lib\system -Dweblogic.alternateTypesDirectory=C:\Oracle\Middleware\wlportal_10.3\portal\lib\security
    Results of running above script:
    C:\Oracle\Middleware\user_projects\domains\SIT11\servers\FPCE1>java.exe -Xms400m -Xmx400m -classpath $CLASSPATH -Dweblogic.Name=FPCE1 -Dbea.home="C:\Oracle\Middleware" -Dweblogic.management.username=b
    eaadmin -Dweblogic.management.password=beaadminsit11 -Dweblogic.management.server=http://sitportal1:8098 -Djava.library.path=c:\Oracle\Middleware\wlserver_10.3\server\bin -Dweblogic.ext.dirs=C:\Oracle
    \Middleware\patch_wls1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_wlp1032\profiles\default\sysext_manifest_classpath;C:\Oracle\Middleware\patch_oepe1111\profiles\default\
    sysext_manifest_classpath;C:\Oracle\Middleware\wlportal_10.3\p13n\lib\system;C:\Oracle\Middleware\wlportal_10.3\light-portal\lib\system;C:\Oracle\Middleware\wlportal_10.3\portal\lib\system;C:\Oracle\M
    iddleware\wlportal_10.3\info-mgmt\lib\system;C:\Oracle\Middleware\wlportal_10.3\analytics\lib\system;C:\Oracle\Middleware\wlportal_10.3\apps\lib\system;C:\Oracle\Middleware\wlportal_10.3\info-mgmt\dep
    recated\lib\system;C:\Oracle\Middleware\wlportal_10.3\content-mgmt\lib\system -Dweblogic.alternateTypesDirectory=C:\Oracle\Middleware\wlportal_10.3\portal\lib\security
    Usage: java [-options] class [args...]
    (to execute a class)
    or java [-options] -jar jarfile [args...]
    (to execute a jar file)
    where options include:
    -server to select the "server" VM
    -hotspot is a synonym for the "server" VM [deprecated]
    The default VM is server.
    -cp <class search path of directories and zip/jar files>
    -classpath <class search path of directories and zip/jar files>
    A ; separated list of directories, JAR archives,
    and ZIP archives to search for class files.
    -D<name>=<value>
    set a system property
    -verbose[:class|gc|jni]
    enable verbose output
    -version print product version and exit
    -version:<value>
    require the specified version to run
    -showversion print product version and continue
    -jre-restrict-search | -jre-no-restrict-search
    include/exclude user private JREs in the version search
    -? -help print this help message
    -X print help on non-standard options

    "bharat nagwani" <[email protected]> wrote:
    >
    Hi,
    Configuration: Weblogic 8.1SP2 on Windows 2000, 1 admin server and 14
    managed
    servers
    whats the right way from these 2 scenarious to create a domain on managed
    server
    1. create domain on managed server using configuration wizard. Then point
    to this
    domain from administration server remote start tab(root directory). This
    is what
    we do so far.This is the best way to create managed servers for your domain.
    >
    2. Just enter user_projects/domains folder/$domain name$ in remote start
    tab(root
    directory)
    on admin server console and when you start the managed server from
    admin console
    the domain folder and files will be created.
    Yes, the managed server is started in this case at the root directory you specified.
    The difference is in the
    1. first case we see all scripts like startManagedWeblogic, setenv, boot.properties
    etc
    this may help(we still dont know) if one wants to bring up managed
    server
    manually using
    startManagedServer.bat without using node manager.Yes, that is correct. You will need to edit the startManagedServer.bat to include
    the admin server URL, username and paswword..
    >
    2. second case only 2-3 files get created like msi-config.xml and SerializedSystemIni.dat
    Basically first case is superset of second case.
    What is the experience of people in this regard?
    thanks much
    bharat

  • Server start arguments ignored when starting managed server

    Hi
    We have configured a bunch of arguments for the managed server through the Admin Console in the Server->Start Arguments
    However those arguments are not picked up when we are starting the managed server.
    We are using a shell script to start the managed server using the weblogic.Admin class functionality.
    If the arguments are set in the JAVA_OPTIONS of setDomainEnv.sh, then they are picked up when starting the managed server.
    The nodemanager is configured with startScriptEnabled=true and startscript set to startWeblogic.sh.
    This is the scenario in Weblogic 10.0.0.
    Can anybody please explain why the arguments are not picked up?
    We tried the same arguments in Weblogic 10.2 and the arguments are picked up even if they are not configured in setDomainEnv.sh
    Is the difference in behavior because of the difference in versions?
    Edited by: user1030647 on Aug 29, 2010 12:26 AM

    Thanks Jay for the immediate responses.
    The thing I am worried about is it seems the behavior in Weblogic 10.0.2 seems to be in consistent with the behavior in Weblogic 10.0.0.
    In Weblogic 10.0.2, even if the JAVA_OPTIONS in setDomainEnv.sh do not include the paramaters that are set in "Server Start->Arguments", when starting the managed servers, they are picked up as can be seen from the managed server log files.
    However, in Weblogic 10.0.0, it seems that these options are not picked up when they are configured in "Server Start->Arguments". Only when they are configured in setDomainEnv.sh are they picked up.
    Do you have any info which points to this discrepancy?

  • While i am starting a Managed server some security Exception is raised

    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=:/home/durgasoft/HDFC_bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/durgasoft/HDFC_bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/durgasoft/HDFC_bea/jdk160_05/lib/tools.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic_sp.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic.jar:/home/durgasoft/HDFC_bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/webservices.jar:/home/durgasoft/HDFC_bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/home/durgasoft/HDFC_bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/home/durgasoft/HDFC_bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/xqrl.jar::
    PATH=/home/durgasoft/HDFC_bea/wlserver_10.3/server/bin:/home/durgasoft/HDFC_bea/modules/org.apache.ant_1.6.5/bin:/home/durgasoft/HDFC_bea/jdk160_05/jre/bin:/home/durgasoft/HDFC_bea/jdk160_05/bin:/usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/durgasoft/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.6.0_05"
    Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
    Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
    Starting WLS with line:
    /home/durgasoft/HDFC_bea/jdk160_05/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Xverify:none -da -Dplatform.home=/home/durgasoft/HDFC_bea/wlserver_10.3 -Dwls.home=/home/durgasoft/HDFC_bea/wlserver_10.3/server -Dweblogic.home=/home/durgasoft/HDFC_bea/wlserver_10.3/server -Dweblogic.management.discover=false -Dweblogic.management.server=Admin_URL -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/durgasoft/HDFC_bea/patch_wls1030/profiles/default/sysext_manifest_classpath:/home/durgasoft/HDFC_bea/patch_cie660/profiles/default/sysext_manifest_classpath -Dweblogic.Name=hdfc_mng6_1 -Djava.security.policy=/home/durgasoft/HDFC_bea/wlserver_10.3/server/lib/weblogic.policy weblogic.Server
    <Jun 24, 2012 5:31:42 AM GMT+05:30> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsystems Inc.>
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://Admin_URL.>
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Jun 24, 2012 5:32:11 AM GMT+05:30> <Notice> <Log Management> <BEA-170019> <The server log file /home/durgasoft/HDFC_bea/domains/HDFC_DOV_Domain/servers/hdfc_mng6_1/logs/hdfc_mng6_1.log is opened. All server side log events will be written to this file.>
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters..
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
    at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(Unknown Source)
    at weblogic.security.service.CSSWLSDelegateImpl.initialize(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(Unknown Source)
    Truncated. see log file for complete stacktrace
    com.bea.common.engine.ServiceInitializationException: com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
    at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
    at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
    at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(Unknown Source)
    Truncated. see log file for complete stacktrace
    com.bea.common.store.service.StoreInitializationException: [Security:099060]The URL specified for the data store connection is invalid: ldap://null:-1,please check all host configuration parameters.
    at com.bea.common.ldap.properties.LDAPStoreServicePropertiesConfigurator.convertStoreProperties(LDAPStoreServicePropertiesConfigurator.java:53)
    at com.bea.common.security.internal.service.StoreServiceImpl.initJDOProperties(StoreServiceImpl.java:101)
    at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:73)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
    at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
    Truncated. see log file for complete stacktrace
    >
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
    at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jun 24, 2012 5:32:12 AM GMT+05:30> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

    Hi,
    Please remember to mark the answers accordingly... Helpful or correct... You will be helping the forum community by doing that.
    First thing to fix is the Admin_URL, there should be something like:
    -Dweblogic.management.server=http://localhost:7001How are you starting this managed server? Node manager or command line? Try both options and see if they bring up the same error.
    Cheers,
    Vlad

Maybe you are looking for