server status message

[mgriffininprs]

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

[lfeigen]

Hmmm. What version are you running of (A) the Remote Console and (B) WebLogic?

[mgriffininprs]

weblogic 12.2.1.4.

[moreaut]

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

[moreaut]

Also, how are you starting the manged servers? e.g. are you using the node manager?

[moreaut]

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.

[mgriffininprs]

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.

[mgriffininprs]

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

< HTTP/1.1 200 OK
< Date: Mon, 12 Jun 2023 17:10:52 GMT
< Content-Length: 4358
< Content-Type: application/json
< Vary: Accept-Encoding
< X-ORACLE-DMS-RID: 0
< X-ORACLE-DMS-ECID: b1f151a4-e4af-4e19-9bea-13de84a96760-00001b00
< X-Content-Type-Options: nosniff
<
{
"links": [
{
"rel": "parent",
"href": "http:// /management/weblogic/latest/domainRuntime"
},
{
"rel": "self",
"href": "http:// /management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes"
},
{
"rel": "canonical",
"href": "http:/\ //management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes"
}
],
"items": [
{
"links": [
{
"rel": "self",
"href": "http:///management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/ERMDEV01_ManagedServer1"
},
{
"rel": "canonical",
"href": "http:///management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/ERMDEV01_ManagedServer1"
}
],
"identity": [
"serverLifeCycleRuntimes",
"ERMDEV01_ManagedServer1"
],
"nodeManagerRestartCount": 0,
"middlewareHome": "/u01/app/oracle/Middleware/WL_12214_ermdev01",
"name": "ERMDEV01_ManagedServer1",
"weblogicHome": "/u01/app/oracle/Middleware/WL_12214_ermdev01/wlserver",
"state": "RUNNING",
"type": "ServerLifeCycleRuntime"
},
{
"links": [
{
"rel": "self",
"href": "http:///management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/ERMDEV01_ManagedServer2"
},
{
"rel": "canonical",
"href": "http:///management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/ERMDEV01_ManagedServer2"
}
],
"identity": [
"serverLifeCycleRuntimes",
"ERMDEV01_ManagedServer2"
],
"nodeManagerRestartCount": 0,
"middlewareHome": null,
"name": "ERMDEV01_ManagedServer2",
"weblogicHome": null,
"state": "SHUTDOWN",
"type": "ServerLifeCycleRuntime"
},
{
"links": [
{
"rel": "self",
"href": "http:///management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/ERMDEV02_AdminServer(admin)"
},
{
"rel": "canonical",
"href": "http:///management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/ERMDEV02_AdminServer(admin)"
}
],
"identity": [
"serverLifeCycleRuntimes",
"ERMDEV02_AdminServer(admin)"
],
"nodeManagerRestartCount": 1,
"middlewareHome": "/u01/app/oracle/Middleware/WL_12214_ermdev01",
"name": "ERMDEV02_AdminServer(admin)",
"weblogicHome": "/u01/app/oracle/Middleware/WL_12214_ermdev01/wlserver",
"state": "RUNNING",
"type": "ServerLifeCycleRuntime"
},
{
"links": [
{
"rel": "self",
"href": "http:///management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/ERMDEV01_AdminServer"
},
{
"rel": "canonical",
"href": "http:///management/weblogic/latest/domainRuntime/serverLifeCycleRuntimes/ERMDEV01_AdminServer"
}
],
"identity": [
"serverLifeCycleRuntimes",
"ERMDEV01_AdminServer"
],
"nodeManagerRestartCount": 0,
"middlewareHome": "/u01/app/oracle/Middleware/WL_12214_ermdev01",
"name": "ERMDEV01_AdminServer",
"weblogicHome": "/u01/app/oracle/Middleware/WL_12214_ermdev01/wlserver",
"state": "RUNNING",
"type": "ServerLifeCycleRuntime"
}
]

[mgriffininprs]

Also, how are you starting the manged servers? e.g. are you using the node manager?

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

[moreaut]

Thanks for the data. At this point, the curl command indicates that the servers are properly running, so we don't
need to use WLST yet (WLST is just an alternative way to view the underlying server runtime mbeans).

I've been trying to reproduce the problem and have not been able to.
I'm wondering if this is a transient problem while the server is starting up.

Now that everything has stabilized and should be running, what happens if you
navigate to the Servers table again and then to ManagedServer1? Do the pages
look OK now or are you still seeing the same problem?

[moreaut]

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?

[moreaut]

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!

[moreaut]

Also, does your domain's security realm have a DefaultIdentityAsserter configured?
(go to the edit tree then Security -> Realms -> <your realm, e.g. myrealm> -> Authentication Providers)

[moreaut]

And would you be available for zoom debugging session?

[mgriffininprs]

Also, does your domain's security realm have a DefaultIdentityAsserter configured? (go to the edit tree then Security -> Realms -> <your realm, e.g. myrealm> -> Authentication Providers)

Yes the out of the box DefaultIdentityAsserter is has been created during domain creation

[mgriffininprs]

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?

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.

You receive message