Hi Jochen,
I just want to share with you,
On both cases I got the warnings in /var/log/graylog-server/server.log
and go the got the working connection in /var/log/mongodb/mongod.log.
On Monday, September 19, 2016 at 4:58:07 PM UTC+5, Jochen Schalanda wrote:
>
> Hi Shah,
>
> these aren't warnings
Hi Shah,
these aren't warnings and only hint to a working connection to MongoDB.
Cheers,
Jochen
On Monday, 19 September 2016 13:56:23 UTC+2, Shah Zaib wrote:
>
> Hi Jochen
>
> On both cases, I find the same WARN
>
> but on the Mongodb
>
> /var/log/mongodb/mongod.log
>
> I found
>
>
Hi Jochen
On both cases, I find the same WARN
but on the Mongodb
/var/log/mongodb/mongod.log
I found
2016-09-19T11:46:06.067Z I NETWORK [initandlisten] connection accepted
from 2003:1b3b:fffc:11b:4252:1098:c965:6dd1:43122 #36 (1 connection now
open)
2016-09-19T11:46:06.594Z I ACCESS
Hi Shah,
please create a bug report for this
at https://github.com/Graylog2/graylog2-server/issues/ and include these
logs.
Seems like you'd have to go the route with adding a host name to /etc/hosts
for the time being.
Cheers,
Jochen
On Monday, 19 September 2016 11:39:58 UTC+2, Shah Zaib
Hi Shah,
unfortunately this seems to be bug in the MongoDB Java driver which Graylog
is using under the hood (see https://jira.mongodb.org/browse/JAVA-2220) but
which has been fixed in a more recent version of the driver (see
https://jira.mongodb.org/browse/JAVA-2245). Graylog 2.1.x is using
