BigPicture loading crashed

If you see the following screen, it means that the plugin failed to load:

It might occur in the following few situations.

No locks available

Cause

No file locks are available on the NFS file system. This problem will occur if your Jira is running on an NFS file system - this applies mainly to Jira Data Center.

The situation may occur:

• after performing a "Create Snapshot" operation,

• after starting the "Restore" process,

• after updating the application to a newer version.

Diagnosis

Verify if the following entry appears in the logs:

============================================================================================================
NO LOCKS AVAILABLE, this error is usually caused by the NFS daemons not running or malfunctioning.
Try to restart and verify functionality of all NFS related daemons on your system, most importantly lockd.

You can also make sure this is the case, by manually creating a lock on a file in a directory used by the plugin, e.g. /shared-data/sharedhome/export/softwareplant/bigpicture. As a result of such action the same error should appear as in our application logs i.e. "No locks available".

Solution

Restart and verify functionality of all NFS related daemons on your system, most importantly lockd. See the following page for further reference: http://osr507doc.sco.com/en/NetAdminG/nfsC.daemons.html

Directory Access Denied

Cause

You will see this screen when directory access has been denied for Jira - this applies to Jira Server/Data Center.

The situation may occur:

• after performing a "Create Snapshot" operation,

• after starting the "Restore" process,

• after updating the application to a newer version.

Diagnosis

Verify if the following entry appears in the logs:

============================================================================================================ 
ACCESS DENIED FOR DIRECTORY UNDER PATH: <directoryPath>.
The problem occurs because the directory might not be owned by user that Jira is run on the behalf of.
Check whether that particular user has 'write' access to <directoryPath>.

Solution

The given directory is not accessible to Jira. You should grant the Jira user access to this directory.
If this is not enough, then try to grant access to these two directories in addition:

• /media/atl/<directory-path>/export 

• /media/atl/<directory-path>

For Unix/Unix-like systems use the command: 'chown <user that jira is run on the behalf of> <directoryPath>'
e.g. 'chown jira jira-data'