Error exporting scheduled issues

[Sabrina Odjaghian]

When I try to export scheduled issues from Jira, I get the attached error (Jira_Scheduler_Export_Error.txt). I've already asked my Jira administrator to look at permissions and he provided the output in Jira_Permissions.txt.

Could you please tell me where I need to be looking so I can get the export to work properly? Ultimately I am looking for a template to use to import scheduled issues.

[Sabrina Odjaghian]

Attaching output of permissions

[Bartosz Gilewski]

Hello,

Could you check permissions in the JIRA instalation directory (the permissions that you have included are form JIRA home directory), and if the CurrentGenSchema.xsd file exist there? The problem might be with the access to that file.

Default instalation directory should be in /var/atlassian/jira/

Regards

[Sabrina Odjaghian]

Per my JIRA adminstrator, the file CurrentGenSchema.xsd does not exist anywhere on the server. Is there a problem with our installation? Do we just need to place that file in the directory? I found this other issue that seemed to have a similar error, and I can see the user was sent a CurrentGenSchema.xsd and PreviousGenSchema.xsd.

https://bitbucket.org/apdc/the-scheduler/issues/46/cant-import-xml-backup-from-264-version

Thank you for your help, please let me know the next steps.

[Sabrina Odjaghian]

Checking back to see if you have the files I can use?

[Bartosz Gilewski]

Hello,

The logs indicates that there is problem with creating new file under the JIRA instalation directory. There might be problem with write permissions. Could you check the write rights in the JIRA installation directory?

The issue under link that you provided is not related with yours. Under the link there was a problem with the missing files in the package. In your problem, plugin is trying to create new file or overwrite existing during the export, but it doesn't have permissions. So manually copying that file will propably not work.

Regards

[Bartosz Gilewski]

Hello,

Have you still got problems with this issue?

Regards

[Sabrina Odjaghian]

Yes, we are still having problems. Here are the latest details from my admin:

I ran strace on java and it's child processes while the issue was reproduced. It appears the file the code is referencing is not being referenced by the full path?

stat("CurrentGenSchema.xsd", 0x7f6e1fbdfaf0) = -1 ENOENT (No such file or directory) open("CurrentGenSchema.xsd", O_WRONLY|O_CREAT|O_TRUNC, 0666) = -1 EACCES (Permission denied)

-rw-r--r-- 1 jira jira 0 Oct 13 12:14 /var/atlassian/application-data/jira/data/CurrentGenSchema.xsd

In https://bitbucket.org/apdc/the-scheduler/issues/46/cant-import-xml-backup-from-264-version there is mention of a bug where creating "Please to create folder "plugin" in "... /jira-home/data/"." is the workaround. It would appear that they are asking to create the directory: /var/atlassian/application-data/jira/data/. I created that directory and the jira user has rw/access.

Full path to the "plugin" directory created. /var/atlassian/application-data/jira/data/plugin

[Sabrina Odjaghian]

My admin was finally able to resolve this by changing the permissions on the bin directory:

According to /proc/$(pgrep java)/environ: PWD=/opt/atlassian/jira/bin I made a temporary change to allow the jira group to write to the above directory. Please try again and let's see if it is able to create and write the file it is trying to. change: chgrp jira /opt/atlassian/jira/bin/ && chmod g+w /opt/atlassian/jira/bin/