Hi Ivo,
For something like this, unfortunately, although it would be best to open a support case to have an engineer look into this with you as it may require a bit of code review to see what the function is actually looking for that is not there, because this is a 12.7 environment, and is no longer supported, this wont be possible. What I would say to do is to think about the following:
- when did this first start happening? has it always occurred or is it a newly noticed thing?
- does it seem to occur when certain actions are taken?
- have there been any patches applied or configuration changes made to the product recently? (multi-tenancy?) (cmdb changes? - were CIs loaded in some way?)
Now depending on how often the message is noted in the logs, you can try to run a trace on the file for which this message is coming from which is sec_mgr.c - so you would run "pdm_logstat -f sec_mgr.c VERBOSE" which would log all messages of all types for that file - so this may allow you to see a bit more info about what the function is doing at that time. To turn the logging off run the same command, just take out the VERBOSE at the end. KEEP IN MIND that you do not want to leave that tracing on for an extended period of time as it could hurt performance, as well as cause the logs to overwrite very quickly. So you will first want to look at how often its happening, and try to plan around that.
Hope this helps,
Jon