search

Teevity / ice

AWS Usage Tool
2.85k stars 434 forks source link

Error when issueing docker-compose up. #201

Open khoi-thinh opened 8 years ago

khoi-thinh commented 8 years ago

Here's the output:

ce_1 | 2016-03-03 08:26:17,115 [localhost-startStop-1] INFO core.StandardContext - Unable to set the web application class loader property [clearReferencesStatic] to [false] as the property does not exist. ice_1 | 2016-03-03 08:26:17,116 [localhost-startStop-1] INFO core.StandardContext - Unable to set the web application class loader property [clearReferencesStopThreads] to [false] as the property does not exist. ice_1 | 2016-03-03 08:26:17,116 [localhost-startStop-1] INFO core.StandardContext - Unable to set the web application class loader property [clearReferencesStopTimerThreads] to [false] as the property does not exist. ice_1 | 2016-03-03 08:26:17,116 [localhost-startStop-1] INFO core.StandardContext - Unable to set the web application class loader property [clearReferencesHttpClientKeepAliveThread] to [true] as the property does not exist. ice_1 | 2016-03-03 08:26:17,129 [localhost-startStop-1] INFO startup.ContextConfig - No global web.xml found ice_1 | 2016-03-03 08:26:17,369 [localhost-startStop-1] INFO [localhost].[/ice] - No Spring WebApplicationInitializer types detected on classpath ice_1 | 2016-03-03 08:26:17,385 [localhost-startStop-1] INFO [localhost].[/ice] - Initializing Spring root WebApplicationContext ice_1 | Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000000d9b47000, 30011392, 0) failed; error='Cannot allocate memory' (errno=12) ice_1 | # ice_1 | # There is insufficient memory for the Java Runtime Environment to continue. ice_1 | # Native memory allocation (malloc) failed to allocate 30011392 bytes for committing reserved memory. ice_1 | # An error report file with more information is saved as: ice_1 | # /opt/ice/hs_err_pid1.log dockerice_ice_1 exited with code 1.

I don't understand what the reason was. Can someone help me about this please?

NitriKx commented 8 years ago 
# There is insufficient memory for the Java Runtime Environment to continue. 
# Native memory allocation (malloc) failed to allocate

means that your JVM does not have enough memory to run.

Take a look at http://serverfault.com/questions/662992/java-on-linux-insufficient-memory-even-though-there-is-plenty-of-available-memor

khoi-thinh commented 8 years ago

Thank you for pointing it out. So i had to take a test on a new cloud server (this time 8GB RAM) and this error never happened. But this time, another error appeared and it said: connection refused while connecting to up stream. Here's a screenshot. Can you take a look at it and tell me how to fix this? It was driving me crazy all day. http://www.upsieutoc.com/images/2016/03/08/error.jpg