stderr File descriptor leak

[opsgenie]

stderr File descriptor leak

[metehanozturk]

Which version do you use? The problem is solved with the 1.0.3 version (commit version: 5e83474). After the new version, only one lumberjack being instantiated for each mapped action and OEC are re-using it every time. Although we tried to create and close the logger every single triggered action, lumberjack continues to leak. I guess lumberjack has a memory leak issue itself and we track the news from the library. Now, we alternatively create limited lumberjack, use constantly and do not close it. If you can confirm the version, we can get the clue to understanding whether it caused by the same problem or not.
Thanks.

[ThrosturX]

Thanks for the swift feedback. I will report back at the earliest opportunity.

[ThrosturX]

Hi @metehanozturk, thank you for getting back to me.
I've verified the issue was reproduced on version 1.0.1, we'll try upgrading soon and report back if the problem persists.
In any case, you're right about Lumberjack leaking: natefinch/lumberjack#81

I'd still like to point out that if you do decide to close the logger at some point, you can't use an io.MultiWriter and expect the exec.Cmd to close the underlying writers.
I will re-open the issue or create a new one if we can reproduce a similar issue in the new version.