bug report

Thanks for the quick reply, Marten.  Everything seems to work fine now.

:-) 
-Andy 

>
>Andy,
>
>first and very quick guess. This problem does not seem to appear in
>the version running at the NCC. There are some routes in there with
>the withdrawn attribute that have been cleaned many many times. So
>here's my guess. Check the definition you have for the route objects
>in your config, specifically the ATSQ line. From what I see below, you
>have the wd attribute in there twice, once after the advisory
>attribute and once after the change attribute....
>
>-Marten
>
>
>Andrew Adams <ala at merit.edu> writes
> * 
> * Ok, here's a fun bug for you all.
> * 
> * 1) Create a new database (mine was called PALA) and run netdbm on it.
> * 
> * 2) Add a single maintainer object. (Below is the one I added).
> * 
> *    mntner:      MAINT-AS568
> *    descr:       People authorized to make changes for AS568
> *    admin-c:     Not Available from PRDB
> *    upd-to:      ala at merit.edu
> *    auth:        MAIL-FROM ala at merit.edu
> *    auth:        MAIL-FROM ala at home.merit.edu
> *    auth:        MAIL-FROM ala at shockwave.merit.edu
> *    auth:        MAIL-FROM ala at twain.merit.edu
> *    auth:        MAIL-FROM ala at toad.merit.edu
> *    remarks:     DDN NIC Staff
> *    remarks:     PRE-APPROVAL: AS 568 pre-approves any requests involving th
e
> * ir AS.
> *    changed:     DB-admin at ra.net 950404
> *    source:      PALA
> * 
> * 
> * 3) Add a single route object which ref's the maintainer you just added.
> *    (Below is the one I added).
> * 
> *    route:       137.8.0.0/14
> *    descr:       DISA, DSAC
> *    descr:       P. O. Box 1605
> *    descr:       Columbus
> *    descr:       OH 43216-5002, USA
> *    origin:      AS568
> *    withdrawn:   950404
> *    advisory:    AS690 1:568(144) 2:568(145)
> *    mnt-by:      MAINT-AS568
> *    changed:     ala at merit.edu 950404
> *    source:      PALA
> * 
> * 4) Now read the object back via whois.
> * 
> *    shockwave.merit.edu: whois -h radb2.ra.net '-s PALA 137.8.0.0/14'
> *    route:       137.8.0.0/14
> *    descr:       DISA, DSAC
>
> *    descr:       P. O. Box 1605
> *    descr:       Columbus
> *    descr:       OH 43216-5002, USA
> *    origin:      AS568
> *    withdrawn:   950404
> *    withdrawn:   950404
> *    advisory:    AS690 1:568(144) 2:568(145)
> *    mnt-by:      MAINT-AS568
> *    changed:     ala at merit.edu 950404
> *    withdrawn:   950404
> *    withdrawn:   950404
> *    source:      PALA
> * 
> *    Notice that the single, original withdrawn attribute has turned into
> *    four withdrawn attributes.
> * 
> * 5) Now run cleandb on the database. (cleandb -c pala.db)
> * 
> * 6) Now read the object back via whois.
> * 
> *    shockwave.merit.edu: !wh
> *    whois -h radb2.ra.net '-s PALA 137.8.0.0/14'
> *    route:       137.8.0.0/14
> *    descr:       DISA, DSAC
> *    descr:       P. O. Box 1605
> *    descr:       Columbus
> *    descr:       OH 43216-5002, USA
> *    origin:      AS568
> *    withdrawn:   950404
> *    withdrawn:   950404
> *    withdrawn:   950404
> *    withdrawn:   950404
> *    advisory:    AS690 1:568(144) 2:568(145)
> *    mnt-by:      MAINT-AS568
> *    changed:     ala at merit.edu 950404
> *    withdrawn:   950404
> *    withdrawn:   950404
> *    withdrawn:   950404
> *    withdrawn:   950404
> *    source:      PALA
> * 
> *    Notice that the four withdrawn attributes has turned into 8!
> * 
> * 7) And every time clean db runs, the number of withdrawn attributes
> *    doubles!
> * 
> * 8) Another data point - if the original route object contains an error, say
> *    the mask doesn't match the prefix, the error message that is returned
> *    contains the original object with two withdrawn attributes, instead of t
h
> * e
> *    original, single one. 
> * 
> *    We have a route object in the radb number of withdrawn attributes is 
> *    starting to get really long! (cleandb runs every nite). :-)
> *    
> * -Andy



-------- Logged at  Wed Apr 5 21:20:01 MET DST 1995  ---------