Client console log is tiny, and messed up

  • For some reason the SUPPORT directory contains a whole pile of console files, all of which contain 1K of … mess. It’s like the logger thinks the file should only be 1k and is doing wrap-around logging, so newer entires appear on top and older ones are one the bottom, but never more than 1K of actual log. I seem to recall I set up some sort of debug logging way back when, for a PMR, and that utterly borked client logging. That’s never been addressed. I’d be delighted to have the normal logging back again.

  • Just poked around in my notes.ini and don’t see anything out of the ordinary, other than an HTTPJVMMaxHeapSize entry, which seems like it may be out of place in a client’s configuration. There is not one single entry concerning console log file, console log enabling, debug setting, or anything of that nature anywhere, by visual inspection or regexp search. Any ideas what’s going on there?

Thanks for your time…

Subject: INI

Try adding console_log_enabled=1 to your INI and restart notes

Subject: That will make the logs bigger.

If that is what you want.

Some items will write to a console log regardless.

Unless your diagnosing an issue you can nuke the IBM_TECHNICAL_SUPPORT folder (while server is not running). The server will recreate it at next server start.

Subject: What I would prefer is the default behaviour…

  • Normally stuff appears in *SUPPORT, but it’s not overly verbose. Then if I do as Andrew suggests it will log more volume, as will other debug settings. But the log it does generate should not “wrap” at 1K in either case … the log should grow for that session, then get renamed (with a date stamp if I recall) for the next session, and so on. I’ve never paid attention to whether any aging of this directory ever happens because that’s never been important.

  • But how do I get it to make a log larger than 1k, and rename for the next session? It’s this size limit, and the fact that it overwrites oldest entries all day long, and it never generates more than the current session’s log, that’s vexing.

Thanks for your time…