Hi!
Congrats for the 4.15 release! UI makes a great difference.
I started launching deployment tests with 4.15 and I just noticed that the
manager is running out of memory were 4.14 did not.
This is in a test environment where the manager host resources are constrained
yet 100% functional in 4.14.
Anybody experiencing this?
● cloudstack-management.service - CloudStack Management Server
Loaded: loaded (/lib/systemd/system/cloudstack-management.service; enabled;
vendor preset: enabled)
Drop-In: /etc/systemd/system/cloudstack-management.service.d
└─mesh-dep.conf, mysql-dep.conf
Active: failed (Result: exit-code) since Tue 2021-01-19 11:02:44 EST; 15h ago
Process: 6641 ExecStart=/usr/bin/java $JAVA_DEBUG $JAVA_OPTS -cp $CLASSPATH
$BOOTSTRAP_CLASS (code=exited, status=1/FAILURE)
Main PID: 6641 (code=exited, status=1/FAILURE)
Jan 19 11:02:40 manager java[6641]: INFO [c.c.c.ConsoleProxyManagerImpl]
(AgentTaskPool-8:ctx-71ff758f) (logid:58f404cb) Console p
Jan 19 11:02:40 manager java[6641]: WARN [c.c.a.m.AgentManagerImpl]
(AgentConnectTaskPool-2683:ctx-abc795fe) (logid:c4046d5d) Reso
Jan 19 11:02:44 manager java[6641]: OpenJDK 64-Bit Server VM warning: INFO:
os::commit_memory(0x000000009ea80000, 26738688, 0) fail
Jan 19 11:02:44 manager java[6641]: #
Jan 19 11:02:44 manager java[6641]: # There is insufficient memory for the Java
Runtime Environment to continue.
Jan 19 11:02:44 manager java[6641]: # Native memory allocation (mmap) failed to
map 26738688 bytes for committing reserved memory.
Jan 19 11:02:44 manager java[6641]: # An error report file with more
information is saved as:
Jan 19 11:02:44 manager java[6641]: #
/var/log/cloudstack/management/cloudstack-management.err
Jan 19 11:02:44 manager systemd[1]: cloudstack-management.service: Main process
exited, code=exited, status=1/FAILURE
Jan 19 11:02:44 manager systemd[1]: cloudstack-management.service: Failed with
result 'exit-code'.
