I use a Oracle WebLogic Server 12c and when I start it on Eclipse it shows this error, it does'nt allow me to log in localhost neither when I try to access it
from another computer in a different domain, in the log appears that the server is not reacheable.
This is the exception that appears in Eclipse.
This Exception occurred at Wed Nov 13 08:11:07 CET 2019.
weblogic.nodemanager.NMConnectException: Connection refused: connect. Could not connect to NodeManager. Check that it is running at localhost/127.0.0.1:5556.
Problem invoking WLST - Traceback (innermost last):
File "C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\bin\scripts_manejados\StartBT.wlst", line 1, in ?
File "<iostream>", line 111, in nmConnect
File "<iostream>", line 552, in raiseWLSTException
WLSTException: Error occurred while performing nmConnect : Cannot connect to Node Manager. : Connection refused: connect. Could not connect to NodeManager. Check that it is running at localhost/127.0.0.1:5545.
This is my nodemanager properties:
#Tue Nov 12 09:45:58 CET 2019
#Node manager properties
#Fri Jun 24 14:55:43 CEST 2016
DomainsFile=C\:\\Oracle\\Middleware\\Oracle_Home\\user_projects\\domains\\base_domain\\nodemanager\\nodemanager.domains
LogLimit=0
PropertiesVersion=12.1.3
AuthenticationEnabled=true
NodeManagerHome=C\:\\Oracle\\Middleware\\Oracle_Home\\user_projects\\domains\\base_domain\\nodemanager
JavaHome=C\:\\Program Files\\Java\\jdk1.7.0_75
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.cmd
ListenAddress=localhost
NativeVersionEnabled=true
ListenPort=5540
LogToStderr=true
SecureListener=false
LogCount=1
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=false
StartScriptEnabled=true
LogFile=C\:\\Oracle\\Middleware\\Oracle_Home\\user_projects\\domains\\base_domain\\nodemanager\\nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
And this is my StartBt script file, used to start the server and specify some preferences:
nmConnect('weblogic','AXLWL20040','localhost','5521','base_domain','C:/Oracle/Middleware/Oracle_Home/user_projects/domains/base_domain','plain')
nmStart('AdminServer')
nmDisconnect()
I want to make it accesible, not only for local.
nmConnect('weblogic','AXLWL20040','localhost',**'5521'**,'base_domain','C:/Oracle/Middleware/Oracle_Home/user_projects/domains/base_domain','plain')
Port should listen to 5545.
You wrongly configure the ports. Your NodeManager listen on port 5540
ListenPort=5540
You try to connect to 5545
WLSTException:..Could not connect to NodeManager. Check that it is running at localhost/127.0.0.1:5545
Related
I'm trying to startup OBIEE 12c
Database is up and running
But running the start.cmd fails when starting Admin Server with this error message.
"""""
Starting AdminServer ...
Unable to connect to AdminServer on host: ***********
Failed to start one or more Servers
/Servers/AdminServer/ListenPort=9500
Accessing admin server using URL t3://*************
Start Admin Server connect Exception caught Error occurred while performing connect : Error getting the initial context. There is no server running at t3://************* : Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3://*************: Destination **********, 9500 unreachable.; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.
Use dumpStack() to view the full stacktrace :
Reading domain...
Error: runCmd() failed. Do dumpStack() to see details.
Failed to get Status of Servers and System Components
"""""
Start.cmd error message
Also, trying to check the status come up with this error.
"""""
Start Admin Server connect Exception caught Error occurred while performing connect : Error getting the initial context. There is no server running at t3://************* : Failed to initialize JNDI context, tried 2 time or times totally, the interval of each time is 0ms.
t3://*************: Destination 10.10.3.88, 9500 unreachable.; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.
Use dumpStack() to view the full stacktrace :
Reading domain...
Error: runCmd() failed. Do dumpStack() to see details.
Problem invoking WLST - Traceback (innermost last):
File "F:\Middleware\bi\modules\oracle.bi.sysman\scripts\status_servers.py", line 29, in ?
File "F:\Middleware\bi\modules\oracle.bi.sysman\scripts\process_control.py", line 581, in statusComponents
File "F:\Middleware\bi\modules\oracle.bi.sysman\scripts\process_control.py", line 455, in outputComponentsStatus
File "F:\Middleware\bi\modules\oracle.bi.sysman\scripts\process_control.py", line 243, in connectAdminServer
File "F:\Middleware\bi\modules\oracle.bi.sysman\scripts\process_control.py", line 179, in requestCredentialsAndConnectToAdminServer
File "F:\Middleware\bi\modules\oracle.bi.sysman\scripts\process_control.py", line 513, in getAdminServerUrl
File "C:\Users\Administrator\AppData\Local\Temp\1\WLSTOfflineIni5666259588766029647.py", line 131, in readDomain
File "C:\Users\Administrator\AppData\Local\Temp\1\WLSTOfflineIni5666259588766029647.py", line 19, in command
60713: Attempt to execute command "readDomain" in invalid state: Configuration
"""""
STATUS ERROR MESSAGE
Impala not working in cloudera-quickstart-vm-5.10 as Impala Daemon is not starting.
Following is the status of the three required roles for Impala:
Impala Daemon is down
Impala Catalog Server has bad health &
Impala StateStore has good health
Getting following error messages:
Jul 22, 9:57:33.262 AM ERROR impala-server.cc:252
Could not read the root directory at hdfs://quickstart.cloudera:8020. Error was: Call From quickstart.cloudera/127.0.0.1 to quickstart.cloudera:8020 failed on connection exception: java.net.ConnectException: Connection refused; For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
Jul 22, 9:57:33.262 AM ERROR impala-server.cc:255
Aborting Impala Server startup due to improper configuration. Impalad exiting.
Tried restarting the service through command line.
[cloudera#quickstart ~]$ sudo service impala-server restart
Stopped Impala Server: [ OK ]
Started Impala Server (impalad): [ OK ]
[cloudera#quickstart ~]$ service impala-server status
Impala Server is dead and pid file exists [FAILED]
Still it is not working.
Not sure if I can do some configuration changes for it or not. If so, could not find what exactly can be changed for it to work.
I'm trying to start the Standalone Agent Using Node Manager with this tutorial: https://docs.oracle.com/en/middleware/data-integrator/12.2.1.3/tutorial-creating-standalone-agent/#StartingtheStandaloneAgentUsingNodeManager
(Windows)
Node manager has been started with command:
startNodeManager.cmd
But can't start the agent OracleDIAgent1 with command:
startComponent.cmd OracleDIAgent1
Full output:
Please enter Node Manager password:
Connecting to Node Manager ...
<Jan 15, 2019 4:54:57 PM MSK> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.>
<Jan 15, 2019 4:54:57 PM MSK> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.>
<Jan 15, 2019 4:54:58 PM MSK> <Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation: weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.>
This Exception occurred at Tue Jan 15 16:54:58 MSK 2019.
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
Error: Error occurred while performing nmConnect : Cannot connect to Node Manager. : Unrecognized SSL message, plaintext connection?
Use dumpStack() to view the full stacktrace :
Exiting WebLogic Scripting Tool.
Done
File nodemanager.properties has SecureListener off:
SecureListener=false
Please help to start agent. Thanks a lot in advanced.
Stop your node manager then try to change the value as "SecureListener=false" and in the console, verify the node manager protocol is "plain". Restart your node manager.
Today I configured a basic tinyproxy.
I expected it to act as proxy for ubuntu repositories.
But when trying to download stuff from repositories I got this on tinyproxy log
CONNECT Mar 27 17:30:46 [20348]: Connect (file descriptor 9): [unknown] [192.168.2.30]
CONNECT Mar 27 17:30:46 [20348]: Request (file descriptor 9): GET http://br.archive.ubuntu.com/ubuntu/pool/main/t/tdb/python-tdb_1.2.12-1_amd64.deb HTTP/1.1
INFO Mar 27 17:30:46 [20348]: No upstream proxy for br.archive.ubuntu.com
ERROR Mar 27 17:30:56 [20348]: opensock: Could not retrieve info for br.archive.ubuntu.com
INFO Mar 27 17:30:56 [20348]: no entity
I stuck on some misconcept. Do not tinyproxy send requests for outside servers directly?
I supllied an external proxy server to fix this
upstream 117.79.64.29:80
I'm trying to setup Hudson on a Windows server.
When I attempt to run Hudson with the command java -jar hudson.war, then I receive an error that the address is already in use for the HTTP listener.
I've confirmed that port 8080 (the default Hudson HTTP port) is not being used. I have also tried starting Hudson on another port (java -jar hudson.war --httpPort=8888) with the same error.
If I browse to http://localhost:8080, then I get an 'It works!' message on the web page. However, if I browse to http://localhost:8080/hudson, I receive a 404 error.
Here is log:
D:\hudson>java -jar hudson.war
Running from: D:\hudson\hudson.war
[Winstone 2010/10/27 11:07:47] - Beginning extraction from war file
hudson home directory: C:\Documents and Settings\scottk\.hudson
[Winstone 2010/10/27 11:07:54] - Error during HTTP listener init or shutdown
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.bind(Unknown Source)
at java.net.ServerSocket.<init>(Unknown Source)
at java.net.ServerSocket.<init>(Unknown Source)
at winstone.HttpListener.getServerSocket(HttpListener.java:102)
at winstone.HttpListener.run(HttpListener.java:116)
at java.lang.Thread.run(Unknown Source)
[Winstone 2010/10/27 11:07:54] - HTTP Listener shutdown successfully
[Winstone 2010/10/27 11:07:54] - AJP13 Listener started: port=8009
Using one-time self-signed certificate
[Winstone 2010/10/27 11:07:54] - Winstone Servlet Engine v0.9.10 running: controlPort=disabled
Oct 27, 2010 11:07:55 AM hudson.model.Hudson$4 onAttained
INFO: Started initialization
Oct 27, 2010 11:07:56 AM hudson.model.Hudson$4 onAttained
INFO: Listed all plugins
Oct 27, 2010 11:07:56 AM hudson.model.Hudson$4 onAttained
INFO: Prepared all plugins
Oct 27, 2010 11:07:56 AM hudson.model.Hudson$4 onAttained
INFO: Started all plugins
Oct 27, 2010 11:07:57 AM hudson.model.Hudson$4 onAttained
INFO: Loaded all jobs
Oct 27, 2010 11:08:01 AM hudson.model.Hudson$4 onAttained
INFO: Completed initialization
Oct 27, 2010 11:08:01 AM hudson.TcpSlaveAgentListener <init>
INFO: JNLP slave agent listener started on TCP port 1162
Port 8080 is not being used:
D:\>netstat -o
Active Connections
Proto Local Address Foreign Address State PID
TCP dev1:1038 dev1.GCCU.local:15003 ESTABLISHED 1668
TCP dev1:1142 dev1.GCCU.local:1143 ESTABLISHED 1668
TCP dev1:1143 dev1.GCCU.local:1142 ESTABLISHED 1668
TCP dev1:1144 dev1.GCCU.local:1145 ESTABLISHED 1668
TCP dev1:1145 dev1.GCCU.local:1144 ESTABLISHED 1668
TCP dev1:15003 dev1.GCCU.local:1038 ESTABLISHED 1316
TCP dev1:1081 172.16.1.7:1000 ESTABLISHED 2100
TCP dev1:1127 app1.gccu.local:netbios-ssn ESTABLISHED 4
TCP dev1:1129 gccufs1.gccu.local:microsoft-ds ESTABLISHED 4
TCP dev1:1138 sql1.gccu.local:netbios-ssn ESTABLISHED 4
TCP dev1:1167 dc2.gccu.local:microsoft-ds TIME_WAIT 0
TCP dev1:ms-wbt-server devpc1.gccu.local:54699 ESTABLISHED 2916
I downloaded the latest .war file from http://hudson-ci.org/download/war/, specified port 8888 instead of 8080, and now it works. Looks like there must be something running on port 8080 and the version that I had tried to use earlier than 1.381 had an issue.