Admin Server console not showing Managed Server is running

I am using WLS 7.0.1.0 SP1 runing on Windows 2000. I have setup a node manager, Admin server and Managed Server as Windows Services. Admin Server has -delaySeconds as 2min. Manager Server(MS) has been made to depend on Admin Server start. When I boot my machine, all the three services come up properly. I can access my application which is running on MS properly. But for some reason the Admin Console doesn't show the MS as running. If I use the Admin Console now to start up MS all it does it "Reconnects to the admin server" since the MS is in started state. What is the reason for this

It could be the ordering dependency and the rediscovery of the MS by the AS.
An AS has a notion of where MS's live on disk and it could be an issue with
AS bouncing in between MS's constant state of upness.
Cheers
mbg
"Ajay Kulkarni" <[email protected]> wrote in message
news:3ede0306$[email protected]..
I am using WLS 7.0.1.0 SP1 runing on Windows 2000. I have setup a nodemanager, Admin server and Managed Server as Windows Services. Admin Server
has -delaySeconds as 2min. Manager Server(MS) has been made to depend on
Admin Server start. When I boot my machine, all the three services come up
properly. I can access my application which is running on MS properly. But
for some reason the Admin Console doesn't show the MS as running. If I use
the Admin Console now to start up MS all it does it "Reconnects to the admin
server" since the MS is in started state. What is the reason for this

Similar Messages

Weblogic Server does not show managed server started when I used the Windows service to start it.

I created a windows service to start a managed server and the services was created successfully and stated. WHen I go to the Weblogic Server Admn console, the server is still showing shutdown. Whenm I try to start it, it returns with error that the the service is not able to start. Has anyone ran into anything similar. I am running on Windows Server 2008R2 and running Weblogic Server 10.3.6 and Fusion Middleware 11.1.6.
C

Hi,
For starting managed server as windows service there is no need of nodemanager .
Please follow the steps given in the below doc:
How to Install MS Windows Services For FMW 11g WebLogic Domain Admin and Managed Servers (Doc ID 1060058.1)
Thanks,
Sharmela

Secondary DPM server does not show "protected server group" when attempting to protect primary server

Hi Guys,
I have a bit of a weird situation with DPM 2012(pre SP1). We have a primary server which is running quite happily(protects 8 SQL servers). I'm attempting to setup a secondary. When I've done this in the past with other DPM versions(this version included)
all i have to do is this following:
Install the same version of DPM on the "secondary machine"
Attach the agent on the "primary server"
Create a new protection group for everything
The catch is that I only see the following:
I can successfully protect the database of the primary server. However the secondary server cannot see any computers protected on the primary for some reason. Any ideas why this object doesn't show at all?

Hi,
At any time, was the primary DPM Server rebuilt and it's database restored ?
Can you verify that the DPMWriter service is running.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

I can not startup Managed server via admin server

Admin server ip:172.16.219.25
Admin server name:nstwssadm1.webex.com
Managed server ip:172.16.219.189
Managed server name:nstwss001.webex.com.
I can start Managed server in comand line like 'startManagedWebLogic.sh nstwss001-s1 t3s://nstwssadm1.webex.com:9002'
But, I can not startup Managed server in console, it appears following log:
=========
<Jun 29, 2006 8:56:16 AM EDT> <Info> <NodeManager@*.*:5555> <Starting Server nst1::nstwss001-s1 ...>
<Jun 29, 2006 8:56:16 AM EDT> <Info> <NodeManager@*.*:5555> <BaseProcessControl: saving process id of WebLogic Managed server 'nstwss001-s1', pid: 11072>
<Jun 29, 2006 8:56:19 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_08 JVM R24.5.0-61 Version ari-49095-20050826-1856-linux-ia32 from BEA Systems, Inc.>
<Jun 29, 2006 8:56:19 AM EDT> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at https://172.16.219.25:9002 to check if there exists a running admin server at this URL.>
<Jun 29, 2006 8:56:20 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
<Jun 29, 2006 8:56:20 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
<Jun 29, 2006 8:56:21 AM EDT> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jun 29, 2006 8:56:21 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 >
<Jun 29, 2006 8:56:21 AM EDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server https://172.16.219.25:9002 to retrieve the initial configuration.>
<Jun 29, 2006 8:56:22 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/bea/weblogic81/common/nodemanager/nstwss001-s1/nstwss001-s1.log is opened. All server side log events will be written to this file.>
<Jun 29, 2006 8:56:23 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
<Jun 29, 2006 8:56:23 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
<Jun 29, 2006 8:56:26 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
<Jun 29, 2006 8:56:26 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
<Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file /opt/bea/weblogic81/server/lib/DemoIdentity.jks.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
<Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file /opt/bea/weblogic81/server/lib/DemoIdentity.jks.>
<Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
<Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
<Jun 29, 2006 8:56:28 AM EDT> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : localhost>
<Jun 29, 2006 8:56:28 AM EDT> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
===============================
Who can help me on it?
Thanks.

your error says:
'his server is unable to establish a connection to the <b>node manager</b>'
check that your node manager is running when you try to start de manage server.

Essbase server is not showing in the windows services (11.1.2.1)

Hi All,
Essbase server is not showing in the windows services 11.1.2.1. when I checked the processes from task manager it is there.
Regards,

The windows service for essbase in 11.1.2.x is an OPMN service "Oracle Process Manager..."
Cheers
John
http://john-goodwin.blogspot.com/

The report I published on the SQL server report server is not showing in the application we use to retrieve reports.

The report I published on the SQL server report server is not showing in the application we use to retrieve reports. My cell phone number is {removed}
Thanks.

Hello Roger Tenn,
Thank you for posting in the TechNet Forum.
As this issue is related to SQL server report server, to receive better report, it is recommended to ask in the SQL server forum.
https://social.technet.microsoft.com/Forums/en-US/home?category=sqlserver
The professionals here will be glad to help you.
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

JCO.SERVER could not find the server function

Hi,
I am calling "BAPI_COMPANY_GETDETAIL".thuough the zprogram"ZBAPI_COMPANY_GETDETAIL"
REPORT ZBAPI_COMPANY_GETDETAIL.
DATA:BEGIN OF ITAB,
RCOMP LIKE T880-RCOMP,
END OF ITAB.
ITAB-RCOMP = 99999.
CALL FUNCTION 'BAPI_COMPANY_GETDETAIL'
EXPORTING
COMPANYID = ITAB.
IMPORTING
COMPANY_DETAIL =
RETURN =
The Details I Gave......
In SM59 of R/3:
PROGRAMID:LCRSAPRFC_PIT
GATEWAYHOST:PITEST
GATEWAYSERVICE:sapgw01
Tested the connection and it is running
ID:
In Communication Channel.
Application server (Gateway):PITEST
Application server Service (Gateway):
PROGRAMID:LCRSAPRFC_PIT
RFC Metadata Repository parameter.
ip of XI Server
System No Xi System NO
username
pwd
In SM58 I find the Following error.
"JCO.SERVER could not find the server function BAPI_COMPANY_GETDETAIL.
I Tested RFC ADAPTOR in RWG and it is ok.
I do not Understand where the problem is.
Please clarify.
Thanks,
Srinivasa

Thanks for the reply,
Yes RFC is in the Sender side.
I am calling "BAPI_COMPANY_GETDETAIL".thuough the zprogram"ZBAPI_COMPANY_GETDETAIL"
REPORT ZBAPI_COMPANY_GETDETAIL.
DATA:BEGIN OF ITAB,
RCOMP LIKE T880-RCOMP,
END OF ITAB.
ITAB-RCOMP = 99999.
CALL FUNCTION 'BAPI_COMPANY_GETDETAIL'
EXPORTING
COMPANYID = ITAB.
IMPORTING
COMPANY_DETAIL =
RETURN =
The Details I Gave......
In SM59 of R/3:
PROGRAMID:LCRSAPRFC_PIT
GATEWAYHOST:PITEST(XI system name)
GATEWAYSERVICE:sapgw01
Tested the connection and it is running
ID:
In Communication Channel.
Application server (Gateway):PITEST(XI system name)
Application server Service (Gateway):
PROGRAMID:LCRSAPRFC_PIT
RFC Metadata Repository parameter.
ip of XI Server
System No Xi System NO
username
pwd
In SM58 I find the Following error.
"JCO.SERVER could not find the server function BAPI_COMPANY_GETDETAIL.
I Tested RFC ADAPTOR in RWG and it is ok.
I do not Understand where the problem is.
These is what I gave,

Query not showing detailed result when run through query Designer or Portal

Hi,
There is one query which not showing detailed result while running through Query Designer or run in Portal.
But strange thing is that it is showing the detailed result when i run it through BeX Analyzer.
While all the other queries don't have this problem in system. All showing the correct detailed result.
If anyone have some idea on this issue plz let me know.
Regards,
Javed
Edited by: Javed Akhtar on Jul 7, 2009 3:59 PM

Hi,
We can do this setting in WAD. Please check the web template and try to remove that setting. When you have hierarchy then we can display only till certain level in portal, this setting is done in web template APIs, but in bex analyzer you can see all the detailed information.
Edited
Go through this thread for some more detailed information
http://help.sap.com/saphelp_nw2004s/helpdata/en/44/7b5f0a95ce12d0e10000000a422035/frameset.htm
Regards,
rik

Workshop App Works on Admin but Not On Managed Server

Hi all, I have a very simple test Workshop App that works fine on an Admin server
but not on a Managed Server. I have all the JMS and JDBC resources that the apps
need, the console does not complain, they deploy fine, but for some reason I get
exceptions when deployed to the Managed server but works fine on the Admin server.
What's the difference between both servers? I start one with startWebLogic.cmd
and the other one with startManageWebLogic.cmd in the same domain directory. The
only resource that I have not been able to target to the managed server is WSStoreForwardInternalJMSServercgServer
which I have no idea what it is or if it matters. Some portions of the app works
when deployed to the managed server so I know it has deployed fine and some simple
pages compile and work fine but when using certain JAR files in the lib directory
I get weird exceptions on the managed server and not on the Admin server.
I'd appreciate any help.
Thanks, Jose

Hi all, I have a very simple test Workshop App that works fine on an Admin server
but not on a Managed Server. I have all the JMS and JDBC resources that the apps
need, the console does not complain, they deploy fine, but for some reason I get
exceptions when deployed to the Managed server but works fine on the Admin server.
What's the difference between both servers? I start one with startWebLogic.cmd
and the other one with startManageWebLogic.cmd in the same domain directory. The
only resource that I have not been able to target to the managed server is WSStoreForwardInternalJMSServercgServer
which I have no idea what it is or if it matters. Some portions of the app works
when deployed to the managed server so I know it has deployed fine and some simple
pages compile and work fine but when using certain JAR files in the lib directory
I get weird exceptions on the managed server and not on the Admin server.
I'd appreciate any help.
Thanks, Jose

Managed server doesn't show in server list in JDev

I have admin server (AdminServer) and managed server (soa_server1) configured in my domain. I started both server successfully, and in WL console, I see soa_server state is running, and soa-infra is Active; in em I see SOA node on the left panel, and soa_server1 status is up. When I tried to deploy my composite to server (I want to deploy it to soa_server1), I only see AdminServer in the SOA servers list, not soa_server1. how could I make soa_server1 shown?
Edited by: wiky on 19-Jul-2011 6:30 AM

To be more specific, this is what I did and the problem I am facing:
1. configured admin server and manged server (soa_server1) on my domain(weblogic 10.3.5).
2. started the admin server
3. started soa_server1
4. see both servers in WL control, both server state=running
5. see both server in EM console, both server status are up
6. in JDev(11.1.1.5.0), created an application server connection, and tested the connection successfully
7. when I tried to deploy my composite from JDev, I selected the application server connection, on step "SOA servers", it only lists AdminServer.
I want to deploy my composite to soa_server1. How could I make soa_server1 shown on the list?
Edited by: wiky on Jul 18, 2011 2:46 PM
Edited by: wiky on Jul 18, 2011 4:13 PM
Edited by: wiky on 18-Jul-2011 5:45 PM
Edited by: wiky on 18-Jul-2011 5:52 PM

Nodemanager does not restart managed server after Linux OS reboot

Running Linux 2.6.18, Sun JDK 1.6.0_14, and WebLogic 10.3, we have a correctly functioning nodemanager watching a single managed server. If I kill -9 the managed server, the nodemanager fires up a new one immediately. If, however, we reboot the box, the nodemanager will start cleanly and will not start the managed server. It appears to believe the node should remain down and reports its status as UNKNOWN.
I've seen where this is a known problem on Windows boxes, easily gotten around by supplying the -Xrs parameter to the startup parms for the managed server. (Section 5 of the general nodemanager config doc.) I don't see, however, where there's an equally clean solution for Linux.
Things I've tried:
+ When I set the server to DEBUG, it shows zero sign of receiving a shutdown signal. It's dumping loads of cluster messages, etc, into the log and then suddenly the log just ends so it's dying via kill -9. If the nodemanager is still running at that time, it might try to restart the managed server and log it somewhere as permanently failed.
+ The nodemanager only logs to INFO level, and logs no evidence of deciding to leave the node down. (DEBUG is an invalid LogLevel, so that's all I've got.)
+ A restart signal sent from our AdminServer (on another Linux box) successfully starts the managed node through the nodemanager. Nothing unusual occurs or is logged.
Things I'm curious about:
+ Is there some way to see in what state the nodemanager believes the managed server to be?
+ Is there some value in some doc somewhere that might say the server should not be restarted?
+ Is there not a log of NodeManager client actions? I don't see anything in domain.log or AdminServer.log except when the NM is down.
Thanks,
Kevin
ListenPort=5556
ListenBacklog=50
SecureListener=true
AuthenticationEnabled=true
NativeVersionEnabled=false
CrashRecoveryEnabled=true
JavaHome=/appl/java/jre
StartScriptEnabled=false
StopScriptEnabled=false
StartScriptName=startWebLogic.sh
StopScriptName=
LogFile=/appl/bea/wlserver_10.3/common/nodemanager/logs/nodemanager.log
LogLevel=INFO
LogLimit=0
LogCount=1

can you set NativeVersionEnabled to true. We have faced this in windows which was fixed by changing this property. Some notes from that issue:
Faced this interesting issue in Windows 2008 environment. Managed Servers were started by node manager and it was expected that on a system restart after a crash, the node manager will restore the state of the managed servers to the state it was before the crash. Node Manger was configured to run as a windows service. Hence it started after the server restart. But the individual managed servers were not getting started. Interestingly, for the managed servers started by the node manager there were no <Managed_Server_Name>.lck file in the <Server>/data/NodeManger folder.
To fix this always set the following properties in the nodemanager.properties on the node maager home directory.
CrashRecoveryEnabled=true /* This by default is set to false. This needs to be turned for auto restart after crash to work */
NativeVersionEnabled=true /* This is by default set to true and it should be set as such. If you turn this off on platforms for which weblogic provide native JNI libraries ( e.g. as in Windows 2008) then this wont create the .lck file and hence node manager wont restart the managed server after the crash.
Note: As per official documentation .lck files are required for weblogic node managers to do auto restart after system crash
From Official documentation:
After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.
If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
*/

Can not start managed server

Hi All,
I am trying to start one of the managed server which are in cluster but i am getting below error:
Please suggest the issue and resolution if anyone has come across the same situation.
<Oct 14, 2011 7:56:16 AM EDT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.BasicServerRef@274, implementation: 'weblogic.jms.dispatcher.DispatcherImpl@4f6fa0b6', oid: '628', implementationClassName: 'weblogic.jms.dispatcher.DispatcherImpl'
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers].
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers]
at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:833)
at weblogic.security.service.SecurityServiceManager.getSealedSubjectFromWire(SecurityServiceManager.java:522)
at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:349)
at weblogic.rmi.internal.BasicServerRef.acceptRequest(BasicServerRef.java:953)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:351)
Truncated. see log file for complete stacktrace
>
<Oct 14, 2011 7:56:16 AM EDT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.BasicServerRef@274, implementation: 'weblogic.jms.dispatcher.DispatcherImpl@4f6fa0b6', oid: '628', implementationClassName: 'weblogic.jms.dispatcher.DispatcherImpl'
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers].
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers]
at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:833)
at weblogic.security.service.SecurityServiceManager.getSealedSubjectFromWire(SecurityServiceManager.java:522)
at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:349)
at weblogic.rmi.internal.BasicServerRef.acceptRequest(BasicServerRef.java:953)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:351)
Truncated. see log file for complete stacktrace
>
<Oct 14, 2011 8:12:03 AM EDT> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
<Oct 14, 2011 8:12:06 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to SUSPENDING>
[JCABindingManager] : This operation is not supported for JCA based MDB
<Oct 14, 2011 8:12:07 AM EDT> <Notice> <Cluster> <BEA-000163> <Stopping "async" replication service>
<Oct 14, 2011 8:12:08 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Oct 14, 2011 8:12:08 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to SHUTTING_DOWN>
<Oct 14, 2011 8:12:08 AM EDT> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 10.172.108.9:26362 was shutdown.>

From the managed server folder like servers/yourManagedServer rename the fodler named "data". Then restart the server. Basically this "data" folder will have ldap information and all groups, policies etc. It will create this folder again and get a copy of full data folder from admin server. Give this a shot.
Thanks
Ravi Jegga

Visio SCOM Add-In - Distributed Application Export not Contacting Management Server

I have installed the Visio 2010 SCOM Add-In to my copy of Visio 2013 (since there is no 2013 Add-in and there seemed to be enough articles that it *should* work). I can connect to my Management server from a blank diagram and add objects without issue, although
I seem to have to reconnect every time I start a new drawing. Not that the configuration is gone, I just can't do anything until I go into Configure and click OK. The real issue though is that when I go into SCOM and export a Distributed Application as a Visio
Diagram and then open it in Visio, it is not connecting to the Management server and none of the objects seem to have any SCOM data associated with them. I have tried manually linking the objects in the drawing to SCOM objects but this does not work, even
though I can see the SCOM objects.
For reference, I am doing all of this work on my Win7 machine with Visio 2013. I have the SCOM console installed on my machine. SCOM is SCOM2012 R2 running on a 2012 server.
Thanks for any suggestions.

Hi,
Would you please install this add-in on another new brand Windows and check the result.
I hope these can help you:
SCOM 2012 - Visio Integration Add-In Not Loading
http://kevingreeneitblog.blogspot.dk/2012/08/scom-2012-visio-integration-add-in-not.html
Install the Visio 2010 Add-in
http://technet.microsoft.com/en-us/library/hh920815.aspx
Regards,
Yan Li
Regards, Yan Li

Shared Storage is not showing in SErver pool physical disk .

Hi i have added couple of images to give you exact picture what i am doing .. please have a look
OVM can see Shared storage from Openfiler
http://www.picpanda.com/viewer.php?file=u1pf8hre1oqufkx6vyr3.gif
OVM , SErver Pool (physical disk ) can see Shared Storage name
http://www.picpanda.com/viewer.php?file=0h2dn48x6gh5avr6fob.gif
OVM does not show the physical disk from Shared storage
http://www.picpanda.com/viewer.php?file=c3njd7bg4exyjpymsit.gif
if i remmeber, When i tryed with NFS share from openfiler, its worked before ... but this time i am trying with ISCSI target ..
thanks
is there any thing do i have to do to make it work ??

Fosiul wrote:
if i remmeber, When i tryed with NFS share from openfiler, its worked before ... but this time i am trying with ISCSI target ..
is there any thing do i have to do to make it work ??Check to see if the physical disk appears under the default volume group for your san. If not, refresh the san and wait until it does. Also, make sure you have an admin server configured for that san and that your Oracle VM servers are in the default access group.

Sun Java System Web Proxy Server (4.0.2) - manage server will not start

In short here's the scenario and main problem.
a. Proxy admin server start - no problem
b. Create a new manage server (no proxying - just testing it) using different port. It just won't start. No logs produced either.
Here's the server.xml for the new manage server.
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE SERVER PUBLIC "-//Sun Microsystems Inc.//DTD Sun Java System Web Proxy Server 4.0//EN" "file:///E:/Sun/ProxyServer40/bin/proxy/dtds/sun-web-proxy-server_4_0.dtd">
<SERVER>
    <PROPERTY name="accesslog" value="E:/Sun/ProxyServer40/proxy-server3/logs/access"/>
    <LS id="ls1" port="8083" servername="cbaob-b3-csddb1.adp1.cibc.pte"/>
    <MIME id="mime1" file="mime.types"/>
    <ACLFILE id="acl1" file="E:/Sun/ProxyServer40/httpacl/generated.proxy-server3.acl"/>
    <USERDB id="default"/>
    <FILECACHE enabled="true" maxage="30" mediumfilesizelimit="537600" mediumfilespace="10485760" smallfilesizelimit="2048" smallfilespace="1048576" transmitfile="false" maxfiles="1024" hashinitsize="0"/>
    <CACHE enabled="true" cachecapacity="2000" cachedir="E:/Sun/ProxyServer40/proxy-server3/cache">
        <PARTITION partitionname="part1" partitiondir="E:/Sun/ProxyServer40/proxy-server3/cache" maxsize="100" minspace="5" enabled="true"/>
<GC enabled="true" gchimargin="80" gclomargin="70" gcleavefsfull="60" gcextramargin="30"/>
    </CACHE>
    <LOG file="E:/Sun/ProxyServer40/proxy-server3/logs/errors" loglevel="finest"/>
</SERVER>
Nothing seems to be wrong with this. The XML format follows the specified DTD.
Would appreciate any help.
Thanks.

Thanks for your reply. Yes. This is really odd.
Anyway to make the whole story short, i uninstall this proxy server 4.0.2 on this server (say server1) and try to reinstall a new proxy 4.0.13 but having odd problem (i have administration rights)
Here it goes.
a. CMD java -version is 1.4.2_XX
b. Double click the proxy 4.0.13 setup.exe - nothing happen.
c. CMD setup --javahome c:\jdk1.6_XX - nothing happen
Here retrying.
a. Login to server2 and map conection to server1
b. Double click the proxy 4.0.13 setup.exe on server1 (while on server2) - setup.exe runs. This proves the proxy setup.exe on server1 is good.
c. Make a copy of proxy 4.0.13 on server2
d. Login to server1 and map connection to server2
e. Double click the proxy 4.0.13 setup.exe on server2 (while on server1) - setup.exe did not run.
Both servers are on the same domain and i'm using same ID to access both servers
Again, no logs on the windows events (security, application, system)
This is becoming mind a boggling mystery.
Any idea what's going on?
Thanks.

Admin Server console not showing Managed Server is running

Similar Messages

Maybe you are looking for