Script field failed on issue

[Gnanabaskar]

Hi, 

I am facing issue with User Management Active Directory Sync. 

Sync is failing and When I checked Log , noticed that there are many errors related to Script field failed on issue .

2022-08-19 11:30:27,790 https-jsse-nio-443-exec-27 ERROR sonali.chatte 690x171768x3 15lqchs 10.202.3.104 /secure/QuickCreateIssue.jspa [c.o.scriptrunner.customfield.GroovyCustomField] *************************************************************************************
2022-08-19 11:30:27,790 https-jsse-nio-443-exec-27 ERROR sonali.chatte 690x171768x3 15lqchs 10.202.3.104 /secure/QuickCreateIssue.jspa [c.o.scriptrunner.customfield.GroovyCustomField] Script field failed on issue: D2C-483, field: Deadline 

Kindly assist to fix this issue. Not sure whether because of this Active Directory sync is failing.

Thanks

Baskar

[DanielG · Accepted solution]

After checking all the permissions of my database and do the recommendations (performance) that you said to me, I checked again the database and I saw that the table 'changegroup' was corrupt. Lucky I do daily backups of my database, so I restore and I could solve the problem...

I don't know why my database was broken because I don't do anything the time that I go out (holidays)... maybe a restart of JIRA or the system is the cause of these problem.

Thank you guys

[Tiago Comasseto]

Hi Daniel,

One thing that just crossed my mind, perhaps this can be related to DNS change, is MySQL installed on the same server as JIRA? In case yes, you may change the MySQL server address to localhost or the direct IP address into the dbconfig.xml file, that is located inside your JIRA home directory.

Cheers

[DanielG]

Tiago,

MySQL is installed on the same server as JIRA, so I check dbconfig.xml and the MySQL Adress is 'localhost' so it's ok.

[EddieW]

Odd that it only occurs for issue updates.

Have you verified other write/updates? (edit a version release date, create a component, etc)

May be a timeout issue on the mySQL side.

Be sure you have configured the "validation query" outlined in this page, https://confluence.atlassian.com/display/JIRA/Surviving+Connection+Closures

And I suggest trying "testOnBorrow" = true as well p- http://commons.apache.org/proper/commons-dbcp/configuration.html

If those don't work, see this page to forcefully evict connections from JIRA's side before MySQL gets a chance. Resolution assumes "max_wait_time" in MYSQL is set to 8 hours, so verify that first.

https://confluence.atlassian.com/display/CONFKB/'Communications+link+failure'+CommunicationsException+Error+with+JIRA+User+Management+on+MySQL

[DanielG]

Thanks for your recommendations. I do all of these but my database doesn't works because it was corrupted. I finally had to restore the database with backup.