nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Moving from 3.14 to 4.4.5 jira version errors

Pavel Khvostov

I'm moving to 4.4.5 version

I've installed SQl server, Create new base call JIRADB, conected well and trying to upgrade the xml file from 3.14 version.

When all 100% complete there is an error 'Jira has already been set up'

and then:

==============================

You cannot access JIRA at present.

An error occurred performing JIRA upgrade task

Exception thrown during upgrade: java.util.concurrent.ExecutionException: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Ошибка входа пользователя "jiradbuser".)
java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Ошибка входа пользователя "jiradbuser".)
	at com.atlassian.jira.index.FutureResult.await(FutureResult.java:35)
	at com.atlassian.jira.index.CompositeResultBuilder$CompositeResult.await(CompositeResultBuilder.java:82)
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexAll(DefaultIndexManager.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:81)
	at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28)
	at $Proxy124.reIndexAll(Unknown Source)
	at com.atlassian.jira.util.index.IndexLifecycleManager$Composite.reIndexAll(IndexLifecycleManager.java:112)
	at com.atlassian.jira.upgrade.tasks.AbstractReindexUpgradeTask.doUpgrade(AbstractReindexUpgradeTask.java:43)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSuccess(UpgradeManagerImpl.java:609)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.runUpgradeTasks(UpgradeManagerImpl.java:496)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgrade(UpgradeManagerImpl.java:426)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:370)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:309)
	at com.atlassian.jira.bc.dataimport.DefaultDataImportService.upgradeJira(DefaultDataImportService.java:562)
	at com.atlassian.jira.bc.dataimport.DefaultDataImportService.performImport(DefaultDataImportService.java:497)
	at com.atlassian.jira.bc.dataimport.DefaultDataImportService.doImport(DefaultDataImportService.java:214)
	at com.atlassian.jira.web.action.setup.DataImportAsyncCommand.call(DataImportAsyncCommand.java:65)
	at com.atlassian.jira.web.action.setup.DataImportAsyncCommand.call(DataImportAsyncCommand.java:28)
	at com.atlassian.jira.task.ImportTaskManagerImpl$TaskCallableDecorator.call(ImportTaskManagerImpl.java:147)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForTenant(DefaultMultiTenantManager.java:61)
	at com.atlassian.multitenant.juc.MultiTenantExecutors$WrappedRunnable.run(MultiTenantExecutors.java:160)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: java.util.concurrent.ExecutionException: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Ошибка входа пользователя "jiradbuser".)
	at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
	at java.util.concurrent.FutureTask.get(FutureTask.java:83)
	at com.atlassian.jira.index.FutureResult.await(FutureResult.java:31)
	... 32 more
Caused by: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Ошибка входа пользователя "jiradbuser".)
	at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:96)
	at com.atlassian.jira.association.UserAssociationStoreImpl.getAssociations(UserAssociationStoreImpl.java:168)
	at com.atlassian.jira.association.UserAssociationStoreImpl.getUsernamesFromSink(UserAssociationStoreImpl.java:128)
	at com.atlassian.jira.issue.watchers.DefaultWatcherManager.getCurrentWatcherUsernames(DefaultWatcherManager.java:89)
	at com.atlassian.jira.issue.watchers.DefaultIssueWatcherAccessor.getWatcherNames(DefaultIssueWatcherAccessor.java:46)
	at com.atlassian.jira.issue.index.indexers.impl.WatcherIndexer.addIndex(WatcherIndexer.java:40)
	at com.atlassian.jira.issue.index.IssueDocument.getDocument(IssueDocument.java:40)
	at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory.get(DefaultIssueDocumentFactory.java:15)
	at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory.get(DefaultIssueDocumentFactory.java:11)
	at com.atlassian.jira.issue.index.DefaultIssueIndexer$IssueLockDocumentCreationStrategy$2.get(DefaultIssueIndexer.java:512)
	at com.atlassian.jira.issue.index.DefaultIssueIndexer$IssueLockDocumentCreationStrategy$2.get(DefaultIssueIndexer.java:509)
	at com.atlassian.util.concurrent.ManagedLocks$ManagedLockImpl.withLock(ManagedLocks.java:315)
	at com.atlassian.jira.issue.index.DefaultIssueIndexer$IssueLockDocumentCreationStrategy.get(DefaultIssueIndexer.java:508)
	at com.atlassian.jira.issue.index.DefaultIssueIndexer$IssueLockDocumentCreationStrategy.get(DefaultIssueIndexer.java:496)
	at com.atlassian.jira.issue.index.DefaultIssueIndexer$IndexIssuesOperation.perform(DefaultIssueIndexer.java:371)
	at com.atlassian.jira.issue.index.DefaultIssueIndexer$4$1.get(DefaultIssueIndexer.java:255)
	at com.atlassian.jira.issue.index.DefaultIssueIndexer$4$1.get(DefaultIssueIndexer.java:251)
	at com.atlassian.jira.index.SimpleIndexingStrategy.get(SimpleIndexingStrategy.java:9)
	at com.atlassian.jira.index.SimpleIndexingStrategy.get(SimpleIndexingStrategy.java:5)
	at com.atlassian.jira.index.MultiThreadedIndexingStrategy$1.call(MultiThreadedIndexingStrategy.java:39)
	at com.atlassian.jira.index.MultiThreadedIndexingStrategy$1.call(MultiThreadedIndexingStrategy.java:36)
	at com.atlassian.jira.util.concurrent.BoundedExecutor$2.call(BoundedExecutor.java:70)
	... 7 more
Caused by: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Ошибка входа пользователя "jiradbuser".)
	at org.ofbiz.core.entity.jdbc.SQLProcessor.getConnection(SQLProcessor.java:371)
	at org.ofbiz.core.entity.jdbc.SQLProcessor.prepareStatement(SQLProcessor.java:515)
	at org.ofbiz.core.entity.GenericDAO.selectListIteratorByCondition(GenericDAO.java:1034)
	at org.ofbiz.core.entity.GenericDAO.selectByAnd(GenericDAO.java:605)
	at org.ofbiz.core.entity.GenericHelperDAO.findByAnd(GenericHelperDAO.java:131)
	at org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:790)
	at org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:775)
	at org.ofbiz.core.entity.GenericDelegator.findByAnd(GenericDelegator.java:752)
	at sun.reflect.GeneratedMethodAccessor178.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$AbstractMultiTenantAwareInvocationHandler.invokeInternal(MultiTenantComponentFactoryImpl.java:181)
	at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$MultiTenantAwareMethodInterceptor.intercept(MultiTenantComponentFactoryImpl.java:230)
	at org.ofbiz.core.entity.GenericDelegator$$EnhancerByCGLIB$$4a3c2b90.findByAnd()
	at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:92)
	... 28 more

==============================

I've tryed to clear the Index directory, the files in it creating during te upgrade

SQL base also has all the tables 

Wrat am I doing wrong?

Accepted answers

All comments

Nic Brough -Adaptavist-

The error message is telling you that it can't connect to the database - either a network error, or you've got the wrong credentials for the database user. As you've connected before to set it up, that's unlikley unless you've been changing things on the database side. However, check the permissions on the user too - make sure it's got full read/write/delete/drop/index rights inside the schema.

rambabu patina

May be the problem is with authentication type in the SQL server. Please check it.

Pavel Khvostov

this error also when I trying to upgrade on default jira database - hsql...

Is there any other things that I need to check?

Nic Brough -Adaptavist-

You've probably not swapped back all the settings from SQL Server to HSQL. It's the same problem - your authentication or user details for the database are incorrect.

Pavel Khvostov

And the SQL base is full after upgrade

Pavel Khvostov

Nic, I will check, thanks

Pavel Khvostov

I gave the maximum rights to JIRADBUSER, but still when the upgrade is in 96%,and the process "Reindexing data: Indexing" I have an "JIRA has already been set up" error

Pavel Khvostov

Where could I give the full read/write/delete/drop/index rights inside the schema?

Nic Brough -Adaptavist-

That's a totally different error. You'll need to give us more information about the error and what the log says from start up until you get that error.

Nic Brough -Adaptavist-

It's a setting on the account in the database server.

Pavel Khvostov

I don't know exactly what happend, I re'install JIRA ,SQL Server and it works.

Thanks, Nic.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira