AIQUM 9.18 encounters an out-of-memory condition that causes the service to stop and become inaccessible
Applies to
ActiveIQ Unified Manager (AIQUM) 9.18
Issue
- The
journalcl.txtshowsoom-killerevents indicating that the Java process (ocie.service) is terminated due to memory exhaustion.
kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/ocie.service,task=java,pid=1139484,uid=999kernel: Out of memory: Killed process 1139484 (java) total-vm:7000784kB, anon-rss:3011720kB, file-rss:0kB, shmem-rss:0kB, UID:999 pgtables:6944kB oom_score_adj:0systemd[1]: ocie.service: A process of this unit has been killed by the OOM killer.systemd[1]: ocie.service: Failed with result 'oom-kill'.
- Multiple
ConfigAdvisorCLIprocesses are running concurrently inps.out.txt,
jboss 4076354 1 0.0 Mar30 4 2023295 ? 00:13:18 4 564352 /opt/netapp/ocum/configadvisor/ConfigAdvisorCLI/ConfigAdvisorCLI --multiprocessing-fork tracker_fd=19 pipe_handle=25
- The logs under
/var/log/ocie/recording/AIQCASecureData/collected_log/ConfigAdvisorAIDE/Logs/JobLogs/XXXXXXXXX.logshow errors such as:
Collection from <ONTAP_IP>_<AIQUM>_202311251252.0.files Failed with error - database is locked' Traceback (most recent call last): File "peewee.py", line 3237, in execute_sql sqlite3.OperationalError: database is locked
