I have a fresh opendistro cluster that works fine, but I try to disable some traces in log and there is one that I can't remove.
The lines of log look like this :
[2020-04-22T10:09:17,502][INFO ][stats_log ] [myhost01] ------------------------------------------------------------------------
Program=PerformanceAnalyzerPlugin
StartTime=1580542897.428
EndTime=Wed, 21 Apr 2020 10:09:17 CEST
Time=60074 msecs
Timing=total-time:60074.0/1
Counters=TotalError=0
EOE
It's clearly written by the PerformanceAnalyzer Plugin provided by opendistro, so I try to change the log config/log4j2.properties of this plugin and I've restarted the master (myhost01 in this example) but no change in log.
My question is : How to change the log level of this plugin?
Related
I am trying to use mmnormalize to structure text logs. Both with rsyslog 8.16.x and with 8.39.0 when trying to use mmnormalize as an action logs show that the module was not recognized. Below are details.
How can I set up to use mmnormalize with rsyslog?
remediation already tried
Installed separately liblognorm, libstr, json-c,libfastjson
Upgraded rsyslog from 8.16.x to 8.39.0
rsyslog .conf
module(load="mmnormalize") # text parsing
syslog log messages
Dec 3 11:33:55 sys1 systemd[1]: Starting System Logging Service...
Dec 3 11:33:55 sys1 systemd[1]: Started System Logging Service.
Dec 3 11:33:55 sys1 rsyslogd: could not load module 'mmnormalize',
errors: trying to load module /usr/lib/rsyslog/mmnormalize.so:
/usr/lib/rsyslog/mmnormalize.so: cannot open shared object file: No
such file or directory [v8.39.0 try http://www.rsyslog.com/e/2066 ]
Dec 3 11:33:55 sys1 rsyslogd: module name 'mmnormalize' is unknown
[v8.39.0 try http://www.rsyslog.com/e/2209 ]
Dec 3 11:33:55 sys1 rsyslogd: error during parsing file
/etc/rsyslog.d/52-tomcat.conf, on or before line 52: errors occured in
file '/etc/rsyslog.d/52-tomcat.conf' around line 52 [v8.39.0 try
http://www.rsyslog.com/e/2207 ]
The following way to install mmnormalize worked for me. I was running this on Ububutu (Xenial)
sudo apt-get install rsyslog-mmnormalize
Rich Megginson (thank you) answered as below to the same question I posted to rsyslog mailing list (rsyslog#lists.adiscon.com). As mentioned above it worked for me.
"On RHEL/CentOS/Fedora and similar platforms, the rsyslog-mmnormalize is a separate RPM that must be installed separately e.g.
yum install rsyslog rsyslog-mmnormalize ....
"
I have maven project, with the help of which I am trying to execute a jmx file, running JMeter with (jmeter-maven-plugin). I have the following console output
P E R F O R M A N C E T E S T S
[INFO] -------------------------------------------------------
[INFO] Invalid value detected for <postTestPauseInSeconds>. Setting pause to 0...
[INFO]
[INFO]
[INFO] Executing test: ZawyaJmeterTest.jmx
[INFO] Writing log file to: D:\tools\jmeter_examples\Example\jmeter-maven-example\target\jmeter\logs\ZawyaJmeterTest.jmx.log
[INFO] Error in NonGUIDriver java.lang.IllegalArgumentException: Problem loading XML from:'D:\tools\jmeter_examples\Example\jmeter-maven-example\target\jmeter\testFiles\ZawyaJmeterTest.jmx', missing class com.thoughtworks.xstream.converters.ConversionException: No field 'sentBytes' found in class 'org.apache.jmeter.samplers.SampleSaveConfiguration' : No field 'sentBytes' found in class 'org.apache.jmeter.samplers.SampleSaveConfiguration'
I thought in order to fix the issue org.apache.jmeter.samplers.SampleSaveConfiguration I tried to add SampleSaveConfiguration class in dependency
<dependency>
<groupId>org.apache.jmeter</groupId>
<artifactId>ApacheJMeter_core</artifactId>
<version>3.1</version>
</dependency>
But It did not helped in fact. Than I looked for problem No field 'sentBytes' found in class 'org.apache.jmeter.samplers.SampleSaveConfiguration', but in class SampleSaveConfiguration I found field private boolean sentBytes;
I do not know in what way search such issue.
When running JMeter test locally it is fine -
d:\tools\jmeter_examples\Example\jmeter-maven-example>jmeter -n -t D:\tools\jmeter_examples\Example\jmeter-maven-example\src\test\jmeter\ZawyaJmeterTest.jmx -l D:\tools\jmeter_examples\Example\jmeter-maven-example\target\jmeter\results\ZawyaJmeterTest.jtl
Writing log file to: d:\tools\jmeter_examples\Example\jmeter-maven-example\jmeter.log
Created the tree successfully using D:\tools\jmeter_examples\Example\jmeter-maven-example\src\test\jmeter\ZawyaJmeterTest.jmx
Starting the test # Wed Nov 30 17:26:53 EET 2016 (1480519613563)
Waiting for possible Shutdown/StopTestNow/Heapdump message on port 4445
Tidying up ... # Wed Nov 30 17:27:07 EET 2016 (1480519627819)
... end of run
Does anybody faced such issue? Or recommend some ways of the decision, please!!!
It seems that current version of jmeter-maven-plugin (2.0.3) lags a bit behind the JMeter versions (current is 3.1).
I had absolutely the same exception when tried to run my 3.1-versioned jmx. But, when I've recreated the jmx with JMeter GUI of version 2.13, it worked well with jmeter-maven-plugin of version 2.0.3.
Probably it is worth to downgrade your working version of JMeter.
Last version 2.6.0 of jmeter-maven-plugin now support last version of JMeter 3.3 and is now maintained by 2 persons among which one committer of Apache JMeter project so it now tightly follows JMeter releases.
See this on how to configure it:
https://wiki.apache.org/jmeter/JMeterMavenPlugin
https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/wiki/Basic-Configuration
All your issues should be fixed.
On starting TeamCity from URL, I get following error :
It was working fine till last week. And when opened today, it is showing error.
I logged in as administrator to view logs. Below is the stacktrace :
<pre>jetbrains.buildServer.processes.ProcessTreeTerminatorException: Process has not exited within 30 seconds
at jetbrains.buildServer.processes.ProcessTreeTerminatorImplBase.readCommandOutput(ProcessTreeTerminatorImplBase.java:159)
at jetbrains.buildServer.processes.ProcessTreeTerminatorImplBase.buildProcessTree(ProcessTreeTerminatorImplBase.java:315)
at jetbrains.buildServer.processes.ProcessTreeTerminatorImplBase.getProcessVisitor(ProcessTreeTerminatorImplBase.java:82)
at jetbrains.buildServer.processes.ProcessTreeTerminatorImplBase.getCurrentPid(ProcessTreeTerminatorImplBase.java:28)
at jetbrains.buildServer.processes.ProcessTreeTerminator$1.getCurrentPid(ProcessTreeTerminator.java:144)
at jetbrains.buildServer.processes.ProcessTreeTerminator.getCurrentPid(ProcessTreeTerminator.java:101)
at jetbrains.buildServer.maintenance.StartupProcessor.createPidFile(StartupProcessor.java:476)
at jetbrains.buildServer.maintenance.StartupProcessor.doInitialStage(StartupProcessor.java:326)
at jetbrains.buildServer.maintenance.StartupProcessor.processConcreteStage(StartupProcessor.java:83)
at jetbrains.buildServer.maintenance.StartupProcessor.processConcreteStageSafe(StartupProcessor.java:503)
at jetbrains.buildServer.maintenance.StartupProcessor.processTeamCityLifecycle(StartupProcessor.java:558)
at jetbrains.buildServer.maintenance.StartupProcessor.access$000(StartupProcessor.java:92)
at jetbrains.buildServer.maintenance.StartupProcessor$1.run(StartupProcessor.java:2)
at java.lang.Thread.run(Thread.java:745)
Some more information :
Current Startup State
Startup status
Current step: TeamCity server startup error
Next step: not defined yet
Data Directory
Data Directory path is not specified/detected yet
Database
Not connected to the database yet.
Versions
Software version: 722
Data directory version: unknown
Database version: unknown
Logs
Logs path: C:\TeamCity\logs
What should be done to resolve error?
As this is an EAP build, you should report this issue to JetBrains with complete information logs here
While running Jmeter in Ubuntu Amazon Instance, I am getting the following error--
ubuntu#ip-172-31-22-219:~/Jmeter/apache-jmeter-2.9/bin$ jmeter
[warning] /usr/bin/jmeter: Unable to locate commons-net in /usr/share/java
[warning] /usr/bin/jmeter: Unable to locate geronimo-activation-1.1-spec in /usr/share/java
[warning] /usr/bin/jmeter: Unable to locate geronimo-javamail-1.4-provider in /usr/share/java
[warning] /usr/bin/jmeter: Unable to locate jboss-j2ee in /usr/share/java
[warning] /usr/bin/jmeter: Unable to locate jdom1 in /usr/share/java
[warning] /usr/bin/jmeter: No JAVA_CMD set for run_java, falling back to JAVA_CMD = java
java.lang.Throwable: Could not access /usr/share/jmeter/lib/junit
at org.apache.jmeter.NewDriver.<clinit>(NewDriver.java:96)
An error occurred: Can't connect to X11 window server using 'localhost:0.0' as the value of the DISPLAY variable.
I don't know where exactly the problem is . Can any one please help?
Thanks,
Vimal
Seems like you are trying to start the GUI version of JMeter and not the NON GUI version.
If you want to run JMeter on the commandline, you can take a look at this page: http://developer.amd.com/community/blog/using-apache-jmeter-in-non-gui-mode/
jmeter -n -t MyTestPlan.jmx
-n ensures it runs in non-GUI mode.
You should see something like -
Created the tree successfully using Post Request.jmx
Starting the test # Mon Jun 02 16:10:44 IST 2014 (1401705644820)
Waiting for possible shutdown message on port 4445
Tidying up ... # Mon Jun 02 16:10:47 IST 2014 (1401705647509)
... end of run
Frontend developer desperately trying to get a WAMP running on Windows 7 (Home Premium, 64 bit, SP1). I've tried WAMPSERVER and XAMPP. Starting the Apache service failed on both, returning the exact same critical error in their error.log-files:
[Thu Dec 13 14:38:56.905257 2012] [mpm_winnt:crit] [pid 4868:tid 280]
(OS 109)The pipe has been ended. : AH00404: Child: Unable to read
socket data from parent
[Thu Dec 13 14:38:57.028264 2012] [mpm_winnt:crit] [pid 5100:tid 408]
AH00427: Parent: child process exited with status 3 -- Aborting.
I've googled for over 2 hours for this problem and have tried several things. Checking/freeing up Port 80, using a different port, turning off MSSE's real-time protection, disabling LMHOSTS Lookup, dozens of reinstalls... All to no avail.
Please help :(
Go to Control Panel -> Administrative Tools -> Services. Find "Web Deployment Agent Service" right click and stop. Start up Apache and see if it sticks. If so, right click on Web Deployment Agent again and go to properties and set the startup type to Manual.
In my case, the error log was this:
[crit] (OS 109)The pipe has been ended. : setup_inherited_listeners: Unable to read socket data from parent
The solution was that Apache was set to listen on IPv6 interface, but there was no IPv6 interface enabled.