TeamCity Shuts Down Suddenly

Hi, I'm trying to run Team City from an Amazon EC2 instance.

The problem I'm been struggling against is while the server configures itself.

I haven't even been able to use Team City. The problem happens while the server is being automatically set up (when the team city managment screen appears and informs that it is creating the database, initializing components, etc).

While Team City is "Initializing TeamCity server components", after a while waiting, the site goes down, and throws me a 404 error. The configuration process seems to stop right there and does not continue in any way. I could observe this by looking at the logs. None of the java logs provide useful information, or say anything about an error.

Here are the server logs of the last lauch

[2014-01-30 13:03:51,862]   INFO -  jetbrains.buildServer.STARTUP - Database connection URL: jdbc:mysql://localhost:3306/team_city
[2014-01-30 13:03:51,888]   INFO -  jetbrains.buildServer.STARTUP - Using database connection URL from the database properties file. The URL is: jdbc:mysql://localhost:3306/team_city
[2014-01-30 13:03:51,888]   INFO -  jetbrains.buildServer.STARTUP - Using external (MYSQL) database
[2014-01-30 13:03:51,888]   INFO -  jetbrains.buildServer.STARTUP - Current stage: Connecting to the database
[2014-01-30 13:04:23,631]   INFO -  jetbrains.buildServer.STARTUP - Connected to the database successfully
[2014-01-30 13:04:23,636]   INFO -  jetbrains.buildServer.STARTUP - Current stage: Checking the database
[2014-01-30 13:04:34,075]   INFO -  jetbrains.buildServer.STARTUP - Database contains no tables.
[2014-01-30 13:04:34,076]   INFO -  jetbrains.buildServer.STARTUP - Current stage: Database is empty or doesn't exist
[2014-01-30 13:04:34,076]   INFO -  jetbrains.buildServer.STARTUP - Administrator login is required from web UI using authentication token: 3739502618892632221
[2014-01-30 13:12:47,748]   INFO -  jetbrains.buildServer.STARTUP - Successful authentication token entry from IP address: /190.245.171.40
[2014-01-30 13:12:59,247]   INFO -  jetbrains.buildServer.STARTUP - Current stage: Creating a new database
[2014-01-30 13:12:59,251]   INFO -  jetbrains.buildServer.STARTUP - Database contains no tables.
[2014-01-30 13:12:59,252]   INFO -  jetbrains.buildServer.STARTUP - Creating database schema
[2014-01-30 13:13:02,914]   INFO -  jetbrains.buildServer.STARTUP - Database contains 110 tables.
[2014-01-30 13:13:02,918]   INFO -  jetbrains.buildServer.STARTUP - Database version is 628
[2014-01-30 13:13:02,918]   INFO -  jetbrains.buildServer.STARTUP - Current stage: Initializing TeamCity server components
[2014-01-30 13:13:02,990]   INFO -  jetbrains.buildServer.STARTUP - Starting the main application
[2014-01-30 13:13:03,221]   INFO - ebDispatcherApplicationContext - Refreshing jetbrains.buildServer.maintenance.WebDispatcherApplicationContext@627e9505: startup date [Thu Jan 30 13:13:03 UTC 201$
[2014-01-30 13:13:03,277]   INFO - MainTeamCityApplicationContext - Refreshing WebApplicationContext for namespace 'buildServer-servlet': startup date [Thu Jan 30 13:13:03 UTC 2014]; parent: jetbr$
[2014-01-30 13:13:18,325]   INFO -   jetbrains.buildServer.SERVER - Loading test names index from database...
[2014-01-30 13:13:18,503]   INFO -   jetbrains.buildServer.SERVER - Finished loading test names index
[2014-01-30 13:13:19,184]   INFO -   jetbrains.buildServer.SERVER - Start initializing build durations cache...
[2014-01-30 13:13:19,223]   INFO -   jetbrains.buildServer.SERVER - Finished initializing build durations cache
[2014-01-30 13:13:36,004]   INFO -   jetbrains.buildServer.SERVER - Loading roles from the configuration file: /var/www/data/config/roles-config.xml
[2014-01-30 13:15:06,973]   INFO -  jetbrains.buildServer.STARTUP - TeamCity Spring context contains 945 beans
[2014-01-30 13:15:07,241]   INFO -  jetbrains.buildServer.STARTUP - TeamCity Spring context created in: 123969 ms
[2014-01-30 13:15:08,127]   INFO - rver.plugins.PluginManagerImpl - ===========================================================
[2014-01-30 13:15:08,127]   INFO - rver.plugins.PluginManagerImpl - Plugins initialization started...
[2014-01-30 13:15:08,128]   INFO - rver.plugins.PluginManagerImpl - Scanning plugins folders
[2014-01-30 13:15:08,129]   INFO - .plugins.files.JarSearcherBase - Scanning plugin folder: /var/TeamCity/webapps/ROOT/WEB-INF/plugins
[2014-01-30 13:15:26,204]   INFO - .plugins.files.JarSearcherBase - Scanning plugin folder: /var/www/data/plugins
[2014-01-30 13:15:26,210]   INFO - rver.plugins.PluginManagerImpl - Found 72 plugins: [agent-system-info (ver:27767), agent.push (ver:27767), Ant (ver:27767), ant-net-tasks (ver:27767), Apache Ant$
[2014-01-30 13:15:41,200]   INFO - rver.plugins.PluginsCollection - Load standalone classloaders for 30 plugins [agent-system-info, agent.push, assembly-info-patcher, bugzilla, cloud-amazon, dotne$
[2014-01-30 13:15:41,201]   INFO - rver.plugins.PluginsCollection - Load shared classloader for 42 plugins [Ant, ant-net-tasks, Apache Ant, artifactsSizeStatistics, buildDurationStatisticsPlugin, $
[2014-01-30 13:16:49,223]   WARN -   jetbrains.buildServer.SERVER - Failed to obtain disk free space, watcher is disabled.


The last entry looks interesting. I've installed and reinstalled and created and recreated the server many times, and this last entry is the last one I observe in the logs before the loggings stop and the shutdown happens (after log this we find no more data). It's always seen while loading plugins.

Once, this log appeared
[2014-01-30 07:32:33,821]   WARN -   jetbrains.buildServer.SERVER - Failed to obtain disk free space, watcher is disabled.
[2014-01-30 07:34:27,101]   WARN - erverSide.search.SearchService - Creating new index (version.24)
[2014-01-30 07:34:33,302]   WARN -   jetbrains.buildServer.SERVER - Failed to obtain disk free space, watcher is disabled.


They are just warnings, and that is what seems odd, they are no fatal errors, and I couldn't find any error in any of the other logs. I DO have enough disk space, if one might wonder... And also, TeamCity has enough privileges to manipulate the destination folder.

I thank you very much for your time

1 comment
Comment actions Permalink

I've looked up a little bit. I have disk space available, but it's not the 3GB disk space reserved for an agent by the default watcher.

Is there ANY way I can change this configuration?

0

Please sign in to leave a comment.