Scheduler not started error

we are currently running Jira on a solories server. we are planning to migrate to our linux 64bit server soon, so as part of testing we have migrated one of the test instance using archive installable.followed the steps given in "install Jira from Archive file for windows,linux,Solories". once after start the jira. we have recived the "JIRA 5.2.7 build: 850 started. You can now access JIRA through your web browser" and [atlassian.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: JIRA not setup yet. we are not able to see weblink comingup "http://servername:8080/". Could someone help us to sort this out please.

4 answers

2 accepted

Accepted Answer
0 votes

You need to keep reading the log. It should contain reasons why the service has not started fully.

Accepted Answer
0 votes

issue got fixed after the ports are enabled on the new servers

we have checked the logs. we couldn't find any other errors

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

JIRA 5.2.7 build: 850 started. You can now access JIRA through your web browser.

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

2014-01-16 11:36:52,486 localhost-startStop-1 INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: JIRA not setup yet.

Jan 16, 2014 11:36:52 AM org.apache.coyote.AbstractProtocol start

INFO: Starting ProtocolHandler ["http-bio-8007"]

Jan 16, 2014 11:36:52 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 78505 ms

2014-01-16 11:36:55,528 Modification Check:thread-1 INFO [atlassian.jira.startup.JiraStartupLogger]

___ Modifications ___________________________

Modified Files : jira-application.properties, secure/views/createsubtaskissue-start.jsp, secure/views/createsubtaskissue-details.jsp, images/icons/requirement.gif

Removed Files : None

It might not look like errors. What does the log say from "You can now access JIRA" onwards?

There should be more than that. Even when it fails to start, there should be more.

If it really is just stopping dead at that point, then you probaby need to check the load on the server - is it thrashing memory and/or CPU

below are few errors. not sure will it really stop jira to comup.

2014-01-16 10:35:36,138 localhost-startStop-2 ERROR [osgi.container.felix.FelixOsgiContainerManager] Error writing persistent state to bundle archive.

2014-01-16 10:35:36,139 localhost-startStop-2 ERROR [osgi.container.felix.FelixOsgiContainerManager] org.apache.felix.framework.cache.BundleArchive: Unable to record last modification time - java.io.FileNotFoundException: /u01/app/jira/jira_home/panist1_DEV/plugins/.osgi-plugins/felix/felix-cache/bundle106/bundle.lastmodified (No such file or directory)

2014-01-16 10:35:36,139 localhost-startStop-2 ERROR [osgi.container.felix.FelixOsgiContainerManager] Error writing last modification time to bundle archive.

2014-01-16 10:35:36,140 localhost-startStop-2 ERROR [osgi.container.felix.FelixOsgiContainerManager] org.apache.felix.framework.cache.BundleArchive: Unable to record state - java.io.FileNotFoundException: /u01/app/jira/jira_home/panist1_DEV/plugins/.osgi-plugins/felix/felix-cache/bundle110/bundle.state (No such file or directory)

2014-01-16 10:35:36,140 localhost-startStop-2 ERROR [osgi.container.felix.FelixOsgiContainerManager] Error writing persistent state to bundle archive.

2014-01-16 10:35:36,141 localhost-startStop-2 ERROR [osgi.container.felix.FelixOsgiContainerManager] org.apache.felix.framework.cache.BundleArchive: Unable to record last modification time - java.io.FileNotFoundException: /u01/app/jira/jira_home/panist1_DEV/plugins/.osgi-plugins/felix/felix-cache/bundle110/bundle.lastmodified (No such file or directory)

2014-01-16 10:35:36,141 localhost-startStop-2 ERROR [osgi.container.felix.FelixOsgiContainerManager] Error writing last modification time to bundle archive.

Well, actually, yes, a broken file system will stop it completing startup. This looks like it got part way through starting, failed and then when you restarted failed again.

I would

  • Stop Jira, leaving it for several seconds and checking with a process viewer that Jira is no longer running at all ("ps -ef | grep java" for example)
  • Check all the permissions. If Jira is running as a user who logs in as say "jirauser" then check that jirauser has full read/write/execute/delete permissions on jira_home and all the directories below it
  • Move the directory /u01/app/jira/jira_home/panist1_DEV/plugins/.osgi-plugins to somewhere else (the recommendation is usually "delete it", but I've found being able to put it back can be useful sometimes. Just put it somewhere safe with a different name)
  • Same for /u01/app/jira/jira_home/panist1_DEV/plugins/.bundled-plugins - move it somewhere safe

Restart Jira and re-read the logs.

i tried this. we is the details in the log file.

JIRA 5.2.7 build: 850 started. You can now access JIRA through your web browser.

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

2014-01-17 09:36:11,662 localhost-startStop-1 INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: JIRA not setup yet.

Jan 17, 2014 9:36:11 AM org.apache.coyote.AbstractProtocol start

INFO: Starting ProtocolHandler ["http-bio-8007"]

Jan 17, 2014 9:36:11 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 105902 ms

2014-01-17 09:36:19,200 Modification Check:thread-1 INFO [atlassian.jira.startup.JiraStartupLogger]

___ Modifications ___________________________

Modified Files : jira-application.properties, secure/views/createsubtaskissue-start.jsp, secure/views/createsubtaskissue-details.jsp, images/icons/requirement.gif

Removed Files : None

Jan 17, 2014 9:43:02 AM org.apache.jasper.compiler.TldLocationsCache tldScanJar

INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

There should be more log than that. But, can you have a look at system load - how much memory and cpu are in use? What are you allocating to the JVM when it starts up?

cpu and memeory usage is less than 10%.. JVM minum and maximumi are set to 1024. in dont think resouce are issues. i am able to launching from linux. as below

devjira@server440[DEVELOPMENT]$ wget http://server440:8007

--2014-01-17 11:10:01-- http://server:8007/

Resolving server440... 149.185.160.223

Connecting to server440|ip address|:8007... connected.

HTTP request sent, awaiting response... 302 Moved Temporarily

Location: http://server440:8007/secure/SetupDatabase!default.jspa[following]

--2014-01-17 11:10:01-- http://server440:8007/secure/SetupDatabase!default.jspa

Reusing existing connection to server440:8007.

HTTP request sent, awaiting response... 302 Moved Temporarily

Location: http://server440:8007/secure/SetupApplicationProperties!default.jspa[following]

--2014-01-17 11:10:01-- http://server440:8007/secure/SetupApplicationProperties!default.jspa

Reusing existing connection to server440:8007.

HTTP request sent, awaiting response... 200 OK

Length: 7065 (6.9K) [text/html]

Saving to: âSetupApplicationProperties!default.jspaâ

100%[==============================================================================================================================>] 7,065 --.-K/s in 0s

2014-01-17 11:10:01 (171 MB/s) - âSetupApplicationProperties!default.jspaâ

Er, hang on, you're getting the setup screen there.

So, it's working.

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

JIRA 5.2.7 build: 850 started. You can now access JIRA through your web browser.

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

2014-01-16 11:36:52,486 localhost-startStop-1 INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: JIRA not setup yet.

Jan 16, 2014 11:36:52 AM org.apache.coyote.AbstractProtocol start

INFO: Starting ProtocolHandler ["http-bio-8007"]

Jan 16, 2014 11:36:52 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 78505 ms

2014-01-16 11:36:55,528 Modification Check:thread-1 INFO [atlassian.jira.startup.JiraStartupLogger]

___ Modifications ___________________________

Modified Files : jira-application.properties, secure/views/createsubtaskissue-start.jsp, secure/views/createsubtaskissue-details.jsp, images/icons/requirement.gif

Removed Files : None

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Featured Groups

Tuesday tips & tricks: What is the Atlassian Community?

It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...

99 views 3 7
View post

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you