YouTrack not available via Browser

Hi there,

I installed TeamCity at Port 12346, it runs and is accessible.

The install worked (Windows Server 2008 with IIS), Port is 81, service is correctly running. But when I call localhost:81 it doesn't work: "Connection failed".

But somehow I can't access Youtrack via the browser. I tried deactivating the firewall. But still no connection possible. The log files are not giving me any help. Any ideas? How can I diagnose whats happening?

Netstat gives me the ports

C:\Server\Programs\_YouTrack\bin>netstat -a -p tcp

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:81             TURBINE:0              LISTENING
  TCP    0.0.0.0:88             TURBINE:0              LISTENING
  TCP    0.0.0.0:135            TURBINE:0              LISTENING
  TCP    0.0.0.0:389            TURBINE:0              LISTENING
  TCP    0.0.0.0:445            TURBINE:0              LISTENING
  TCP    0.0.0.0:464            TURBINE:0              LISTENING
  TCP    0.0.0.0:593            TURBINE:0              LISTENING
  TCP    0.0.0.0:636            TURBINE:0              LISTENING
  TCP    0.0.0.0:1025           TURBINE:0              LISTENING
  TCP    0.0.0.0:1026           TURBINE:0              LISTENING
  TCP    0.0.0.0:1027           TURBINE:0              LISTENING
  TCP    0.0.0.0:1029           TURBINE:0              LISTENING
  TCP    0.0.0.0:1030           TURBINE:0              LISTENING
  TCP    0.0.0.0:1031           TURBINE:0              LISTENING
  TCP    0.0.0.0:3268           TURBINE:0              LISTENING
  TCP    0.0.0.0:3269           TURBINE:0              LISTENING
  TCP    0.0.0.0:3306           TURBINE:0              LISTENING
  TCP    0.0.0.0:3389           TURBINE:0              LISTENING
  TCP    0.0.0.0:6001           TURBINE:0              LISTENING
  TCP    0.0.0.0:6002           TURBINE:0              LISTENING
  TCP    0.0.0.0:6004           TURBINE:0              LISTENING
  TCP    0.0.0.0:8002           TURBINE:0              LISTENING
  TCP    0.0.0.0:8003           TURBINE:0              LISTENING
  TCP    0.0.0.0:8009           TURBINE:0              LISTENING
  TCP    0.0.0.0:12346          TURBINE:0              LISTENING
  TCP    0.0.0.0:41531          TURBINE:0              LISTENING
  TCP    0.0.0.0:41532          TURBINE:0              LISTENING
  TCP    0.0.0.0:41540          TURBINE:0              LISTENING
  TCP    0.0.0.0:48565          TURBINE:0              LISTENING
  TCP    0.0.0.0:51777          TURBINE:0              LISTENING
  TCP    0.0.0.0:59318          TURBINE:0              LISTENING
  TCP    0.0.0.0:59322          TURBINE:0              LISTENING
  TCP    0.0.0.0:59338          TURBINE:0              LISTENING
  TCP    0.0.0.0:59350          TURBINE:0              LISTENING
  TCP    0.0.0.0:59372          TURBINE:0              LISTENING
  TCP    0.0.0.0:59383          TURBINE:0              LISTENING
  TCP    0.0.0.0:59410          TURBINE:0              LISTENING
  TCP    127.0.0.1:25           TURBINE:0              LISTENING
  TCP    127.0.0.1:53           TURBINE:0              LISTENING
  TCP    127.0.0.1:81           TURBINE:48584          ESTABLISHED
  TCP    127.0.0.1:8005         TURBINE:0              LISTENING
  TCP    127.0.0.1:8105         TURBINE:0              LISTENING
  TCP    127.0.0.1:12346        TURBINE:48573          TIME_WAIT
  TCP    127.0.0.1:48407        TURBINE:48408          ESTABLISHED
  TCP    127.0.0.1:48408        TURBINE:48407          ESTABLISHED
  TCP    127.0.0.1:48409        TURBINE:48410          ESTABLISHED
  TCP    127.0.0.1:48410        TURBINE:48409          ESTABLISHED
  TCP    127.0.0.1:48584        TURBINE:hosts2-ns      ESTABLISHED
  TCP    169.254.156.53:139     TURBINE:0              LISTENING
  TCP    192.168.178.55:53      TURBINE:0              LISTENING
  TCP    192.168.178.55:139     TURBINE:0              LISTENING
  TCP    192.168.178.55:445     BigFlo:54220           ESTABLISHED
  TCP    192.168.178.55:3389    BigFlo:54211           ESTABLISHED
  TCP    192.168.178.55:12346   BigFlo:54440           TIME_WAIT
  TCP    192.168.178.55:12346   BigFlo:54612           ESTABLISHED

When I stop the service and start it manualy via catalina.bat it shows the following:

C:\Server\Programs\_YouTrack\bin>catalina.bat run
Using CATALINA_BASE:   "C:\Server\Programs\_YouTrack"
Using CATALINA_HOME:   "C:\Server\Programs\_YouTrack"
Using CATALINA_TMPDIR: "C:\Server\Programs\_YouTrack\temp"
Using JRE_HOME:        "../jre"
Using CLASSPATH:       "C:\Server\Programs\_YouTrack\bin\bootstrap.jar"
16.03.2012 10:21:37 org.apache.catalina.core.AprLifecycleListener init
INFO: Loaded APR based Apache Tomcat Native library 1.1.20.
16.03.2012 10:21:37 org.apache.catalina.core.AprLifecycleListener init
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
16.03.2012 10:21:38 org.apache.coyote.http11.Http11AprProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-81
16.03.2012 10:21:38 org.apache.coyote.ajp.AjpAprProtocol init
INFO: Initializing Coyote AJP/1.3 on ajp-8009
16.03.2012 10:21:38 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 912 ms
16.03.2012 10:21:38 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
16.03.2012 10:21:38 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.26
16.03.2012 10:21:38 org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory ROOT
16.03.2012 10:21:38 org.apache.coyote.http11.Http11AprProtocol start
INFO: Starting Coyote HTTP/1.1 on http-81
16.03.2012 10:21:38 org.apache.coyote.ajp.AjpAprProtocol start
INFO: Starting Coyote AJP/1.3 on ajp-8009
16.03.2012 10:21:38 org.apache.catalina.startup.Catalina start
INFO: Server startup in 442 ms

8 comments
Comment actions Permalink

Florian,

Let's start with the simpliest case. Pls, download youtrack.jar (http://download.jetbrains.com/charisma/youtrack-3.2.2.jar) and start it using command:

java -jar youtrack.jar 81

0
Comment actions Permalink

Thanks for your quick answer.

Calling the jar via java works. I get the setup page in the browser at http://localhost:81/setUp

What does this mean?

0
Comment actions Permalink

Can I test my existing intallation? Run it not as a service - via java!?

0
Comment actions Permalink

That means that YouTrack successfully started.

0
Comment actions Permalink

Florain,

Do I understand correct thathistory was next:

- first you had YouTrack running under IIS at port 81.

- then you installed TeamCity from exe file at port 12346.

- after that YouTrack stoped responding.

0
Comment actions Permalink

Hi Sergey,

thanks for answering. It is frustrating, also the fresh installation of Windows Server did not help.

- it runs via the JAR you provided.

- I did also try it with a fresh installation of Windows Server 2008 R2, YouTrack has the same issue

- Does not matter if TeamCity is installed or not, tried both ways, TeamCity always works, YouTrack does not

I got some strange things to report, maybe that helps getting into the issue:

- localhost:81, delivers 'connection failed' in browser

- localhost:81/something, no matter for what something stands, it always leads to YouTrack's 'This page was not found!...' page

- localhost:81/login, works, the login screen appears, but as I got no users I can't login

- localhost:81/setUp or localhost:81/dashboard, redirects me to https://turbine/login (turbine is my internal domain name)

I'm lost, seems to me as the configuration is somehow wrong and I do not get the setup page, which should appear on a fresh installation, right?

Here's an excerp of youtrack.log:

20 Mar 2012 06:27:29,053 INFO  [MainServlet                   ] [http request: /login                              ] Start processing request /login
20 Mar 2012 06:27:29,053 INFO  [MainServlet                   ] [http request: /login                              ] Finish processing request /login in 0ms
20 Mar 2012 06:27:32,267 INFO  [MainServlet                   ] [http request: /setUp                              ] Start processing request /setUp
20 Mar 2012 06:27:32,267 INFO  [MainServlet                   ] [http request: /setUp                              ] Finish processing request /setUp in 0ms
20 Mar 2012 06:27:36,058 INFO  [MainServlet                   ] [http request: /login                              ] Start processing request /login
20 Mar 2012 06:27:36,058 INFO  [MainServlet                   ] [http request: /login                              ] Finish processing request /login in 0ms
20 Mar 2012 06:27:39,115 INFO  [MainServlet                   ] [http request: /a                                  ] Start processing request /a
20 Mar 2012 06:27:39,115 ERROR [ResponseFactory               ] [http request: /a                                  ] No response action for uri: /a
20 Mar 2012 06:27:39,115 ERROR [MainServlet                   ] [http request: /a                                  ] No response action for uri: /a
20 Mar 2012 06:27:39,115 INFO  [MainServlet                   ] [http request: /a                                  ] Finish processing request /a in 0ms
20 Mar 2012 06:27:39,115 INFO  [MainServlet                   ] [http request: /NotFound                           ] Start processing request /NotFound
20 Mar 2012 06:27:39,131 INFO  [MainServlet                   ] [http request: /NotFound                           ] Finish processing request /NotFound in 16ms
20 Mar 2012 06:27:47,181 INFO  [MainServlet                   ] [http request: /_events?window_id=18 [_heart_beat] ] Start processing request /_events?window_id=18 [_heart_beat]
20 Mar 2012 06:27:47,181 INFO  [MainServlet                   ] [http request: /_events?window_id=18 [_heart_beat] ] Finish processing request /_events?window_id=18 [_heart_beat] in 0ms
20 Mar 2012 06:28:19,224 INFO  [MainServlet                   ] [http request: /_events?window_id=24 [_heart_beat] ] Start processing request /_events?window_id=24 [_heart_beat]
20 Mar 2012 06:28:19,224 INFO  [MainServlet                   ] [http request: /_events?window_id=24 [_heart_beat] ] Finish processing request /_events?window_id=24 [_heart_beat] in 0ms
20 Mar 2012 06:28:27,195 INFO  [MainServlet                   ] [http request: /_events?window_id=18 [_heart_beat] ] Start processing request /_events?window_id=18 [_heart_beat]
20 Mar 2012 06:28:27,195 INFO  [MainServlet                   ] [http request: /_events?window_id=18 [_heart_beat] ] Finish processing request /_events?window_id=18 [_heart_beat] in 0ms

Any ideas?

0
Comment actions Permalink

Well,

there are 2 points:

- fresh installation uses existing DataBase in {user.home}/teamsysdata folder by default (unless you provided another path )

- it looks like conflict with redirection to baseURL that is set in your DataBase, to slove it you should:

1) goto localhost:81/login

login using root/root

2) goto localhost:81/setUp

and set baseURL

0
Comment actions Permalink

That pointed me to the right direction.

For the record, even after uninstall and installing YouTrack again, the database is not removed and it did still use the same in c:\teamsysdata (which makes sense in a way, but I had guessed that after a reinstall the db is fresh). That did fail the redirection, which was once set, but not correctly.

So for solving this deleting or moving the teamsysdata folder helps, YouTrack then generates a fresh database.

Big thanks Sergey!

0

Please sign in to leave a comment.