1.When a user is trying to login with multiple attempts then CAPTCHA is displaying a improper language with lamda expressions and lessthan ,greater than symbols.
2.In Many of the dashboard gadgets Same improper language is getting displayed in place of english.
It looks like this is a very similar problem that can be seen in Linux environments that have removed/updated specific fonts from the Operating System. As @Suporte Itamaraty noted for Jira this is tracked in:
We have had other reports of this in Confluence such as this thread: https://community.atlassian.com/t5/Confluence-questions/unreadable-text-in-the-macro-header/qaq-p/661943
In both cases, it appears that you can follow the work-around on the bug ticket to reinstall these fonts manually to correct this problem:
yum install ghostscript yum install dejavu-fonts-common yum install dejavu-sans-fonts yum install dejavu-sans-mono-fonts yum install motif
That's a new one to me! So, some questions...
Is it happening for everyone, or just one user?
Is it consistent? If, for example, you go back to the pie chart again, are the labels the same rubbish, or do they change?
Can you check the "system information" page for any settings related to location, region or language - are they all consistent?
Similar to the one above, what is the database collation and character set? (Should be on the system info page)
Are you behind a proxy?
What language has the user set in their profile?
Hello @Nic Brough [Adaptavist]
1.This is for everyone including admins.
2.Its consistent in dashboards and in CAPTCHA whenever we are refreshing CAPTCHA a new one is generating but with the same unknown language.
3.I checked in System info but database collation and charecter set im unable to find.
4.Our instance is inside the firewall
5.I checked all settings and all are fine.
6.We have test/Dev JIRA instance and i checked overthere and it is veryfine with out these errors or bugs.
7.Riased to atlassian and we use 6.3.1(end of life version) so they said they cannot support.
8.We are in plan of upgradation this month but this issue we have to resolve because its impacting many users.
So please help..if anyone can???
Can you go in user's profile --> Preferences and see what langauge is set over there?
Although I doubt there could be an issue because of that but could you also see what your database charecter set and collation is?
SELECT SCHEMA_NAME 'database', default_character_set_name 'charset', DEFAULT_COLLATION_NAME 'collation' FROM information_schema.SCHEMATA;
Unfortunately I dont have Backend access to check logs.That is owned by parent company .need to raise req for that.
We have not done any changes..But will check with that team again.
And for running that query also i dont have access..
What it will show if i run that query???
Anybody believe that updating the JAVA might be a quick fix to some of the issues that we are having.
( I know this talks about confluence but it is basically the same issue that is being experienced in JIRA)
yes I raised for atlassian and i have sen them logs too and they replied like this..
Checking the logs provided, we could not identify any information that could point to a probable cause for this issue. One thing we still would like to check with you: does this issue persists is you access Jira from the server where it is running?
One other thing that we can test is to connect to Jira using a different connector, which uses default configuration. To do this, you can edit the JIRA-INSTALL/conf/server.xml file and remove the comment tags for the connector on port 8080. If this port is not available on the server, you can simply change the port to one available, but it is important to only change the port number. Once this is done, save the changes and then access Jira using the SERVER-IP:8080 or any other configured port.
what does this mean??
i really did not understood because i dont have backend access and i dont have networking knowledge..
please help me
You server would be installed on some Linux machine probably, right?
So find out what that machine is, get the IP of that machine and access it through Remote Connection.
You should have the credentials of the admin account ideally.
So once you make a remote access, open up the browser from there and access JIRA and verify if the problem persists or not.
Secondly, they are telling you to try running your instance on port 8080. In you server.xml file under JIRA-INSTALLATION/conf/ you must've commented out the tag for port 8080.
So uncomment that and try running your instance on port 8080. Or any other port that is available.
Server.xml should look something like this
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
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!
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