Problem Description
You want to produce smaller log files by configuring them to contain only error and warning messages, and not info messages. ...
Show More
Problem Description
You want to produce smaller log files by configuring them to contain only error and warning messages, and not info messages.
Solution
Edit the logging level in the logging.yml file, located in the C:\Talend\x.x.x\logserv\elasticsearch-2.4.0\config folder, and change the log level from INFO to WARN or ERROR.
Your updated file should look similar to this:
#es.logger.level: INFO
es.logger.level: WARN
rootLogger: ${es.logger.level}, console, file
logger:
# log action execution errors for easier debugging
action: DEBUG
# deprecation logging, turn to DEBUG to see them
deprecation: INFO, deprecation_log_file
# reduce the logging for aws, too much is logged under the default INFO
com.amazonaws: WARN
# aws will try to do some sketchy JMX stuff, but its not needed.
com.amazonaws.jmx.SdkMBeanRegistrySupport: ERROR
com.amazonaws.metrics.AwsSdkMetrics: ERROR
org.apache.http: WARN
Overview
Elasticsearch version 1.1.1 used in Talend Log Server has a security vulnerability issue, and this article proposes a solution to this i...
Show More
Overview
Elasticsearch version 1.1.1 used in Talend Log Server has a security vulnerability issue, and this article proposes a solution to this issue that impacts Talend products versions 5.4.x to 5.6.1.
For more information on this issue, please read the Security Issues page on the Elastic official website.
Environment
This article only applies to Talend products version between 5.4.x to 5.6.1.
Resolution
If you are running a Talend product with a version between 5.4.x and 5.6.1, and you have the Talend Log Server installed, you need to complete the following configuration changes to properly secure your system:
Create a file called elasticsearch.yml in your Talend Log Server installation directory (/Talend/version/Talend_logServer_dir).
Edit the file and add the following lines to disable dynamic scripting:
Symptoms
start_logserver.sh will not start, and displays the following behavior.
[user@system logserv]$ pwd
/apps/Talend-6.3.1/logserv
[user@sy...
Show More
Symptoms
start_logserver.sh will not start, and displays the following behavior.
The Elasticsearch service will appear to be running when the services are checked, but the Kibana and Logserver services will not start.
Diagnosis
The data/node that is actively being worked on has become corrupt.
Solution
Delete the node number by removing the corresponding folder located at \elasticsearch\nodes. After deleting the number from under nodes, Elasticsearch will recreate the nodes folder when starting the stack of ELK.