QUAGGA OSPF not working after upgrade 2.3.1



  • I'm having difficulties with getting quagga going again after the upgrade. Again the persistence of settings between removal and installation of packages appears to make all the bad things stick aswell.

    I wish there was a way of removng EVERYTHING associated with a package.

    Here is the log showing the problem…

    21 08:39:13 zebra 44808 Could not lock pid_file /var/run/quagga/zebra.pid, exiting
    May 21 08:39:13 zebra 45061 Zebra 1.0.20160315 starting: vty@2601
    May 21 08:39:13 ospfd 45284 OSPFd 1.0.20160315 starting: vty@2604
    May 21 08:39:13 ospfd 45565 Could not lock pid_file /var/run/quagga/ospfd.pid, exiting
    May 21 08:39:13 zebra 45061 client 13 says hello and bids fair to announce only ospf routes

    No neighbours are ever shown in status.

    Any help appreciated.


  • Rebel Alliance Developer Netgate

    I upgraded three systems to 2.3.1 that had quagga (four really, one was an HA cluster) and all were fine.

    Check to see if it's already running:

    : ps uxawww | grep quagga
    

    If you see it running, kill it and also

    rm /var/run/quagga/*
    

    And then restart from the GUI. If it's not running, try just the rm.


Log in to reply