Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Orion (Archived) » Problems starting Orion (using the source code setup)
Problems starting Orion (using the source code setup) [message #1144173] Fri, 18 October 2013 17:58 Go to next message
Cristian Spiescu is currently offline Cristian SpiescuFriend
Messages: 100
Registered: July 2009
Senior Member
Hello,

I have downloaded the source code for Orion and followed the corresponding guide (http://wiki.eclipse.org/Orion/Getting_the_source).

However, the server doesn't seem to start correctly (i.e. fully initialized). I am able to create an account and login, but the menu only shows "Git Repositories, Project, Shell". And the user menu (at the right on the header bar) only shows "Keyboard Shortcuts, Sign Out".

Do you have any hints on what's wrong with my setup? Or some suggestions on how I could debug this?

Here is the server log at startup:

osgi> SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://103.fwk1957792108:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://103.fwk1957792108:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
19:55:19,502 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
19:55:19,502 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
19:55:19,502 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [bundleresource://2.fwk1957792108:1/logback.xml]
19:55:19,526 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@6509dc6 - URL [bundleresource://2.fwk1957792108:1/logback.xml] is not of type file
19:55:19,541 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
19:55:19,542 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Adding LoggerContextListener of type [ch.qos.logback.classic.jul.LevelChangePropagator] to the object stack
19:55:19,556 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@16a63567 - Propagating DEBUG level on Logger[ROOT] onto the JUL framework
19:55:19,556 |-INFO in ch.qos.logback.classic.joran.action.LoggerContextListenerAction - Starting LoggerContextListener
19:55:19,556 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
19:55:19,558 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
19:55:19,591 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - This appender no longer admits a layout as a sub-component, set an encoder instead.
19:55:19,591 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
19:55:19,591 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
19:55:19,592 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.eclipse.orion.server.login] to INFO
19:55:19,592 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@16a63567 - Propagating INFO level on Logger[org.eclipse.orion.server.login] onto the JUL framework
19:55:19,592 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.eclipse.orion.server.account] to INFO
19:55:19,592 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@16a63567 - Propagating INFO level on Logger[org.eclipse.orion.server.account] onto the JUL framework
19:55:19,592 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.openid4java] to WARN
19:55:19,592 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@16a63567 - Propagating WARN level on Logger[org.openid4java] onto the JUL framework
19:55:19,592 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.eclipse.orion.server.config] to INFO
19:55:19,592 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@16a63567 - Propagating INFO level on Logger[org.eclipse.orion.server.config] onto the JUL framework
19:55:19,592 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to WARN
19:55:19,592 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@16a63567 - Propagating WARN level on Logger[ROOT] onto the JUL framework
19:55:19,592 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT]
19:55:19,593 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
19:55:19,593 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@79fc08ce - Registering current configuration as safe fallback point

SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
2013-10-18 19:55:19.662 [Start Level Event Dispatcher] INFO  org.eclipse.orion.server.config - Server configuration file loaded from: D:\data\java_work\git_repo_fp_orion.client\bundles\org.eclipse.orion.client.core\web-ide.conf
2013-10-18 19:55:20.339 [Worker-0] INFO  org.eclipse.orion.server.config - Initializing server metadata store


Thank you in advance for your help!
Best regards,
Cristian.

Report message to a moderator

Re: Problems starting Orion (using the source code setup) [message #1145395 is a reply to message #1144173] Sat, 19 October 2013 13:32 Go to previous messageGo to next message
Rafael Chaves is currently offline Rafael ChavesFriend
Messages: 161
Registered: July 2009
Senior Member
I have seen similar issues when launching a new version of Orion from a website I started Orion from before, i.e. a caching issue. For me, what fixes it is a hard refresh (in Chrome, show dev tools, then hold the refresh button until a menu shows), or emptying the browser cache, or opening it from a new incognito session.

Report message to a moderator

Re: Problems starting Orion (using the source code setup) [message #1145671 is a reply to message #1145395] Sat, 19 October 2013 18:00 Go to previous messageGo to next message
Cristian Spiescu is currently offline Cristian SpiescuFriend
Messages: 100
Registered: July 2009
Senior Member
Thank you.

I think this was the issue indeed. However, an odd thing happened: I have cleared the cache (I'm using Firefox), and I was still not having the full menus. However, I had 2 additional entries: Navigator and Editor. After clicking one of them, everything started to behave like expected.

I notice in the status bar, left side: @buildLabel@. I think this is normal, as I am running directly from the IDE (and not as a result of the build script); right?

Best regards,
Cristian.

Report message to a moderator

Re: Problems starting Orion (using the source code setup) [message #1148555 is a reply to message #1145671] Mon, 21 October 2013 15:42 Go to previous message
Mark Macdonald is currently offline Mark MacdonaldFriend
Messages: 35
Registered: July 2009
Member
Cristian Mising name wrote on Sat, 19 October 2013 14:00
Thank you.
I notice in the status bar, left side: @buildLabel@. I think this is normal, as I am running directly from the IDE (and not as a result of the build script); right?


Yes this is normal when running Orion from source.

Cristian, it sounds like you ran into a case of stale localStorage (which Orion uses for persisting some data, including the menu links). If this happens again, Clear Private Data (which all items checked, and time range set to Everything) is the most reliable way of fixing it.

Report message to a moderator

Previous Topic:One minute install as advertised, but opps...
Next Topic:customize the default page
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Tue Nov 28 22:51:24 GMT 2023

Powered by FUDForum. Page generated in 0.01774 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly