You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the os level, "lsof -p [pid] | wc -l" will show an increasing amount of opened sockets on each writes to the log.
Same goes for "ls -l /proc/[pid]/fd | wc -l"
Using 1.0.13, there are no problems
At 1.0,14 and 1.0.15, the above code won't run. I get: error: uncaughtException: winstonGraylog is not a constructor
At 1.0.16 and 1.0.17, this is when I see the problem with file handles being consumed indefinetely,
The text was updated successfully, but these errors were encountered:
It looks like whenever there's a write to the log, a file handle is consumed and never recovered. After a while, file handles are exhausted.
Here's how I'm using it:
At the os level, "lsof -p [pid] | wc -l" will show an increasing amount of opened sockets on each writes to the log.
Same goes for "ls -l /proc/[pid]/fd | wc -l"
Using 1.0.13, there are no problems
At 1.0,14 and 1.0.15, the above code won't run. I get: error: uncaughtException: winstonGraylog is not a constructor
At 1.0.16 and 1.0.17, this is when I see the problem with file handles being consumed indefinetely,
The text was updated successfully, but these errors were encountered: