i have run in to a weird bug and dont know how to proceed/debug. i have an app thats written in nodejs and uses winston for logging. everything was working fine until i brought up a new production server yesterday and retired the old one. my prod server has 4 nodejs processes running. on the new production server, winston logs the very first log message per .js file. period. it stops logging after that. changing the log level doesnt work. my app has got about 6 .js files, and incase of any error on any of those files, the very first error msg gets logged but any subsequent errors/warning/info are not logged.
the funny thing is winston was working just fine on the old prod server and the dev server still works fine.
i am on winston 0.6.2 on both dev and prod. as far as i know all the sw packages are the same between dev and prod.
i dont know how to debug this issue. any help is much appreciated.
--su
After some research, I came across this issue => https://github.com/flatiron/winston/issues/227
Looks like, the new way of handling streams in the latest version of node has broken file transport in winston. I am going back to node v0.8.22 for the time being as a work around.
What transports are you using for logging? Does the console transport work? Perhaps the new production server has a network issue that prevents it logging to a remote service such as CouchDB or Loggly.
If you add a simple console.log('...') line next to your winston log lines do those get fired. This will confirm or deny that your winston log lines are getting called on the production server
winston.info('winston log test')
console.log('console log test')
You can can expose the logger instance and have a URL to trigger the required log level. I had the same need so I came up with a dynamic log level setter for Winston https://github.com/yannvr/Winston-dynamic-loglevel