Upsource fails to start on Windows - log4j...No Appenders could be found

Hi,

I downloaded upsource today (2014-12-10), untipped it into c:\Program Files (x86)\Upsource, changed directory into c:\Program Files (x86)\Upsource\bin and tried to start it:


C:\Program Files (x86)\Upsource\bin>upsource.bat start
log4j:WARN No appenders could be found for logger (com.jetbrains.launcher.ep.com
mands.BaseCommand).
log4j:WARN Please initialize the log4j system properly.
Upsource failed to start.

C:\Program Files (x86)\Upsource\bin>

and it fails to start.

What is the correct way forward?

7 comments
Comment actions Permalink

I believe I got that same message in my log when setting up, but it didn't prevent me from starting everything.

Did you follow the instructions on https://www.jetbrains.com/upsource/help/1.0/install_config.html

Notably, "Things to configure before starting Upsource"

0
Comment actions Permalink

yes, I did follow the instructions - as for the moment it shall run standalone (aka, no addtional Apache or Lynx), the standard port is fine, the OS has 64bit (Win7).
As per the linked instructions, on Windows JDK shall be bundletd, and my hostname is pingable and resolving to a fine IPv6 adress.

running
upsource.bat configure leads to the same logger errors...

0
Comment actions Permalink

Similar/same problem here. Windows Server 2012 R2 Update, installed fresh just for this.

I filled in the install form when it started, then it went to http://win-u7ndk3fni04/bundle/starting/ (win-u7ndk3fni04 is the machine name) and nothing appears.

Restarted and still nothing.

Is Windows Server 2012 R2 Update a tested configuration?

Log directory attached.

Source of blank page looks like:

<!doctype html>
<!--[if lt IE 7]>      <html > <![endif]-->
<!--[if IE 7]>         <html > <![endif]-->
<!--[if IE 8]>         <html > <![endif]-->
<!--[if gt IE 8]><!--> <html > <!--<![endif]-->
  <head>
    <meta charset="utf-8">
    <title>Upsource 1.0</title>
    <meta name="description" content="">
    <meta name="viewport" content="width=device-width">


    <base href="/bundle/starting/">


    <link rel="stylesheet" href="bower_components/ring-ui/ring-lib.min.css">
    <link rel="stylesheet" href="styles/f36b018f.main.css"/>

    <!--[if lt IE 9]>
    <script src="bower_components/es5-shim/es5-shim.js"></script>
    <script src="bower_components/json3/lib/json3.min.js"></script>
    <![endif]-->
    <link rel="shortcut icon" href="favicon.ico">
  </head>
  <body ng-app="bundleClient">
    <!--[if lt IE 7]>
      <p >You are using an <strong>outdated</strong> browser. Please <a href="http://browsehappy.com/">upgrade your browser</a> to improve your experience.</p>
    <![endif]-->

    <div ng-view=""></div>

    <script src="scripts/bf064ac5.lib.js"></script>

    <script src="scripts/02de17f7.app.js"></script>
</body>
</html>



Attachment(s):
logs.zip
0
Comment actions Permalink

Hi Harald,

From the given output it's difficult to say what really happened, so when you have a chance please zip and send all entire contents of the following folder <Upsource_home_directory>\logs to upsource-support@jetbrains.com

0
Comment actions Permalink

Hi Artem,

there was no logs directory... which directed me to the immediate problem: I had put upsource within the Programs and Files directory... where the logs directory could not be created.
That was the reason for this failure. I moved upsource to another directory, now the startup continues and fails at another point... will clean the installs and if it fails again, mail the logs to the mentioned email adress.

thanks,

Harald

0
Comment actions Permalink

Hi Rik,

We have carefully reviewed your log files and seams that all Upsource services got started successfully. So to continue the investigation could you please clarify what browser(and version) are you using? Also please provide us "conf" directory, that is also located in <Upsource_home_directory>

Thanks for your patience!

0
Comment actions Permalink

Hi,

I've found how to make it work.

IE was set to 'Display intranet sites in Compatibility View' (no idea why this is the default) and was choosing an IE7 document mode!

It also works fine in Chrome.

Cheers,
Rik

0

Please sign in to leave a comment.