Scratch this, I mistyped the LDAP Search String... all working now
On Wednesday, July 13, 2016 at 1:44:48 PM UTC+1, Kev Johnson wrote:
>
> Hi
>
> I've deployed 2.0.3 from the OVA, and configured up LDAP with a service
> account, which is lovely and everything works.
>
> T
Hi
I've deployed 2.0.3 from the OVA, and configured up LDAP with a service
account, which is lovely and everything works.
The first time I tried to test the authentication for a test user account
it worked fine. I then tried using my domain account, and get "user found",
but "invalid
After going through some further testing I've filed this
at https://github.com/Graylog2/collector-sidecar/issues/37 - it looks to be
an issue with NXlog CE handling the input and output modules as GUIDs.
On Thursday, 7 July 2016 17:11:41 UTC+1, Kev Johnson wrote:
>
> Firstly: I love th
that
the collector sidecar service is running, and it's called the nxlog process.
On Friday, 8 July 2016 10:19:52 UTC+1, Kev Johnson wrote:
>
> Ok - so I've built a clean Windows Server 2012 R2, disabled the firewall
> and run through the same process with the same result - the onl
some log data. At this point I'm reasonably happy that it's not McAfee
causing the issue.
Next port of call is going to be adding some snippets from NXlog.conf files
that I know work, let's see if that makes any difference!
On Friday, 8 July 2016 07:03:27 UTC+1, Kev Johnson wrote:
>
>
the root cause. Maybe you can try with a test
> host with all firewalls disabled.
>
> On 7 July 2016 at 20:38, Kev Johnson <k...@drunkmonkey.co.uk
> > wrote:
>
>>
>> <https://lh3.googleusercontent.com/-z7mPWg_KxJA/V36hBRtxUfI/EjQ/njRGd-GswWAHBnP-ivYvz2
syslog all works fine.
On Thursday, 7 July 2016 19:27:47 UTC+1, Marius Sturm wrote:
>
> The generated config looks fine, maybe a screenshot of the Graylog input
> puts some light on this?
>
> On 7 July 2016 at 19:50, Kev Johnson <k...@drunkmonkey.co.uk
> > wrote:
>
>&
verify the port number with the one
> you configured for nxlog in the collector configuration.
> Another thing, Windows is not sending logs all the time so maybe you just
> need to create an event that is triggering a log e.g. opening the control
> panel?
>
> If that doesn't help
Firstly: I love the idea of being able to push out updated configuration
files to my collectors. That said: I'm having issues getting logs to my
Graylog box (deployed from the OVA)
Steps taken so far are as follows
- Installed NXlogCE
- Uninstalled the NXlog service
- Installed the
