1 Reply Latest reply on Mar 1, 2016 8:44 AM by whoiskevin

    Force setup

    claisseflorent

      Hi fellow Jive developpers,

       

      After installing jive v8 rpm on a fresh server, I successfully accessed the setup page (where you should set your database configurations and other things).

      This setup crashed when configuring the core database.

      After that, the setup pages weren't displaying at all.

      I tried to restart Jive, but the server is not displaying any page from now.

       

      There is absolutly no error in sbs.out but there is this little one in sbs.log:

       

      2015-06-16 10:50:24,199 [localhost-startStop-1] [::] FATAL com.jivesoftware.community.license.JiveLicenseManagerImpl - The "jive.license" license file was not found, evaluation mode will be used
      2015-06-16 10:50:31,368 [localhost-startStop-1] [::] ERROR com.jivesoftware.community.impl.DbThemeManager - Could not load theme mappings
      2015-06-16 10:50:53,989 [localhost-startStop-1] [::] ERROR com.jivesoftware.base.event.v2.EventDispatchHelper - Error dispatching event:com.jivesoftware.community.lifecycle.ApplicationStateChangeEvent@47c5f23e[eventType=CHANGE,payload=<null>,params={prevState=Initialized, newState=Setup started},createdDate=Tue Jun 16 10:50:31 CEST 2015,actor=EntityDescriptor{objectID=-9223372036854775808, objectType=3},callingstack=<null>] to Listener:com.jivesoftware.community.web.soy.SoyResourceBundler@48073b3a
      java.lang.NullPointerException
              at com.jivesoftware.community.web.soy.SoyTemplateBuilder.compileResource(SoyTemplateBuilder.java:292)
              at com.jivesoftware.community.web.soy.SoyTemplateBuilder.build(SoyTemplateBuilder.java:192)
              at com.jivesoftware.community.web.soy.SoyTemplateBuilder.buildAll(SoyTemplateBuilder.java:107)
              at com.jivesoftware.community.web.soy.impl.SoyTemplateRegistryImpl.compileCoreSoy(SoyTemplateRegistryImpl.java:226)
              at com.jivesoftware.community.web.soy.impl.SoyTemplateRegistryImpl.initialize(SoyTemplateRegistryImpl.java:194)
              at com.jivesoftware.community.web.soy.SoyResourceBundler.handle(SoyResourceBundler.java:544)
              at com.jivesoftware.community.web.soy.SoyResourceBundler.handle(SoyResourceBundler.java:1)
              at com.jivesoftware.base.event.v2.EventDispatchHelper.dispatchEventInline(EventDispatchHelper.java:228)
              at com.jivesoftware.base.event.v2.NonBlockingEventDispatcherImpl.fireInline(NonBlockingEventDispatcherImpl.java:133)
              at com.jivesoftware.community.lifecycle.JiveApplication.setApplicationState(JiveApplication.java:357)
              at com.jivesoftware.community.Jive.doPostInit(Jive.java:166)
              at com.jivesoftware.community.Jive.start(Jive.java:155)
              at com.jivesoftware.community.web.JiveApplicationContextLoaderListener.contextInitialized(JiveApplicationContextLoaderListener.java:29)
              at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4797)
              at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5221)
              at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
              at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
              at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
              at java.util.concurrent.FutureTask.run(FutureTask.java:266)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
              at java.lang.Thread.run(Thread.java:745)
      

       

      Is this related to the failed setup? and is there any way to force jive to run setup again?

       

      Regards,

      Florent.

        • Re: Force setup
          whoiskevin

          Not sure about that error but to force Jive into the setup again modify the jive_startup.xml file in your jive home folder.  There is a line there <setup>true</setup>.  Change that to <setup>false</setup> and you should be able to start up and access the setup.