I tried the dirty solution first and got this: tom@tom-laptop:~$ sudo /usr/local/quagga/sbin/zebra -i /tmp/zebra.pid [sudo] password for tom: 2011/08/18 15:52:26 ZEBRA: Can't bind to unix socket /var/run/zserv.api: Permission denied 2011/08/18 15:52:26 ZEBRA: zebra can't provide full functionality due to above error 2011/08/18 15:52:26 ZEBRA: Zebra 0.99.17 starting: vty@2601
As far as the "proper" solution is concerned. Does this have to do with that initial warning: ----------------- Quagga configuration -------------------- quagga version : 0.99.17 host operating system : linux-gnu source code location : . compiler : gcc compiler flags : -Os -fno-omit-frame-pointer -g -std=gnu99 -Wall -Wsign-compare -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -Wchar-subscripts -Wcast-qual make : make includes : linker flags : -lcrypt -lrt -lm state file directory : /var/run config file directory : /usr/local/quagga/etc example directory : /usr/local/quagga/etc user to run as : quagga group to run as : quagga group for vty sockets : config file mask : 0600 log file mask : 0600 The above user and group must have read/write access to the state file directory and to the config files in the config file directory. ------------------ Is it possible to get it to work with my current username somehow without making a new username and group? I'm not too familiar with linux users/groups. After everything is setup I'm still confused why everything is different from the "default" install of quagga as referenced in this tutorial: http://openmaniak.com/quagga_tutorial.php Example: 1. from site: *cp /usr/share/doc/quagga/examples/zebra.conf.sample /etc/quagga/zebra.con* * * The source path is no longer valid * * * * Thanks On Thu, Aug 18, 2011 at 3:49 PM, Everton Marques <[email protected]>wrote: > 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 >
