And if I could link to the "master" mongoDB then obviously that would
defeat the point of giving search ability to users without making them an
admin on the master?
On Monday, June 15, 2015 at 6:17:23 AM UTC-7, Jochen Schalanda wrote:
>
> Hi Mark,
>
> input configurations are being stored inside MongoDB and are linked to the
> node ID. If your "slave" Graylog instance is either using another node ID
> or isn't able to access the MongoDB with the input configurations, you'll
> see the message ("deleted input on outdated node") in the web interface.
>
> Cheers,
> Jochen
>
> On Friday, 12 June 2015 21:52:50 UTC+2, Mark Moorcroft wrote:
>>
>> I asked this back in April and I'm still looking for an answer.
>>
>> I have a protected VM running graylog/mongo/elastic, and all of our
>> actual graylog usage takes place on a slave VM due to the way user accounts
>> work.
>>
>> My question is about the slave graylog log events. They all show
>> "Received by deleted input on outdated node" presumably because none of the
>> "inputs" are local, and the elastic index is also remote. Is this a
>> configuration error on my part, or is this just a consequence of using this
>> arrangement? Is there any way to have them appear with the input and node
>> on the remote?
>>
>
--
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/d/optout.
