iRulesLX Logging Not Working - No log statements appear in /var/log/ltm

Same problem here, but only on my 13.0.0 VE system. I haven’t found a solution either. As a workaround I use the node.js fs module and write logs to a file. However on another hardware appliance the console.log function works like it should.

I'm seeing similar behavior, actually. I've seen the logging work in v13 (I think it was a VE in a cloud instance, so not necessarily hardware, but maybe different than this VE), so on some devices it works, but in this VE it just doesn't. I have no idea why it works on some devices but not others. I guess I'll have to try opening a support case.

Got the answer to this. The issue was a custom log filter, custom log publisher, and custom logging destination. I didn't initially realize I had any of those, because on the box I was working on (which was not one I originally set up) there was no customized logging in the Common partition. But it turns out there was another partition on the box, and it had all those custom logging objects in it.

The log filter was set to "all sources", and the level was set to "info", meaning it was grabbing all logs that were the level of info or above. The publisher and destination objects were sending them out to a remote Splunk server (that no longer even exists, ironically), and "local-syslog" was not in the list of destinations in the publisher object, meaning no copies of the log statements were being stored locally.

So in effect, nearly every log on my box (unless it was debug level, or something coded to write directly to the log like certain TCL log commands) was getting shipped out to nowhere, and that included all the iRulesLX logs. Once I added "local-syslog" as a destination in the publisher, they all started showing up.

So hopefully this will help someone else... watch for logging objects in partitions other than Common!