[6692] server shuts down with no apparent reason

I've upgraded to TC 6692 yesterday and I get intermittent shutdowns of the
server with no apparent reason in the logs other than the fact that the server
is shutting down:


Anyone seen this or knows how to get around this? This happened 3 timed since
installing the server yesterday. Hope I do not need to revert back and confuse
people who used the server to build.

Cheers,

Bonny

5 comments
Comment actions Permalink

Bonny,

Can you please also provide the Tomcat console output? If run without the console, the output should be in the logs\catalina.*.log file
How do you run the TeamCity - as service or via console?

What is the OS? What TeamCity distribution do you use?

Can it be some trivial reason like some script sending shutdown command to the Tomcat or Ctrl+C accidentally pressed in the console?

--
Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0
Comment actions Permalink

Yegor,

Not currently in the office, so cannot send the catalina.out file, but from recollection, it said something like the http server is pausing and then that it's shutting down.

The server is run on a RHEL3 box, using the runAll.sh script.
The distribution is the standalone tomcat one, not the war.

The server is running in the background as a result of the script, so no Ctrl-C would
make a difference.

Cheers,

Bonny

0
Comment actions Permalink

Hello,

I would suggest to check Tomcat logs. Usually when server shuts down in such
a way it means that Tomcat was unable to bound to a port.

--
Pavel Sher
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"



"Bonny Rais" <bonnyr@optushome.com.au> wrote in message
news:10805626.1203686829220.JavaMail.itn@is.intellij.net...

Yegor,

>

Not currently in the office, so cannot send the catalina.out file, but
from recollection, it said something like the http server is pausing and
then that it's shutting down.

>

The server is run on a RHEL3 box, using the runAll.sh script.
The distribution is the standalone tomcat one, not the war.

>

The server is running in the background as a result of the script, so no
Ctrl-C would
make a difference.

>

Cheers,

>

Bonny



0
Comment actions Permalink

I'm seeing a similar problem on Build 8944 (Release 4.5) on Ubuntu 8.10.

It only occurs when I manually execute a build on the TeamCity server machine that fires up Tomcat (i.e. from a shell manually execute a build via ANT).
I suspect it to be caused by a port collision, although I can't identify what port causes the collision with the TeamCity server.
Also, netstat is providing no useful information on potential causes of a collision.

In addition to the TeamCity server port (8111 in my case), what other ports are required by TeamCity?

Regards,

Matthew Ueckerman

0
Comment actions Permalink

Tomcat requires one more port to be open, usually it is 8005. This port is specified in the TeamCity/conf/server.xml file. Actualy this port is used for Tomcat own commands like STOP.

0

Please sign in to leave a comment.