Log flooding: [c.r.j.p.i.s.imports.jirauser.JIRAUserImportServiceImpl] Can't save avatar on import: No suitable ImageReader found for source data.

Jacques
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 14, 2016

Hello,

I have "something" configured in a JIRA Service Desk environment that is flooding my atlassian-jira.log file. Every other milisecond I have this errormessage:

2016-11-14 17:28:19,567 Caesium-1-2 WARN username     [c.r.j.p.i.s.imports.jirauser.JIRAUserImportServiceImpl] Can't save avatar on import: No suitable ImageReader found for source data.
2016-11-14 17:28:19,600 Caesium-1-1 WARN username     [c.r.j.p.i.s.imports.jirauser.JIRAUserImportServiceImpl] Can't save avatar on import: No suitable ImageReader found for source data.
2016-11-14 17:28:19,613 Caesium-1-2 WARN username     [c.r.j.p.i.s.imports.jirauser.JIRAUserImportServiceImpl] Can't save avatar on import: No suitable ImageReader found for source data.
2016-11-14 17:28:19,639 Caesium-1-1 WARN username     [c.r.j.p.i.s.imports.jirauser.JIRAUserImportServiceImpl] Can't save avatar on import: No suitable ImageReader found for source data.
2016-11-14 17:28:19,660 Caesium-1-2 WARN username     [c.r.j.p.i.s.imports.jirauser.JIRAUserImportServiceImpl] Can't save avatar on import: No suitable ImageReader found for source data.

I have tried disabling various add-ons I thought were responsible for this error, but it still remains. Even after a few JIRA restarts.

I have tried to empty the avatars folder, but to no success.

 

Does this error message ring a bell to anyone?

 

Thanks,
Jacques.

1 answer

1 vote
Steve Rhodes
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 17, 2016

Hi Jacques,

I too am getting this same problem. This is since we started a user import with the Insight addon. Disabling the addon has stopped the flooding.

Suggest an answer

Log in or Sign up to answer