Hi Stephen, > There's no error messages that match this pattern? > "nslog: logging disabled: write() failed: '%s'" > You're saying you only nslog error message you get is: > "nslog: flush failed: '%s'" > > Are you sure? This doesn't make sense to me...
Hm, what I have is this: # grep nslog: server1.log*| grep -v "'Success'"| \ grep -v "Inappropriate ioctl"| \ grep -v "No such file or dir"| \ grep -v "Resource temporarily unavailable"| \ grep -v closed | grep -v opened Error: nslog: flush failed: 'Broken pipe' Error: nslog: flush failed: 'Broken pipe' Error: nslog: flush failed: 'Is a directory' Error: nslog: flush failed: 'Connection reset by peer' Error: nslog: flush failed: 'Is a directory' Error: nslog: flush failed: 'Connection reset by peer' Error: nslog: flush failed: 'Is a directory' But what I found is a long forgotten proc ns_log {priority args} { } sourced after startup that simply "puts" out extended information that shows up in the server.log. So I looked up this "Is a directory" message, e.g.: [20/Jul/2007:08:10:53][15853.1257366624][dispatch_caching { }] Warning: could'nt cache file ( /www/servers/net/pages/hlr ) because: couldn't open "/www/servers/net/pages/hlr ": illegal operation on a directory [20/Jul/2007:08:10:53][15853.3037600672][-conn:server1:3] Error: nslog: flush failed: 'Is a directory' Bernd. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel