forums.smartfoxserver.com

The game stopped working and we realized that the problem was with SFS (not connecting).
The ./sfs status was runnigg but not responding
./sfs stop did not worked, I needed to kill the proccess and then start again.

I found this lines before it crashed:

INFO | jvm 1 | 2019/03/14 10:47:49 | [kiducaDB.as]: db.id: buscaDadosDesafio
INFO | jvm 1 | 2019/03/14 10:47:49 | [kiducaDB.as]: db.id: buscaDadosDesafio
INFO | jvm 1 | 2019/03/14 10:52:33 | Java HotSpot(TM) 64-Bit Server VM warning:
INFO | wrapper | 2019/03/14 10:53:36 | Wrapper Process has not received any CPU time for 25 seconds. Extending timeouts.
INFO | jvm 1 | 2019/03/14 10:54:24 | Attempt to allocate stack guard pages failed.
INFO | jvm 1 | 2019/03/14 10:54:56 | [kiducaDB.as]: db.id:
INFO | jvm 1 | 2019/03/14 10:55:32 | [loginDuplicado.as]: [userLost] _os_type: kiduca
INFO | jvm 1 | 2019/03/14 10:55:56 | Java HotSpot(TM) 64-Bit Server VM warning: Attempt to allocate stack guard pages failed.
INFO | jvm 1 | 2019/03/14 10:56:27 | Java HotSpot(TM) 64-Bit Server VM warning: Attempt to allocate stack guard pages failed.
INFO | wrapper | 2019/03/14 10:56:58 | Wrapper Process has not received any CPU time for 97 seconds. Extending timeouts.
INFO | jvm 1 | 2019/03/14 10:57:30 | [loginDuplicado.as]: ROOM it.gotoandplay.smartfoxserver.data.Room@63903190
INFO | jvm 1 | 2019/03/14 10:58:20 | [loginDuplicado.as]: [userLost] _os_type: kiduca
INFO | wrapper | 2019/03/14 10:59:02 | Wrapper Process has not received any CPU time for 58 seconds. Extending timeouts.
INFO | jvm 1 | 2019/03/14 10:59:29 | [loginDuplicado.as]: ROOM it.gotoandplay.smartfoxserver.data.Room@60520a66
INFO | jvm 1 | 2019/03/14 10:59:59 | [loginDuplicado.as]: [userLost] _os_type: kiduca
INFO | jvm 1 | 2019/03/14 11:00:35 | [loginDuplicado.as]: ROOM it.gotoandplay.smartfoxserver.data.Room@60520a66
INFO | wrapper | 2019/03/14 11:01:06 | Wrapper Process has not received any CPU time for 58 seconds. Extending timeouts.
ERROR | wrapper | 2019/03/14 11:02:38 | JVM appears hung: Timed out waiting for signal from JVM.
STATUS | wrapper | 2019/03/14 12:19:00 | --> Wrapper Started as Daemon
STATUS | wrapper | 2019/03/14 12:19:01 | Launching a JVM...

Any help?

edited: the server (AWS) was running without problems at that moment (CPU, Memory)

Hi,
these errors appear when the system is running very low on resources (typically RAM) and the JVM is struggling allocating new ones.
It's also possible that the EC2 instance killed the process when there's little memory available to the OS.

I'd recommend monitoring the memory usage of your application at runtime and see if there are signs of memory leak (e.g. memory usage growing constantly even after many cycles of GC)

You can take a look at this guide too:
http://docs2x.smartfoxserver.com/Advanc ... ive-server

Hope it helps