Re: n4u.server.log-file-size...
a...@novell.com
Hash: SHA1
I'm not sure I understand what you're after. In your quote from the
documentation it states that this parameter does not apply to ndsd.log,
but then you show the size of ndsd.log and ask if anybody can get the
setting to be enforced, which is contrary to the docs. What am I missing?
It may be worth adding a command to your post_ndsd_stop script (if patched
on 8.8.5.1 or later it will be in /opt/novell/eDirectory/sbin instead of
/etc/init.d) that renames and compresses the ndsd.log file to help manage
this. logrotate works well if a service can be quickly bounced (like
syslog) but eDir isn't really that way as much.
Good luck.
On 08/18/2010 10:36 AM, djbrightman wrote:
>
> I was checking log levels, file sizes. etc. from the doc:
> 'Novell Documentation'
> (http://www.novell.com/documentation/edir88/edir88new/?page=/documentation/edir88/edir88new/data/bvws4fo.html)
>
> In there it states:
>>>
> - *Specifying the Log File Size*
>
> To specify the size of the log file, use the n4u.server.log-file-size
> parameter in the nds.conf file. The maximum file limit can be 2 GB and
> the default file size is 1 MB. However, you can set the file size to
> below 1 MB also.
>
> This setting is not applicable to the ndsd.log file.
>
> If the log file size reaches the specified limit, then logger
> overwrites the log file from the start.-
> <<
>
> So, on our servers the defaults seem about right:
>>>
> # ndsconfig get |grep log
> n4u.server.log-levels=LogFatal
> n4u.server.log-file=/var/opt/novell/eDirectory/log/ndsd.log
> n4u.server.log-file-size=1048576
> <<
>
> However, the log files are not limited, and show entries from their
> start of life, despite numerous restarts i.e. it doesn't do anything on
> restart...
> e.g.
>>>
> -rw------- 1 root root 41711508 Aug 18 17:11
> /var/opt/novell/eDirectory/log/ndsd.log
> <<
>
> So, is there anything else required to enforce this
> 'n4u.server.log-file-size' setting?
> Anyone else seeing it working?
>
> Anyone doing anything with logrotate?
>
> Thanks
>
> David
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMe8zpAAoJEF+XTK08PnB5mC4P/1rUrEE8KMX4F1xzTYBK0nn+
W43GYp06Urd2gOXN09V5YXZPTAiZUzJMBh6IDXkmf59AtLUBhqsgPqh+qWN5X2Gu
CAsjRp7Hru17e0g55RnjblsM8aGCDcCY9OrLeQWfXQCwfvxHHW8M8mj5exa5r2KR
CgGn502T0myP/vMjTbhzuimGwRo+SVs1xR025lVSr6n6lCH5oIHJ9BlpIIQwuxzp
JoZ3V7s8RP33d/YWvQkhnLkR8J1uNDyHqkh3rTowhknX5GYhcXP1qgQYN+f1cP+t
sM+Qup0Si8KhAljZfWeA1uJ8Y0/8fwYO6jpp9FJcd+xb7T1BHESFp1zYNTCq4dqD
A9u8SRPuoiekMUlhtq/gP1n2JkYAbfqqxxbKPJ54X0PWVWeju8s4CltqzqAz8yiO
0Pp+5Ere5gDlkjUmjSG8h6a9gAcCMqvt0Fd6PR99wnN92727Vmdym3xDHLxPhcMn
MUmvRn1LxD4IjU4WnAbFH4dRpeRFpmvWIABFlO7i4h7bxct280UviyDpXq/DxFa8
rXqIkReL1cg7WRmAC3fugT+enARJc78QdGFbEUaITdZ94O6oj9hFj/Zdc6bH/aoh
0YvFeQEzeTP6OgJRviQcZFjcycSi6rxz/88u3/EeyM6ufljZV0177nVxz+q+fTI6
h+hGbZF0mBKKxrCGy7qq
=6dcF
-----END PGP SIGNATURE-----
a...@novell.com
Hash: SHA1
I mentioned the post_ndsd_stop but the pre_ndsd_start is equally
applicable, and maybe more-so since it should still be run after a crash
and could clean up the log files. I appreciate you submitting the comment
on the documentation site; that is probably the quickest way possible (for
you or me) to get something clearer on there. I'll see if I can find out
which files are affected and try to ensure that the docs mention those
explicitly (as well as update this thread).
Good luck.
On 08/31/2010 03:06 AM, djbrightman wrote:
>
> Hi Aaron
>
> I guess I should read a bit closer, I honestly didn't spot that...!
> However, what is the point of this parameter then?!? It is clearly the
> ndsd.log that needs managing, just saying 'This setting is not
> applicable to the ndsd.log file.' is ridiculous (and I shall add a
> comment via the doc page)
>
> If you have MAJOR issues with ncp/ndsd, as we do at the moment, and
> need to rack up logging to max, then we need a proper way to manage the
> log file
>
> post_ndsd script is of no use to us (and perhaps other people using
> debug mode to troubleshoot issues), as the problem we have is that the
> ndsd process is just dying i.e. process 'ndsd dead'... Apparently this
> is an ncp issue, and a bug has been raised, etc. etc.
>
> This functionality really does need thinking about and including - the
> settings are currently misleading and of no use
>
> Cheers
>
> David
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJMfRfUAAoJEF+XTK08PnB5D9IQAK1MGYR55HIxoNg1uU25p5hN
LF/mIrkWG4TSSxHnsOQ09xzfC8DqAwmUnE1kkNFsRcPmk9D5KqJ4aWeUp1pHuXix
LwDjMG6TK224uLjQRW/ZrXjRy5U2GyigeCvCJSGC/U4lVMX7B72wBpBaOqbAAUAj
8nLAElYJsTtsCfI9s3GR1vi7gISDCH0VgebbPmHXuOfc7Bp2fC/Q2YiDtxzloBrl
0XlCQ97J9vv/yO7F3Py3TY22iI1BfWQ2H1XWQmhpGSVNZa0RldF/SHXzKwt0wd1D
FJdMsXgwd/+bag/X5cla/GBrV5VwX1yS8cySltSAAPXMqQsh/GomPNVS19qndpEM
1xCNJXH1+hjeTHhU3TS7oG8rQu5XWWGTfYxNGFUavVBiVxVHkd4wjeznald0zw06
Mok6sZZHW6ZBPF8PAyNwcZNY2zr5J540Jdbr74PaOIj0QKVL0AgQMP13kTOgHOu8
EY2xhF2EJRwNdifagDl1aLpEpAni2ldEg+JvjK28TXGS34B1sjDYInATkRz/CZQZ
O01Yt2l4hbzsHEYx6dR1qhxLK+DTAI7UO07dCF9ZUT7jfRgRjdBmfUEFQFJHxGKP
ZYZCo999f11ERNh2ZSKMKMvG+nnqq0kq4tYgeKiY3HQmQOQ17kDriCpXLZyq8+6q
Q424qUcvb6rDFMYziOf7
=v61y
-----END PGP SIGNATURE-----