-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
server status message #48
Comments
Hmmm. What version are you running of (A) the Remote Console and (B) WebLogic? |
Can you try some curl commands to get more info from WLS? curl -v -k --user {username}:{password} http://{ERMDEV01_AdminServer host}:{ERMDEV01_AdminServer port}:/management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes curl -v -k --user {username}:{password} http://{ERMDEV01_AdminServer host}:{ERMDEV01_AdminServer port}:wlsadminserverport/management/weblogic/latest/domainRuntime/serverRuntimes curl -v -k --user {username}:{password} http://{ERMDEV01_AdminServer host}:{ERMDEV01_AdminServer port}:/management/weblogic/latest/serverRuntime curl -v -k --user {username}:{password} http://{ERMDEV01_ManagedServer1 host}:{ERMDEV01_ManagedServer1 port}:/management/weblogic/latest/serverRuntime curl -v -k --user {username}:{password} http://{ERMDEV01_ManagedServer2 host}:{ERMDEV01_ManagedServer2 port}:/management/weblogic/latest/serverRuntime |
Also, how are you starting the manged servers? e.g. are you using the node manager? |
Also, what happens if you go to the admin console (not the remote console), and navigate to Servers then click the Control tab? And then click ERMDEV01_ManagedServer1 in the table then click the Monitoring tab? And click the Control tab? Also, do you have access to WLST? If so, I'll send some WLST commands I'd like you to try. |
All of this works correctly. Also yes I have access to WLST. |
< HTTP/1.1 200 OK |
Well its not possible to restart them from the remote control console...So they are started through scripting via node manager by executing ./startNodeManger.sh and ./startWeblogic.sh |
Thanks for the data. At this point, the curl command indicates that the servers are properly running, so we don't I've been trying to reproduce the problem and have not been able to. Now that everything has stabilized and should be running, what happens if you |
Also, if you've configured the node manager, you should be able to start the managed servers from the remote console via the 'Start' button on the Servers table under monitoring (it worked for me). Give it a try? Also, does the 'Start' button in the admin console work for your servers? |
Can you try this curl command? curl -v -k --user {username}:{password} http://{ERMDEV01_AdminServer host}:{ERMDEV01_AdminServer port}:wlsadminserverport/management/weblogic/latest/domainRuntime/serverRuntimes Thanks! |
Also, does your domain's security realm have a DefaultIdentityAsserter configured? |
And would you be available for zoom debugging session? |
Yes the out of the box DefaultIdentityAsserter is has been created during domain creation |
If the Weblogic console for a domain is shutdown, it doesnt appear to me there is anyway through the remote control panel -> kiosk panel to connect to much less start/restart any managed server. |
Also no it isnt a mistake that I have two ADMIN servers running under one Weblogic console. From a management/monitoring point of view(s) this is the next best thing to do outside of having a clustered environment which in our case we are running non-clustered. Eventually I will have one DOMAIN ERMDEV that will contain ERMDEV01 domain and ERMDEV02 domain both of these Admin console(s) for these domains and then their respective managed servers under each |
Thanks for the data. I'll discuss it with the rest of the remote console team then get back to you. |
I'm a little unclear about your configuration. Can you attach your domains' config.xmls and screen shots of:
Also, would you be available for a zoom debugging session? Thanks! |
|
|
|
Thanks for the screen shots. Unfortunately, I'm not able to debug what's going on from just the screen shots. I need lower level data. Can you attach your domains' config.xmls and the curl output from: curl -v -k --user {username}:{password} http://{ERMDEV01_AdminServer host}:{ERMDEV01_AdminServer port}:wlsadminserverport/management/weblogic/latest/domainRuntime/serverRuntimes and curl -v -k --user {username}:{password} http://{ERMSIT02_AdminServer host}:{ERMSIT02_AdminServer port}:wlsadminserverport/management/weblogic/latest/domainRuntime/serverRuntimes |
Also, can we do a zoom debugging session? I probably need to run a number of curl commands to get to the bottom of the issue. I'm a developer on Oracle's remote console team. I'm available this afternoon (EST). I'm also available most of Friday. |
$ curl -v -k --user
< HTTP/1.1 200 OK
|
Thanks for the curl output. Could you get me the output for curl -H X-RequestedBy:myclient --user:.. .../domainRuntime/serverRuntimes ? (v.s. you gave me the output for .../domainRuntimes/serverLifeCycleRuntimes) (I need to see this to help figure out why the admin server isn't able to see the running managed servers) |
Hello @mgriffininprs it would be easier to help you if you could register to our public weblogic workspace. Use the following link https://join.slack.com/t/oracle-weblogic/shared_invite/zt-1ni1gtjv6-PGC6CQ4uIte3KBdm_67~aQ to register your self and once in, please go to #remote-console and lets continue the thread there. |
I mean no offense nor is it my intent to be uncooperative when I say this but Im going to respectfully to decline to register for yet another messaging type of application regardless of how technically beneficial it could be or provide |
Even though my managed server ERMDEV01_ManagedServer1 is running verified in Weblogic console and Enterprise Manager console, it shows status of not running under the Weblogic Remote console ->Monitoring -> servers window
Yet if you click on the managed server Weblogic Remote console ->Monitoring ->ERMDEV01_ManagedServer1, the status shows running
BTW for entirely different server i have in my kiosk panel the functionality works as expected
The text was updated successfully, but these errors were encountered: