On Wed, Apr 09, 2014 at 01:36:31PM +0400, Peter Andreev wrote:
> Hi everybody,
>
> I'm trying to set up bird 1.4.2 on FreeBSD 9.1 and stuck on the following:
>

> PTTlg    BGP      master   start  13:10:24    Connect       Socket: Invalid
> argument
> MLPA1    BGP      master   start  13:10:24    Connect       Socket:
> Operation timed out
> MLPA2    BGP      master   start  13:10:24    Connect       Socket: Invalid
> argument
>

> All these BGP protocols are inherited from one template. The only
> difference is that those are established, use another source address which
> is configured on virtual interface.
>
> However my question is how to find out what's going on and how to detect a
> problem? Setting "log syslog all;" is not very helpful - it only fills the
> log file with a lot of "bird6: KRT: Error sending route 2c0f:fb50::/0 to
> kernel: No such process" messages.

Hi

Socket errors are usually errors reported by OS kernel related to TCP
(for BGP) socket, so there is not much to debug in BIRD. You could add
'debug all' to that BGP protocols, but i would guess these errors
are just reactions to connect() syscall.

--
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAlNGVSIACgkQw1GB2RHercPDXACfWRI/aRzF7INqmLswP8HM+vp6
RccAnRCqcPwcav02cMj/XgMk/Xg1aa7r
=0JRZ
-----END PGP SIGNATURE-----