Anyone seen this: New license initialized / Field mapping errors
We’re seeing errors across the logs of all our Collibra environments as of Tuesday evening, about 23:20, and suspect that this is not related to anything we’re doing. Has anyone else seen this?
2023-05-09 23:29:12.597 [pool-35-thread-1] INFO c.c.d.c.l.impl.LicenseServiceImpl - Start reading license file. []
2023-05-09 23:29:12.600 [pool-35-thread-1] INFO c.c.d.c.l.impl.LicenseServiceImpl - New license initialized: License{expirationDate=…, valid=true, writerCount=…, readerCount=…, apiCount=…, maxAssets=…, maxWorkflows=…, company=’…’, guestAccess=…, products=[GLOSSARY, …, STEWARDSHIP], onTheGoMobile=true, onTheGoWindows=true, legacyUsers=0} [authenticated_id=00000000-0000-0000-0000-000000900001, session_hash=…]
2023-05-09 23:29:12.618 [pool-35-thread-1] ERROR c.g.d.core.MappingProcessor - Field mapping error -->
MapId: null
Type: null
Source parent class: com.collibra.dgc.core.model.user.impl.RoleImpl
Source field name: rights
Source field type: null
Source field value: null
Dest parent class: com.collibra.dgc.core.api.model.role.impl.RoleImpl
Dest field name: permissions
Dest field type: java.util.List [session_hash=…, authenticated_id=00000000-0000-0000-0000-000000900001, trace_id=…, trace_flags=01, span_id=…]
tjbrodeur1
·3 years ago · EditedYes. We were getting this issue as well. We stumbled across it on Friday (5/12) on our DEV instance while I was testing some workflow stuff. This morning we discovered it was also taking place in our PROD instance.
It does appear that restarting resolves this issue.
One rather disturbing component to this (at least it seems related) is that dcg log files appear to have been deleted from our console. Wondering if anyone else is seeing that same thing. Note: This doesn’t seem to be occurring for the dcg_recommender or dcg_jobs files, just the regular console log files (formatted dcg.YYYY-MM-DD-X.log)
I know it is deleting them for two reasons:
Anyway, can someone else verify their log files before 5/12 are no longer available?
arthurburkhardt
·3 years ago · Edited@tj.brodeur Just checked both our instances, no logs have disappeared.
List of files in prod (for your confirmation)Are you interested to meet quickly and compare notes on log management? I’d be curious to see how you manage it. I’m currently quite happy with the automation and insights we extract from the logs, but I’d like to move to the next step and integrate with a proper monitoring tool.
tjbrodeur1
·3 years ago · Edited@arthur.burkhardt Thank you for the confirmation. And, yes, I’d love to chat about log management. We’re extracting some pretty useful information out of ours and are also planning no more automated event monitoring, so this would be very valuable.
I’ll PM you.
daverichard
·3 years ago · EditedA restart has also resolved this in our instance. As I am still currently testing workflows I will be able to see if it starts up again.
arthurburkhardt
·3 years ago · EditedYep, same here. I opened a support ticket a few day ago.
This prompted me to update this thread: https://datacitizens.collibra.com/forum/t/error-logs-management/621/7?u=arthur.burkhardt
Yesterday, a developer was trying to find the error caused by his workflow, but the answer lies in 0.01% of loglines, so good luck for finding it!
daverichard
·3 years ago · EditedYes, I was testing a workflow and getting so many of these stack traces that I had to download the logs every time to check errors. It is quite annoying. Whatever is happening the error started at 9AM EDT in our server and is happening about every 10 seconds.
So far, we are at 1937 instances since 9AM this morning.
Tom Friesen
OP3 years ago · EditedThanks for chiming in, Dave!
So why now? Is this a byproduct of some third party’s patch Tuesdays? Has Collibra gone and changed something outside of the regular maintenance window? Is this something to do with SSO?
Anyone else?
bartvanderlocht
·3 years ago · EditedWe were also having the same issue. Reboot seems to have solved it (for now)
No idea what’s the cause…