What is Suicide Watcher? and why did it shutdown my TeamCity server?
Our TeamCity server service shutdown today for no known reason. The only thing we can find in the logs in the following entry in the teamcity-mavenserver.log
[2017-12-06 12:48:55,549] INFO - r.maven.remote.MavenServerImpl - Suicide Watcher: shutting down server due to activity on system.in stream
[2017-12-06 12:48:55,549] WARN - r.maven.remote.MavenServerImpl - Forced shutdown due to: [Suicide Watcher: shutting down server due to activity on system.in stream]
Please sign in to leave a comment.
Any updates on this? We have it twice a month....
Hi there,
The MavenServer simply kills itself when the main TeamCity application is terminated in an unexpected way. That is the suicide watcher. Therefore, this log entry doesn't say much about the source of the problem, only its effects. I recommend you look into teamcity-server.log or teamcity-winservice.log, these give much more detailed information.
In my case, it turned out that the JVM thought it was out of memory and crashed. I read the following part of the documentation: https://confluence.jetbrains.com/display/TCD10/Installing+and+Configuring+the+TeamCity+Server#InstallingandConfiguringtheTeamCityServer-Using64bitJavatoRunTeamCityServer
The most interesting bit: "the 32-bit JVM can reliably work with up to 1Gb heap memory (-
Xmx1024m). (This can be increased to-Xmx1200m, but JVM under Windows might crash occasionally with this setting.)"Our server ran the 32-bit version but somehow, by default it specified
-Xmx1200mwhich was probably causing the crashes, as described. I decreased that to -Xmx1024mand I've been closely monitoring the stability of our server and it didn't crash again so far.