com.onresolve.jira.groovy.GroovyService failed after updating script files

[Vid Kraner]

Hi,

we have several com.onresolve.jira.groovy.GroovyService services under Administration/Services. They are running fine until we update files in JIRA scripts root folder which are referenced by these services. After change, they are not being run anymore.

Does someone have any clue what could be done to avoid this errors? We already tried to open the service and point it to same file and then saving. It didn't help.

In the logs this is the error we get:

2019-11-04 21:00:00,032 Caesium-1-1 ERROR anonymous ExportTeamMetrics [c.o.jira.groovy.GroovyService] Script service failed: /jira/home/scripts/teamexport/ExportMonthlyTeamMetricsScript.groovy java.lang.NullPointerException at org.apache.felix.framework.BundleRevisionImpl.getResourcesLocal(BundleRevisionImpl.java:531) at org.apache.felix.framework.BundleWiringImpl.findResourcesByDelegation(BundleWiringImpl.java:1173) at org.apache.felix.framework.BundleWiringImpl.getResourcesByDelegation(BundleWiringImpl.java:1083) at org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava5.getResources(BundleWiringImpl.java:1870) at org.apache.felix.framework.BundleWiringImpl$BundleClassLoaderJava5$getResources.call(Unknown Source) at com.onresolve.scriptrunner.runner.classloading.MultiParentClassLoader$_getResources_closure5.doCall(MultiParentClassLoader.groovy:65) at com.onresolve.scriptrunner.runner.classloading.MultiParentClassLoader.getResources(MultiParentClassLoader.groovy:64) at com.onresolve.scriptrunner.runner.AbstractScriptRunner.loadScriptByName(AbstractScriptRunner.groovy:339) at com.onresolve.scriptrunner.runner.ScriptRunner$loadScriptByName$11.callCurrent(Unknown Source) at com.onresolve.scriptrunner.runner.ScriptRunnerImpl.runScript(ScriptRunnerImpl.groovy:220) at com.onresolve.scriptrunner.runner.ScriptRunner$runScript$10.callCurrent(Unknown Source) at com.onresolve.scriptrunner.runner.AbstractScriptRunner.runScriptAndGetContext(AbstractScriptRunner.groovy:129) at com.onresolve.scriptrunner.runner.AbstractScriptRunner$runScriptAndGetContext$0.callCurrent(Unknown Source) at com.onresolve.scriptrunner.runner.AbstractScriptRunner.runFileAsScript(AbstractScriptRunner.groovy:238) at com.onresolve.scriptrunner.runner.AbstractScriptRunner.runFileAsScript(AbstractScriptRunner.groovy) at com.onresolve.scriptrunner.runner.ScriptRunner$runFileAsScript$18.call(Unknown Source) at com.onresolve.jira.groovy.GroovyService.run(GroovyService.groovy:40) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:68) at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:62) at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:44) at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:32) at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153) at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118) at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:438) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:462) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:390) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282) at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65) at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59) at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)

[Peter-Dave Sheehan]

Look at the file permission and ownership for the script files. When you edited it, perhaps you rendered it unreadable by the users that jira is running as in your environment.

[Vid Kraner]

Thank you for the answer!

We changed the ownership to jira with chown (jira:jira), so this shouldn't be the problem.