Errors in logs for Email Account read. How to fix?

[rita_m]

Hi - 

I'm seeing a lot of errors in our non production logs that look like the following ones:  

EmailReader: Email Account record with sys_id 'b695c10000001010fde885507e4bcb26' either cannot be found or its inactive. Email Read cannot be processed.
com.glide.email_accounts.EmailReadProcessor.processEmailRead(EmailReadProcessor.java:40)
com.glide.email_accounts.EmailAccountGroupReader.processEmailReadOnEmailAccountGroup(EmailAccountGroupReader.java:211)
com.glide.email_accounts.EmailAccountGroupReader.process(EmailAccountGroupReader.java:106)
com.glide.email_accounts.EmailReaderJob.execute(EmailReaderJob.java:82)
com.glide.schedule.JobExecutor.lambda$executeJob$0(JobExecutor.java:140)
com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:143)
com.glide.schedule.JobExecutor.execute(JobExecutor.java:127)
com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:328)
com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$0(SchedulerWorkerThread.java:219)
com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)
com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:219)
com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:100)
: no thrown error

error creating email reader: java.lang.NullPointerException: java.lang.NullPointerException: java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1011)
java.base/java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:1006)
java.base/java.util.Properties.put(Properties.java:1340)
java.base/java.util.Properties.setProperty(Properties.java:228)
com.glide.email.oauth2.imap.IMAPOAuth2Reader.initialize(IMAPOAuth2Reader.java:59)
com.glide.notification.EmailHandler.getExtendedEmailHandler(EmailHandler.java:116)
com.glide.notification.EmailHandler.getExtendedEmailReader(EmailHandler.java:60)
com.glide.notification.inbound.EmailReader.getEmailReader(EmailReader.java:136)
com.glide.notification.inbound.EmailReader.getEmailReader(EmailReader.java:112)
com.glide.email_accounts.EmailReadProcessor.processEmailRead(EmailReadProcessor.java:48)
com.glide.email_accounts.EmailAccountGroupReader.processEmailReadOnEmailAccountGroup(EmailAccountGroupReader.java:211)
com.glide.email_accounts.EmailAccountGroupReader.process(EmailAccountGroupReader.java:106)
com.glide.email_accounts.EmailReaderJob.execute(EmailReaderJob.java:82)
com.glide.schedule.JobExecutor.lambda$executeJob$0(JobExecutor.java:140)
com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:143)
com.glide.schedule.JobExecutor.execute(JobExecutor.java:127)
com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:328)
com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$0(SchedulerWorkerThread.java:219)
com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)
com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:219)
com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:100)

The errors are not occurring on prod, but I do wonder if they're related to cloning prod over our non-prod instances.

There's no email account/email account group with the mentioned sys_id in our nonprod OR prod system, tho. (I've also checked inbound actions and user accounts, with no match.)

Does anyone know what might be trying to read email accounts that don't exist? Is there a scheduled job or something that needs to be fixed somehow, and if so, how?

These errors are occurring about every 10 seconds, so cleaning them up would really help keep our logs cleaner.

Thanks!

-R

[Tony Chatfield1]

Hi, if your sys_email_account records appear to be correct and there is no long running\confused scheduled job\task

then I would log this with Now Support for investigation\resolution, especially if it started occurring after a clone.
OOB it looks like a DEV instance email reader cycle is 2 minutes, which doesn't align with your 10 second log occurrence.
Does your email diagnostics show anything unusual

/nav_to.do?uri=%2Femail_diagnostics.do