Server Dying in SysLogs

[acrumley (Alex Crumley)]

Which IIQ version are you inquiring about?

8.3sp2

Issue Summary

I have been debugging issues in production and attempted to use SysLog. However, I have found that our SysLog is being overfilled with these logs:

PS: This is filtered on how many logs returned in a single day

I have dug into our Identity Refresh tasks and the Task Schedules to see if I could fix anything there. However, even disabling our most frequently ran scheduled tasks and watching the Tasks in the Administrator Console, I cannot see what process is continually spitting out these logs. Our servers are getting overrun with SysLog, and it has been very frustrating trying to keep the logs clean and diagnose the root-cause issue.

Thanks,
Alex C

[acrumley (Alex Crumley)]

Have you ever seen this before? @pattabhi

[pattabhi (Pattabhi Nandarapu)]

Hi @acrumley

I have not seen similarly issue.

My pointers, disable syslog.

1. look at log4j2.properties settings.
2. Gear icon – > Global settings – > IdentityIQ Configuration – > Miscellaneous – > Syslog Settings
   
   

[ryan_toornburg]

Hi @acrumley - This is an issue with the BundleProfileRelation. You can disable it by going to the Administrator console > Environment and clicking on the gear next to the server and turning it off if you are not using the Bundle Profile relations.

From SP: “Profiles were not originally designed to be searchable because they were exclusively intended to only be used for role detection. Requirements have evolved over time, and this design has made it difficult to support features that require timely Profile searches. The Bundle Profile Relation table is a normalized view of the Profiles that expedites these searches. Any changes you make to your Bundles should automatically be propagated to the table by the BundleProfileRelation service.”

[acrumley (Alex Crumley)]

Your root cause analysis was correct. It is an issue with 8.3

Issue was solved by upgrading to 8.4sp2