While executing below command I am getting the below error
./tsdb mkmetric mymetric
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
Exception in thread "main" java.lang.ClassCastException: org.slf4j.impl.Log4jLoggerAdapter cannot be cast to ch.qos.logback.classic.Logger
at net.opentsdb.tools.CliOptions.honorVerboseFlag(CliOptions.java:161)
at net.opentsdb.tools.CliOptions.parse(CliOptions.java:82)
at net.opentsdb.tools.UidManager.main(UidManager.java:97)
As a workaround you can try by adding --verbose argument.
./tsdb mkmetric mymetric --verbose=class
Related
When Exchange imports Hive data, I get the following error:
Exception in thread "main" org.apache.spark.sql.AnalysisException: Table or view not found
Check whether the -h parameter is omitted in the command for submitting the NebulaGraph Exchange task and whether the table and database are correct, and run the user-configured exec statement in spark-SQL to verify the correctness of the exec statement.
What can the following be due to / how to debug it? it happens when closing my MPI application
[1612979755.727913] [compute-0-9:21112:0] tag_match.c:61 UCX WARN unexpected tag-receive descriptor 0x2b2bf64cdbc0 was not matched
Assuming the application exited normally, this probably means that some process sent a message (e.g. calling MPI_Send) to a destination process that did not post a matching receive before calling MPI_Finalize. See https://github.com/openucx/ucx/issues/6331#issuecomment-778428537
I have downloaded the corda example project: spring-observable-stream and try to run it from IntelliJ. While started the server, It gives error:
W 11:01:55 1 AnnotationConfigEmbeddedWebApplicationContext.refresh - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'nodeRPCConnection' defined in file [C:\Corda\spring-observable-stream\server\out\production\classes\net\corda\server\NodeRPCConnection.class]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [net.corda.server.NodeRPCConnection]: Constructor threw exception; nested exception is ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.]
You need to start the nodes before you start the servers. See the instructions here: https://docs.corda.net/tutorial-cordapp.html#running-the-example-cordapp.
I have had a similar issue with the cordapp-example on the Mac. I found that running the runnodes command in headless mode worked for me as per the instructions here: https://docs.corda.net/docs/corda-os/4.4/tutorial-cordapp.html#running-the-example-cordapp-2
I have a very simply Jython script over Unix. It was working perfectly during WebSphere 7 and now, after we upgraded to WAS 8.5 it isn't working anymore. Obviously, I changed the path to point to WAS8.5. I spent the whole day struglling to find the reason for this falling and I am completely stuck. The exception descrition doesn't help much.
From a JCL JOB I call the Jython script.
/WebSphere/was85/dtl85cel/ledm85nd/DeploymentManager/profiles/default/bin/wsadmin.sh -lang jython -f /WebSphereDevelopment/scripts/dtl/WAS85/Install.jy
The Jython script is really simple.
Basically, I call AdminApp.install("myEAR path", ...with the options below:
-nopreCompileJSPs -installed.ear.destination /WebSphereDevelopment/MYAPP/dtl/curr/deployment/ -distributeApp -nouseMetaDataFromBinary -nodeployejb -appname DVL-MYAPP -createMBeansForResources -noreloadEnabled -nodeployws -validateinstall warn -processEmbeddedConfig -filepermission ..dll=755#. .so=755#..a=755#.*.sl=755 -noallowDispatchRemoteInclude -noallowServiceRemoteInclude -asyncRequestDispatchType DISABLED -nouseAutoLink -contextroot / -MapModulesToServers ÝÝ MyApp MyApp.war,WEB-INF/web.xml WebSphere:cell=dtl85cel,node=wleMyAppa,server=WLEMYAPP¨¨
)
The error log is:
WASX7017E: Exception received while running file "/WebSphereDevelopment/scripts dtl/MYAPP/MYAPP_DTL_DEPLOY.jy"; exception information: com.ibm.websphere.management.application.client.AppDeploymentException: com.ibm.websphere.management.appliccation.client.AppDeploymentException: ÝRoot exception is java.lang.RuntimeException: Deploying /WebSphere/was85/dtl85cel/ledm85nd/DeploymentManager/profiles/d java.lang.RuntimeException: java.lang.RuntimeException: Deploying /WebSphere/wa s85/dtl85cel/ledm85nd/DeploymentManager/profiles/default/temp/app69105293327198772690.ear failed.
Turn on tracing under wsadmin.properties:
com.ibm.ws.scripting.traceString
Just trying to run a very simple word count example but getting the following null pointer when submitting the job:
oozie job -oozie=http://localhost:11000/oozie/ -config job.properties -run
[cloudera#localhost Oozie_Example]$ oozie job -oozie=http://localhost:11000/oozie/ -config job.properties -run
java.lang.RuntimeException: java.lang.NullPointerException
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1242)
at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2714)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:477)
at org.apache.oozie.client.OozieClient$JobSubmit.call(OozieClient.java:586)
at org.apache.oozie.client.OozieClient$JobSubmit.call(OozieClient.java:561)
at org.apache.oozie.client.OozieClient$ClientCallable.call(OozieClient.java:479)
at org.apache.oozie.client.OozieClient.run(OozieClient.java:655)
at org.apache.oozie.cli.OozieCLI.jobCommand(OozieCLI.java:918)
at org.apache.oozie.cli.OozieCLI.processCommand(OozieCLI.java:579)
at org.apache.oozie.cli.OozieCLI.run(OozieCLI.java:552)
at org.apache.oozie.cli.OozieCLI.main(OozieCLI.java:199)
Caused by: java.lang.NullPointerException
at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:106)
at sun.misc.CharacterEncoder.encode(CharacterEncoder.java:188)
at sun.net.www.protocol.http.NegotiateAuthentication.setHeaders(NegotiateAuthentication.java:156)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1482)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
... 8 more
java.lang.NullPointerException
here is my job properties file:
nameNode=hdfs://localhost:8020
jobTracker=localhost:8021
queueName=default
inputDir=${nameNode}/user/dev/oozie/workflow/wordcount/input/
outputDir=${nameNode}/user/dev/oozie/workflow/wordcount/output/
oozie.libpath=${nameNode}/user/oozie/workflow/wordcount/lib
oozie.use.system.libpath=true
user.name=dev
oozie.wf.application.path=${nameNode}/user/${user.name}/oozie/workflow/wordcount/
Any ideas? It happens pretty early so I think it has something to do with Oozie or namenode.
Would like to add to the answer of this question.
When oozie client got a NullPointerException, that usually means that request caused server thread failure. If you want to find out the "true" reason, you should look at the server log such as /var/log/oozie/oozie.log for CDH.
There you will find detailed stacktrace. That proved to be very helpful. At least in our case, it tells exactly what happened such as "a hdfs workflow file doesn't exist, blah..."
java.lang.NullPointerException is due to an error in your job.properties file.
Have you placed the workflow XML into HDFS? Also, you should specify:
oozie.wf.application.path=${nameNode}/user/${user.name}/oozie/workflow/wordcount/my-workflow.xml