Thanks Marius,
Sorry it's taken me so long to repsond, I just had an unexpected week in 
the hospital.

I've just tested the changes in beta 4 and I can now save those fields 
without a value however the generated config file still includes the 
entries like so...

<Output 57a9d7abd42b92084133c330>
 Module om_ssl
 Host graylog2.example.org
 Port 12443
 OutputType GELF_TCP
 CAFile 
 CertFile 
 CertKeyFile 
 AllowUntrusted True
 Exec $short_message = $raw_event; # Avoids truncation of the short_message 
field.
 Exec $gl2_source_collector = '9e2660a6-b960-4daf-8d90-e37c3c0e1684';
 Exec $Hostname = hostname_fqdn();
</Output>

This doesn't work as nxlog doesn't like the missing values
2016-08-24 11:34:58 INFO nxlog-ce-2.9.1716 started
2016-08-24 11:34:58 ERROR SSL error, Failed to open certfile: ; The device 
does not recognize the command. 

The config will need to be generated without those entries.

As an aside, is the mailing list the best place to provide this type of 
feedback or should I be putting comments back against the issue in github?

Thanks,
Michael

On Monday, 15 August 2016 20:45:51 UTC+10, Marius Sturm wrote:
>
> Hi Michael,
> this was done here: 
> https://github.com/Graylog2/graylog-plugin-collector/issues/13
> Should be available in Graylog 2.1.0-RC1
>
> Cheers,
> Marius
>
>
> On 12 August 2016 at 13:20, Michael Anthon <michael...@infoview.com.au 
> <javascript:>> wrote:
>
>> Thanks Marius,
>> I've just upgraded to the latest beta and it certainly is looking a lot 
>> better, it also looks like it might solve another issue I was going to 
>> raise with the verbatim configurations since we want to do some custom 
>> processing on inputs to strip sensitive data before it's sent over to 
>> graylog.
>>
>> I still do however have an issue getting this to work.  The 3 field for 
>> the CA, certificate and key files are currently required before you can 
>> save the output.  I have no need of client certificates and don't have any 
>> since my goal is just to ensure that the data in transit is encrypted.  
>>
>> I've tried configuring these with just a space, a dot or a double quoted 
>> empty string but the nxlog config always includes the values which causes 
>> nxlog to reject the output configuration since the files don't exist.
>>
>> I have tried shutting down sidecar, removing those 3 lines from the 
>> config and running nxlog manually and this definitely works, it connects 
>> and sends messages to graylog.
>>
>> If those 3 fields could be made optional and not add those entries to the 
>> generated nxlog.conf then I think this would work perfectly.
>>
>> Cheers,
>> Michael
>>
>> On Friday, 12 August 2016 01:59:50 UTC+10, Marius Sturm wrote:
>>>
>>> Ah ja ok, we shipped the SSL feature recently. So you will see it in the 
>>> next Graylog release or you test the beta version.
>>>
>>>
>>> -- 
>> 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+u...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/graylog2/2e018723-1fbc-42f9-8f43-097b9d6acee0%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/graylog2/2e018723-1fbc-42f9-8f43-097b9d6acee0%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Developer
>
> Tel.: +49 (0)40 609 452 077
> Fax.: +49 (0)40 609 452 078
>
> TORCH GmbH - A Graylog Company
> Poolstraße 21
> 20335 Hamburg
> Germany
>
> https://www.graylog.com <https://www.torch.sh/>
>
> Commercial Reg. (Registergericht): Amtsgericht Hamburg, HRB 125175
> Geschäftsführer: Lennart Koopmann (CEO)
>

-- 
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/f8ee9ddd-977d-4998-9af9-508a195f7e79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to