Hi Friends,
when i tried to do streams i am getting this error. any idea.
The Graylog server encountered an error while trying to send an email. This
is the detailed error message: org.apache.commons.mail.EmailException:
Sending the email to the following server failed : smtp.gmail.com:465
(c
Hi Tokred,
Thanks a lot for your assist. I can find the Stream Rule setting that
you're mentioned. I can filter the source from thru the Stream now.
Once again thanks a lot.
On Tue, May 17, 2016 at 3:57 PM, wrote:
> Yes, add a rule that uses the "source" field to match on one of your
> Windows
Anyone have any thoughts?
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit
http
yeah, thats what linking is, exposing ports and pointing to the ip.
But here you can hit the tcp ports, but the nginx logs show connection
refused... something is not right.
On Thursday, 26 May 2016 13:06:23 UTC+2, Jirayut Nimsaeng wrote:
>
> No. I can confirm that both containers can access eac
On Thursday, 26 May 2016 17:20:44 UTC+2, Dennis Oelkers wrote:
>
> What happens when you do something like:
>
> curl -XPOST -u admin -v -H "Content-Type: application/json" -d
> '{"metrics": []}' http://localhost:12900/cluster/metrics/multiple
>
> looks good:
* Trying 127.0.0.1...
* Connected
Hi,
This appears to be more of an ElasticSearch question, rather than a
Graylog-specific question.
I'm going to guess that your ElasticSearch cluster doesn't have any
(primary) shards replicated to the other nodes in the cluster. When you
brought down one node, these shards were "lost" and El
Hey Pranay,
you need to make sure that the browser is able to access the Graylog server’s
REST API port directly, if you want the web interface to work.
Kr,
D.
> On 26.05.2016, at 17:47, Pranay Manwatkar wrote:
>
> ### Problem description
> I am unable to understand why browser is red
*### Problem description*
I am unable to understand why browser is redirecting the ELB request to
internal IP 12900.
What am I missing in configuration. I am getting this error as I blocked
the security group to access 12900 directly from browser host. What port I
need to add so that request doe
What happens when you do
curl -XPOST -u admin -v -H "Accept: application/json" -H "Content-Type:
application/json" -d '{"metrics": []}'
http://10.0.26.10:12900/system/metrics/multiple
on your server node itself?
Kr,
D.
> On 26.05.2016, at 15:55, kaiser wrote:
>
> Hello,
>
> I tried
What happens when you do something like:
curl -XPOST -u admin -v -H "Content-Type: application/json" -d '{"metrics":
[]}' http://localhost:12900/cluster/metrics/multiple
and
curl -XPOST -u admin -v -H "Content-Type: application/json" -H "Accept:
application/json” -d '{"metrics": []}'
http://l
Well the POST requests worked with authorization, but said it didnt
understand me. I tried with another api request that seemed to work fine
when I authenticate properly.
# curl -i -X GET http://localhost:12900/system/inputs -u admin
Enter host password for user 'admin':
HTTP/1.1 200 OK
X-Graylo
Hello,
I tried to setup the tls security for web and rest api.
Everything is ok; I managed to access the graylog-web but all inputs are
not running.
In my logs I have the following type of logs:
2016-05-05T13:38:03.685Z WARN [ProxiedResource] Unable to call
http://10.0.26.10:12900/system/me
Hi
Please find the attachment. I am getting this error while send test mail
pls advice
On Thursday, May 26, 2016 at 2:21:17 PM UTC+5:30, rvb n wrote:
>
> I am using ctlscript to configure mail . can you give some working sample
> config for mail alert pls
>
> On Thursday, May 26, 2016 at 11
> On 26.05.2016, at 10:53, Martin René Mortensen
> wrote:
> Exactly what its saying. but it doesnt make any sense.
> 2016-05-26T09:20:46.527+02:00 WARN [ProxiedResource] Unable to call
> http://localhost:12900/system/metrics/multiple on node
> , result: Service Unavailable
> 2016-05-26T09:20:4
No. I can confirm that both containers can access each others. because I
already exposed port 9000 and 12900
# in nginx container
root@nginx:/# telnet 172.17.0.1 9000
Trying 172.17.0.1...
Connected to 172.17.0.1.
Escape character is '^]'.
^]
telnet> quit
Connection closed.
root@nginx:/# telnet 17
- We run it on t2.medium. (4GB RAM, 2 cores)
- About 1 incoming message per second.
- tried 2.0.0 and now running 2.0.1
Anyone use Image in real world application? Graylog 2.0 image fails after
few days. Is this Image problem or Graylog in general?
It runs fine for about a week. After that ther
This command showing the attached error. pls help
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubscr...@googlegroups.com.
To view this discussion
2 separate containers dont have access to eachothers resrouces unless they
are linked. This would explain the connection refused.
Read all about it: https://docs.docker.com/compose/link-env-deprecated/
(this is the old method, for pre docker 1.10)
Brgds.
Martin
On Thursday, 26 May 2016 11:03:3
Hey Marius,
Thanks for your help now i am getting log from my pc . Now i tried to
configure email alert but not working
On Tuesday, May 24, 2016 at 8:16:06 PM UTC+5:30, Marius Sturm wrote:
>
> You want to configure your network security and not install another
> collector. Nxlog alone is suffi
Nginx is a completely separate container from the graylog. So no linked
container and nginx need to access to graylog with the graylog exposed
ports 9000 and 12900.
Jirayut
On Thursday, May 26, 2016 at 3:58:00 PM UTC+7, Martin René Mortensen wrote:
>
> I think your rest and web listen uri has t
Hi Jochen,
thanks a lot for your answer. It seems pipelines/rules can do the same.
However, I would have another question - is it possible to modify rules
outside of Graylog GUI, in other words is there documentation available so
I can work with rules from standalone script?
Thanks again.
Rega
I think your rest and web listen uri has to have port number configured.
Thats also the problem, there is no listener on the port you proxy to.
Is the nginx in a separate linked docker container? on the docker host? in
the graylog container? You have to expose the ports correctly if the nginx
i
On Thursday, 26 May 2016 10:33:03 UTC+2, Dennis Oelkers wrote:
>
> Hey Martin,
>
> > On 26.05.2016, at 09:19, Martin René Mortensen > wrote:
> >
> > After upgrading and reconfiguring my apache proxy for the new
> graylog-server 2.0.1 according to
> http://docs.graylog.org/en/2.0/pages/confi
I am using ctlscript to configure mail . can you give some working sample
config for mail alert pls
On Thursday, May 26, 2016 at 11:51:17 AM UTC+5:30, rvb n wrote:
>
> Thanks for the reply, There are Two config file to configure mail
> 1) graylog-settings.json
> 2) opt/graylog/conf# graylog.c
Hey Martin,
> On 26.05.2016, at 09:19, Martin René Mortensen
> wrote:
>
> After upgrading and reconfiguring my apache proxy for the new graylog-server
> 2.0.1 according to
> http://docs.graylog.org/en/2.0/pages/configuring_webif.html I can get it to
> login and see messages, but some pages a
Hi Trisha,
normally the ip of the appliance comes from the dhcp server in your
network. So I would start there and see why it is not providing an ip to
the appliance. There could be many reasons, e.g. wrong vswitch settings or
some firewall rules or whatever. Maybe some local admin could provide so
After upgrading and reconfiguring my apache proxy for the new
graylog-server 2.0.1 according to
http://docs.graylog.org/en/2.0/pages/configuring_webif.html I can get it to
login and see messages, but some pages are blank or wont load. In web
browser debug mode I can see
It seems that graylog
I'm using graylog2/server:2.0.1-2 docker image from here
https://hub.docker.com/r/graylog2/server/. So I'm going to do everything
behind the nginx reverse proxy with https to secure communication both web
interface and rest api. This is my nginx configuration
server {
listen 80;
server_name
28 matches
Mail list logo