Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

What happened to our Jira?

It had been working fine until last Tuesday morning when it suddenly would not launch.  The Jira administrator and I have both looked at this and need some insight. 

 

This is from TomCat:

at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttp
Client.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttp
Client.java:83)
at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpCli
entRequest.java:103)
... 33 more
2019-04-30 12:09:10,317 JIRA-Bootstrap WARN [c.o.s.runner.startup.JiraStart
upManager] Waiting for jql functions registration
2019-04-30 12:09:10,395 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.Active
ObjectsServiceFactory] getService bundle [com.onresolve.jira.groovy.groovyrunner
]
2019-04-30 12:09:14,911 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.Active
ObjectsServiceFactory] getService bundle [com.pyxis.greenhopper.jira]
2019-04-30 12:09:14,958 JIRA-Bootstrap INFO [c.a.j.p.e.bamboo.service.PlanS
tatusUpdateServiceImpl] PlanStatusUpdateJob scheduled to run every 60 seconds
2019-04-30 12:09:15,317 JIRA-Bootstrap INFO [c.a.j.config.managedconfigurat
ion.DefaultManagedConfigurationItemStore] Managed Configuration Item registered:
com.atlassian.jira.config.managedconfiguration.ManagedConfigurationItem@62e0410
e[id=10200,itemId=customfield_11230,itemType=CUSTOM_FIELD,isManaged=true,configu
rationItemAccessLevel=LOCKED,sourceId=<null>,descriptionI18nKey=admin.managed.co
nfiguration.items.generic.description.locked]
2019-04-30 12:09:17,255 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.Active
ObjectsServiceFactory] getService bundle [com.atlassian.labs.hipchat.hipchat-for
-jira-plugin]
2019-04-30 12:09:17,255 JIRA-Bootstrap INFO [c.a.j.p.hipchat.service.HipCha
tPluginLauncher] HipChat Plugin launched successfully
2019-04-30 12:09:17,255 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] On plugin event: com.atlassian.jira.plugins.hipchat.model.
event.PluginStartedEvent
2019-04-30 12:09:17,255 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] Registering a new hipchatInstallGlancesJob task.
2019-04-30 12:09:17,270 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] On plugin event: com.atlassian.jira.plugins.hipchat.model.
event.PluginStartedEvent
2019-04-30 12:09:17,270 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] Registering a new hipchatUpdateGlancesDataJob task.
2019-04-30 12:09:17,270 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] On plugin event: com.atlassian.jira.plugins.hipchat.model.
event.PluginStartedEvent
2019-04-30 12:09:17,270 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] Registering a new hipchatRefreshConnectionStatusJob task.
2019-04-30 12:09:17,302 WaitForAO DEBUG [c.a.activeobjects.osgi.ActiveObjec
tsServiceFactory] getService bundle [com.atlassian.jira.plugins.jira-dvcs-connec
tor-plugin]
2019-04-30 12:09:18,255 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.Active
ObjectsServiceFactory] getService bundle [com.fdu.jira.plugin.jira-timesheet-plu
gin]
2019-04-30 12:09:18,755 JIRA-Bootstrap INFO [c.a.j.c.embedded.ofbiz.Indexed
UserDao] Reindex all users took: 283.1 ms
2019-04-30 12:09:18,786 JIRA-Bootstrap INFO [c.a.jira.scheduler.JiraSchedul
erLauncher] Starting the JIRA Scheduler....
2019-04-30 12:09:18,802 JIRA-Bootstrap INFO [c.a.jira.scheduler.JiraSchedul
erLauncher] JIRA Scheduler started.
2019-04-30 12:09:18,911 JIRA-Bootstrap WARN [c.a.jira.startup.JiraStartupLo
gger]

****************************************************************************
********************************************************************************
********************************************
___ FAILED PLUGIN REPORT _____________________

2 plugins failed to load during JIRA startup.

'is.origo.jira.tempo-plugin' - 'Tempo Plugin' failed to load.
Error loading class [com.tempoplugin.scheduler.job.RemindAllJob]
for bean with name 'remindAllJob' defined in URL [bundle://201.0:0/META-INF/spr
ing/atlassian-plugins-components.xml]: problem with class file or dependent clas
s; nested exception is java.lang.NoClassDefFoundError: com.tempoplugin.scheduler
.job.RemindAllJob not found from bundle [is.origo.jira.tempo-plugin (is.origo.ji
ra.tempo-plugin)]
com.tempoplugin.scheduler.job.RemindAllJob not found fro
m bundle [is.origo.jira.tempo-plugin (is.origo.jira.tempo-plugin)]
org/quartz/Job
org.quartz.Job not found by is.origo.jir
a.tempo-plugin [201]

It was loaded from E:\jira\application-data\plugins\installed-pl
ugins\plugin.7607553867445573603.tempo-plugin-6.3.0-jira42.jar

'com.sysbliss.jira.plugins.jira-workflow-designer' - 'Jira Workflow Desi
gner' failed to load.
Cannot start plugin: com.sysbliss.jira.plugins.jira-workflow-des
igner
Unresolved constraint in bundle com.sysbliss.jira.plugin
s.jira-workflow-designer [191]: Unable to resolve 191.0: missing requirement [19
1.0] osgi.wiring.package; (osgi.wiring.package=com.sysbliss.flex.service)

It was loaded from E:\jira\application-data\plugins\installed-pl
ugins\jira-workflow-designer-1.1.1.jar
5 plugins are unaccounted for.
Unaccounted for plugins load as artifacts but fail to resolve into full plug
ins.

'com.metainf.jira.plugin.emailissue' - 'Email This Issue' is unaccounte
d for.

It was loaded from E:\jira\application-data\plugins\installed-pl
ugins\plugin.5378938955666719782.emailissue-7.1.1.15.jar

'com.intergalactic.plugins.teamcity-view-builds' - 'TeamCity Builds View
er' is unaccounted for.

It was loaded from E:\jira\application-data\plugins\installed-pl
ugins\teamcity-view-builds-1.0-Beta1.jar

'com.suggestimate' - 'SuggestiMate for Jira' is unaccounted for.

It was loaded from E:\jira\application-data\plugins\installed-pl
ugins\plugin.1012234339694390718.suggestimate-3.2.7.jar

'plugin.jep' - 'Enhancer Plugin for JIRA' is unaccounted for.

It was loaded from E:\jira\application-data\plugins\installed-pl
ugins\plugin.4402489658181633022.jira-enhancer-plugin-5.41.1.jar

'create.issue.and.link' - 'Link New Issue Operation Plugin' is unaccoun
ted for.

It was loaded from E:\jira\application-data\plugins\installed-pl
ugins\link-new-issue-operation-2.7.2.jar

****************************************************************************
********************************************************************************
********************************************

2019-04-30 12:09:19,099 Caesium-1-3 INFO [c.a.crowd.directory.DbCachingRemo
teDirectory] INCREMENTAL synchronisation for directory [ 10200 ] starting
2019-04-30 12:09:19,145 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherConte
xtListener] Memory Usage:
----------------------------------------------------------------------------
-----
Heap memory : Used: 463 MiB. Committed: 673 MiB. Max: 749 MiB
Non-heap memory : Used: 277 MiB. Committed: 301 MiB. Max: 1264 MiB
----------------------------------------------------------------------------
-----
TOTAL : Used: 740 MiB. Committed: 973 MiB. Max: 2013 MiB
----------------------------------------------------------------------------
-----
2019-04-30 12:09:19,145 Caesium-1-3 INFO [c.a.crowd.directory.DbCachingRemo
teDirectory] Attempting INCREMENTAL synchronisation for directory [ 10200 ]
2019-04-30 12:09:19,177 Caesium-1-3 INFO [c.a.c.d.ldap.cache.UsnChangedCach
eRefresher] After restarting, full sync of directory [10200] is necessary before
incremental sync is possible.
2019-04-30 12:09:19,177 Caesium-1-3 INFO [c.a.crowd.directory.DbCachingRemo
teDirectory] Incremental synchronisation for directory [ 10200 ] was not complet
ed, falling back to a full synchronisation
2019-04-30 12:09:19,177 Caesium-1-3 INFO [c.a.crowd.directory.DbCachingRemo
teDirectory] INCREMENTAL synchronisation for directory [ 10200 ] was not success
ful, attempting FULL
2019-04-30 12:09:20,271 CrowdUsnChangedCacheRefresher:thread-2 INFO [c.a.c.
d.ldap.cache.UsnChangedCacheRefresher] found [ 20 ] remote groups in [ 1001ms ]
2019-04-30 12:09:20,255 CrowdUsnChangedCacheRefresher:thread-1 INFO [c.a.c.
d.ldap.cache.UsnChangedCacheRefresher] found [ 17 ] remote users in [ 985ms ]
2019-04-30 12:09:20,677 Caesium-1-3 INFO [c.a.crowd.directory.DbCachingRemo
teChangeOperations] scanned and compared [ 17 ] users for delete in DB cache in
[ 47ms ]
2019-04-30 12:09:20,677 Caesium-1-3 INFO [c.a.crowd.directory.DbCachingRemo
teChangeOperations] scanned for deleted users in [ 47ms ]
2019-04-30 12:09:20,677 Caesium-1-3 INFO [c.a.crowd.directory.DbCachingRemo
teChangeOperations] scanning [ 17 ] users to add or update
2019-04-30 12:09:20,692 Caesium-1-3 INFO [c.a.crowd.directory.DirectoryCach
eImplUsingChangeOperations] scanned and compared [ 17 ] users for update in DB c
ache in [ 15ms ]
2019-04-30 12:09:20,692 Caesium-1-3 INFO [c.a.crowd.directory.DirectoryCach
eImplUsingChangeOperations] synchronised [ 17 ] users in [ 15ms ]
2019-04-30 12:09:20,708 Caesium-1-3 INFO [c.a.crowd.directory.DbCachingRemo
teChangeOperations] scanned and compared [ 20 ] groups for delete in DB cache in
[ 16ms ]
2019-04-30 12:09:20,708 Caesium-1-3 INFO [c.a.crowd.directory.DirectoryCach
eImplUsingChangeOperations] scanning [ 20 ] groups to add or update
2019-04-30 12:09:20,708 Caesium-1-3 INFO [c.a.crowd.directory.DbCachingRemo
teChangeOperations] scanned and compared [ 20 ] groups for update in DB cache in
[ 0ms ]
2019-04-30 12:09:20,724 Caesium-1-3 INFO [c.a.crowd.directory.DirectoryCach
eImplUsingChangeOperations] synchronized [ 20 ] groups in [ 16ms ]
2019-04-30 12:09:20,817 Caesium-1-3 INFO [c.a.c.d.ldap.cache.AbstractCacheR
efresher] finished group attribute sync with 0 failures in [ 93ms ]
2019-04-30 12:09:20,864 Caesium-1-1 WARN [c.a.j.p.dvcs.service.RepositorySy
ncServiceImpl] Repo list had updates when DB reconciled with bitbucket. [EmbTrak
Enterprise, AncientHistory, StandaloneUtilities, EmbTrakNet, Catalog.NET, EmbTra
k, InterfaceEngine] repos deleted, [] new repos
2019-04-30 12:09:22,239 Caesium-1-3 INFO [c.a.crowd.directory.DbCachingRemo
teDirectory] FULL synchronisation complete for directory [ 10200 ] in [ 3140ms ]

2019-04-30 12:09:25,990 Caesium-1-2 INFO [c.a.jira.startup.CacheWarmerLaunc
her] Warming up 3 caches.
2019-04-30 12:09:26,146 Caesium-1-1 INFO ServiceRunner [c.a.j.index.ha.Defau
ltIndexRecoveryManager] Latest index date: {2019-04-18 16:55:52}, Latest DB date
: {2019-04-18 16:55:52}
2019-04-30 12:09:26,161 Caesium-1-2 INFO [c.a.jira.i18n.I18nWarmer] Init i1
8n cache
2019-04-30 12:09:26,255 ForkJoinPool.commonPool-worker-1 INFO [c.a.j.cache.
soy.SoyCacheWarmer] Warming 41 soy modules
2019-04-30 12:09:32,974 Caesium-1-4 INFO anonymous Backup Service [c.a.j.bc.d
ataimport.DefaultExportService] Data export completed in 13219ms. Wrote 337569 e
ntities to export in memory.
2019-04-30 12:09:32,990 Caesium-1-4 INFO anonymous Backup Service [c.a.j.bc.d
ataimport.DefaultExportService] Attempting to save the Active Objects Backup
2019-04-30 12:09:39,412 Caesium-1-1 DEBUG ServiceRunner [c.a.activeobjects.o
sgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.plugins.base-h
ipchat-integration-plugin-api]
2019-04-30 12:09:39,412 Caesium-1-3 INFO [c.a.j.p.h.service.ping.RefreshCon
nectionStatusJobHandler] Running RefreshConnectionStatusJobHandler...
2019-04-30 12:09:42,990 Caesium-1-3 INFO [c.a.j.p.h.service.connect.Install
GlancesJobHandler] Running InstallGlancesJobHandler...
2019-04-30 12:09:43,209 Caesium-1-3 INFO [c.a.j.p.h.service.connect.Install
GlancesJobHandler] There is no link to HipChat, no need to install glances.
2019-04-30 12:09:45,100 ForkJoinPool.commonPool-worker-1 INFO [c.a.j.cache.
soy.SoyCacheWarmer] Warmed 41 soy module(s) in 18829 ms, 0 module(s) were not pr
esent or disabled, 0 failed.
2019-04-30 12:09:45,100 Caesium-1-4 INFO anonymous Backup Service [c.a.j.bc.d
ataimport.DefaultExportService] Finished saving the Active Objects Backup
2019-04-30 12:09:51,975 Caesium-1-2 INFO [c.a.jira.i18n.I18nWarmer] Initial
ised i18n cache in 25814
2019-04-30 12:09:51,975 Caesium-1-2 INFO [c.a.jira.startup.CacheWarmerLaunc
her] Warmed cache(s) in 25923 ms.
2019-04-30 12:10:06,444 Caesium-1-2 INFO [c.a.jira.upgrade.UpgradeScheduler
] Running scheduled upgrades
2019-04-30 12:10:06,475 Caesium-1-2 INFO [c.a.jira.upgrade.LoggingUpgradeSe
rvice] run upgrades has started
2019-04-30 12:10:06,506 Caesium-1-2 INFO [c.a.j.upgrade.util.BuildNumberDao
] Setting current build number to 712004
2019-04-30 12:10:06,522 Caesium-1-2 DEBUG [c.a.activeobjects.osgi.ActiveObj
ectsServiceFactory] getService bundle [com.atlassian.jira.plugins.webhooks.jira-
webhooks-plugin]
created com.atlassian.jira.plugins.webhooks.ao.WebhookDaoImpl@47b2afb5 120289272
5 with events worklog_created
board_deleted
option_unassigned_issues_changed
comment_updated
user_created
jira:version_created
board_configuration_changed
project_deleted
comment_deleted
project_updated
option_issuelinks_changed
sprint_created
jira:issue_updated
sprint_updated
comment_created
option_timetracking_changed
option_attachments_changed
jira:issue_created
issuelink_deleted
jira:issue_deleted
sprint_deleted
project_created
issuelink_created
jira:version_unreleased
board_created
jira:version_moved
sprint_closed
user_updated
jira:version_released
jira:version_deleted
sprint_started
jira:version_merged
worklog_deleted
jira:worklog_updated
jira:version_updated
option_subtasks_changed
worklog_updated
user_deleted
board_updated
AO_4AEACD_WEBHOOK_DAO {ID = 1} 36132
2019-04-30 12:10:06,584 Caesium-1-2 INFO [c.a.jira.upgrade.UpgradeIndexMana
ger] There is no reindex requests of type [IMMEDIATE, DELAYED] so none will be r
un
2019-04-30 12:10:06,584 Caesium-1-2 INFO [c.a.j.upgrade.util.BuildNumberDao
] Setting current version to 7.12.3
2019-04-30 12:10:06,600 Caesium-1-2 INFO [c.a.j.upgrade.util.BuildNumberDao
] Setting downgrade version to 7.1.2
2019-04-30 12:10:06,616 Caesium-1-2 INFO [c.a.jira.upgrade.LoggingUpgradeSe
rvice] run upgrades has finished successfully, and took 141 milliseconds to proc
ess.
2019-04-30 12:10:06,616 Caesium-1-2 INFO [c.a.jira.upgrade.UpgradeScheduler
] JIRA upgrades completed successfully
2019-04-30 12:10:06,631 Caesium-1-2 INFO [c.a.jira.upgrade.UpgradeScheduler
] Plugins upgrades completed successfully
2019-04-30 12:10:06,631 Caesium-1-2 INFO [c.a.jira.upgrade.UpgradeIndexMana
ger] Reindexing is not allowed after this upgrade and there is no immediate rein
dex requests
2019-04-30 12:10:12,459 Modification Check:thread-1 INFO [c.a.jira.startup.
JiraStartupLogger]

___ Modifications ___________________________

Modified Files : jira-application.proper
ties, WEB-INF/web.xml
Removed Files : None

2019-04-30 12:10:30,960 HealthCheckWatchdog:thread-4 WARN ServiceRunner [c.a
.t.healthcheck.concurrent.SupportHealthCheckTask] Health check Application links
was unable to complete within the timeout of 20000.
2019-04-30 12:10:30,960 Caesium-1-1 DEBUG ServiceRunner [c.a.activeobjects.o
sgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.troubleshootin
g.plugin-jira]

 

 

3 answers

1 vote
Tarun Sapra Community Leader May 01, 2019

Hello @Brian Medford 

As per the logs

"2 plugins failed to load during JIRA startup."

So you are unable to start Jira because plugins are not loading.

You need to start Jira in safe mode(only with system plugins and without any custom plugins, you can enable them later from manage apps section)

Please see the fix here (from Jira 7.3 onwards)

https://jira.atlassian.com/browse/JRASERVER-65343

--disable-all-addons (or /disablealladdons for windows users)
--disable-addons=<addon keys> or (/disableaddons=<addon keys> for windows users)

If you can't do the above then try this

  1. Stop JIRA
  2. Navigate to <JIRA_HOME>/plugins/installed-plugins, rename the installed-plugins directory to installed2-plugins as this forces JIRA to start without all additionally installed plugins.

Once Jira is started then try to install all the plugins one by one, this will help you troubleshoot the exact plugin which is causing problem.

Generally plugins downloaded from marketplace are well tested and rarely cause startup problems. Thus, double check the plugin version compatibility with your Jira instance version or install the right version via the UPM.

If it still doesn't work, then contact that specific plugin vendor via the contact link on the plugin listing on the marketplace.

Tarun Sapra Community Leader May 01, 2019

Also, uninstalling and then reinstalling a plugin doesn't lead to lose of the plugin data. So if you have time-sheet entries in tempo plugin and you uninstall it and then again install it back then the data would still be-intact

I changed the installed-plugins folder name and Jira did create a new one.  Now we are hung in this location:

 

2019-05-01 10:40:13,578 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'com.atlassian.jira.ext.charting' and name 'JIRA Charting P
lugin' and version '2.3.0' is being removed from the system.
2019-05-01 10:40:13,578 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'plugin.jep' and name 'Enhancer Plugin for JIRA' and versio
n '5.41.1' is being removed from the system.
2019-05-01 10:40:13,593 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'jira-timesheet-plugin' and name 'Timesheet Reports and Gad
gets' and version '3.3.9' is being removed from the system.
2019-05-01 10:40:13,593 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'tac.jira software.languages.pl_PL' and name 'JIRA Software
Polish (Poland) Language Pack' and version '7.13.0.v20180831085841' is being re
moved from the system.
2019-05-01 10:40:13,593 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'tac.jira software.languages.nl_NL' and name 'JIRA Software
Dutch (Netherlands) Language Pack' and version '7.13.0.v20180831085841' is bein
g removed from the system.
2019-05-01 10:40:13,671 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'com.pyxis.greenhopper.jira' and name 'JIRA Agile' and vers
ion '7.12.0-DAILY20180906101548' is being removed from the system.
2019-05-01 10:40:13,671 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'com.soyatec.jira.plugins.jira-ganttchart-project' and name
'Gantt-Chart Project for Jira - Enterprise Edition' and version '3.6.31' is bei
ng removed from the system.
2019-05-01 10:40:13,671 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'tac.jira software.languages.et_EE' and name 'JIRA Software
Estonian (Estonia) Language Pack' and version '7.13.0.v20180831085841' is being
removed from the system.
2019-05-01 10:40:13,671 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'com.atlassian.jira.plugin.ext.bamboo' and name 'Jira Bambo
o Plugin' and version '7.4.11' is being removed from the system.
2019-05-01 10:40:13,687 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'com.atlassian.jira.plugins.jira-transition-triggers-plugin
' and name 'Atlassian JIRA - Plugins - Transition Trigger Plugin' and version '6
.0.0' is being removed from the system.
2019-05-01 10:40:13,687 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'de.polscheit.jira.plugins.gantt' and name 'Gantt-Chart for
JIRA' and version '4.4.0-JIRA7-8' is being removed from the system.
2019-05-01 10:40:13,687 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'tac.jira software.languages.ro_RO' and name 'JIRA Software
Romanian (Romania) Language Pack' and version '7.13.0.v20180831085841' is being
removed from the system.
2019-05-01 10:40:13,687 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'com.atlassian.jira.plugins.jira-software-monitor-plugin' a
nd name 'JIRA Software Monitor Plugin' and version '0.1.0-D20150923T085539' is b
eing removed from the system.
2019-05-01 10:40:13,703 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'com.sysbliss.jira.plugins.jira-workflow-designer' and name
'Jira Workflow Designer' and version '1.1.1' is being removed from the system.
2019-05-01 10:40:13,703 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'create.issue.and.link' and name 'Link New Issue Operation
Plugin' and version '2.7.2' is being removed from the system.
2019-05-01 10:40:13,718 JIRA-Bootstrap INFO [c.a.jira.plugin.JiraPluginMana
ger] Plugin with key 'com.atlassian.jira.ext.calendar' and name 'JIRA Calendar P
lugin' and version '4.0.3' is being removed from the system.
2019-05-01 10:40:13,718 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLo
gger]

___ Plugin System Started _________________

2019-05-01 10:40:13,781 JIRA-Bootstrap INFO [c.a.jira.upgrade.UpgradeSchedu
ler] Scheduling upgrades to run in 1 minute(s)
2019-05-01 10:40:14,078 JIRA-Bootstrap INFO [c.a.j.c.embedded.ofbiz.Indexed
UserDao] Reindex all users took: 280.2 ms
2019-05-01 10:40:14,343 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.Active
ObjectsServiceFactory] getService bundle [com.atlassian.jira.plugins.webhooks.ji
ra-webhooks-plugin]
created com.atlassian.jira.plugins.webhooks.ao.WebhookDaoImpl@47b882c9 120327444
1 with events worklog_created
board_deleted
option_unassigned_issues_changed
comment_updated
user_created
jira:version_created
board_configuration_changed
project_deleted
comment_deleted
project_updated
option_issuelinks_changed
sprint_created
jira:issue_updated
sprint_updated
comment_created
option_timetracking_changed
option_attachments_changed
jira:issue_created
issuelink_deleted
jira:issue_deleted
sprint_deleted
project_created
issuelink_created
jira:version_unreleased
board_created
jira:version_moved
sprint_closed
user_updated
jira:version_released
jira:version_deleted
sprint_started
jira:version_merged
worklog_deleted
jira:worklog_updated
jira:version_updated
option_subtasks_changed
worklog_updated
user_deleted
board_updated
AO_4AEACD_WEBHOOK_DAO {ID = 1} 15592
2019-05-01 10:40:14,656 JIRA-Bootstrap DEBUG [c.a.activeobjects.osgi.Active
ObjectsServiceFactory] getService bundle [com.atlassian.labs.hipchat.hipchat-for
-jira-plugin]
2019-05-01 10:40:14,671 JIRA-Bootstrap INFO [c.a.j.p.hipchat.service.HipCha
tPluginLauncher] HipChat Plugin launched successfully
2019-05-01 10:40:14,687 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] On plugin event: com.atlassian.jira.plugins.hipchat.model.
event.PluginStartedEvent
2019-05-01 10:40:14,687 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] Registering a new hipchatRefreshConnectionStatusJob task.
2019-05-01 10:40:14,734 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] On plugin event: com.atlassian.jira.plugins.hipchat.model.
event.PluginStartedEvent
2019-05-01 10:40:14,734 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] Registering a new hipchatUpdateGlancesDataJob task.
2019-05-01 10:40:14,750 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] On plugin event: com.atlassian.jira.plugins.hipchat.model.
event.PluginStartedEvent
2019-05-01 10:40:14,828 JIRA-Bootstrap INFO [c.a.j.p.h.service.scheduling.A
bstractTaskScheduler] Registering a new hipchatInstallGlancesJob task.
2019-05-01 10:40:14,921 JIRA-Bootstrap INFO [c.a.jira.scheduler.JiraSchedul
erLauncher] Starting the JIRA Scheduler....
2019-05-01 10:40:15,375 JIRA-Bootstrap INFO [c.a.jira.scheduler.JiraSchedul
erLauncher] JIRA Scheduler started.
2019-05-01 10:40:15,812 UpmScheduler:thread-2 WARN anonymous [c.a.upm.pac.Pa
cClientImpl] Update check request may take longer because of the number of add-o
ns
2019-05-01 10:40:15,968 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherConte
xtListener] Memory Usage:
----------------------------------------------------------------------------
-----
Heap memory : Used: 237 MiB. Committed: 721 MiB. Max: 731 MiB
Non-heap memory : Used: 210 MiB. Committed: 230 MiB. Max: 1264 MiB
----------------------------------------------------------------------------
-----
TOTAL : Used: 447 MiB. Committed: 951 MiB. Max: 1995 MiB
----------------------------------------------------------------------------
-----
2019-05-01 10:40:16,031 Caesium-1-3 INFO [c.a.jira.startup.CacheWarmerLaunc
her] Warming up 3 caches.
2019-05-01 10:40:16,984 Caesium-1-3 INFO [c.a.jira.i18n.I18nWarmer] Init i1
8n cache
2019-05-01 10:40:16,984 ForkJoinPool.commonPool-worker-1 INFO [c.a.j.cache.
soy.SoyCacheWarmer] Warming 41 soy modules
2019-05-01 10:40:20,781 Caesium-1-4 INFO [c.a.j.index.ha.DefaultIndexRecove
ryManager] Latest index date: {2019-04-18 16:55:52}, Latest DB date: {2019-04-18
16:55:52}
2019-05-01 10:40:21,468 Modification Check:thread-1 INFO [c.a.jira.startup.
JiraStartupLogger]

___ Modifications ___________________________

Modified Files : jira-application.proper
ties, WEB-INF/web.xml
Removed Files : None

2019-05-01 10:40:21,734 Caesium-1-1 INFO [c.a.crowd.directory.DbCachingRemo
teDirectory] INCREMENTAL synchronisation for directory [ 10200 ] starting
2019-05-01 10:40:22,218 Caesium-1-1 INFO [c.a.crowd.directory.DbCachingRemo
teDirectory] Attempting INCREMENTAL synchronisation for directory [ 10200 ]
2019-05-01 10:40:22,593 Caesium-1-1 INFO [c.a.c.d.ldap.cache.UsnChangedCach
eRefresher] After restarting, full sync of directory [10200] is necessary before
incremental sync is possible.
2019-05-01 10:40:22,656 Caesium-1-1 INFO [c.a.crowd.directory.DbCachingRemo
teDirectory] Incremental synchronisation for directory [ 10200 ] was not complet
ed, falling back to a full synchronisation
2019-05-01 10:40:22,671 Caesium-1-1 INFO [c.a.crowd.directory.DbCachingRemo
teDirectory] INCREMENTAL synchronisation for directory [ 10200 ] was not success
ful, attempting FULL
2019-05-01 10:40:24,218 Caesium-1-1 INFO [c.a.c.directory.ldap.SpringLdapTe
mplateWrapper] Timed call for lookup on took 1304ms
2019-05-01 10:40:24,703 CrowdUsnChangedCacheRefresher:thread-2 INFO [c.a.c.
directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on
cn=Users,dc=embtrak,dc=com took 1071ms
2019-05-01 10:40:24,937 CrowdUsnChangedCacheRefresher:thread-1 INFO [c.a.c.
directory.ldap.SpringLdapTemplateWrapper] Timed call for search with handler on
cn=Users,dc=embtrak,dc=com took 1302ms
2019-05-01 10:40:25,125 CrowdUsnChangedCacheRefresher:thread-2 INFO [c.a.c.
d.ldap.cache.UsnChangedCacheRefresher] found [ 20 ] remote groups in [ 2125ms ]
2019-05-01 10:40:25,453 CrowdUsnChangedCacheRefresher:thread-1 INFO [c.a.c.
d.ldap.cache.UsnChangedCacheRefresher] found [ 17 ] remote users in [ 2438ms ]
2019-05-01 10:40:26,531 Caesium-1-1 INFO [c.a.crowd.directory.DbCachingRemo
teChangeOperations] scanned and compared [ 17 ] users for delete in DB cache in
[ 47ms ]
2019-05-01 10:40:26,609 Caesium-1-1 INFO [c.a.crowd.directory.DbCachingRemo
teChangeOperations] scanned for deleted users in [ 219ms ]
2019-05-01 10:40:26,671 Caesium-1-1 INFO [c.a.crowd.directory.DbCachingRemo
teChangeOperations] scanning [ 17 ] users to add or update
2019-05-01 10:40:27,968 Caesium-1-1 INFO [c.a.crowd.directory.DirectoryCach
eImplUsingChangeOperations] scanned and compared [ 17 ] users for update in DB c
ache in [ 1297ms ]
2019-05-01 10:40:28,312 Caesium-1-1 INFO [c.a.crowd.directory.DirectoryCach
eImplUsingChangeOperations] synchronised [ 17 ] users in [ 1641ms ]
2019-05-01 10:40:28,593 Caesium-1-1 INFO [c.a.crowd.directory.DbCachingRemo
teChangeOperations] scanned and compared [ 20 ] groups for delete in DB cache in
[ 140ms ]
2019-05-01 10:40:28,593 Caesium-1-1 INFO [c.a.crowd.directory.DirectoryCach
eImplUsingChangeOperations] scanning [ 20 ] groups to add or update
2019-05-01 10:40:28,812 Caesium-1-1 INFO [c.a.crowd.directory.DbCachingRemo
teChangeOperations] scanned and compared [ 20 ] groups for update in DB cache in
[ 219ms ]
2019-05-01 10:40:29,046 Caesium-1-1 INFO [c.a.crowd.directory.DirectoryCach
eImplUsingChangeOperations] synchronized [ 20 ] groups in [ 453ms ]
2019-05-01 10:40:29,250 Caesium-1-1 INFO [c.a.c.d.ldap.cache.AbstractCacheR
efresher] finished group attribute sync with 0 failures in [ 204ms ]
2019-05-01 10:40:30,484 Caesium-1-1 INFO [c.a.crowd.directory.DbCachingRemo
teDirectory] FULL synchronisation complete for directory [ 10200 ] in [ 8750ms ]

2019-05-01 10:40:31,546 Caesium-1-3 INFO [c.a.jira.i18n.I18nWarmer] Initial
ised i18n cache in 14562
2019-05-01 10:40:33,609 Caesium-1-4 INFO [c.a.j.p.h.service.ping.RefreshCon
nectionStatusJobHandler] Running RefreshConnectionStatusJobHandler...
2019-05-01 10:40:33,656 Caesium-1-4 DEBUG [c.a.activeobjects.osgi.ActiveObj
ectsServiceFactory] getService bundle [com.atlassian.plugins.base-hipchat-integr
ation-plugin-api]
2019-05-01 10:40:33,750 ForkJoinPool.commonPool-worker-1 INFO [c.a.j.cache.
soy.SoyCacheWarmer] Warmed 34 soy module(s) in 16766 ms, 7 module(s) were not pr
esent or disabled, 0 failed.
2019-05-01 10:40:33,765 Caesium-1-3 INFO [c.a.jira.startup.CacheWarmerLaunc
her] Warmed cache(s) in 17125 ms.
2019-05-01 10:40:44,828 Caesium-1-1 INFO [c.a.j.p.h.service.connect.Install
GlancesJobHandler] Running InstallGlancesJobHandler...
2019-05-01 10:40:44,828 Caesium-1-1 INFO [c.a.j.p.h.service.connect.Install
GlancesJobHandler] There is no link to HipChat, no need to install glances.
2019-05-01 10:41:13,796 Caesium-1-3 INFO [c.a.jira.upgrade.UpgradeScheduler
] Running scheduled upgrades
2019-05-01 10:41:13,828 Caesium-1-3 INFO [c.a.jira.upgrade.LoggingUpgradeSe
rvice] run upgrades has started
2019-05-01 10:41:13,875 Caesium-1-3 INFO [c.a.j.upgrade.util.BuildNumberDao
] Setting current build number to 712004
created com.atlassian.jira.plugins.webhooks.ao.WebhookDaoImpl@5ba1034f 153727879
9 with events worklog_created
board_deleted
option_unassigned_issues_changed
comment_updated
user_created
jira:version_created
board_configuration_changed
project_deleted
comment_deleted
project_updated
option_issuelinks_changed
sprint_created
jira:issue_updated
sprint_updated
comment_created
option_timetracking_changed
option_attachments_changed
jira:issue_created
issuelink_deleted
jira:issue_deleted
sprint_deleted
project_created
issuelink_created
jira:version_unreleased
board_created
jira:version_moved
sprint_closed
user_updated
jira:version_released
jira:version_deleted
sprint_started
jira:version_merged
worklog_deleted
jira:worklog_updated
jira:version_updated
option_subtasks_changed
worklog_updated
user_deleted
board_updated
AO_4AEACD_WEBHOOK_DAO {ID = 1} 15592
2019-05-01 10:41:13,921 Caesium-1-3 INFO [c.a.jira.upgrade.UpgradeIndexMana
ger] There is no reindex requests of type [IMMEDIATE, DELAYED] so none will be r
un
2019-05-01 10:41:13,921 Caesium-1-3 INFO [c.a.j.upgrade.util.BuildNumberDao
] Setting current version to 7.12.3
2019-05-01 10:41:13,937 Caesium-1-3 INFO [c.a.j.upgrade.util.BuildNumberDao
] Setting downgrade version to 7.1.2
2019-05-01 10:41:13,953 Caesium-1-3 INFO [c.a.jira.upgrade.LoggingUpgradeSe
rvice] run upgrades has finished successfully, and took 125 milliseconds to proc
ess.
2019-05-01 10:41:13,968 Caesium-1-3 INFO [c.a.jira.upgrade.UpgradeScheduler
] JIRA upgrades completed successfully
2019-05-01 10:41:13,984 Caesium-1-3 INFO [c.a.jira.upgrade.UpgradeScheduler
] Plugins upgrades completed successfully
2019-05-01 10:41:13,984 Caesium-1-3 INFO [c.a.jira.upgrade.UpgradeIndexMana
ger] Reindexing is not allowed after this upgrade and there is no immediate rein
dex requests
2019-05-01 10:41:18,671 Caesium-1-3 DEBUG [c.a.activeobjects.osgi.ActiveObj
ectsServiceFactory] getService bundle [com.atlassian.troubleshooting.plugin-jira
]

Tarun Sapra Community Leader May 01, 2019

Also @Brian Medford 

Could you attach the atlassian-jira.log file.

0 votes
Peter DeWitt Community Leader May 01, 2019

@Brian Medford , To be honest, parsing logs is not my song suit. If you haven't already, I would open a case with Atlassian. Their internal support team is pretty helpful with issues like this and have assisted us many times in the past.  

https://support.atlassian.com/contact/#/

-pjd

I wish that were an option.  Unfortunately this is a starter license and they refused, saying my only options were upgrading and/or using the Community. 

Hi @Brian Medford - did you get the issue resolved, or would need additional assistance?

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

180 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you