Logging Creation and Deletion

[David Hoskinson]

I am having a bit of trouble understanding creation and deletion of logs.  Creation is max
number of logs = 10, fie size 100 MB, and create a new log every day.  This is the default
I believe as I haven't changed it.  My question is does one of these parameters over
ride the other?  For example we want to keep 24 weeks of logs, and for example create a
log everyday.  And logs are quite small for us, so would the 100 mb parameter take
precedence or the one day setting?

Same with deletion... would like the when drive has less then 5 mb and delete files over
24 weeks old but don't care about the 500 mb total size.

I see some fields can be set with -1 to inactivate them but some can't...

If anyone can explain this a little clearer I am sure its just something I am missing

David Hoskinson | DATATRAK International
Systems Engineer
Mayfield Heights, Ohio, USA
+1.440.443.0082 x 124 (p) | +1.440.391.7753 (m)
[e-mail]<mailto:[e-mail]> |
www.datatrak.net<http://www.datatrak.net/>

[Arpit Tolani]

Hie

2012/1/17 David Hoskinson <david.hoskinson(a)datatrak.net&gt;

>  I am having a bit of trouble understanding creation and deletion of
> logs.
>  Creation is max number of logs = 10, fie size 100 MB, and create a new log
>  every day.  This is the default I believe as I haven’t changed it.  My
>  question is does one of these parameters over ride the other?  For example
>  we want to keep 24 weeks of logs, and for example create a log everyday.
>  And logs are quite small for us, so would the 100 mb parameter take
>  precedence or the one day setting?   ****
>
>  ** **
>
>  Same with deletion… would like the when drive has less then 5 mb and
>  delete files over 24 weeks old but don’t care about the 500 mb total size.
>  ****
>
>  ** **
>
>  I see some fields can be set with -1 to inactivate them but some can’t…***
>  *
>
>  ** **
>
>  If anyone can explain this a little clearer I am sure its just something I
>  am missing****
>
>
>  
Of course per day time will take preference over the size limit of 100 MB &
vice versa.

> From what I understood you want to have log files for 24 weeks (168
> days) 
One log file per day.

nsslapd-accesslog-maxlogsperdir: 168
nsslapd-accesslog-mode: 600
nsslapd-accesslog-maxlogsize: 1   <-- We have set 1 so that it will ignore
the size of file and rotate only after a day regardless of the size of a
log file.
nsslapd-accesslog-logrotationtime: 1 <-- Since we want to rotate daily
nsslapd-accesslog-logrotationtimeunit: day

Same will be with errorlogs & audit logs.

Regarding Logs delete. (whichever come first)

nsslapd-accesslog-logmaxdiskspace: 500 <--- Maximum disk space taken by
access logs, If exceeds Oldest file will be deleted
nsslapd-accesslog-logminfreediskspace: 5 <--------- minimum free disk in
MB, If goes below this Oldest file will be deleted

Regards
Arpit Tolani

openldap ldif to 389.

[Dan H. Eicher]

   I'm trying to import an ldif that was created from openldap and 
importing it in to 389-ds by using import database from the 389-console.

   When I look at my rejects file I see the following error (multiple 
times):
      The error was sent by the server: "Object Class Violation 
Attribute entryuuid not allowed".

   I did find this nugget on bugzilla: 
https://bugzilla.redhat.com/show_bug.cgi?id=220222
       (No support for RFC 4530 entryUUID attribute - from 01/04/2012)

   -and- This bit of wisdom on syncing between openldap and 389:
                
http://directory.fedoraproject.org/wiki/Howto:OpenldapIntegration

   But, I didn't find any advice for importing an ldif that uses this 
attribute.
   Any advice from a veteran would be appreciated.

Dan

openldap ldif to 389.

[Terry Soucy]

The attribute entryUUID is server assigned, and is the same as the nsUniqueId attribute in
389.  You should remove that attribute from the ldif before importing.

Terry


--
Terry Soucy, Systems Analyst             Information Technology Services
University of New Brunswick, Fredericton Campus  http://www.unbf.ca/its
Voice: 506.447.3018     Fax: [phone]    E-mail: terry.soucy(a)unb.ca
**    ITS is a scent-reduced workplace - www.unbf.ca/its/policies    **




On 2012-02-02, at 4:57 PM, Dan H. Eicher wrote:

>  
>   I'm trying to import an ldif that was created from openldap and importing it in to
> 389-ds by using import database from the 389-console.
>  
>   When I look at my rejects file I see the following error (multiple times):
>      The error was sent by the server: "Object Class Violation Attribute entryuuid
> not allowed".
>  
>   I did find this nugget on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=220222
>       (No support for RFC 4530 entryUUID attribute - from 01/04/2012)
>  
>   -and- This bit of wisdom on syncing between openldap and 389:
>                http://directory.fedoraproject.org/wiki/Howto:OpenldapIntegration
>  
>   But, I didn't find any advice for importing an ldif that uses this attribute.
>   Any advice from a veteran would be appreciated.
>  
>  Dan
>  
>  --
>  389 users mailing list
>  389-users(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/389-users