JIRA Auditor plugin does not work

Donna Elwood October 28, 2014
 

2 answers

0 votes
Donna Elwood October 31, 2014

I did raise an issue with them…

The auditing in JIRA 6+ is not as advanced as the plugin which is the reason we just purchased it.   Somewhere a notice should be posted to let users know the plugin functionality is being incorporated into JIRA 6+ so they know whether or not to purchase it.   In our case, we use JIRA 6.3.4 and  would not have purchased the plugin.  Now we have the daunting task of trying to obtain a refund.

Thank-you for your help.

 

 

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 28, 2014

Define "does not work".  What have you configure and how?  I know what the auditor is supposed to do, but the question is what you're expecting and where you are looking?

Donna Elwood October 29, 2014

Installed and configured JIRA Auditor plugin.  Ran several administrative tasks to view log.  The audit log did not display any entries.  

A SQL Exception was reported in the log file. Have you seen this error before? Do you know how to resolve it?

/secure/admin/JiraAuditorBrowse!view.jspa [plugenta.jiraauditor.database.DataLayer] Error executing SELECT count(*) FROM AUDIT_LOG_EVENTS WHERE 1=1: java.sql.SQLException: Invalid object name 'AUDIT_LOG_EVENTS'.
2014-10-29 18:34:53,574 http-bio-8080-exec-16 ERROR elwood 1114x127504x2 184v99j 172.19.120.7 /secure/admin/JiraAuditorBrowse!view.jspa [plugenta.jiraauditor.database.DataLayer] Error executing event query: java.sql.SQLException: Invalid object name 'AUDIT_LOG_EVENTS'.

 

 

 

 

 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 29, 2014

That suggests the installation of the plugin failed to create (or correctly create anyway) the tables it needs in the database. I'd look further back through the log to see if there were errors during the installation. Or try removing it completely and re-installing it, and see if that provokes a repeat of the errors.

Donna Elwood October 30, 2014

Uninstalled the plugin. Cleared the JIRA Plugin cache and work directories. Reinstalled JIRA Auditor - The log file states an error creating the Audit Log Events table(below). We have an MSSQL database, and have not had any previous issues with plugin installations. I can have the table created manually, however I do not know what other data is required. The JIRA Audit log 2014-10-30 11:53:48,312 UpmAsynchronousTaskManager:thread-2 INFO elwood 712x547x2 19upq86 172.19.120.7 /rest/plugins/1.0/available/featured [atlassian.plugin.loaders.ScanningPluginLoader] No plugins found to be installed 2014-10-30 11:53:48,582 UpmAsynchronousTaskManager:thread-2 INFO elwood 712x547x2 19upq86 172.19.120.7 /rest/plugins/1.0/available/featured [atlassian.plugin.manager.PluginEnabler] Waiting for ENABLING plugins: [com.plugenta.jiraauditor] 2014-10-30 11:53:48,582 UpmAsynchronousTaskManager:thread-2 INFO elwood 712x547x2 19upq86 172.19.120.7 /rest/plugins/1.0/available/featured [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [com.plugenta.jiraauditor], 60 seconds remaining 2014-10-30 11:53:49,582 UpmAsynchronousTaskManager:thread-2 INFO elwood 712x547x2 19upq86 172.19.120.7 /rest/plugins/1.0/available/featured [atlassian.plugin.manager.PluginEnabler] Plugin 'com.plugenta.jiraauditor' is now ENABLED 2014-10-30 11:55:27,513 http-bio-8080-exec-23 INFO elwood 715x889x1 19upq86 172.19.120.7 /rest/plugins/1.0/com.atlassian.jira.plugins.jira-importers-bitbucket-plugin-key [atlassian.plugin.manager.DefaultPluginManager] Disabling com.atlassian.jira.plugins.jira-importers-bitbucket-plugin 2014-10-30 11:55:51,829 http-bio-8080-exec-2 ERROR elwood 715x907x1 19upq86 172.19.120.7 /secure/admin/JiraAuditorBrowse!view.jspa [plugenta.jiraauditor.database.DataLayer] Error executing CREATE TABLE AUDIT_LOG_EVENTS ( id BIGINT not NULL, event_type VARCHAR(255) not NULL, user_name VARCHAR(255), ip_address VARCHAR(255), event_time CHAR(30), PRIMARY KEY ( id )): java.sql.SQLException: The default schema does not exist. 2014-10-30 11:55:51,854 http-bio-8080-exec-2 ERROR elwood 715x907x1 19upq86 172.19.120.7 /secure/admin/JiraAuditorBrowse!view.jspa [plugenta.jiraauditor.database.DataLayer] Error executing CREATE TABLE AUDIT_LOG_EVENT_PARAMETERS ( id BIGINT not NULL, event_id BIGINT not NULL, parameter_name VARCHAR(255) not NULL, parameter_value VARCHAR(255), PRIMARY KEY ( id )): java.sql.SQLException: The default schema does not exist. 2014-10-30 11:55:51,872 http-bio-8080-exec-2 ERROR elwood 715x907x1 19upq86 172.19.120.7 /secure/admin/JiraAuditorBrowse!view.jspa [plugenta.jiraauditor.database.DataLayer] Error executing SELECT MAX(id) FROM AUDIT_LOG_EVENTS: java.sql.SQLException: Invalid object name 'AUDIT_LOG_EVENTS'. 2014-10-30 11:55:51,875 http-bio-8080-exec-2 ERROR elwood 715x907x1 19upq86 172.19.120.7 /secure/admin/JiraAuditorBrowse!view.jspa [plugenta.jiraauditor.database.DataLayer] Error executing SELECT MAX(id) FROM AUDIT_LOG_EVENT_PARAMETERS: java.sql.SQLException: Invalid object name 'AUDIT_LOG_EVENT_PARAMETERS'. 2014-10-30 11:55:51,884 http-bio-8080-exec-2 ERROR elwood 715x907x1 19upq86 172.19.120.7 /secure/admin/JiraAuditorBrowse!view.jspa [plugenta.jiraauditor.database.DataLayer] Error executing SELECT count(*) FROM AUDIT_LOG_EVENTS WHERE 1=1: java.sql.SQLException: Invalid object name 'AUDIT_LOG_EVENTS'.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 30, 2014

Hmm, I think you have hit a bug in the auditing plugin then - the failure to identify the schema to create the tables in is pretty much broken. You could raise this with Plugenta, but I'm not sure they're developing it any further because the functionality has been absorbed into Jira 6.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events