Hello Cornelius,
I am totally ashamed right now. The thing is having to search within even 2
hours got me results. I made a fool out of myself :|
thanks for pointing that out and thanks to all those who helped with this
issue. I would be grateful if anyone can point me to any resource
regard
Hello Joe,
seems as if your search-window is too small (only 5 minutes back). What
happens, if you switch to "Search in all messages"?
regards, Cornelius
On Sunday, June 29, 2014 3:15:52 PM UTC+2, Joseph DJOMEDA wrote:
>
> Hello All,
>
> Anybody on the rescue? I am on the verge on giving up. I
Hello All,
Anybody on the rescue? I am on the verge on giving up. I am not sure what
exactly is wrong with my setup. I was going to push this for official use
but with these entry level obstacles , I have not been able to appreciate
all graylog2 has to offer.
Thanks to all those who tried to h
Hello All
Sorry for the late response. I have travelled. I have added logstash user
and group and added logstash to adm group. I verified I could open (less
and nano) the log files . For some reason I could still see the line:
_discover_file_glob: /var/lib/tomcat7/b_log.log: glob is: [] {:
You don't need GELF TCP input, 'cause logstash sends GELF over UDP.
_discover_file_glob: /var/lib/tomcat7/b_log.log: glob is: [] {:level=>:debug,
:file=>"filewatch/watch.rb", :line=>"117"}
The message "glob is: []" in most cases means that logstash process does
not have permissions to read file.
Hi Thanks for the feedback and your effort.
Did you explicitly created a tcp gelf input?
On Thursday, May 29, 2014 12:26:26 PM UTC, Dmitri Stoljarov wrote:
>
> Joseph,
>
> You cannot telnet to UDP port (your netstat shows only udp port).
>
> Here's my output:
>
> $ netstat -ano | grep 12201 |gre
Joseph,
You cannot telnet to UDP port (your netstat shows only udp port).
Here's my output:
$ netstat -ano | grep 12201 |grep -v ESTAB
tcp0 0 0.0.0.0:12201 0.0.0.0:*
LISTEN off (0.00/0/0)
udp0 0 0.0.0.0:12201
0.0.0.0:
Hello Arkadiy ,
thanks for your effort my answers *inline*
On Monday, 26 May 2014 06:31:13 UTC, Arkadiy Shinkarev wrote:
>
> Hi!
> You can also check this things:
> 1. Is logstash process user has properly permissions to read Tomcat's log?
>
*Yes *
> 2. Is SELinux enabled?
>
*~/graylog2-web
Hi!
You can also check this things:
1. Is logstash process user has properly permissions to read Tomcat's log?
2. Is SELinux enabled?
2. Is iptables running? Is there accept rules for GELF input?
--
Sincerely,
Arkadiy Shinkarev
e-mail: kewa...@gmail.com
Cell.: +7 (926) 147-51-87
2014-05-25 22
Hello I have tried your example and even tried java log of a different
application on a totally different box and still I can't see anything on
graylog. Is there really something I am not doing right? I have this time
used the grokdebug.herokuapp.com application to check my patterns.
with debug
You have an error in grok pattern, try this one:
%{DATESTAMP:datestamp} %{LOGLEVEL:loglevel} \[%{GREEDYDATA:thread}\]
\[%{GREEDYDATA:classinfo}\] %{GREEDYDATA:loginfo}
Later, you can use Grok Debugger - http://grokdebug.herokuapp.com/
On Saturday, April 19, 2014 4:19:57 PM UTC+4, Joseph DJOMEDA
Hello Kay,
So sorry I could not get back to you this time only. I have check firewall
etc. Added a global GELF UDP input but still not seeing any thing and still
seeing:
*_discover_file_glob: /opt/tomcatinstances/my_app/logs/catalina.out: glob
is: ["/opt/tomcatinstances/my_app/logs/catalina
Hi Joseph!
Is the GELF UDP input running properly on the server with the .112 ip?
You need to configure it first, it is not starting automatically.
Then everything should be working.
Best,
Kay
On Saturday, April 19, 2014 2:19:57 PM UTC+2, Joseph DJOMEDA wrote:
>
> Hello Good People,
>
> I am co
13 matches
Mail list logo
