{"id":1252,"date":"2018-05-23T19:29:22","date_gmt":"2018-05-23T19:29:22","guid":{"rendered":"http:\/\/www.penguino.co.uk\/?p=1252"},"modified":"2018-05-23T19:33:09","modified_gmt":"2018-05-23T19:33:09","slug":"nfsidmap-segfault","status":"publish","type":"post","link":"http:\/\/www.penguino.co.uk\/computing\/nfsidmap-segfault","title":{"rendered":"nfsidmap segfault"},"content":{"rendered":"\n\n\r\n\n\n\n
Recently I have seen an Ubuntu 16.04 server producing segfaults errors in kern.log and dmesg. It was traced to a process calls nfsidmap<\/p>\n
May 22 03:36:56 penguinoserver1 kernel: [241227.277964] nfsidmap[28966]: segfault at 0 ip 00007f2471ff6ad3 sp 00007ffc480fa048 error 4 in libc-2.23.so[7f2471f6d000+1c0000]\r\nMay 22 03:36:56 penguinoserver1 kernel: [241228.117058] nfsidmap[28970]: segfault at 0 ip 00007f044aa31ad3 sp 00007fff80f0a998 error 4 in libc-2.23.so[7f044a9a8000+1c0000]\r\nMay 22 03:41:59 penguinoserver1 kernel: [241530.495847] nfsidmap[29502]: segfault at 0 ip 00007f43660a7ad3 sp 00007fff98ec35a8 error 4 in libc-2.23.so[7f436601e000+1c0000]\r\nMay 22 03:41:59 penguinoserver1 kernel: [241530.686111] nfsidmap[29504]: segfault at 0 ip 00007f16e26f1ad3 sp 00007fff1f439398 error 4 in libc-2.23.so[7f16e2668000+1c0000]<\/pre>\nLater I found that in \/var\/log\/apport.log the offending command line appears.<\/p>\n
ERROR: apport (pid 49878) Thu May 3 03:10:44 2018: executable: \/usr\/sbin\/nfsidmap (command line \"nfsidmap -t 600 480996374 uid:\")<\/pre>\nRunning the command directly does replicate the problem<\/p>\n
root@penguinoserver1:\/etc\/request-key.d# nfsidmap -t 600 692838889 uid:\r\nSegmentation fault (core dumped)<\/pre>\nI read that nfsidmap above is triggered by the file id_resolver.conf. But I do not know exactly how and why.<\/p>\n
root@penguinoserver1:\/etc\/request-key.d# cat id_resolver.conf\r\ncreate id_resolver * * \/usr\/sbin\/nfsidmap -t 600 %k %d<\/pre>\nMore reading from the website<\/p>\n