Unfortunately, not all the log entries are nicely categorized -- "Failed to resolve" is normal on startup, as are the other logged entries.
Try looking for "assert", "exiting" (use "grep -i" so it's case-insensitive) to see what else you find. Sometimes, it's a matter of commenting out (you can use the C style /* */) portions of the configuration until it comes up, and adding in elements bit by bit to isolate where the error is. FYI, the upcoming version will handle configuration file issues in a much friendlier manner. Justin On Jan 17, 2008 1:40 PM, Shane McKinley <[EMAIL PROTECTED]> wrote: > This is what I have for this command -- 'cat /var/log/messages | grep > ERROR' > > ======================================================================== > ========================================= > > Jan 17 16:35:56 localhost xorp_rtrmgr: [ 2008/01/17 16:35:55 ERROR > xorp_rtrmgr:5628 FINDER +1079 > /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxipc/find > er.cc announce_new_instance ] Failed to resolve > finder://[EMAIL PROTECTED]/finder > _event_observer/0.1/xrl_target_birth?target_class:txt=fea&target_instanc > e:[EMAIL PROTECTED] > Jan 17 16:36:05 localhost xorp_rtrmgr: [ 2008/01/17 16:36:05 ERROR > xorp_rtrmgr:5628 FINDER +85 > /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxipc/find > er_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed out > > ======================================================================== > ========================================= > > And for this command 'cat /var/log/messages | grep WARNING' > > ======================================================================== > ========================================= > > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: eth0 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: eth0/eth0 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: > eth0.504 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: > eth0.504/eth0.504 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth0.504/eth0.504/69.40.11.198 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:10 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth0.504/eth0.504/69.40.11.210 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: > eth0.514 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: > eth0.514/eth0.514 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth0.514/eth0.514/66.128.134.130 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: eth1 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: eth1/eth1 > Jan 17 16:35:11 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/10.0.0.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.69.63.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.80.121.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.85.140.33 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.85.143.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/63.128.143.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/66.128.128.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/66.128.130.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/66.128.135.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > eth1/eth1/66.128.139.1 > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for interface not in libfeaclient tree: lo > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for vif not in libfeaclient tree: lo/lo > Jan 17 16:35:12 localhost xorp_fea: [ 2008/01/17 16:35:11 WARNING > xorp_fea FEA ] Got update for address no in libfeaclient tree: > lo/lo/63.69.63.6 > Jan 17 16:35:20 localhost xorp_rib: [ 2008/01/17 16:35:19 WARNING > xorp_rib LIBFEACLIENT ] NetlinkHead::io_event(), iface is empty > Jan 17 16:35:20 localhost xorp_rib: [ 2008/01/17 16:35:19 WARNING > xorp_rib LIBFEACLIENT ] NetlinkHead::io_event(), iface is empty > Jan 17 16:35:40 localhost xorp_static_routes: [ 2008/01/17 16:35:39 > WARNING xorp_static_routes LIBFEACLIENT ] NetlinkHead::io_event(), iface > is empty > Jan 17 16:35:40 localhost xorp_static_routes: [ 2008/01/17 16:35:39 > WARNING xorp_static_routes LIBFEACLIENT ] NetlinkHead::io_event(), iface > is empty > Jan 17 16:35:49 localhost xorp_bgp: [ 2008/01/17 16:35:48 WARNING > xorp_bgp:6466 LIBFEACLIENT +193 > /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libfeaclient > /netlink_head.cc io_event ] NetlinkHead::io_event(), iface is empty > Jan 17 16:35:49 localhost xorp_bgp: [ 2008/01/17 16:35:49 WARNING > xorp_bgp:6466 LIBFEACLIENT +193 > /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libfeaclient > /netlink_head.cc io_event ] NetlinkHead::io_event(), iface is empty > Jan 17 16:35:55 localhost snmpd: [ 2008/01/17 16:35:54 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 29.000004 > seconds > Jan 17 16:35:55 localhost snmpd: [ 2008/01/17 16:35:54 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 28.000006 > seconds > Jan 17 16:35:55 localhost snmpd: [ 2008/01/17 16:35:54 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 27.000008 > seconds > Jan 17 16:35:55 localhost snmpd: [ 2008/01/17 16:35:54 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 26.000010 > seconds > Jan 17 16:35:55 localhost snmpd: [ 2008/01/17 16:35:55 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 25.000012 > seconds > Jan 17 16:35:55 localhost snmpd: [ 2008/01/17 16:35:55 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 24.000014 > seconds > Jan 17 16:35:55 localhost snmpd: [ 2008/01/17 16:35:55 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 23.000016 > seconds > Jan 17 16:35:56 localhost snmpd: [ 2008/01/17 16:35:55 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 22.000018 > seconds > Jan 17 16:35:56 localhost snmpd: [ 2008/01/17 16:35:55 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 22.000001 > seconds > Jan 17 16:35:56 localhost snmpd: [ 2008/01/17 16:35:55 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 21.000003 > seconds > Jan 17 16:35:56 localhost snmpd: [ 2008/01/17 16:35:55 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 20.000005 > seconds > Jan 17 16:35:56 localhost snmpd: [ 2008/01/17 16:35:55 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 19.000007 > seconds > Jan 17 16:35:56 localhost snmpd: [ 2008/01/17 16:35:55 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 18.000009 > seconds > Jan 17 16:35:56 localhost snmpd: [ 2008/01/17 16:35:56 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 17.000011 > seconds > Jan 17 16:35:56 localhost snmpd: [ 2008/01/17 16:35:56 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 16.000013 > seconds > Jan 17 16:35:56 localhost snmpd: [ 2008/01/17 16:35:56 WARNING snmpd > LIBXORP ] Timer Expiry *much* later than scheduled: behind by 15.000015 > seconds > > ======================================================================== > ========================================= > > Does this make sense to anyone? I am going to try the verbose logging > per Justin's suggestion. > > Shane McKinley > Habersham EMC > > -----Original Message----- > From: Justin Fletcher [mailto:[EMAIL PROTECTED] > > Sent: Thursday, January 17, 2008 4:35 PM > To: Shane McKinley > Cc: vyatta-users@mailman.vyatta.com > Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... > > You can enable verbose debugging by changing > > VERBOSERTRMGR= > > on line 51 of /opt/vyatta/sbin/rtrmgr.init > > to > > VERBOSERTRMGR=-v > > As a caution, this will generate a LOT of output in your log files!! > > Justin > > On Jan 17, 2008 1:31 PM, Shane McKinley <[EMAIL PROTECTED]> wrote: > > I did. I am trying to comment out my static routes to see if that will > > > help. > > > > Any other suggestions? > > > > > > Shane McKinley > > Habersham EMC > > > > -----Original Message----- > > > > From: Michael Larson [mailto:[EMAIL PROTECTED] > > Sent: Thursday, January 17, 2008 4:27 PM > > To: Shane McKinley > > Cc: vyatta-users@mailman.vyatta.com > > Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... > > > > Hi Shane, > > > > Did you restart the syslog daemon after you modified the syslog.conf > > file? > > > > /etc/init.d/sysklogd restart > > > > Mike > > > > ----- Original Message ----- > > From: "Shane McKinley" <[EMAIL PROTECTED]> > > To: vyatta-users@mailman.vyatta.com > > Sent: Thursday, January 17, 2008 1:23:06 PM (GMT-0800) > > America/Los_Angeles > > Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... > > > > I have changed /etc/syslog.conf to *.* and restarted the vyatta-ofr. I > > > don't see anything that just pops out at me in /var/log/messages since > > > the restart. I did truncate the file before attempting to restart the > > vyatta-ofr service. > > > > Any way to pinpoint which line in my config is causing the issue? > > > > (SIDE NOTE: (No offense meant) Why should changing interface notations > > > and static routes cause anything to crash?) > > > > Shane McKinley > > Habersham EMC > > > > -----Original Message----- > > From: Justin Fletcher [mailto:[EMAIL PROTECTED] > > Sent: Thursday, January 17, 2008 3:58 PM > > To: Marat Nepomnyashy > > Cc: Shane McKinley; vyatta-users@mailman.vyatta.com > > Subject: Re: [Vyatta-users] Waiting for xorp_rtrmgr... > > > > You'll also want to edit /etc/syslog.conf and change *.warning to *.* > > to record all log messages; otherwise, lower-level messages will be > > discared > > > > You can check startup by hand by running "/etc/init.d/vyatta-rtrmgr > > start" which will save you the physical reboot -- > > > > Justin > > > > On Jan 17, 2008 12:54 PM, Marat Nepomnyashy <[EMAIL PROTECTED]> wrote: > > > Hi Shane, > > > > > > Most likely the rtrmgr did not start. The best log file to check > > > when > > > > > that happens is '/var/log/messages'. > > > > > > Which Vyatta version are you using? > > > > > > Thanks, > > > Marat > > > > > > > > > ----- Original Message ----- > > > From: "Shane McKinley" <[EMAIL PROTECTED]> > > > To: <vyatta-users@mailman.vyatta.com> > > > Sent: Thursday, January 17, 2008 12:51 PM > > > Subject: [Vyatta-users] Waiting for xorp_rtrmgr... > > > > > > > > > > After entering some static routes and changing some subnetting > > > > around I rebooted. Now the rtrmgr won't start -- the commit took > > > > fine before I rebooted. > > > > > > > > Is there a way I can pull the proper error messages to > > > > troubleshoot this problem? What log files would be best to look > at? > > > > > > > > Any more ideas on why this would happen? I really am dedicated to > > > > getting this router into production, but the odds seem against me > > > > this round. > > > > > > > > Thanks, > > > > > > > > Shane McKinley > > > > Habersham EMC > > > > Tel: 706-839-4130 > > > > Cel: 706-968-3186 > > > > _______________________________________________ > > > > Vyatta-users mailing list > > > > Vyatta-users@mailman.vyatta.com > > > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > > > > > > > > _______________________________________________ > > > Vyatta-users mailing list > > > Vyatta-users@mailman.vyatta.com > > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > > > _______________________________________________ > > Vyatta-users mailing list > > Vyatta-users@mailman.vyatta.com > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > > _______________________________________________ > > Vyatta-users mailing list > > Vyatta-users@mailman.vyatta.com > > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > > > _______________________________________________ > Vyatta-users mailing list > Vyatta-users@mailman.vyatta.com > http://mailman.vyatta.com/mailman/listinfo/vyatta-users > _______________________________________________ Vyatta-users mailing list Vyatta-users@mailman.vyatta.com http://mailman.vyatta.com/mailman/listinfo/vyatta-users
