NetWorker: nsrd core dumps when gstclreport command is used to generate NMC Reports

Summary: A Linux server is configured as both the NetWorker server and NetWorker Management Console (NMC) server. The gstclreport command is used to generate NMC Reports from command line. This cases the NetWorker server daemon (nsrd) to crash with a core dump. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

The gstclreport command is used to generate NetWorker Management Console (NMC) Reports on a Linux server.
The NetWorker server daemon (nsrd) crashes, reporting a core dump. The server's /nsr/logs/daemon.raw shows:

5 09/18/25 02:00:06  1 1 0 0 unknown unknown LOG unrendered Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00007fe090608000, 12288, 0) failed; error='Cannot allocate memory' (errno=12)
5 09/18/25 02:00:06  1 1 0 0 unknown unknown LOG unrendered #
5 09/18/25 02:00:06  1 1 0 0 unknown unknown LOG unrendered # There is insufficient memory for the Java Runtime Environment to continue.
5 09/18/25 02:00:06  1 1 0 0 unknown unknown LOG unrendered # Native memory allocation (mmap) failed to map 12288 bytes for committing reserved memory.
5 09/18/25 02:00:06  1 1 0 0 unknown unknown LOG unrendered # An error report file with more information is saved as:
5 09/18/25 02:00:06  1 1 0 0 unknown unknown LOG unrendered # /nsr/cores/nsrd/hs_err_pid24453.log
143494 09/18/25 02:05:17  2 1 0 657065792 24304 0 NETWORKER_SERVERNAME nsrd SYSTEM warning Authentication Proxy exited with status code 256 
143496 09/18/25 02:05:18  1 1 0 657065792 24304 0 NETWORKER_SERVERNAME nsrd SYSTEM notice Successfully restarted Authentication Proxy with PID 15062 
173354 09/18/25 02:05:18  4 5 0 657065792 24304 0 NETWORKER_SERVERNAME nsrd NSR severe ****************************************************. 
173355 09/18/25 02:05:18  4 5 0 657065792 24304 0 NETWORKER_SERVERNAME nsrd NSR severe A core file can indicate a problem in NetWorker software. 
173356 09/18/25 02:05:18  4 5 0 657065792 24304 0 NETWORKER_SERVERNAME nsrd NSR severe If the problem persists, investigate, collect the core file and the daemon.raw log. 
174008 09/18/25 02:05:18  4 5 0 657065792 24304 0 NETWORKER_SERVERNAME nsrd NSR severe New Core File Created 2025-09-18T02:05:17 /nsr/cores/nsrd/hs_err_pid24453.log 
173358 09/18/25 02:05:18  4 5 0 657065792 24304 0 NETWORKER_SERVERNAME nsrd NSR severe New Cores = 1, Total Core Files = 56 
173354 09/18/25 02:05:18  4 5 0 657065792 24304 0 NETWORKER_SERVERNAME nsrd NSR severe ****************************************************. 
71191 09/18/25 02:05:18  0 0 0 657065792 24304 0 NETWORKER_SERVERNAME nsrd NSR info Server Critical event: Process nsrd crashed. New core file found on server NETWORKER_SERVERNAME. Check daemon.raw for details.
NOTE: the unrendered daemon.raw can be rendered using nsr_render_log /nsr/logs/daemon.raw > /nsr/logs/daemon_$(date -I).log 2<&1. The review the rendered .log file.

Cause

Physical memory was not exceeded on the host, there is sufficient memory on the host. The NMC reports generation is exceeding the hard coded Java max heap settings of the auth_proxyd  JVM. The auth_proxyd memory heap cannot be modified.

Resolution

Open an elevated shell on the NetWorker server and use one of the following options to allow memory over commitment:

Option One:

  1. Allow overcommitment without prechecks
  2. Modify sysctl.conf:
vi /etc/sysctl.conf
  1. Add the following lines:
vm.overcommit_memory=1
  1. Reload the system parameters:
sysctl -p
  1. Restart NetWorker services: 
nsr_shutdown
systemctl start networker

#OR

/etc/init.d/networker start
NOTE: This setting always allows overcommit. The kernel allows all memory allocations, regardless of the current memory status. The JVM and NetWorker daemons rarely use all reserved memory simultaneously. 

Option Two:

  1. Allow overcommitment with precheck and overcommitment ratio.
  2. Modify sysctl.conf
vi /etc/sysctl.conf
  1. Add the following lines:
vm.overcommit_memory=2
vm.overcommit_ratio=150
  1. Reload the system parameters:
sysctl -p
  1. Restart NetWorker services:
nsr_shutdown
systemctl start networker

#OR

/etc/init.d/networker start
NOTE: The system only allows memory allocations if there is enough free RAM + swap space to fulfill the request. This allows more memory to be allocated than physically exists, but only within a controlled and calculated limit.

 

Generate the NMC reports using the gstclreport command and monitor if any service interruptions are observed. The above changes are expected to resolve the failure.

Additional Information

If the system is over using physical memory, ensure that the server has appropriate resources configured to manage the NetWorker datazone. See the NetWorker Performance Optimization and Planning regarding recommended CPU and Memory settings. See: Support for NetWorker | Manuals & Documents

 

If the server is sized appropriately but you are noticing higher than expected resource utilization, see: NetWorker: Troubleshooting High Memory or CPU usage by Process

Affected Products

NetWorker

Products

NetWorker Family
Article Properties
Article Number: 000382952
Article Type: Solution
Last Modified: 19 رجب 1447
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.