Without knowing what requires all the memory it's IMPOSSIBLE to give you any advice how you might be able to improve your server configuration.

You already posted the same question no long ago and I already gave you some hints what you could try to find out what might be wrong. Have you tried any of my suggestions at all? If you ask the same question again and again without trying for yourself what has been suggested you won't get it any improvements ever. It's simply not possible to give you this one advice that will fix the problem for sure because there could be many reasons for the out-of-memory issue (plugin requires too much memory or at least more than memory_limit in .htaccess, keeping connections of mysql alive with a too hight maximum number of connections or some bad settings in mysql configuration not suitable for the amount of ram of your server etc. etc.).

You need to monitor your server and test out memory consumption at least for a few hours or days to find out when the memory consumption gets critical.

Or hire someone with good knowledge of server administration or administrating Elgg sites (or knowledge about both) to help you with improving your server configuration. For example, you could ask for (paid) help here in the Professional services group and you might get contacted with someone who takes such jobs. Even if it will cost you it might be your only chance to get it fixed if you are not ready to learn more about server administration on your own (something you can't do in just a few hours or days for sure!).

Try to disable PHP secure stuffs that you have enabled in WHM.. Re-configure Apache when you do make sure you only choose what you know are try to choose only what elgg requires..

When you Re-configure / Rebuild Apache make sure you don't choose anything extra other than what elgg basic requirement needs & try to run the site & check this can solve ur problem ..    

It quite impossible to give any good advice what might need to be improved in the server config with just a single top output.

You need to investigate what happens over a certain time. Is it a RAM bottleneck or could it be a matter of disc I/O blocking processes? Is the MySQL config, Apache config suitable for the amount of RAM available? Could it some plugin of Elgg causing a high server load due to causing many http requests and/or database queries? All this is something you need to investigate over a certain time while trying out stuff on the Elgg site a typical user would do (log in, move on the site from page to page, post something) while keeping an eye on the server load / output of top.

In general you can check what runs on the server apart from Apache, MySQL, mail server and security services and stop what you don't need to save RAM and CPU load. Then you need to learn what might improve performance in tuning the MySQL and Apache config (e.g. cache settings and several other settings in my.cnf). You might need to decrease some of the my.cnf setting values to have more free RAM for Apache and PHP processes (which only run for a few seconds each but require some free RAM). It's not easy to find a good configuration and it will take some time. But it's something you need to learn as it's very server specific and difficult to give any general advice here.

Hire someone, or ask your hoster

• Upgrade
• Performance

The relevant error message is

[Fri Mar 23 01:50:52 2018] [error] [client 195.154.60.90] PHP WARNING: 2018-03-23 01:50:52 (EDT): "mysql_connect(): User nsikdar_elgg63 already has more than 'max_user_connections' active connections"

That's not happening due to a bug in Elgg but due to an insufficient server config (of the MySQL server). See also my reply at https://elgg.org/discussion/view/2629349/error-has-exceeded-the-max-user-connections.

I am also getting these error messages .

[Mon Mar 26 03:30:41 2018] [error] [client 191.102.153.18] PHP WARNING: 2018-03-26 03:30:41 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/all
[Mon Mar 26 03:25:44 2018] [error] [client 91.200.12.127] PHP WARNING: 2018-03-26 03:25:44 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/owner/MillieLevi
[Mon Mar 26 03:25:37 2018] [error] [client 91.200.12.127] PHP WARNING: 2018-03-26 03:25:37 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/owner/MillieLevi
[Mon Mar 26 03:18:24 2018] [error] [client 91.200.12.170] PHP WARNING: 2018-03-26 03:18:24 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/owner/MillieLevi
[Mon Mar 26 03:18:06 2018] [error] [client 91.200.12.170] PHP WARNING: 2018-03-26 03:18:06 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/owner/MillieLevi
[Mon Mar 26 03:17:37 2018] [error] [client 91.200.12.185] PHP WARNING: 2018-03-26 03:17:36 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/owner/MillieLevi
[Mon Mar 26 03:17:33 2018] [error] [client 91.200.12.173] PHP WARNING: 2018-03-26 03:17:33 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/owner/MillieLevi
[Mon Mar 26 03:17:33 2018] [error] [client 91.200.12.169] PHP WARNING: 2018-03-26 03:17:33 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/owner/MillieLevi
[Mon Mar 26 03:17:29 2018] [error] [client 91.200.12.185] PHP WARNING: 2018-03-26 03:17:29 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/owner/MillieLevi
[Mon Mar 26 03:17:26 2018] [error] [client 91.200.12.169] PHP WARNING: 2018-03-26 03:17:26 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/owner/MillieLevi
[Mon Mar 26 03:17:26 2018] [error] [client 91.200.12.173] PHP WARNING: 2018-03-26 03:17:26 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/owner/MillieLevi
[Mon Mar 26 03:12:26 2018] [error] [client 212.83.133.63] PHP WARNING: 2018-03-26 03:12:26 (EDT): "array_reverse() expects parameter 1 to be array, boolean given" in file /home/nsikdar/public_html/mod/blog/views/default/blog/sidebar/archives.php (line 17), referer: http://safalaya.com/blog/all

That's a warning and not an error and has nothing to do with database connection problem.

There's a very old plugin at https://github.com/juliendangers/Elgg-Scoop-It (it's very unlike that it still works on recent versions of Elgg and it might never have fully worked in the first place according to the readme). You could use this plugin as a starting point and update/fix it to work for you. Or you could hire a developer to do the job for you. Without such a plugin you won't be able to make use of scoop.it.