Gareth Jones
Gareth Jones
My guess is that your node.js server is running with different permissions to your user. If you're using unix then check the umask for the node.js process. If you can...
Hi, thanks for raising this. It looks to be the same issue as #547. It's something we will be looking at once we get version 3.x of log4js released.
@sinbargit You could give the module that @liujingbreak has written a try. I will take a look at this, but currently my focus is on the version-3.x release to remove...
Could you give me a bit more detail, please? What is the rest of your config? What do you mean by "error and debug invalid after set" - what happens?
If you're running this on a single machine, then use node's cluster module for your processes and things get a lot simpler (no need to use the multiprocess appender at...
It isn't supported at the moment. In fact the context values are only preserved in a particular instance of a logger. So calling `getLogger` twice for the same category will...
[BurstFilter documentation](https://logging.apache.org/log4j/2.0/log4j-core/apidocs/org/apache/logging/log4j/core/filter/BurstFilter.html) - if anyone feels like implementing this, I'd be happy to see a PR.
This would be a good one to tackle using the new cluster wrapper in version-3.x
From your config, debug level logs should be written. Did you find a solution, or is this still happening?
log4js just uses the node.js standard zlib module and compresses using gzip, doesn't do anything fancy. Are you uncompressing these files on the same server that you're writing the files?...