About Wrapper.conf and data archiving
Hello. I'm "noob" in SCP. I got server with configured SCP, but many times per day SCP web service goes down. So have started search why. And have some question for supporting community. Server configuration: Windows Server 2008 R2 x64 4CPU and 6Gb ram
1. How to know which wrapper.conf is in use for web service.
1.1
"C:\ManageEngine\SupportCenter\bin\wrapper.conf" - there only one line: "wrapper.debug=true" very stange. in same folder i can found log file named "wrapper.log" there i found. some error when my SCP goes down. And i think that is main wrapper configuration file, i'm right?
STATUS | wrapper | 2017/04/04 16:53:53 | JVM appears hung: Timed out waiting for signal from JVM. Restarting JVM.
ERROR | wrapper | 2017/04/04 16:54:33 | Shutdown failed: Timed out waiting for signal from JVM.
ERROR | wrapper | 2017/04/04 16:54:33 | JVM did not exit on request, termination requested.
STATUS | wrapper | 2017/04/04 16:54:33 | JVM exited after being requested to terminate.
STATUS | wrapper | 2017/04/04 16:54:39 | Launching a JVM...
INFO | jvm 2 | 2017/04/04 16:54:40 | WrapperManager: Initializing...
INFO | jvm 2 | 2017/04/04 16:54:42 | TRYING TO STOP DB WITH COMMAND:::stopDB.bat ../mysql 33356 root
INFO | jvm 2 | 2017/04/04 16:54:42 | This copy is licensed to ADB
INFO | jvm 2 | 2017/04/04 16:54:56 | Unclean shutdown of previous run.
...
INFO | jvm 2 | 2017/04/04 16:55:39 | Server Started.
1.2
The second error is strange too, it is look like missing some settings in configuration for logging..
WARN | wrapper | 2017/04/05 14:43:22 | Unable to write to the configured log directory: server\default\log (The system cannot find the path specified. (0x3))
WARN | wrapper | 2017/04/05 14:43:22 | The directory does not exist.
WARN | wrapper | 2017/04/05 14:43:22 | Unable to write to the configured log file: server\default\log\wrapper.log (The system cannot find the path specified. (0x3))
WARN | wrapper | 2017/04/05 14:43:22 | Falling back to the default file in the current working directory: wrapper.log
1.3 Third error with Java and out of memory:
INFO | jvm 2 | 2017/04/04 12:55:03 | Please connect your client at
http://localhost:80
STATUS | wrapper | 2017/04/04 13:23:03 | Pinging the JVM took 7 seconds to respond.
STATUS | wrapper | 2017/04/04 13:23:46 | Pinging the JVM took 12 seconds to respond.
STATUS | wrapper | 2017/04/04 13:23:46 | Pinging the JVM took 8 seconds to respond.
STATUS | wrapper | 2017/04/04 13:23:56 | Pinging the JVM took 8 seconds to respond.
STATUS | wrapper | 2017/04/04 13:24:16 | Pinging the JVM took 9 seconds to respond.
INFO | jvm 2 | 2017/04/04 13:26:31 | WrapperManager Error: Server daemon died!
INFO | jvm 2 | 2017/04/04 13:26:33 |
INFO | jvm 2 | 2017/04/04 13:26:33 | WrapperManager Error: java.lang.OutOfMemoryError: GC overhead limit exceeded
INFO | jvm 2 | 2017/04/04 13:26:33 | WrapperManager Error:
at java.net.SocketInputStream.read(SocketInputStream.java:209)
INFO | jvm 2 | 2017/04/04 13:26:33 | WrapperManager Error:
at java.io.DataInputStream.readByte(DataInputStream.java:265)
INFO | jvm 2 | 2017/04/04 13:26:33 | WrapperManager Error:
at org.tanukisoftware.wrapper.WrapperManager.handleBackend(WrapperManager.java:5325)
INFO | jvm 2 | 2017/04/04 13:26:33 | WrapperManager Error:
at org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:5695)
INFO | jvm 2 | 2017/04/04 13:26:33 | WrapperManager Error:
at java.lang.Thread.run(Thread.java:745)
INFO | jvm 2 | 2017/04/04 13:26:33 | WrapperManager Error: The backend was closed unexpectedly. Restart to resync with the Wrapper.
INFO | jvm 2 | 2017/04/04 13:26:45 | AdventNetSupportCenter [STOPPED]
b. "C:\ManageEngine\SupportCenter\server\default\conf\wrapper.conf" also here i have file "wrapper_64.conf" and "wrapper.conf.recomended" with a many settings inside. So i have confused which file is used for SCP or we need to use in production portal.
2. We use Windows Server R2 x64. In server taks manager i found working process java.exe*32, and i remeber about memory errors in point 1.3 "WrapperManager Error: java.lang.OutOfMemoryError: GC overhead limit exceeded" i found solution that some customer have change wrapper.conf "wrapper.java.maxmemory=1024" Can i use more than 1024, for exaple 4096 and this will works?? Or i have to use java.exe for x64bit?
I hope the solution will be simple..