After I installed voltsql successfully, the following error occurred while executing voltsql
[whz#izbp16d6c3ttl701mgdkc7z voltdb]$ ./bin/voltsql
> SHOW tables;
Couldn't find log4j configuration file.
how to solve this problem ？
Related
I'm upgrading from SoapUI 5.4.0 to 5.7.0 and trying to put the log files in a specific directory. Note: The alternate error logs directory was working prior to the upgrade.
I have both the following specified in my JAVA_OPTS for SoapUITestCaseRunner
-Dsoapui.logroot="%SOAPUI_LOGSDIR%"
-Dsoapui.log4j.config="%SOAPUI_HOME%/soapui-log4j.xml"
In my soapui-log4j.xml I specify the error file as:
<RollingFile name="ERRORFILE"
fileName="${soapui.logroot}/soapui-errors.log"
filePattern="${soapui.logroot}/soapui-errors.log.%i"
append="true">
The error file then gets created without resolving ${soapui.logroot} e.g.
$ find . -name "*errors*"
./${soapui.logroot}/soapui-errors.log
I also tried it as lookup but ended up with this:
ERROR Unable to create file ${sys:soapui.logroot}/soapui-errors.log java.io.IOException: The filename, directory name, or volume label syntax is incorrect
Am I missing anything? Any ideas for next steps?
I tried replacing
fileName="${soapui.logroot}/soapui-errors.log"
with
fileName="${sys:soapui.logroot}/soapui-errors.log"
and it worked for me.
I no longer see unresolved '${soapui.logroot}' directory created.
A
I am trying to run logstash on windows.
using the following command -
logstash.bat -f D:\confignfig.txt --path.settings D:\Software\Elasticsearch\logstash-5.5.0\config\ -l LogstashLogs
But I get this error -
ERROR StatusLogger No log4j2 configuration file found. Using default
configuration: logging only errors to the console. WARNING: Could not
find logstash.yml which is typically located in $LS_HOME/config or
/etc/logstash. You can specify the path using --path.settings.
Continuing using the defaults An unexpected error occurred! :error =>
bad URI(is not URI?):
file:///D:\Software\Elasticsearch\logstash-5.5.0\config" -
LogstashLogs"/log4j2.properties, :backtrace =>
["D:/Software/Elasticsearch/logstash-5.5.0/vendor/jruby/lib/ruby/1.9/uri/common.rb:176:in
split",
"D:/Software/Elasticsearch/logstash-5.5.0/vendor/jruby/lib/ruby/1.9/uri/common.rb:210:in
parse",
"D:/Software/Elasticsearch/logstash-5.5.0/vendor/jruby/lib/ruby/1.9/uri/common.rb:747:in
parse",
"D:/Software/Elasticsearch/logstash-5.5.0/vendor/jruby/lib/ruby/1.9/uri/common.rb:994:in
URI",
"D:/Software/Elasticsearch/logstash-5.5.0/logstash-core/lib/logstash/logging/logger.rb:77:in
initialize", "org/jruby/ext/thread/Mutex.java:149:in synchronize'",
"D:/Software/Elasticsearch/logstash-5.5.0/logstash-core/lib/logstash/logging/logger.rb:75:in
initialize",
"D:/Software/Elasticsearch/logstash-5.5.0/logstash-core/lib/logstash/runner.rb:229:in
execute",
"D:/Software/Elasticsearch/logstash-5.5.0/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/command.rb:67:in
run",
"D:/Software/Elasticsearch/logstash-5.5.0/logstash-core/lib/logstash/runner.rb:209:in
run",
"D:/Software/Elasticsearch/logstash-5.5.0/vendor/bundle/jruby/1.9/gems/clamp-0.6.5/lib/clamp/command.rb:132:in
run",
"D:\Software\Elasticsearch\logstash-5.5.0\lib\bootstrap\environment.rb:71:in
(root)"]
Any idea what is going here? Any suggestion will be much appreciated.
This seems to be a known issue and is expected to get fixed in next logstash release , 5.6.0.
Pls refer: https://discuss.elastic.co/t/logstash-5-5-0-error-statuslogger-no-log4j2-configuration-file-found/92921
https://github.com/elastic/logstash/issues/7526
Running logstash from root folder fixed this. I don't know if this is known issue or not but if you run logstash from bin folder you might get 'ERROR StatusLogger No log4j2 configuration file found'
This is just for future reference since I solved it myself.
When I switched from logstash 2.x to 5.x, I was dealing with this warning (when I was runnig my logstash on this path D:\somepath\logstash-5.0.1):
Could not find log4j2 configuration at path /somepath/logstash-5.0.1/config/log4j2.properties. Using default config which logs to console
After some searching on internet and digging in ruby code (in the extracted logstash) I have found out this:
necessary to use path.settings (as mentioned many times) correctly
use correctly file or directory as URL path.
Finally I run my logstash as:
logstash.bat --path.settings=file://D:/somepath/logstash-5.0.1/config
I'm trying to convert JSCover to cobertura xml.
Based on what i've read the command is as follows:
java -cp JSCover-all.jar jscover.report.Main --format=COBERTURAXML REPORT-DIR SRC-DIRECTORY
But I get an error
"Error: Could not find or load main class jscover.report.Main"
Even if I set the fully qualified path of there the JSCover-all.jar is located.
So I tried including the JSCover-al.jar into the classpath and run the following command instead:
java -cp jscover.report.Main --format=COBERTURAXML target/local-storage-proxy target/local-storage-proxy/original-src
I no longer get the first error but i'm now getting the following error:
Unrecognized option: --format=COBERTURAXML
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
I hope someone could help me with it. Many thanks!
The first attempt is the correct approach. The error means that JSCover-all.jar is not in the same directory that you are executing the command from. An absolute path to is not needed - a relative one will do.
In the second approach, you have passed 'jscover.report.Main' as the class-path to the JVM and '--format=COBERTURAXML' as parameter to the 'java' command.
I'm trying to get slf4j 1.7.7 to use log4j 2.0.2 as its implementation. I think I have all the necessary JARs in my WAR and the log4j.xml just gets dropped into the classes directory, but when my webapp starts up, it can't locate the log4j.xml. When I crack open the WAR, I can see it in the WEB-INF/classes, so it should be on the classpath. What am I missing?
meta-inf/manifest.mf
index.html
...
WEB-INF/web.xml
WEB-INF/classes/log4j.xml
...
WEB-INF/lib/log4j-api-2.0.2.jar
...
WEB-INF/lib/slf4j-api-1.7.7.jar
...
WEB-INF/lib/log4j-core-2.0.2.jar
WEB-INF/lib/log4j-slf4j-impl-2.0.2.jar
...
Jetty has this in its stderrout.log file, recording its disappointment...
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
Well that is subtle. log4j-core-2.0.2 isn't looking for log4j.xml, its looking for log4j2.xml. The FAQ page http://logging.apache.org/log4j/2.x/faq.html has, in bold, "By default, Log4j looks for a configuration file named log4j2.xml (not log4j.xml) in the classpath." Renaming my file to log4j2.xml gets it found. Now I've got to make it correct.
2014-10-24 10:34:53,542 ERROR Unknown object "property" of type org.apache.logging.log4j.core.config.Property is ignored.
2014-10-24 10:34:53,545 ERROR Unknown object "logger" of type org.apache.logging.log4j.core.config.LoggerConfig is ignored.
2014-10-24 10:34:53,546 ERROR Unknown object "root" of type org.apache.logging.log4j.core.config.LoggerConfig is ignored.