Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

IRRd-Discuss


Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: email update with 2.1.4

  • From: David Miller
  • Date: Tue Apr 16 13:05:42 2002

On Tue, 16 Apr 2002, Christerfer R. Frazier wrote:

> David,
> 	It seems you are referencing 2 different irrd.conf files in
> this message. Initially in your email alias the location is given as
> /usr/local/etc/irrd.conf.

Good eyes!  Sorry I let that slip in, but it's not the problem:

su-2.05# ls -l /etc/irrd.conf 
lrwxr-x---  1 root  wheel  24 Apr  8 22:43 /etc/irrd.conf ->
/usr/local/etc/irrd.conf

I seemed to be having trouble convincing the utilities to look in
/usr/local/etc, so I just symlinked it.

Any other guesses?  Is there anything wrong in the alias itself?

Thanks,

--- David



> 
> > auto-dbm:       "|/usr/local/sbin/irr_rpsl_submit -v -f
> > /usr/local/etc/irrd.conf -h whois.mainexp.net"
> 
> while later your message you reference the location as
> /etc/irrd.conf. 
> 
> > su-2.05# cat /etc/irrd.conf
> 
> Im wondering if your config in /usr/local/etc/irrd.conf contains 
> the statement 
> 
> > irr_database meep authoritative
> 
> If it does not you can change your alias to use /etc/irrd.conf or
> modify your /usr/local/etc/irrd.conf by adding the statement above.
>  
> -chris
> 
> On Mon, Apr 15, 2002 at 11:39:43PM -0400, David Miller wrote:
> > I'm stumped.
> > 
> > I'm running 2.1.4 on FreeBSD 4.5-stable.
> > 
> > irr_rpsl_submit -D -v < update_template updates the database fine, using
> > an override password.
> > 
> > The same change submitted via email complains about the database being
> > unknown database:
> > 
> > ------------------------------------------------------------
> > 
> > 
> > UPDATE FAILED: [aut-num] AS65500
> > aut-num:            AS65500
> > as-name:            MEEP
> > [snip]
> > mnt-by:             MAINT-AS65500
> > changed:            dmiller@mainexp.net 20011128
> > source:<?>             MEEP
> > #ERROR: 19: source: Unknown database
> > 
> > 
> > ------------------------------------------------------------
> > 
> > I *thought* I had this working before 2.1.4.
> > 
> > The alias is setup as:
> > 
> > auto-dbm:       "|/usr/local/sbin/irr_rpsl_submit -v -f
> > /usr/local/etc/irrd.conf -h whois.mainexp.net"
> > 
> > The maillog shows it came in:
> > 
> > Apr 15 23:35:57 riley postfix/local[25016]: 52DAD18D4D5: 
> > to=<auto-dbm@whois.mainexp.net>,
> > relay=local, delay=0, status=sent ("|/usr/local/sbin/irr_rpsl_submit -v -f
> > /usr/local/etc/irrd.conf -h whois.mainexp.net")
> > 
> > The database looks active:
> > 
> > riley IRRd# show data
> > Listening on port 43 (fd=13)
> > Memory-only indexing
> > RPSL Syntax
> > 
> > Default Database Query Order: meep 
> > 
> >   Database       Size (kb)    Rt Obj    AutNum Obj    Serial #    Last
> > Export #
> > -------------    ---------    ------    ----------    --------
> > -------------
> >  meep                 10.4        10             6           4                 
> >  TOTAL                10.4        10             6
> > 
> > meep  AUTHORITATIVE
> >    Last email/tcp update Never
> >    Last loaded 23:21:44 04/15/2002
> >    Next dbclean in 47:34:02
> > 
> > 
> > Lastly, in case it helps, irrd.conf:
> > 
> > su-2.05# cat /etc/irrd.conf 
> > #
> > #debug all /var/log/irrd.server 0
> > #
> > db_admin dmiller@sparks.net
> > irr_directory /usr/local/db/irrd
> > irr_database meep authoritative
> > #irr_database mainex authoritative
> > #irr_port 43 [ access 0 ]
> > debug server file-name /var/log/server.irrd
> > debug server syslog
> > #debug server syslog
> > debug submission file-name /var/log/submission.irrd
> > line vty
> >   login
> >   password ********
> > 
> > 
> > 
> > /var/log/submission.irrd has nothing in it, like I'm trying to connect to
> > some other server, despite the -h in the command line.  tcpdump doesn't
> > show any packets on either port 43 or 5673 while the attempted update
> > takes place.
> > 
> > 
> > Someone please hit me with a cluebyfour, I'm missing something.
> > 
> > Thanks,
> > 
> > --- David
> > 
> > 
> 



[an error occurred while processing this directive]