"TERM trapped. Shutting down" server stops unexpe

johnsquires · Post by **johnsquires** » 19 Jul 2008, 08:04

Hi guys
I have got SFS Basic working well, with a flash application I wrote. It is excellent!
But, every so often, the server shuts down for no reason. I get this error:

INFO | jvm 1 | 2008/07/19 09:27:49 | 09:27:49.053 - [ INFO ] > Server is up and running!
STATUS | wrapper | 2008/07/19 09:47:25 | TERM trapped. Shutting down.

or here is another example:
INFO | jvm 1 | 2008/07/18 00:01:04 | 00:01:04.254 - [ INFO ] > Server is up and running!
INFO | jvm 1 | 2008/07/18 00:20:23 | 00:20:23.913 - [ WARNING ] > SysHandler -> Bad room id. Action: asObj >> java$
STATUS | wrapper | 2008/07/18 00:30:33 | TERM trapped. Shutting down.

So, the server runs for 20 or 30 mins then dies.

I am not a Linux expert, so can you help me to diagnose the problem?

John

Post by **Lapo** » 20 Jul 2008, 05:46

Try starting the server with the start.sh script instead of sfs. This will start the JVM alone without the native third-party wrapper.
If you need to restart/stop the server you can use the provided admin tool

Hope it helps

nurdogan · Post by **nurdogan** » 12 Dec 2008, 15:16

Lapo wrote:Try starting the server with the start.sh script instead of sfs. This will start the JVM alone without the native third-party wrapper.
If you need to restart/stop the server you can use the provided admin tool

Hope it helps

Today i also had this Error Message "Error Trapped".

INFO | jvm 1 | 2008/12/12 11:28:41 | INFO: Disconneting idle user: xxx
INFO | jvm 1 | 2008/12/12 11:31:21 | 11:31:21.893 - [ INFO ] > Disconneting idle user: xxxx
INFO | jvm 1 | 2008/12/12 11:31:21 | Dec 12, 2008 11:31:21 AM it.gotoandplay.smartfoxserver.lib.ConnectionCleanerTask run
INFO | jvm 1 | 2008/12/12 11:31:21 | INFO: Disconneting idle user: xxx
STATUS | wrapper | 2008/12/12 11:34:37 | TERM trapped. Shutting down.

Is there a known Problem with Tanuki?

Post by **Lapo** » 12 Dec 2008, 16:22

We know that Tanuki and Linux CentOS tend to fight each other, although the reason is unknown.
What version of SFS are you using?
Judging from the last message fired by the Wrapper it would be also possible that the application has received a SIG_TERM from an admin? ( a kill, in other words ) Possible?

kmk · Post by **kmk** » 16 Dec 2008, 15:32

Lapo wrote: Judging from the last message fired by the Wrapper it would be also possible that the application has received a SIG_TERM from an admin? ( a kill, in other words ) Possible?

It should be possible to ignore SIG_TERM and -INT.

Please read here how to do that:
http://wrapper.tanukisoftware.org/doc/e ... gnals.html

Post by **Lapo** » 16 Dec 2008, 16:10

Thanks for pointing to that page. I found this interesting:

On UNIX systems, some backup programs that run as cron jobs will send out system wide TERM signals that can cause the Wrapper to shutdown. These signals can be ignored by setting this property to true.

... could be the culprit.

As suggested you should be able to add this line:

Code: Select all

wrapper.ignore_signals=true

in your Server/conf/wrapper.conf file to ignore those signals.

Let me know if it works