"Requests failed: fisheye (not_configured)" warnings in JIRA logs

We are getting lots of Warnings in JIRA logs for "Requests failed: fisheye (not_configured)" almost for every 30 seconds. JIRA logs are getting flooded with these warnings.

It seems application link works fine since I could see Changelists submitted in Perforce are visible under Source Tab in JIRA issues.

following are few lines from Logs

 

015-11-25 12:29:14,751 http-bio-138.106.7.13-8443-exec-1716 WARN User1 749x851060x4 lljcwm 138.106.193.197,138.106.7.199 /rest/dev-status/1.0/issue/summary [plugin.devstatus.provider.DefaultCoordinator] Requests failed: fisheye (not_configured)
2015-11-25 12:29:15,472 http-bio-138.106.7.13-8443-exec-1644 WARN User2 749x851084x7 16jot4p 138.106.135.142,138.106.7.199 /rest/dev-status/1.0/issue/summary [plugin.devstatus.provider.DefaultCoordinator] Requests failed: fisheye (not_configured)
2015-11-25 12:29:17,951 http-bio-138.106.7.13-8443-exec-1700 WARN User3 749x851200x9 1iu3jpk 138.106.193.229,138.106.7.199 /rest/dev-status/1.0/issue/summary [plugin.devstatus.provider.DefaultCoordinator] Requests failed: fisheye (not_configured)
2015-11-25 12:29:19,478 http-bio-138.106.7.13-8443-exec-1644 WARN ELIWM1 749x851304x10 16jot4p 138.106.135.142,138.106.7.199 /rest/dev-status/1.0/issue/summary [plugin.devstatus.provider.DefaultCoordinator] Requests failed: fisheye (not_configured)
2015-11-25 12:29:19,649 http-bio-138.106.7.13-8443-exec-1690 WARN MGIQ31 749x851315x11 10lv20f 138.106.159.123,138.106.7.199 /rest/dev-status/1.0/issue/summary [plugin.devstatus.provider.DefaultCoordinator] Requests failed: fisheye (not_configured)
2015-11-25 12:29:19,659 http-bio-138.106.7.13-8443-exec-1697 WARN KSUYDH 749x851313x9 v8q6s 10.255.252.134,138.106.7.199 /rest/dev-status/1.0/issue/summary [plugin.devstatus.provider.DefaultCoordinator] Requests failed: fisheye (not_configured)
2015-11-25 12:29:22,178 http-bio-138.106.7.13-8443-exec-1721 WARN SSSBMC 749x851351x4 lljcwm 138.106.193.197,138.106.7.199 /rest/dev-status/1.0/issue/summary [plugin.devstatus.provider.DefaultCoordinator] Requests failed: fisheye (not_configured)
2015-11-25 12:29:24,583 http-bio-138.106.7.13-8443-exec-1731 WARN EHEQFG 749x851382x6 13hgbxy 138.106.159.157,138.106.7.199 /rest/dev-status/1.0/issue/summary [plugin.devstatus.provider.DefaultCoordinator] Requests failed: fisheye (not_configured)
2015-11-25 12:29:24,635 http-bio-138.106.7.13-8443-exec-1542 WARN FHEA4V 749x851384x6 1c98m5f 10.99.100.168,138.106.7.199 /rest/dev-status/1.0/issue/summary [plugin.devstatus.provider.DefaultCoordinator] Requests failed: fisheye (not_configured)
2015-11-25 12:29:27,779 http-bio-138.106.7.13-8443-exec-1552 WARN MPOAJQ 749x851401x1 1iu3jpk 138.106.193.229,138.106.7.199 /rest/dev-status/1.0/issue/summary [plugin.devstatus.provider.DefaultCoordinator] Requests failed: fisheye (not_configured)

Did someone faced this kind of warnings before? Would really appreciate your advice on this.

Thanks,

Suhas

2 answers

0 votes

Hi Suhas, 

 

This looks to be related to OAuth authentication. As workaround you could try to enable Basic Access and disabling Trusted Applications but this might not work for some use-cases. 

In case you are using reverse proxy, this might being caused for mod_jk. Please check this documentation: https://confluence.atlassian.com/display/JIRAKB/Oauth+after+Initial+configuration+doesn%27t+work

Cheers, 

Renato Rudnicki

Hello Renato,

We are already using basic authentication and trusted applications are disabled. Still we are getting this warnings in the logs.

In our environment, JIRA is SSLed but Fisheye is not.

Currently we are facing lot of performance issues in JIRA 6.4.12. Do you think this affects JIRA performance significantly? Perhaps we are using the same setup since long time in JIRA 6.3.8 and we didnt face any performance issues there.

Any other thoughts on this?

 

Regards,

Suhas

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

35 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you