jemalloc | general purpose malloc implementation

After reaching out to Quotaguard, they patched the qgtunnel binary and there is no error anymore:

You are trying to compile LWJGL 2 code here. All the imports that it cannot find pertain to the verison 2 of LWJGL. The current version that you can get from the mentioned lwjgl site is 3 and version 3 is incompatible with version 2.

Either explicitly download LWJGL 2 from e.g. http://legacy.lwjgl.org/ or rewrite your code to work with LWJGL 3.

If you go the LWJGL 2 route, though, please note that it hasn't been actively maintained anymore for more than 6 years now.

By default, make check assumes $HOME is shared across nodes, which is the case on most HPC systems. During the test, it creates a temporary directory as a destination for the compiled test program: $HOME/.chpl. Because your home directory is not NFS-mounted, the make check fails.

You can override the temporary directory used for make check by setting CHPL_CHECK_INSTALL_DIR. If you point that environment variable to an NFS-mounted path, make check should work.

The error message says that the JVM failed to commit memory, because mmap syscall returned with the error code 12 (ENOMEM).

This typically happens when the process reaches one of the OS memory limits:

• The number of memory mappings exceeded vm.max_map_count sysctl limit. This is a quite common problem with Cassandra, since Cassandra tends to mmap thousands files, and the default limit is rather low - around 65K.

  How to check: wc -l /proc//maps where is Java process ID.

  How to fix: sudo sysctl vm.max_map_count=1000000

• Total amount of the process' virtual memory exceeded RLIMIT_AS

  How to check: ulimit -v, cat /proc//status | grep Vm

  How to fix: ulimit -v unlimited before starting Cassandra in the same shell.

• Overcommit is disabled, and the overcommit ratio is too low.

  How to check: sysctl vm.overcommit_memory, sysctl vm.overcommit_ratio, cat /proc/meminfo

  How to fix: sudo sysctl vm.overcommit_memory=0

sysupdate and networkservice seem to be malicious services running in your system. Maybe somehow hackers got into your system and upload some scripts which are taking too much of your capacities. Most probably they are mining. So follow the below steps

1. stop that services
2. backup your redis file
3. restart your server
4. you can reinstall your redis
5. better to hire some consultant for hardening your redis server

I think I narrowed it down to "groonga." First I'm hearing of it, but apparently it's a mariadb brew dependency. I found where the "welcome to nginx" text was coming from.

I think this may reflect some of the ambiguity in what "leak" means. Tools like Valgrind will traverse the pointer graph of the program at shutdown, and treat things as leaks if that traversal does not find some live allocation.

Other tools treat "leaks" as simply anything allocated but not freed. The profiling mode in jemalloc works more like this way. It reports an estimation of the live bytes attributable to various call stacks at program termination.

It turns out that

1. openjdk-8-dbg package installs files with debug symbols into /usr/lib/debug/.build-id
2. jeprof looks for debug symbols in /usr/lib/debug/{FULL_SO_PATH}

So, it's a combination of a bug in jeprof that does not parse .note.gnu.build-id section, and a problem of the dbg package that does not include full path symlinks to debug libraries.

To work around this, you may create the corresponding symlink manually:

i rebased my fork with the current master branch. Removed all the files in the src directory. Then did a git hard reset. Then ran git pull. Ran the remove build cache script again. Then kicked off another build. Build is working fine again with the current master branch. So i am guessing the issue was with my src directory not being in sync with the fork repo.