[quagga-dev 5299] Re: RIP failed to send periodic update

Andrew J. Schorr aschorr at telemetry-investments.com
Thu Apr 10 15:32:05 BST 2008


Hi,

On Thu, Apr 10, 2008 at 07:34:31PM +0530, Bhartendu Maheshwari wrote:
> I have observed that "zclient_socket_un" functions fails.
> Connect call in this function fails. I have already created
> "/var/run/zserv.api" and permission is 777.
> 
> Please let me know if any other configuration is required for it.

On my linux Fedora Core 6 system, I see this in /var/run/quagga:

bash$ ls -al /var/run/quagga
total 20
drwxr-x--x  2 quagga quagga   240 Jan 22 19:14 .
drwxr-xr-x 12 root   root     440 Jan 22 18:51 ..
-rw-------  1 quagga quagga     6 Jan 22 19:14 bgpd.pid
srwxrwx---  1 quagga quaggavt   0 Jan 22 19:14 bgpd.vty
-rw-------  1 quagga quagga     6 Jan 22 19:14 ospfd.pid
srwxrwx---  1 quagga quaggavt   0 Jan 22 19:14 ospfd.vty
-rw-------  1 quagga quagga     6 Jan 22 19:14 ripd.pid
srwxrwx---  1 quagga quaggavt   0 Jan 22 19:14 ripd.vty
-rw-------  1 root   root       6 Jan 22 19:14 watchquagga.pid
-rw-------  1 quagga quagga     6 Jan 22 19:14 zebra.pid
srwxrwx---  1 quagga quaggavt   0 Jan 22 19:14 zebra.vty
srwx------  1 quagga quagga     0 Jan 22 19:14 zserv.api

Do you have logging enabled in ripd?  Is ripd logging any error messages
about not being able to connect?

To check your logging config, you can do something like this:

bash$ vtysh -d ripd -c 'show logging'
Logging configuration for ripd:
Syslog logging: level notifications, facility daemon, ident ripd
Stdout logging: disabled
Monitor logging: level debugging
File logging: level debugging, filename /var/log/quagga/ripd.log
Protocol name: RIP
Record priority: disabled
Timestamp precision: 0

If file logging is not enabled, you can add something like this
to your config file to enable it:

   log file /var/log/quagga/ripd.log debugging

Then restart ripd, and look in that file for helpful error messages.

Regards,
Andy



More information about the Quagga-dev mailing list