[prev in list] [next in list] [prev in thread] [next in thread] 

List:       quagga-dev
Subject:    [quagga-dev 5300] Re: RIP failed to send periodic update
From:       "Bhartendu Maheshwari" <Bhartendu.Maheshwari () conexant ! com>
Date:       2008-04-10 15:11:56
Message-ID: 1FD58E748821414E9BDD0BEE0596C83E31AC3913 () noidahub1 ! bbnet ! ad
[Download RAW message or body]

Hello Andrew,

How you have created symbolic file "srwx------"?

I have created normal files. I used perror api it showed me "Address already inuse", \
I am sure its because I have created normal file not "s" files.

Please guide me on this.

Thanks & Regards
Bhartendu M.

-----Original Message-----
From: Andrew J. Schorr [mailto:aschorr@telemetry-investments.com]
Sent: Thursday, April 10, 2008 8:02 PM
To: Bhartendu Maheshwari
Cc: quagga-dev@lists.quagga.net
Subject: Re: [quagga-dev 5295] RIP failed to send periodic update

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

Conexant E-mail Firewall (Conexant.Com) made the following annotations
---------------------------------------------------------------------
********************** Legal Disclaimer **************************** 

"This email may contain confidential and privileged material for the sole use of the \
intended recipient. Any unauthorized review, use or distribution by others is \
strictly prohibited. If you have received the message in error, please advise the \
sender by reply email and delete the message. Thank you." 

********************************************************************** 

---------------------------------------------------------------------


_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-dev


[prev in list] [next in list] [prev in thread] [next in thread]