Instalation Problem Fedora FC14 i386

I just trying to start it on clear Fedora core 14 system.  JDK 1.6.23
Version:6.0Build:15772File size:298.9 Mb
I did not setup any database on this server. I don't have any data deryctory or any config. I just extract tar.gz to /usr/TeamCity/  and run  runAll.sh
I have 1GB ram.

When i start i get this error.[2010-12-09 21:52:52,690]   INFO -   jetbrains.buildServer.SERVER - Starting TeamCity server
   INFO -   jetbrains.buildServer.SERVER - TeamCity version: 6.0 (build 15772), data format version 418
   INFO -   jetbrains.buildServer.SERVER - TeamCity data directory: /root/.BuildServer
   INFO -   jetbrains.buildServer.SERVER - Data directory format version: no configuration found
   INFO -   jetbrains.buildServer.SERVER - Database format version: neither internal database nor 'databas
e.properties' file found
  ERROR -   jetbrains.buildServer.SERVER - Server startup exception: java.lang.RuntimeException: IO failue
when setting up or connecting to database
java.lang.RuntimeException: IO failue when setting up or connecting to database
        at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.setupAndConnectToDB(TeamCityDispatcherServlet.java:207)
        at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.processStartupServerInternal(TeamCityDispatcherServlet.ja
va:6)
        at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.processStartupServerSafe(TeamCityDispatcherServlet.java:2
3)
        at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.access$400(TeamCityDispatcherServlet.java:191)
        at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet$5.run(TeamCityDispatcherServlet.java:2)
        at java.lang.Thread.run(Thread.java:662)
Caused by: java.net.UnknownHostException: stend.triptopru: stend.triptopru
        at java.net.InetAddress.getLocalHost(InetAddress.java:1354)
        at jetbrains.buildServer.rootDispatcher.TeamCityDispatcherServlet.setupAndConnectToDB(TeamCityDispatcherServlet.java:170)
        ... 5 more

1 comment

Hello!

Sorry for the delay with replying.

Is this still actual?

The root cause seems like the host's own address is not configured correctly.

0

Please sign in to leave a comment.