[graylog2] Re: Graylog + AWS : Web Cluster broken

[Zach Stoddard]

I attached an an example of some of the behavior I observe. This is 
sporadic, and switches between one node at a time to all of the nodes for 
extended periods. However, the log reception is at a normal capacity.



On Monday, January 16, 2017 at 9:59:19 AM UTC-7, Zach Stoddard wrote:
>
> Struggling to maintain a web cluster behind a AWS Class load balancer.
>
> I manage to get the cluster master set up and working behind the Load 
> balancer (UI), and the Elasticsearch storage cluster works great.
>
> Trying to add additional web servers to cluster, has funny behavior. 
>
> When the REST API listener is set up on the Additional Web Servers, the 
> Node reporting starts being unstable, and eventually each server, including 
> master, will drop in and out of reporting, and occasionally one server will 
> permanently drop.
> When the REST API listener is not included in the setup, all is hunky dory 
> with cluster behavior. The functionality tied to the REST API is obviously 
> broken, and the LB can't see it for the same reason.
>
> We have another cluster configured in another environment using the same 
> commands and structure, but it has none of the issues this cluster has and 
> each server is running the Graylog 2.0 AMI.
>
> I have included our redacted config below:
>
>
> LB Health Check:
> 
> HTTP:12900/system/lbstatus
>
>
> Cluster Master Config:
> --
> graylog-ctl set-listen-address --service rest --address 
> http://0.0.0.0:12900/
> graylog-ctl set-listen-address --service web --address 
> http://0.0.0.0:9000/
> graylog-ctl set-listen-address --service transport --address 
> https://my-url.net:12900
> graylog-ctl set-external-ip https://my-url.net:12900
> graylog-ctl enforce-ssl
> graylog-ctl set-admin-password *
> graylog-ctl reconfigure-as-server
>
>
> Additional Web Servers (2)
> ---
> ** graylog-ctl set-listen-address --service rest --address 
> http://0.0.0.0:12900/
>
> graylog-ctl set-external-ip https://graylogweb-eu.insidesales.com:12900
> graylog-ctl enforce-ssl
> graylog-ctl set-admin-password *
> graylog-ctl set-cluster-master 10.20.100.21
> graylog-ctl reconfigure-as-server
>
>
>

-- 
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 
https://groups.google.com/d/msgid/graylog2/b5a84e17-b155-4620-b4a6-4cf4f29aa18e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: use elasticsearch not only for graylog

[Jochen Schalanda]

Hi Stefano,

On Monday, 16 January 2017 17:36:38 UTC+1, Stefano Tranquillini wrote:
>
> - what happens if i rename the cluster.name from 'graylog' to something 
> else?
>

Graylog will simply connect to the given Elasticsearch cluster. It will not 
automatically copy indices from the old cluster.

Cheers,
Jochen

-- 
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 
https://groups.google.com/d/msgid/graylog2/603df4e6-6a34-4f22-b1ee-01d82346d7b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Graylog + AWS : Web Cluster broken

[Zach Stoddard]

Struggling to maintain a web cluster behind a AWS Class load balancer.

I manage to get the cluster master set up and working behind the Load 
balancer (UI), and the Elasticsearch storage cluster works great.

Trying to add additional web servers to cluster, has funny behavior. 

When the REST API listener is set up on the Additional Web Servers, the 
Node reporting starts being unstable, and eventually each server, including 
master, will drop in and out of reporting, and occasionally one server will 
permanently drop.
When the REST API listener is not included in the setup, all is hunky dory 
with cluster behavior. The functionality tied to the REST API is obviously 
broken, and the LB can't see it for the same reason.

We have another cluster configured in another environment using the same 
commands and structure, but it has none of the issues this cluster has and 
each server is running the Graylog 2.0 AMI.

I have included our redacted config below:


LB Health Check:

HTTP:12900/system/lbstatus


Cluster Master Config:
--
graylog-ctl set-listen-address --service rest --address 
http://0.0.0.0:12900/
graylog-ctl set-listen-address --service web --address http://0.0.0.0:9000/
graylog-ctl set-listen-address --service transport --address 
https://my-url.net:12900
graylog-ctl set-external-ip https://my-url.net:12900
graylog-ctl enforce-ssl
graylog-ctl set-admin-password *
graylog-ctl reconfigure-as-server


Additional Web Servers (2)
---
** graylog-ctl set-listen-address --service rest --address 
http://0.0.0.0:12900/

graylog-ctl set-external-ip https://graylogweb-eu.insidesales.com:12900
graylog-ctl enforce-ssl
graylog-ctl set-admin-password *
graylog-ctl set-cluster-master 10.20.100.21
graylog-ctl reconfigure-as-server


-- 
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 
https://groups.google.com/d/msgid/graylog2/9e3c1950-74be-413e-ac4f-8f0bee9b2446%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: use elasticsearch not only for graylog

[Stefano Tranquillini]

Thanks,
so my strategy is to rename put them in the same cluster, and have replica 
1. so that the indices are spread to both VMs and once everything is green 
i can switch one of.
Now:
- is there a better strategy?
- what happens if i rename the cluster.name from 'graylog' to something 
else?

On Monday, January 16, 2017 at 4:48:40 PM UTC+1, Jochen Schalanda wrote:
>
> Hi Stefano,
>
> On Monday, 16 January 2017 16:20:35 UTC+1, Stefano Tranquillini wrote:
>>
>> Now, how bad is the idea to have just 1 elasticsearch (so stop the one in 
>> A and keep the one in B) for graylog and our searches? Is that a problem?
>>
>
> If your Elasticsearch cluster can handle the load of Graylog and your own 
> application(s), this should be fine. Graylog will not interfere with 
> non-managed indices.
>
>
> Cheers,
> Jochen
>

-- 
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 
https://groups.google.com/d/msgid/graylog2/63290a23-9773-477c-af8f-1db8a58eb657%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: use elasticsearch not only for graylog

[Jochen Schalanda]

Hi Stefano,

On Monday, 16 January 2017 16:20:35 UTC+1, Stefano Tranquillini wrote:
>
> Now, how bad is the idea to have just 1 elasticsearch (so stop the one in 
> A and keep the one in B) for graylog and our searches? Is that a problem?
>

If your Elasticsearch cluster can handle the load of Graylog and your own 
application(s), this should be fine. Graylog will not interfere with 
non-managed indices.


Cheers,
Jochen

-- 
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 
https://groups.google.com/d/msgid/graylog2/e26b01be-ebf7-4ab3-984a-1368d9836f2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] use elasticsearch not only for graylog

[Stefano Tranquillini]

Hi all,

Question: i've a server with several VMs and one contains elastic+graylog 
etc (let's call it A), then I've a second VM where there's another istance 
of elasticsearch used for other means (we do index documents for searches 
there) (let's call B).

Now, how bad is the idea to have just 1 elasticsearch (so stop the one in A 
and keep the one in B) for graylog and our searches? Is that a problem? 



-- 
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 
https://groups.google.com/d/msgid/graylog2/2e5e81a5-87e9-47ed-a406-34ca38a1a8b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: collector sidecar - Can't fetch configuration from Graylog API

[Scott LeFevre]

Jochen,

The uri http://:12900/ worked. 
Thanks!

On Monday, January 16, 2017 at 4:25:44 AM UTC-5, Jochen Schalanda wrote:
>
> Hi Scott,
>
> without knowing your Graylog configuration, the URI 
> http://:12900/api/ looks wrong. It should probably be either 
> http://:12900/ or http://:9000/api/, depending on 
> your Graylog configuration.
>
> Cheers,
> Jochen
>
> On Sunday, 15 January 2017 16:42:38 UTC+1, Scott LeFevre wrote:
>>
>> I've setup a graylog server running v2.1.2+50e449a and I'm successfully 
>> collecting using gelf and syslog.  This has been running very well for 
>> several months.  I'm now trying to get collector sidecar running on Windows 
>> and Linux servers.  I've installed sidecar v0.1.0-beta3 on a Windows 2016 
>> Server and Ubuntu 14.04 VMs.  I've followed the official documentation and 
>> created a two Collector Configurations and tagged them respectively with 
>> 'windows' and 'linux'.  
>>
>> When I run the collector-side from the command line on either system 
>> (windows or linux), I get the same error messages stating:
>> ERRO[0010] [UpdateRegistration] Bad response from Graylog server: 404 Not 
>> Found 
>> time="2017-01-15T10:23:44-05:00" level=error msg="[RequestConfiguration] 
>> Bad response status from Graylog server: 404 Not Found" 
>> time="2017-01-15T10:23:44-05:00" level=error msg="Can't fetch 
>> configuration from Graylog API: GET 
>> http://:12900/api/plugins/org.graylog.plugins.collector/a5e77211-e90e-4683-a1c0-ab9c9eabd5ef?tags=%5B%22linux%22%2C%22apache%22%5D:
>>  
>> 404 HTTP 404 Not Found"
>>
>> or
>>
>> time="2017-01-15T10:35:00-05:00" level=error msg="[UpdateRegistration] 
>> Bad response from Graylog server: 404 Not Found" 
>> time="2017-01-15T10:35:09-05:00" level=error msg="[RequestConfiguration] 
>> Bad response status from Graylog server: 404 Not Found"
>> time="2017-01-15T10:35:09-05:00" level=error msg="Can't fetch 
>> configuration from Graylog API: GET 
>> http://mon1.watsons.local:12900/api/plugins/org.graylog.plugins.collector/368ceb95-5cc3-4d8e-9179-5510d37484df?tags=%5B%22windows%22%5D:
>>  
>> 404 HTTP 404 Not Found"
>>
>> This appears to be a authentication issue but I can't find any way to 
>> setup the authentication.
>>
>> I've looked at my graylog server configuration and tried changing the 
>> sidecar configuration to match the "rest_listen_uri" in the sever config 
>> (i.e. http://:12900/) but it's made no difference.
>>
>> What am I missing to get this to work?
>>
>>

-- 
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 
https://groups.google.com/d/msgid/graylog2/c3faf90b-bb42-4b37-a62b-fb1d9a913e47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: What is the setup in the supplied graylog OVA

[Jochen Schalanda]

Hi,

please refer 
to 
http://docs.graylog.org/en/2.1/pages/installation/virtual_machine_appliances.html
 
and http://docs.graylog.org/en/2.1/pages/configuration/graylog_ctl.html for 
details about the virtual machine images.

Cheers,
Jochen

On Monday, 16 January 2017 11:11:30 UTC+1, Hyder wrote:
>
> Hello,
>
> I've downloaded and imported the supplied OVA image that is available 
> here.. 
> http://docs.graylog.org/en/2.1/pages/installation/virtual_machine_appliances.html
>
> What is the setup in the supplied Graylog OVA? (how many Elastic Search 
> nodes, Mongodb instances etc.?
>
> Regards,
>
> Hyder
>

-- 
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 
https://groups.google.com/d/msgid/graylog2/f66a50a9-aaa6-41fb-a9f6-fa7694a21c9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] What is the setup in the supplied graylog OVA

[Hyder]

Hello,

I've downloaded and imported the supplied OVA image that is available 
here.. 
http://docs.graylog.org/en/2.1/pages/installation/virtual_machine_appliances.html

What is the setup in the supplied Graylog OVA? (how many Elastic Search 
nodes, Mongodb instances etc.?

Regards,

Hyder

-- 
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 
https://groups.google.com/d/msgid/graylog2/041eb47c-ac96-4464-8347-6d44404e9119%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [graylog2] Re: mongodb_uri doesn't like multiple server urls?

[Jason Haar]

On Mon, Jan 16, 2017 at 10:24 PM, Jochen Schalanda 
wrote:

> please stick to the format explained in http://docs.graylog.org/en/
> 2.1/pages/configuration/multinode_setup.html#graylog-to-mongodb-connection
> and https://github.com/Graylog2/graylog2-server/blob/
> 2.1.2/misc/graylog.conf#L434-L442 for the mongodb_uri setting.
>
>

Groan - I now get it. That isn't a very nice format. For other people's
education, the format is meant to be

mongodb_uri = mongodb://username:password@
[host1:port,host2:port,host3:port]/database

...except that there are no brackets :-)


I did not find that intuitive, but that's the mongodb standard, so I'd
better get used to it :-)

Thanks!

-- 
Cheers

Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +1 408 481 8171
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1

-- 
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 
https://groups.google.com/d/msgid/graylog2/CAFChrgJRxUdGJ_eL6K44o3ZNrajiiaykASj8Gan1oBH%2BpHKqfw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: Can't open web console on host IP

[Jochen Schalanda]

Hi,

how did you configure Graylog?

By default, the Graylog REST API and the web interface will only to 
localhost (127.0.0.1).

Cheers,
Jochen

On Sunday, 15 January 2017 02:31:40 UTC+1, JayJay wrote:
>
> Hi,
> I just installed latest on CentOS7, and can open the web console on 
> 127.0.0.1:9000, but can't on the host IP: 10.10.10.10:9000 on the server 
> itself.
>
> Any idea what I missed in the installation?  Bind host IP url?
>
> Thanks!
>

-- 
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 
https://groups.google.com/d/msgid/graylog2/8b54e2cd-69dd-41af-830c-5b084f81b349%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: collector sidecar - Can't fetch configuration from Graylog API

[Jochen Schalanda]

Hi Scott,

without knowing your Graylog configuration, the URI 
http://:12900/api/ looks wrong. It should probably be either 
http://:12900/ or http://:9000/api/, depending on 
your Graylog configuration.

Cheers,
Jochen

On Sunday, 15 January 2017 16:42:38 UTC+1, Scott LeFevre wrote:
>
> I've setup a graylog server running v2.1.2+50e449a and I'm successfully 
> collecting using gelf and syslog.  This has been running very well for 
> several months.  I'm now trying to get collector sidecar running on Windows 
> and Linux servers.  I've installed sidecar v0.1.0-beta3 on a Windows 2016 
> Server and Ubuntu 14.04 VMs.  I've followed the official documentation and 
> created a two Collector Configurations and tagged them respectively with 
> 'windows' and 'linux'.  
>
> When I run the collector-side from the command line on either system 
> (windows or linux), I get the same error messages stating:
> ERRO[0010] [UpdateRegistration] Bad response from Graylog server: 404 Not 
> Found 
> time="2017-01-15T10:23:44-05:00" level=error msg="[RequestConfiguration] 
> Bad response status from Graylog server: 404 Not Found" 
> time="2017-01-15T10:23:44-05:00" level=error msg="Can't fetch 
> configuration from Graylog API: GET 
> http://:12900/api/plugins/org.graylog.plugins.collector/a5e77211-e90e-4683-a1c0-ab9c9eabd5ef?tags=%5B%22linux%22%2C%22apache%22%5D:
>  
> 404 HTTP 404 Not Found"
>
> or
>
> time="2017-01-15T10:35:00-05:00" level=error msg="[UpdateRegistration] Bad 
> response from Graylog server: 404 Not Found" 
> time="2017-01-15T10:35:09-05:00" level=error msg="[RequestConfiguration] 
> Bad response status from Graylog server: 404 Not Found"
> time="2017-01-15T10:35:09-05:00" level=error msg="Can't fetch 
> configuration from Graylog API: GET 
> http://mon1.watsons.local:12900/api/plugins/org.graylog.plugins.collector/368ceb95-5cc3-4d8e-9179-5510d37484df?tags=%5B%22windows%22%5D:
>  
> 404 HTTP 404 Not Found"
>
> This appears to be a authentication issue but I can't find any way to 
> setup the authentication.
>
> I've looked at my graylog server configuration and tried changing the 
> sidecar configuration to match the "rest_listen_uri" in the sever config 
> (i.e. http://:12900/) but it's made no difference.
>
> What am I missing to get this to work?
>
>

-- 
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 
https://groups.google.com/d/msgid/graylog2/cd2e1d38-d451-4d95-a9e3-ad3718c6955b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[graylog2] Re: mongodb_uri doesn't like multiple server urls?

[Jochen Schalanda]

Hi Jason,

please stick to the format explained 
in 
http://docs.graylog.org/en/2.1/pages/configuration/multinode_setup.html#graylog-to-mongodb-connection
 
and 
https://github.com/Graylog2/graylog2-server/blob/2.1.2/misc/graylog.conf#L434-L442
 
for the mongodb_uri setting.

Also see the error message you received: "The connection string contains 
invalid user information. If the username or password contains a colon (:) 
or an at-sign (@) then it must be urlencoded"

Cheers,
Jochen

On Monday, 16 January 2017 03:10:04 UTC+1, Jason Haar wrote:
>
> Hi there
>
> I just converted our standalone mongodb server into a cluster according to 
> the instructions on 
>
> https://docs.mongodb.com/manual/tutorial/deploy-replica-set/
>
> Looks good, the original is the master and the rest shows the "graylog" 
> database got synched to them and "rs.status()" looks happy (I even 
> confirmed I could log into the mongodb "graylog" database with the same 
> username/password on each slave)
>
> So then I reconfigured server.conf to tell graylog it had multiple servers 
> to point to. I went from this working entry
>
> mongodb_uri = mongodb://graylog:pass@ho.st1:27017/graylog
>
> to
>
> mongodb_uri = 
> mongodb://graylog:pass@ho.st1:27017/graylog,mongodb://graylog:pass@ho.st2:27017/graylog,mongodb://graylog:pass@ho.st3:27017/graylog
>
>
> However that errors out and graylog-server crashes. I see the below error. 
> It's like graylog "likes" the url format, but comma-separated values spook 
> it? I even tried the format in 
>
> http://docs.graylog.org/en/2.2/pages/configuration/multinode_setup.html 
> 
>
> ie 
>
> mongodb_uri = 
> mongodb://graylog:pass@ho.st1:27017/graylog,ho.st2:27017/graylog,ho.st3:27017/graylog
>
> - that didn't work either. 
>
> This is graylog-server-2.2.0-6.beta.4.noarch under CentOS7
>
> Thanks
>
> Jason
>
>
>
> com.github.joschi.jadconfig.ValidationException: Couldn't run validator 
> method
> at 
> com.github.joschi.jadconfig.JadConfig.invokeValidatorMethods(JadConfig.java:227)
>  
> ~[graylog.jar:?]
> at 
> com.github.joschi.jadconfig.JadConfig.process(JadConfig.java:100) 
> ~[graylog.jar:?]
> at 
> org.graylog2.bootstrap.CmdLineTool.processConfiguration(CmdLineTool.java:351) 
> [graylog.jar:?]
> at 
> org.graylog2.bootstrap.CmdLineTool.readConfiguration(CmdLineTool.java:344) 
> [graylog.jar:?]
> at org.graylog2.bootstrap.CmdLineTool.run(CmdLineTool.java:177) 
> [graylog.jar:?]
> at org.graylog2.bootstrap.Main.main(Main.java:44) [graylog.jar:?]
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:1.8.0_111]
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
> ~[?:1.8.0_111]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
> ~[?:1.8.0_111]
> at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_111]
> at 
> com.github.joschi.jadconfig.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:53)
>  
> ~[graylog.jar:?]
> at 
> com.github.joschi.jadconfig.JadConfig.invokeValidatorMethods(JadConfig.java:221)
>  
> ~[graylog.jar:?]
> ... 5 more
> Caused by: java.lang.IllegalArgumentException: The connection string 
> contains invalid user information. If the username or password contains a 
> colon (:) or an at-sign (@) then it must be urlencoded
> at com.mongodb.ConnectionString.(ConnectionString.java:262) 
> ~[graylog.jar:?]
> at com.mongodb.MongoClientURI.(MongoClientURI.java:201) 
> ~[graylog.jar:?]
> at 
> org.graylog2.configuration.MongoDbConfiguration.getMongoClientURI(MongoDbConfiguration.java:55)
>  
> ~[graylog.jar:?]
> at 
> org.graylog2.configuration.MongoDbConfiguration.validate(MongoDbConfiguration.java:60)
>  
> ~[graylog.jar:?]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[?:1.8.0_111]
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
> ~[?:1.8.0_111]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
> ~[?:1.8.0_111]
> at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_111]
> at 
> com.github.joschi.jadconfig.ReflectionUtils.invokeMethodsWithAnnotation(ReflectionUtils.java:53)
>  
> ~[graylog.jar:?]
> at 
> com.github.joschi.jadconfig.JadConfig.invokeValidatorMethods(JadConfig.java:221)
>  
> ~[graylog.jar:?]
> ... 5 more
>
>
> -- 
> Cheers
>
> Jason Haar
> Information Security Manager, Trimble Navigation Ltd.
> Phone: +1 408 481 8171
> PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop