On Thu, Aug 18, 2011 at 4:35 PM, Tom M <[email protected]> wrote: > Didn't seem to work. > 1. with sudo: > tom@tom-laptop:~$ sudo /usr/local/quagga/sbin/zebra > 2011/08/18 15:34:22 ZEBRA: Can't create pid lock file /var/run/zebra.pid > (Permission denied), exiting
zebra is suffering from the permission problem. A proper fix is to tell zebra which user it should run as, and point the PID file to a directory owned by than user, as in: # Supposing you created "quagga" user and group to run the suit: sudo mkdir /var/run/quagga sudo chown quagga:quagga /var/run/quagga sudo /usr/local/quagga/sbin/zebra -u quagga -g quagga -i /var/run/quagga/zebra.pid A dirtier fix is to point the PID file to a friendlier place: sudo /usr/local/quagga/sbin/zebra -i /tmp/zebra.pid > 2. with root: > root@tom-laptop:/home/tom# /usr/local/quagga/sbin/pimd > 2011/08/18 15:35:00 PIM: Boot logging temporarily directed to stdout - begin > 2011/08/18 15:35:00 PIM: Quagga 0.99.17 pimd 0.162 starting > 2011/08/18 15:35:00 PIM: Boot logging temporarily directed to stdout - end > 2011/08/18 15:35:00 PIM: Loading configuration - begin > 2011/08/18 15:35:00 PIM: pim_mroute.c pim_mroute_set: failure: > setsockopt(fd=5,IPPROTO_IP,MRT_INIT=200): errno=98: Address already in use > 2011/08/18 15:35:00 PIM: Could not enable mroute on socket fd=5: errno=98: > Address already in use > % Interface eth0 does not exist > 2011/08/18 15:35:00 PIM: Loading configuration - end > 2011/08/18 15:35:00 PIM: Can't create pid lock file /var/run/pimd.pid > (Permission denied), exiting This means pimd is conflicting with an existing, previous instance of pimd. Kill it first: $ sudo pkill pimd Then restart it: $ sudo /usr/local/quagga/sbin/pimd Cheers, Everton
