[Vyatta-users] Vyatta Crashing -- Have to reboot

2008-02-14 Thread aaron-linuxuser
All,

I have now been using vyatta at two of my locaitons (production) and it has 
been very promising. However, I have run into the problem where I essentially 
cannot do any more 'commits'. This can randomly happen on various things, but 
adding / removing an interface is definitley one of them. The only thing I can 
do to fix the issue is to reboot (init 6) the vyatta box and then add in my new 
configuration once it comes back up. 

I would like some help just troubleshooting / debugging, so I don't have to do 
a full restart to get back to a working condition. I am using VC 3. 

Below is an example log from /var/log/messages


Feb 14 09:10:57 localhost xorp_fea: [ 2008/02/14 09:10:57  ERROR xorp_fea:7163 
FEA +99 
/home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/fea/ifconfig_set.cc 
push_config ] Interface error on eth0.398: interface not recognized

Feb 14 09:10:57 localhost xorp_rtrmgr: [ 2008/02/14 09:10:57  ERROR 
xorp_rtrmgr:3936 LIBXORP +741 
/home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxorp/run_command.cc
 done ] Command /opt/vyatta/sbin/commit_interface.sh: exited with exit status 
255.

Feb 14 09:10:57 localhost xorp_rtrmgr: [ 2008/02/14 09:10:57  ERROR 
xorp_rtrmgr:3936 RTRMGR +1647 
/home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/rtrmgr/task.cc 
execute_done ] Error found on program stderr!
Feb 14 09:10:57 localhost xorp_rtrmgr: [ 2008/02/14 09:10:57  ERROR 
xorp_rtrmgr:3936 RTRMGR +701 
/home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/rtrmgr/master_conf_tree.cc
 commit_pass2_done ] Commit failed:


Any suggestions would be appreciated.

I believe what is 'fixing' my issue is restarting the CLI and possibly router 
program-- perhaps I can do that on the command line without restarting the 
entire machine?

Thanks
-Aaron
___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users


Re: [Vyatta-users] Vyatta Crashing -- Have to reboot

2008-02-14 Thread Justin Fletcher
Unfortunately, you need to restart the system to recover from these
errors in this version.  However, major changes have been made in
Glendale, so you won't see these issues in
the next release.  Alpha 1 is available, so you can give it a try now.

Justin

On Thu, Feb 14, 2008 at 7:27 AM,  [EMAIL PROTECTED] wrote:
 All,

  I have now been using vyatta at two of my locaitons (production) and it has 
 been very promising. However, I have run into the problem where I essentially 
 cannot do any more 'commits'. This can randomly happen on various things, but 
 adding / removing an interface is definitley one of them. The only thing I 
 can do to fix the issue is to reboot (init 6) the vyatta box and then add in 
 my new configuration once it comes back up.

  I would like some help just troubleshooting / debugging, so I don't have to 
 do a full restart to get back to a working condition. I am using VC 3.

  Below is an example log from /var/log/messages


  Feb 14 09:10:57 localhost xorp_fea: [ 2008/02/14 09:10:57  ERROR 
 xorp_fea:7163 FEA +99 
 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/fea/ifconfig_set.cc
  push_config ] Interface error on eth0.398: interface not recognized

  Feb 14 09:10:57 localhost xorp_rtrmgr: [ 2008/02/14 09:10:57  ERROR 
 xorp_rtrmgr:3936 LIBXORP +741 
 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/libxorp/run_command.cc
  done ] Command /opt/vyatta/sbin/commit_interface.sh: exited with exit 
 status 255.

  Feb 14 09:10:57 localhost xorp_rtrmgr: [ 2008/02/14 09:10:57  ERROR 
 xorp_rtrmgr:3936 RTRMGR +1647 
 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/rtrmgr/task.cc 
 execute_done ] Error found on program stderr!
  Feb 14 09:10:57 localhost xorp_rtrmgr: [ 2008/02/14 09:10:57  ERROR 
 xorp_rtrmgr:3936 RTRMGR +701 
 /home/autobuild/builds/master/2007-10-24-0001/ofr/xorp/xorp/rtrmgr/master_conf_tree.cc
  commit_pass2_done ] Commit failed:


  Any suggestions would be appreciated.

  I believe what is 'fixing' my issue is restarting the CLI and possibly 
 router program-- perhaps I can do that on the command line without restarting 
 the entire machine?

  Thanks
  -Aaron
  ___
  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