I was setting up a new instance of Orchestrator inside my lab and came across this issue. Â the Orchestrator Server service would not start, andi nside the vCenter Orchestrator Configuration webpage, we don’t have any output in the log–so we investigate the Windows logs…
In the system log all you see is Error: The VMware vCenter Orchestrator Server service terminated with service-specific error Incorrect function..
Poking around we come across a log file @ C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\bin\wrapper.log which sheds some light on the problem:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 |
C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\bin\wrapper.log STATUS | wrapper | 2011/11/26 18:02:35 | --> Wrapper Started as Console STATUS | wrapper | 2011/11/26 18:02:35 | Java Service Wrapper Professional Edition 64-bit 3.3.9 STATUS | wrapper | 2011/11/26 18:02:35 | Copyright (C) 1999-2009 Tanuki Software, Ltd. All Rights Reserved. STATUS | wrapper | 2011/11/26 18:02:35 | http://wrapper.tanukisoftware.org STATUS | wrapper | 2011/11/26 18:02:35 | Licensed to VMware Global, Inc. for VMware vCenter Orchestrator STATUS | wrapper | 2011/11/26 18:02:35 | STATUS | wrapper | 2011/11/26 18:02:35 | Launching a JVM... INFO | jvm 1 | 2011/11/26 18:02:35 | Error occurred during initialization of VM INFO | jvm 1 | 2011/11/26 18:02:35 | Could not reserve enough space for object heap ERROR | wrapper | 2011/11/26 18:02:35 | JVM exited while loading the application. STATUS | wrapper | 2011/11/26 18:02:40 | Launching a JVM... INFO | jvm 2 | 2011/11/26 18:02:40 | Error occurred during initialization of VM INFO | jvm 2 | 2011/11/26 18:02:40 | Could not reserve enough space for object heap ERROR | wrapper | 2011/11/26 18:02:40 | JVM exited while loading the application. STATUS | wrapper | 2011/11/26 18:02:45 | Launching a JVM... INFO | jvm 3 | 2011/11/26 18:02:45 | Error occurred during initialization of VM INFO | jvm 3 | 2011/11/26 18:02:45 | Could not reserve enough space for object heap ERROR | wrapper | 2011/11/26 18:02:45 | JVM exited while loading the application. STATUS | wrapper | 2011/11/26 18:02:50 | Launching a JVM... INFO | jvm 4 | 2011/11/26 18:02:57 | Error occurred during initialization of VM INFO | jvm 4 | 2011/11/26 18:02:57 | Could not reserve enough space for object heap ERROR | wrapper | 2011/11/26 18:02:57 | JVM exited while loading the application. STATUS | wrapper | 2011/11/26 18:03:01 | Launching a JVM... INFO | jvm 5 | 2011/11/26 18:03:01 | Error occurred during initialization of VM INFO | jvm 5 | 2011/11/26 18:03:01 | Could not reserve enough space for object heap ERROR | wrapper | 2011/11/26 18:03:01 | JVM exited while loading the application. FATAL | wrapper | 2011/11/26 18:03:02 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2011/11/26 18:03:02 | There may be a configuration problem: please check the logs. STATUS | wrapper | 2011/11/26 18:03:02 | |
Your first thought might be disk space, did a log run away? No that isn’t the case–Java Heap refers to memory, looking inside the wrapper.conf from the command above we find more information.
|
1 2 3 4 5 6 |
C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\bin\wrapper.conf # Initial Java Heap Size (in MB) wrapper.java.initmemory=2048 # Maximum Java Heap Size (in MB) wrapper.java.maxmemory=2048 |
Java has to allocate 2Gb of RAM on startup. My VM only had 1.5Gb, that looks like the issue–this is what you get for ignoring the Minimum System Requirements (assuming your running Orchestrator on same server as your vCenter). Â Increase the RAM on your VM and this error should be gone. vCenter Server should have a minimum of 3Gb of RAM.
