TL;DR: I ran a read-only Full for a new provisioner. The DaemonLog reported an error and provided the following message. I don't think this message has the necessary details to fix it, nor the DaemonJob-ID string to search the log4j logs.

provisionerClass: SqlProvisioner, configId: iam_unifieddb_group_memberships2, provisioningType: fullProvisionFull, state: sendChangesToTarget, retrieveSyncGroupsMillis: 2, syncGroupCount: 53, retrieveSyncEntitiesMillis: 43, syncEntityCount: 3723, retrieveSyncMshipsMillis: 81, syncMshipCount: 10989, propagateProvisioningAttributes_millis: 3505, targetRetrieveAllGroups: 1, sqlRemoveDeletedDataAfterHours: 168, sqlRemoveDeletedData: false, targetRetrieveAllEntities: 1, targetRetrieveAllMemberships: 1, retrieveGrouperGroupsMillis: 2, grouperGroupCount: 53, retrieveGrouperEntitiesMillis: 150, grouperEntityCount: 14612, retrieveGrouperMshipsMillis: 167, grouperMshipCount: 13571, provisioningEntitiesToDelete: 100, retrieveDataPass1_millis: 440, grouperGroupsRetrieved: 53, grouperEntitiesRetrieved: 14612, grouperMembershipsRetrieved: 13571, membershipsErrorsClearedCount: 0, groupsErrorsClearedCount: 0, entitiesErrorsClearedCount: 0, retrieveTargetGroupsAndEntitiesMillis: 0, provisioningGroupWrappersWithNoMatch: 53, provisioningEntityWrappersWithNoMatch: 3823, loadDataToGrouper_millis: 1, missingGroupsForCreate: 53, groupTranslationEndedInNoGroupsOnInsert: true, missingEntitiesForCreate: 3723, groupTranslationEndedInNoEntitiesOnInsert: true, retrieveTargetMembershipsMillis: 1, provisioningMembershipWrappersWithNoMatch: 10989, objectErrors: membership error ERR count 10989, group error ERR count 53, entity error ERR count 3823, syncObjectStoreCount: 14868, finalLog: true, queryCount: 37, tookMillis: 14115, took: 00:00:14.115

 

I don't think the context matters, but this happened while trying to establish a new (sql) provisioner that matches the 4-table recommendation. I have no doubt something is wrong with the configuration, so the Error is probably correct, this Jira is just reporting that more information would help find the problem.

I'm probably not stuck, I'll search for the config-id and find the key from there.

 

Also, I don't know remember how messages get included in Grouper's DaemonLog Messages, but,  fwiw, here's an idea to make sure something is always captured... use thread-specific, setup a dynamic logger in the Quartz runner that grab messages logged by the thread, keeping the first N messages for later appending to the Daemon-Log messages, particularly when it fails.