IBM Support

Guardium ktap.log shows many lines of "kern:notice unix: nfs_server: bad sendreply"

Troubleshooting


Problem

Guardium ktap.log shows many lines of "kern:notice unix: nfs_server: bad sendreply"

Symptom

continuous error line is logged into the /var/log/ktap.log file :-

kern:notice unix: nfs_server: bad sendreply

Cause

When STAP is installed, Guardium enables logging of local and kernel errors into the KTAP.log
This means that local and kernel errors in general will get written to ktap.log (not just the Guardium STAP errors )

Environment

Unix STAP

Resolving The Problem

The errors are being generated by your NFS nfs_server. You should address these issues with your Network team as soon as possible

For example - the following is based on the problem seen on AIX :-

The error that gets logged is as detailed in this example
You and your network team should follow the troubleshooting

This developerworks article may also be useful mentioning the commands netstat, netpmon, entstat, and nmon that can be used to check and set settings


Temporary Workaround

As a temporary measure - If the problem is causing space to fill rapidly then the ktap.log log file can be set to rotate and have a maximum size

The following is a procedure you could perform on an AIX system specifically - similar could be done for any Unix system

as user root :-

    1) edit /etc/syslog.conf
      comment out the current log line (eg with the hash # at start of line) and set a rotation and size of log files for example

      #local0.err,kern.debug /var/log/ktap.log
      local0.err,kern.debug /var/log/ktap.log rotate size 50m files 3

    2) if the /var/log/ktap.log has previously been removed to stop the space filling - then you may need to touch the file - for example
      touch /var/log/ktap.log

    3) refresh and stop start the syslogd
      refresh -s syslogd
      stopsrc -s syslogd
      startsrc -s syslogd

    At this point the ktap.log will make 3 log files that rotate and grow to a maximum of 50MB each for example

    4) check the file(s) / sizes
      ls -ltr /var/log/ktap.log*
      -rw-r--r-- 1 root system 2343243 May 18 16:20 /var/log/ktap.log

      over time you may also see other files -
        /var/log/ktap.log.0  
        /var/log/ktap.log.1  

[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"10.0;10.0.1;9.1;9.5","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg21983688