A failure would be logged in your nxlog.log
Suggest you try a simple powershell script that just takes a single word as
an argument, and see if that works. It would prove whether calling out to
powershell works.
My biggest concern would be passing JSON as an argument.
On Friday, 22 August 2014,
Yeah, extending the logging diagnostic would ease my concern entirely
(actually, it would be most preferable), so long as it was complete enough
to answer what/when/where/why
Where would have to include the hostname of the nxlog instance that
experienced the fault, so the log can be traced back pr
Hi,
Have installed nxlog and I would like to call an external script and pass
the contents of £raw_event as JSON to the script. nxlog is installed on a
Windows Server and so powershell is my tool of choice.
How can I call powershell and the relevant .ps1 script file and pass the
$raw_event as JSO
I think you are missing a \ on the second-to-last line }
What is the error message?
On Thursday, 21 August 2014, Didjit Charlebois wrote:
> Hi,
>
> I'm executing th efollowing in an input module:
>
> Exec if %IGNORE_ME% drop(); \
> else
Sent too soon. This is from the manual. What am I doing wrong with my
statement? Thanks Chris
Exec if $raw_event =~ /^#/ drop(); \
else \
{ \
kvp->parse_kvp(); \
delete($EventReceivedTime); \
delete
Hi,
I'm executing th efollowing in an input module:
Exec if %IGNORE_ME% drop(); \
else \
{ \
$Server = $Hostname; \
if $raw_event =~ /(^\d\d.\d\d.\d\d\d
Hi,
On Thu, 21 Aug 2014 09:38:44 +0200 (CEST)
Wojciech Puchar wrote:
> now tcpdump shows such lines are emitted to port 514 host 10.100.100.1:
>
> <14>Aug 21 01:43:44 winserver1 Microsoft-Windows-GroupPolicy[936]: Okresowe
> przetwarzanie zasad dla użyytkownika winserver1\ostrowska zostało uko
Hi,
On Thu, 21 Aug 2014 22:53:57 +1200
Cameron Kerr wrote:
> Cool. The most common bugs I've seen are from the config parser, which
> should be relatively self-contained. Since I've had some (little)
> exposure to bison, perhaps I'll look at tackling some of those.
Ok, great.
BTW the error mess
Hi,
On Tue, 19 Aug 2014 20:42:37 +1200
Cameron Kerr wrote:
> The configuration tree could be modified to support something like a
> simple try/catch
Extending the configuration language with try-catch and other constructs
would lead to a lot of complexity. It was never intended to be a full
feat
Is there any white space or comment after the line? Perhaps it would be
best to post the offending config line completely verbatim.
Another idea to try would be using the Windows equivalent of strace, which
I can't remember the name of; you'll find it as part of the SysInternals
suite of tools.
.
Cool. The most common bugs I've seen are from the config parser, which
should be relatively self-contained. Since I've had some (little) exposure
to bison, perhaps I'll look at tackling some of those.
Ps. Are you aware that the following doesn't work?
Group somegroup #end of line comment
That on
Hi Paul,
On Mon, 18 Aug 2014 16:35:40 +
wrote:
> 1.If you do not specify a Directory when using 'Type Disk' where does
> the buffer get written?
The default value is taken from 'CacheDir', normally this is the 'data'
folder on Windows.
> 2.How do you specify a Directory in this cont
Hi Cameron,
That'd be awesome. For now it's only the source tarball that you'd need
to create and send the patches for. If the number of contributions would
indicate the need, we will set up a public git repo.
Thanks,
Botond
On Tue, 19 Aug 2014 20:02:56 +1200
Cameron Kerr wrote:
> Thanks for t
my fixed nxlog.conf
--
#define ROOT C:\Program Files\nxlog
define ROOT C:\Program Files (x86)\nxlog
Moduledir %ROOT%\modules
CacheDir %ROOT%\data
Pidfile %ROOT%\data\nxlog.pid
SpoolDir %ROOT%\data
LogFile c:\windows\temp\nxlog.log
Module xm_syslog
Module im_msvistalog
14 matches
Mail list logo
