Skip to content
This repository has been archived by the owner on Mar 13, 2018. It is now read-only.

windows collector 0.2.4 log transfer to the server broken? #39

Closed
Dominik81 opened this issue Jun 30, 2015 · 4 comments
Closed

windows collector 0.2.4 log transfer to the server broken? #39

Dominik81 opened this issue Jun 30, 2015 · 4 comments
Assignees
Labels

Comments

@Dominik81
Copy link

Windows Graylog Collector 0.2.4 on Windows2008R2std.x64SP1 & Java 1.8.0_45

config:

server-url = "http://server:no default port/"

message-buffer-size = 128

inputs {
 win-eventlog-application {
    type = "windows-eventlog"
    source-name = "Application"
    poll-interval = 1s
  }
  win-eventlog-system {
    type = "windows-eventlog"
    source-name = "System"
    poll-interval = 1s
  }
  win-eventlog-security {
    type = "windows-eventlog"
    source-name = "Security"
    poll-interval = 1s
  }
}

outputs {
  gelf-udp {
    type = "gelf"
    host = "server"
    port = 12204
  }
}

C:\Program Files\graylog-collector-0.2.4\logs\graylog-collector-stderr.yyyy-mm-dd.log

yyyy-mm-dd hh:mm:ss Commons Daemon procrun stderr initialized
Exception in thread "EventLogThread" Exception in thread "EventLogThread" Exception in thread "EventLogThread" java.lang.UnsatisfiedLinkError: org.hyperic.sigar.win32.EventLog.close()V
    at org.hyperic.sigar.win32.EventLog.close(Native Method)
    at org.hyperic.sigar.win32.EventLogThread.run(EventLogThread.java:175)
    at java.lang.Thread.run(Unknown Source)
java.lang.UnsatisfiedLinkError: org.hyperic.sigar.win32.EventLog.close()V
    at org.hyperic.sigar.win32.EventLog.close(Native Method)
    at org.hyperic.sigar.win32.EventLogThread.run(EventLogThread.java:175)
    at java.lang.Thread.run(Unknown Source)
java.lang.UnsatisfiedLinkError: org.hyperic.sigar.win32.EventLog.close()V
    at org.hyperic.sigar.win32.EventLog.close(Native Method)
    at org.hyperic.sigar.win32.EventLogThread.run(EventLogThread.java:175)
    at java.lang.Thread.run(Unknown Source)

We installed the collector via script which now works fine even with whitespaces.
There is a connection openend to the server viewable in netstat but we don't see any logs incoming from the collector.

If we add an additional log file entry, which worked with 0.2.2, there seems to be somewhat like a memoryleak which gets cleaned up by the garbagecollector from time to time.
additional config entry

  test-file {
    type = "file"
    path = "C:/ProgramData/testfolder1/testfolder2/Log.txt"
  }
@bernd
Copy link
Contributor

bernd commented Jun 30, 2015

Thanks for the report!

So you used the graylog-collector-service.bat script to install the service? And with that you get those errors on startup?

What indicates a memory leak when you add an additional log file entry?

@bernd bernd added the bug label Jun 30, 2015
@bernd bernd self-assigned this Jun 30, 2015
@bernd
Copy link
Contributor

bernd commented Jul 1, 2015

I am able to reproduce this and work on a fix.

@bernd bernd closed this as completed in 08b375e Jul 1, 2015
@bernd
Copy link
Contributor

bernd commented Jul 1, 2015

Found and fixed the issue. Thanks again for the report!

I just released 0.2.5 which has this fix.

@bernd
Copy link
Contributor

bernd commented Jul 1, 2015

@Dominik81 Please let me know if you still see the memory problem with the latest version. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants