I'm trying to create a new domain (Weblogic 12.2.1.2.0, Database 12.1.0.2, Jdk 1.8.0_191, SUSE Linux Enterprise Server 11 SP4) but i'm facing the error below:
cfgfwk-64254 error occurred in security processing phase execution
Encoutered error, traceback (innermost last):
File "<iostream>", Line 51,in ?
File "~Oracle_Home/wlserver/common/wlst/modules/jython-modules.jar/Lib/socket$py.class" ,
line338, in gethostname
gaierror (20001,'getaddrinfo failed')
Have you any idea about the cause of this problem.
Thanks in advance.
Related
I built a new Motoko (or ICP) project using dfx command. For the first time, it started and deployed successfully.
Then I suddenly closed the first terminal which I ran the dfx start command. Then try to restart it again but this error message is appeared:
hread 'main' panicked at 'Error creating persistent pool at: "/root/.local/share/dfx/network/local/state/replicated_state/node-100/ic_consensus_pool/consensus". Error: IO error: While lock file: /root/.local/share/dfx/network/local/state/replicated_state/node-100/ic_consensus_pool/consensus/LOCK: Resource temporarily unavailable', artifact_pool/src/rocksdb_pool.rs:222:25 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
Any idea to resolve this issue?
Hii I am facing issue while connecting to weblogic server. The command i used to connect to it is as follows:
java -Dweblogic.security.SSL.ignoreHostnameVerification=true -
Djava.security.egd=file:/dev/./urandom -DUseSunHttpHandler=true -
Djava.net.preferIPv4Stack=true -Djava.awt.headless=true -
Dsun.jnu.encoding=ISO-8859-1 -Dfile.encoding=ISO-8859-1 weblogic.WLST
<path>/weblogic_configuration_domain_update.py <path>/weblogic-
domain.properties
It gives following error:
javax.naming.CommunicationException [Root exception is
java.net.ConnectException: t3://<IP>:<port>: Destination
unreachable; nested exception is: java.net.ConnectException: Connection
refused; No available router to destination]
Problem invoking WLST - Traceback (innermost last):
File "/<path>/weblogic_configuration_domain_update.py", line 134, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : Error getting the
initial context. There is no server running at t3://<IP>:<port>
Please let me know is there any way to resolve this issue. Thank you in advance.
you have to insert the correct values in the script: weblogic_configuration_domain_update.py
for example: connect(t3://thelisteingadressofthehost.network.com:thelisteningportoftheAdminServer)
and be sure which protocol you are using t3 or t3s...
https://docs.oracle.com/cd/E13222_01/wls/docs92/config_scripting/reference.html
Open terminal and add mentioned below variable JVM_ARGS
[oracle#node1 bin]$ set JVM_ARGS="-Dprod.props.file='${WL_HOME}'/.product.properties ${WLST_PROPERTIES} ${JVM_D64} ${UTILS_MEM_ARGS} ${COMMON_JVM_ARGS} ${CONFIG_JVM_ARGS} -Dweblogic.security.TrustKeyStore=DemoTrust"
[oracle#node1 bin]$ wlst.sh
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline>
I am getting a error when i run this rabbitmqserver.php file.
i googled and i couldn't find the answer.
I have all the libraries installed and i added the extension=amqp.so in the php5/cli file.
the error reads as:
PHP Fatal error: Failed to start request processor: exception 'AMQPConnectionException' with message 'Library error: a socket error occurred - Potential login failure.' in /home/ozzy/git/rabbitmqphp_example/rabbitMQLib.inc:110
Stack trace:
#0 /home/ozzy/git/rabbitmqphp_example/rabbitMQLib.inc(110): AMQPConnection->connect()
#1 /home/ozzy/git/rabbitmqphp_example/testRabbitMQServer.php(35): rabbitMQServer->process_requests('requestProcesso...')
#2 {main} in /home/ozzy/git/rabbitmqphp_example/rabbitMQLib.inc on line 132
I went to localhost:15672 and add a user called test along with a password. then i went inside Virtual host and added a virtual host and it worked.
I got this error message when updating to IP 4.2.6:
Warning: require_once(Ip/script/run.php) [function.require-once]:
failed to open stream:
No such file or directory in /home/stenly/public_html/index.php on line 14
Fatal error: require_once() [function.require]:
Failed opening required 'Ip/script/run.php' (include_path='.:/usr/lib/php:/usr/local/lib/php')
in /home/stenly/public_html/index.php on line 14
What could have gone wrong and is there a solution to this as the website is an active and busy website?
I don't know how that could happen. But try to take Ip/script/run.php from downloaded archive (http://download.impresspages.org/ImpressPages_4_2_6.zip) and palce it on your server.
We are deploying on one of our server and we have below error.
ERROR: tooltwist.fip.FipException Unknown response from server: 500: Internal Server Error
Exception: tooltwist.fip.FipException: tooltwist.fip.FipException: Unknown response from server: 500: Internal Server Error
Looking at the FIP log, it shows:
Error installing batch: tooltwist.fip.FipException: Pre-commit command failed: protected/pre_commit.sh
tooltwist.fip.FipException: Pre-commit command failed: protected/pre_commit.sh
at tooltwist.fip.FipServer_updateExecuter.commitTransaction(FipServer_updateExecuter.java:309)
at tooltwist.fip.FipServer_updateExecuter.prepareUpdates_1_3(FipServer_updateExecuter.java:250)
at tooltwist.fip.FipServer_updateExecuter.executeUpdates(FipServer_updateExecuter.java:142)
at tooltwist.fip.FipServer.destination_installBatchOfFiles(FipServer.java:199)
at tooltwist.fip.jetty.InstallBatchServlet.doPost(InstallBatchServlet.java:134)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:530)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:426)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:931)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:361)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:867)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113)
at org.eclipse.jetty.server.Server.handle(Server.java:337)
at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:581)
at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1020)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:775)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:228)
at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:417)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:474)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:437)
at java.lang.Thread.run(Thread.java:662)
Any idea about the error?
Couple of suggestions:
1. Does the pre_commit.sh shell script exist on the server.
2. Does it have +x permissions?
If FIP was installed using the normal way, it should not cause an issue.
The fipserver initially saves files it receives on the destination server, but into temporary locations. Once all of the files have been received and saved it runs a three step process to complete the installation:
1. Run a script named protected/pre-commit.sh. The normal operation of this script is to shut down the web server.
2. For each new file:
a) move any existing file to .fip-rollback-xxxxxx/filename.
b) move the new file from it's temporary location to the correct location.
3. Run a script named protected/post-commit.sh. This most commonly restarts the server.
The pre and post commit scripts are user provided. They should should normally exit with a status of zero, as any other status indicates that an error has occurred.
As suggested in the previous answer, check that these scripts exist, and that they are executable. If this fails to solve your problem, insert debug into the scripts to determine where and why they are failing.