it has been the second time the server died itself within the week, has never happened before.
i dont see anything in the logs.
sys log just shows smartfox.service: Main process exited, code=exited, status=1/FAILURE
ive checked smartfox.log, boot.log and nothing.
where else can i check to find some indication of whats going on?
server failed, unable to find reason
Re: server failed, unable to find reason
Hi,
you can check the SFS2X/ folder and see if there's any hs_err_pidXXXX.log file.
These files are created by the JVM in case of a hard crash.
Let us know.
you can check the SFS2X/ folder and see if there's any hs_err_pidXXXX.log file.
These files are created by the JVM in case of a hard crash.
Let us know.
Re: server failed, unable to find reason
ok, this is very wierd. the log file says
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 109051904 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
The server has been allocated 3GB max ram and given minimum 1GB ram. 3GB is MORE than plenty.
solutions has "Decrease Java heap size (-Xmx/-Xms)".
is my 3max 1 min bad? ie: allocating too much min bad?
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 109051904 bytes for committing reserved memory.
# Possible reasons:
# The system is out of physical RAM or swap space
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
The server has been allocated 3GB max ram and given minimum 1GB ram. 3GB is MORE than plenty.
solutions has "Decrease Java heap size (-Xmx/-Xms)".
is my 3max 1 min bad? ie: allocating too much min bad?
Re: server failed, unable to find reason
We don't recommend setting memory manually unless you have very good reasons to do so.
Other than that, just let the JVM decide.
For more details see this article from our blog:
https://smartfoxserver.com/blog/sfs2x-m ... on-part-1/
As regards the specific error you found, it looks like there was no more physical memory available in your system and the JVM gave up.
If those heap settings are absolutely necessary, make sure you have enough RAM available. There might be other processes or services using lots of memory as well.
Hope it helps
Other than that, just let the JVM decide.
For more details see this article from our blog:
https://smartfoxserver.com/blog/sfs2x-m ... on-part-1/
As regards the specific error you found, it looks like there was no more physical memory available in your system and the JVM gave up.
If those heap settings are absolutely necessary, make sure you have enough RAM available. There might be other processes or services using lots of memory as well.
Hope it helps
Who is online
Users browsing this forum: No registered users and 87 guests