Hello,compile_imperative'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:49:in compile_graph'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:11:in block in compile_sources'", "org/jruby/RubyArray.java:2580:in map'", "/usr/share/logstash/logstash-core/lib/logstash/compiler.rb:10:in compile_sources'", "org/logstash/execution/AbstractPipelineExt.java:161:in initialize'", "org/logstash/execution/JavaBasePipelineExt.java:47:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:27:in initialize'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:36:in execute'", "/usr/share/logstash/logstash-core/lib/logstash/agent.rb:326:in block in converge_state'"]}
but when i run it with /usr/share/logstash/bin/logstash --path.settings /etc/logstash -f /etc/logstash/conf.d/02-input-beats it works
additional information:
pipeline.id: beats-inputhttps://10.10.2.1:9200 "]
thanks again
i believe by default logstash will use /etc/logstash as path.settings in systemd based system. can you share the content of /etc/systemd/system/logstash.service and /etc/default/logstash ?
hello,
'''''''''''''''''''''''''''''''''''''''''''''''' /etc/systemd/system/logstash.service''''''''''''''''''''''''''''''''''''
[Service]
Load env vars from /etc/default/ and /etc/sysconfig/ if they exist.
Prefixing the path with '-' makes it try to load, but if the file doesn't
exist, it continues onward.
EnvironmentFile=-/etc/default/logstash
[Install]
ptamba
May 15, 2020, 11:16am
4
you should fix the permission issue rather than running logstash as root. however, i couldn’t find anything strange in your service config. do you happen to have path.config or path.setting in logstash.yml? logstash define main pipeline by default, and looks like your pipelines.yml is ignored because it doesn’t contain pipeline id “main” that your error refers to.
check logstash.yml to see if you have path.config uncommented.
i checked the logstash.yml and the path.config is uncommented
ptamba
May 15, 2020, 11:53am
6
can you show your logstash.yml?
Settings file in YAML
Settings can be specified either in hierarchical form, e.g.:
pipeline:
batch:
size: 125
delay: 5
Or as flat keys:
pipeline.batch.size: 125
pipeline.batch.delay: 5
------------ Node identity ------------
Use a descriptive name for the node:
node.name: test
If omitted the node name will default to the machine's host name
------------ Data path ------------------
Which directory should be used by logstash and its plugins
for any persistent needs. Defaults to LOGSTASH_HOME/data
path.data: /var/lib/logstash
------------ Pipeline Settings --------------
The ID of the pipeline.
pipeline.id: main
Set the number of workers that will, in parallel, execute the filters+outputs
stage of the pipeline.
This defaults to the number of the host's CPU cores.
pipeline.workers: 2
How many events to retrieve from inputs before sending to filters+workers
pipeline.batch.size: 125
How long to wait in milliseconds while polling for the next event
before dispatching an undersized batch to filters+outputs
pipeline.batch.delay: 50
Force Logstash to exit during shutdown even if there are still inflight
events in memory. By default, logstash will refuse to quit until all
received events have been pushed to the outputs.
WARNING: enabling this can lead to data loss during shutdown
pipeline.unsafe_shutdown: false
Set the pipeline event ordering. Options are "auto" (the default), "true" or "false".
"auto" will automatically enable ordering if the 'pipeline.workers' setting
is also set to '1'.
"true" will enforce ordering on the pipeline and prevent logstash from starting
if there are multiple workers.
"false" will disable any extra processing necessary for preserving ordering.
pipeline.ordered: auto
------------ Pipeline Configuration Settings --------------
Where to fetch the pipeline configuration for the main pipeline
path.config: /etc/logstash
Pipeline configuration string for the main pipeline
config.string:
At startup, test if the configuration is valid and exit (dry run)
config.test_and_exit: false
Periodically check if the configuration has changed and reload the pipeline
This can also be triggered manually through the SIGHUP signal
config.reload.automatic: false
How often to check if the pipeline configuration has changed (in seconds)
Note that the unit value (s) is required. Values without a qualifier (e.g. 60)
are treated as nanoseconds.
Setting the interval this way is not recommended and might change in later versions.
config.reload.interval: 3s
Show fully compiled configuration as debug log message
NOTE: --log.level must be 'debug'
config.debug: false
When enabled, process escaped characters such as \n and " in strings in the
pipeline configuration files.
config.support_escapes: false
------------ Module Settings ---------------
Define modules here. Modules definitions must be defined as an array.
The simple way to see this is to prepend each name with a -, and keep
all associated variables under the name they are associated with, and
above the next, like this:
modules:
- name: MODULE_NAME
var.PLUGINTYPE1.PLUGINNAME1.KEY1: VALUE
var.PLUGINTYPE1.PLUGINNAME1.KEY2: VALUE
var.PLUGINTYPE2.PLUGINNAME1.KEY1: VALUE
var.PLUGINTYPE3.PLUGINNAME3.KEY1: VALUE
Module variable names must be in the format of
var.PLUGIN_TYPE.PLUGIN_NAME.KEY
modules:
------------ Cloud Settings ---------------
Define Elastic Cloud settings here.
Format of cloud.id is a base64 value e.g. dXMtZWFzdC0xLmF3cy5mb3VuZC5pbyRub3RhcmVhbCRpZGVudGlmaWVy
and it may have an label prefix e.g. staging:dXMtZ...
This will overwrite 'var.elasticsearch.hosts' and 'var.kibana.host'
cloud.id:
Format of cloud.auth is: :
This is optional
If supplied this will overwrite 'var.elasticsearch.username' and 'var.elasticsearch.password'
If supplied this will overwrite 'var.kibana.username' and 'var.kibana.password'
cloud.auth: elastic:
------------ Queuing Settings --------------
Internal queuing model, "memory" for legacy in-memory based queuing and
"persisted" for disk-based acked queueing. Defaults is memory
queue.type: memory
If using queue.type: persisted, the directory path where the data files will be stored.
Default is path.data/queue
path.queue:
If using queue.type: persisted, the page data files size. The queue data consists of
append-only data files separated into pages. Default is 64mb
queue.page_capacity: 64mb
If using queue.type: persisted, the maximum number of unread events in the queue.
Default is 0 (unlimited)
queue.max_events: 0
If using queue.type: persisted, the total capacity of the queue in number of bytes.
If you would like more unacked events to be buffered in Logstash, you can increase the
capacity using this setting. Please make sure your disk drive has capacity greater than
the size specified here. If both max_bytes and max_events are specified, Logstash will pick
whichever criteria is reached first
Default is 1024mb or 1gb
queue.max_bytes: 1024mb
If using queue.type: persisted, the maximum number of acked events before forcing a checkpoint
Default is 1024, 0 for unlimited
queue.checkpoint.acks: 1024
If using queue.type: persisted, the maximum number of written events before forcing a checkpoint
Default is 1024, 0 for unlimited
queue.checkpoint.writes: 1024
If using queue.type: persisted, the interval in milliseconds when a checkpoint is forced on the head page
Default is 1000, 0 for no periodic checkpoint.
queue.checkpoint.interval: 1000
------------ Dead-Letter Queue Settings --------------
Flag to turn on dead-letter queue.
dead_letter_queue.enable: false
If using dead_letter_queue.enable: true, the maximum size of each dead letter queue. Entries
will be dropped if they would increase the size of the dead letter queue beyond this setting.
Default is 1024mb
dead_letter_queue.max_bytes: 1024mb
If using dead_letter_queue.enable: true, the directory path where the data files will be stored.
Default is path.data/dead_letter_queue
path.dead_letter_queue:
------------ Metrics Settings --------------
Bind address for the metrics REST endpoint
http.host: "127.0.0.1"
Bind port for the metrics REST endpoint, this option also accept a range
(9600-9700) and logstash will pick up the first available ports.
http.port: 9600-9700
------------ Debugging Settings --------------
Options for log.level:
* fatal
* error
* warn
* info (default)
* debug
* trace
log.level: info
path.logs: /var/log/logstash
------------ Other Settings --------------
Where to find custom plugins
path.plugins:
Flag to output log lines of each pipeline in its separate log file. Each log filename contains the pipeline.name
Default is false
pipeline.separate_logs: false
------------ X-Pack Settings (not applicable for OSS build)--------------
X-Pack Monitoring
#xpack .monitoring.enabled: false#xpack .monitoring.elasticsearch.username: logstash_system#xpack .monitoring.elasticsearch.password: password#xpack .monitoring.elasticsearch.hosts: ["https://es1:9200 ", "https://es2:9200 "]
an alternative to hosts + username/password settings is to use cloud_id/cloud_auth
#xpack .monitoring.elasticsearch.cloud_id: monitoring_cluster_id:xxxxxxxxxx#xpack .monitoring.elasticsearch.cloud_auth: logstash_system:password#xpack .monitoring.elasticsearch.ssl.certificate_authority: [ "/path/to/ca.crt" ]#xpack .monitoring.elasticsearch.ssl.truststore.path: path/to/file#xpack .monitoring.elasticsearch.ssl.truststore.password: password#xpack .monitoring.elasticsearch.ssl.keystore.path: /path/to/file#xpack .monitoring.elasticsearch.ssl.keystore.password: password#xpack .monitoring.elasticsearch.ssl.verification_mode: certificate#xpack .monitoring.elasticsearch.sniffing: false#xpack .monitoring.collection.interval: 10s#xpack .monitoring.collection.pipeline.details.enabled: true
X-Pack Management
#xpack .management.enabled: false#xpack .management.pipeline.id: ["main", "apache_logs"]#xpack .management.elasticsearch.username: logstash_admin_user#xpack .management.elasticsearch.password: password#xpack .management.elasticsearch.hosts: ["https://es1:9200 ", "https://es2:9200 "]
an alternative to hosts + username/password settings is to use cloud_id/cloud_auth
#xpack .management.elasticsearch.cloud_id: management_cluster_id:xxxxxxxxxx#xpack .management.elasticsearch.cloud_auth: logstash_admin_user:password#xpack .management.elasticsearch.ssl.certificate_authority: [ "/path/to/ca.crt" ]#xpack .management.elasticsearch.ssl.truststore.path: /path/to/file#xpack .management.elasticsearch.ssl.truststore.password: password#xpack .management.elasticsearch.ssl.keystore.path: /path/to/file#xpack .management.elasticsearch.ssl.keystore.password: password#xpack .management.elasticsearch.ssl.verification_mode: certificate#xpack .management.elasticsearch.sniffing: false#xpack .management.logstash.poll_interval: 5shttps://localhost:9200 "]
ptamba
May 15, 2020, 12:16pm
8
please use markdown when you post configuration. it’s hard to see which are being commented and which aren’t
wrap config with ```
i tried to post it in markdown, if not here the uncommented line on my logstash.yml by order
######################################https://localhost:9200 "]
ptamba
May 15, 2020, 1:11pm
10
comment this line and try again
system
June 12, 2020, 1:11pm
11
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.