kern.vm.mmap.return message is repeated followed by a MGWD subsystem restart

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 76

Visibility:: Public

Votes:: 0

Category:: fas-systems

Specialty:: core

Last Updated:

Applies to

A400
ONTAP 9

Issue

The kern.vm.mmap.return message was repeated, followed by a MGWD subsystem restart

Example:

Thu May 01 17:46:45 [node-01: mgwd: kern.vm.mmap.return:notice]: mmap(2) by mgwd (pid 3160) for size 6656000 failed: VMEM limit exceeded, limit 4294967296, error 12.

Thu May 01 17:50:01 [node-01: mgwd: kern.vm.mmap.return:notice]: mmap(2) by mgwd (pid 3160) for size 6656000 failed: VMEM limit exceeded, limit 4294967296, error 12.

Thu May 01 17:52:45 [node-01: mgwd: kern.vm.mmap.return:notice]: mmap(2) by mgwd (pid 3160) for size 6656000 failed: VMEM limit exceeded, limit 4294967296, error 12.

Thu May 01 17:53:18 [node-01: mgwd: ucore.panicString:error]: 'mgwd: Received SIGSEGV (Signal xx) at RIP 0x81a7fa82a accessing address 0x1ffce6e8 (pid 3160, uid 0, timestamp 1746089598)'

Thu May 01 17:53:58 [node-01: spmd: spm.mgwd.process.exit:EMERGENCY]: Management Gateway (mgwd) subsystem with ID 3160 exited as a result of signal normal exit (0). The subsystem will attempt to restart.