Logstash does not show any output on windows with stdout

Elastic Stack Logstash
1

I am using logstash 2.3.4. I tried to parse a file and output it to stdout. Nothing fancy here. Given below is the config file

` input {
file {
path => "/c/logstash-2.3.4/input.txt"
start_position => "beginning"
ignore_older => 0
}
stdin {}
}

output {
stdout { }
}
`

Tried everything that is possible. Yet the output fails to appear. Please note that I have already tried everything specified in "Logstash not showing any output (SOLVED)"
I have deleted sincedb file
I have created new files as input files
I used stdin as another input source. THAT WORKS FINE

What am i missing with respect to text files. Or is logstash not optimised for Windows???

2

This path is on Windows? Please try "C:\logstash-2.3.4\input.txt" or "C:/logstash-2.3.4/input.txt"
Also, running logstash with --verbose will show you what's going on in the background.

3

Thanks
This works like a gem
I used /c/ as it works in the bash I am using in windows.

4

Hi,

I am facing the same issue on windows 7.

config file (test.conf):
input {
file {
path => "C:/ElasticSearch/logstash-2.3.4/userdata/sample_data"
start_position => "beginning"
sincedb_path => "NUL"
ignore_older => 0
}
}

output {
stdout {}
}

sample_data file (some random log):
Date , GPU Core Clock [MHz] , GPU Memory Clock [MHz] , GPU Temperature [°C] , Memory Used [MB] , GPU Load [%] , Memory Controller Load [%] , Video Engine Load [%] , VDDC [V] ,
2013-12-30 10:35:32 , 135.0 , 405.0 , 44.0 , 139 , 0 , 5 , 0 , 0.8870 ,
2013-12-30 10:35:33 , 135.0 , 405.0 , 43.0 , 139 , 0 , 5 , 0 , 0.8870 ,
2013-12-30 10:35:34 , 135.0 , 405.0 , 43.0 , 139 , 0 , 5 , 0 , 0.8870 ,
2013-12-30 10:35:35 , 135.0 , 405.0 , 43.0 , 139 , 0 , 5 , 0 , 0.8870 ,
2013-12-30 10:35:36 , 135.0 , 405.0 , 43.0 , 139 , 0 , 5 , 0 , 0.8870 ,

Following is the output from powershell:

PS C:\ElasticSearch\logstash-2.3.4> .\bin\logstash.bat -f .\bin\test.conf -v
io/console not supported; tty will not be manipulated
←[32mstarting agent {:level=>:info}←[0m
←[32mstarting pipeline {:id=>"main", :level=>:info}←[0m
Settings: Default pipeline workers: 2
←[32mRegistering file input {:path=>["C:/ElasticSearch/logstash-2.3.4/userdata/sample_data"], :level=>:info}←[0m
←[32mStarting pipeline {:id=>"main", :pipeline_workers=>2, :batch_size=>125, :batch_delay=>5, :max_inflight=>250, :level
=>:info}←[0m
Pipeline main started

My guess is, issue is due to path in windows. So I've tried
path => "C:\ElasticSearch\logstash-2.3.4\userdata\sample_data"
with no success.

Please help me out with it.

Thanks,
Abhishek

5

Try

logstash.bat agent -f test.conf --verbose

The --verbose switch will give your more info to troubleshoot.

6

Tried, but no success.
following is the command line output:

PS C:\ElasticSearch\logstash-2.3.4\bin> .\logstash.bat agent -f .\test.conf -v
io/console not supported; tty will not be manipulated
←[32mstarting agent {:level=>:info}←[0m
←[32mstarting pipeline {:id=>"main", :level=>:info}←[0m
Settings: Default pipeline workers: 2
←[32mRegistering file input {:path=>["C:/ElasticSearch/logstash-2.3.4/userdata/sample_data"], :level=>:info}←[0m
←[32mStarting pipeline {:id=>"main", :pipeline_workers=>2, :batch_size=>125, :batch_delay=>5, :max_inflight=>250, :level
=>:info}←[0m
Pipeline main started

Nothing appearing after it.

7

Try to remove this line in your config and run again.

8

I've removed 'ignore_older => 0' from config file and run, but no success.
If needed, I can share --debug output here (although it's very lengthy)

Thanks,
Abhishek

9

Below are what I got from running Logstash 2.3.3 with your config file and sample data

C:\ELK\logstash-2.3.3\bin>logstash.bat agent -f logstash.conf -r --verbose
io/console not supported; tty will not be manipulated
←[32mstarting agent {:level=>:info}←[0m
←[32mstarting pipeline {:id=>"main", :level=>:info}←[0m
Settings: Default pipeline workers: 2
←[32mRegistering file input {:path=>["C:/sample_data"], :level=>:info}←[0m
←[32mStarting pipeline {:id=>"main", :pipeline_workers=>2, :batch_size=>125, :batch_delay=>5, :max_inflight=>250, :l
evel=>:info}←[0m
Pipeline main started
←[33mReceived an event that has a different character encoding than you configured. {:text=>"Date , GPU Core Clock [
MHz] , GPU Memory Clock [MHz] , GPU Temperature [\\xB0C] , Memory Used [MB] , GPU Load [%] , Memory Controller Load
[%] , Video Engine Load [%] , VDDC [V] ,\\r", :expected_charset=>"UTF-8", :level=>:warn}←[0m
2016-08-01T21:58:11.023Z PC-NAME Date , GPU Core Clock [MHz] , GPU Memory Clock [MHz] , GPU Temperature [\xB0C] , M
emory Used [MB] , GPU Load [%] , Memory Controller Load [%] , Video Engine Load [%] , VDDC [V] ,\r
2016-08-01T21:58:11.025Z PC-NAME 2013-12-30 10:35:32 , 135.0 , 405.0 , 44.0 , 139 , 0 , 5 , 0 , 0.8870 ,
2016-08-01T21:58:11.028Z PC-NAME 2013-12-30 10:35:33 , 135.0 , 405.0 , 43.0 , 139 , 0 , 5 , 0 , 0.8870 ,
2016-08-01T21:58:11.028Z PC-NAME 2013-12-30 10:35:34 , 135.0 , 405.0 , 43.0 , 139 , 0 , 5 , 0 , 0.8870 ,
2016-08-01T21:58:11.029Z PC-NAME 2013-12-30 10:35:35 , 135.0 , 405.0 , 43.0 , 139 , 0 , 5 , 0 , 0.8870 ,

Try to run your config on an older version of Logstash to see if it helps.

10

It is working fine now.

Problem was with file name extension, I've created data file(sample_data) using notepad that appends .txt in file name. I am from Unix background, so mostly used vi editor. silly mistake :frowning:
sorry for chaos.

Cheers,
Abhishek