Summary
the nnmtrapreceiver fails / dumps core with signal 11 shortly after start
/var/log/messages:
...
2021-01-27T13:49:55.456031+01:00 ladmnpa003 kernel: [ 982.154795] nnmtrapreceiver[8303]: segfault at 0 ip 00007f17b3ad11eb sp 00007ffdb329b150 error 4 in libc-2.22.so[7f17b3a63000+19b000]
...
Error
the nnmtrapreceiver fails / dumps core with signal 11 shortly after start
/var/log/messages:
...
2021-01-27T13:49:55.456031+01:00 ladmnpa003 kernel: [ 982.154795] nnmtrapreceiver[8303]: segfault at 0 ip 00007f17b3ad11eb sp 00007ffdb329b150 error 4 in libc-2.22.so[7f17b3a63000+19b000]
...
Cause
We noticed that in the output of the systemctl status command the number of tasks being run by nnmtrapreceiver is close to or even at the limit specified ie 512:
only for linux
only for linux
Fix
We noticed that in the output of the systemctl status command the number of tasks being run by nnmtrapreceiver is close to or even at the limit specified ie 512:
This may well be the cause of the problem. On my system I don’t see this line in the output. So, what we propose is to increase this value – or basically unset it. This can be done in a couple of ways:
1) Edit the file /usr/lib/systemd/system/nettrap.service
Under the [Service] section add the line: TaskMax=infinity
Start the service
2) Edit the file /etc/systemd/system.conf
Enter the same line above in the [Service] section
The choice is the customer’s as to whether they want this setting for all processes or just specified ones.
This may well be the cause of the problem. On my system I don’t see this line in the output. So, what we propose is to increase this value – or basically unset it. This can be done in a couple of ways:
1) Edit the file /usr/lib/systemd/system/nettrap.service
Under the [Service] section add the line: TaskMax=infinity
Start the service
2) Edit the file /etc/systemd/system.conf
Enter the same line above in the [Service] section
The choice is the customer’s as to whether they want this setting for all processes or just specified ones.