Can any one share their working /etc/graylg2.conf and
/etc/graylog2-elastcsearch.yml files.  for preview .8 support.

Regrads,
Sunu.

On Sat, Jan 4, 2014 at 11:45 AM, <[email protected]> wrote:

>   Today's Topic Summary
>
> Group: http://groups.google.com/group/graylog2/topics
>
>    - errros with 
> graylog2-server-0.20.0-preive.8<https://mail.google.com/mail/u/0/html/compose/static_files/blank_quirks.html#1435ec9ce8e87ed3_group_thread_0>[1
>  Update]
>    - Problems getting messages in to a new graylog2 server with
>    
> GELF/rsyslog<https://mail.google.com/mail/u/0/html/compose/static_files/blank_quirks.html#1435ec9ce8e87ed3_group_thread_1>[1
>  Update]
>
>  errros with 
> graylog2-server-0.20.0-preive.8<http://groups.google.com/group/graylog2/t/65ed11887c339d08>
>
>    Sunu <[email protected]> Jan 03 01:31PM -0800
>
>    I am seeing errros with graylog2-server-0.20.0-preive.8
>
>    I am running - java -jar graylog2-server.jar --debug and I am getting
>    this errors, please help.
>
>    2014-01-03 10:58:45,424 DEBUG: org.elasticsearch.transport.netty -
>    [graylog2-production] disconnected from
>    [[#zen_unicast_1#][inet[/172.24.1.55:9300]]]
>    2014-01-03 10:58:45,424 DEBUG: org.elasticsearch.discovery.zen -
>    [graylog2-production] filtered ping responses: (filter_client[true],
>    filter_data[false]) {none}
>    2014-01-03 10:58:45,426 DEBUG: org.elasticsearch.transport.netty -
>    [graylog2-production] connected to node
>    [[#zen_unicast_1#][inet[/172.24.1.55:9300]]]
>    2014-01-03 10:58:45,428 DEBUG:
>    org.elasticsearch.discovery.zen.ping.unicast
>    - [graylog2-production] [3] filtering out response from
>    [graylog2-production][RePqKcpDTq-BunBF9TSNaw][inet[/172.24.1.55:9300]],
>    not
>    same cluster_name [elasticsearch]
>    2014-01-03 10:58:46,926 DEBUG:
>    org.elasticsearch.discovery.zen.ping.unicast
>    - [graylog2-production] [3] filtering out response from
>    [graylog2-production][RePqKcpDTq-BunBF9TSNaw][inet[/172.24.1.55:9300]],
>    not
>    same cluster_name [elasticsearch]
>    2014-01-03 10:58:47,420 ERROR: org.graylog2.Main -
>
>    
> ################################################################################
>    ERROR: No ElasticSearch master was found.
>    Need help?
>    * Official documentation: http://support.torch.sh/help/kb
>    * Mailing list:
>    http://support.torch.sh/help/kb/general/forums-mailing-list
>    * Issue tracker: http://support.torch.sh/help/kb/general/issue-trackers
>    * Commercial support: http://www.torch.sh/
>    But we also got some specific help pages that might help you in this
>    case:
>    *
>
>    
> http://support.torch.sh/help/kb/graylog2-server/connecting-to-an-elasticsearch-cluster
>    Terminating. :(
>
>
>
>  Problems getting messages in to a new graylog2 server with 
> GELF/rsyslog<http://groups.google.com/group/graylog2/t/e6b0ad52d60b236c>
>
>    Jeff Schoolcraft <[email protected]> Jan 03 02:31PM -0500
>
>    Here are some examples (I copy/pasted from graylog2 and sanitized the
>    IP address):
>
>    2014-01-03 19:30:31.430 65.xx.xx.xx <38> Jan 3 14:30:30
>    managedapi-qa-node-2 sshd 10593 - - Failed password for invalid user magic
>    from 196.200.176.66 port 57342 ssh2
>    2014-01-03 19:30:31.428 65.xx.xx.xx <38> Jan 3 14:30:30
>    managedapi-qa-node-2 sshd 10593 - - Failed password for invalid user magic
>    from 196.200.176.66 port 57342 ssh2
>    2014-01-03 19:30:29.820 65.xx.xx.xx <84> Jan 3 14:30:28 node1-qa-api
>    sshd 22245 - - pam_unix(sshd:auth): check pass; user unknown
>    2014-01-03 19:30:29.815 65.xx.xx.xx <84> Jan 3 14:30:28 node1-qa-api
>    sshd 22245 - - pam_unix(sshd:auth): check pass; user unknown
>    2014-01-03 19:30:29.778 65.xx.xx.xx <84> Jan 3 14:30:28
>    managedapi-qa-node-2 sshd 10593 - - pam_unix(sshd:auth): check pass; user
>    unknown
>    2014-01-03 19:30:29.775 65.xx.xx.xx <84> Jan 3 14:30:28
>    managedapi-qa-node-2 sshd 10593 - - pam_unix(sshd:auth): check pass; user
>    unknown
>    2014-01-03 19:30:29.631 65.xx.xx.xx <38> Jan 3 14:30:28 node1-qa-api
>    sshd 22245 - - Failed password for invalid user magic from 196.200.176.66
>    port 42391 ssh2
>    2014-01-03 19:30:29.627 65.xx.xx.xx <38> Jan 3 14:30:28 node1-qa-api
>    sshd 22245 - - Failed password for invalid user magic from 196.200.176.66
>    port 42391 ssh2
>    2014-01-03 19:30:29.613 65.xx.xx.xx <38> Jan 3 14:30:28
>    managedapi-qa-node-2 sshd 10593 - - Failed password for invalid user magic
>    from 196.200.176.66 port 57342 ssh2
>    2014-01-03 19:30:29.609 65.xx.xx.xx <38> Jan 3 14:30:28
>    managedapi-qa-node-2 sshd 10593 - - Failed password for invalid user magic
>    from 196.200.176.66 port 57342 ssh2
>
>
>
>    --
>    Jeff Schoolcraft
>
>
>    On Friday, January 3, 2014 at 12:12 PM, Lennart Koopmann wrote:
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "graylog2" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to