Forum Discussion
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!