Date: Thu, 10 Jul 2008 21:51:45 +0200 From: =?utf-8?Q?Daniel_Dvo=C5=99=C3=A1k?= <dandee@hellteam.net> To: "'Sergey Matveychuk'" <sem@FreeBSD.org> Cc: ports@FreeBSD.org, 'Boris Kovalenko' <boris@tagnet.ru> Subject: FreeBSD Port: quagga-0.99.10_3 Message-ID: <56874B070CEF4FA5B60B2D158D5A9113@tocnet28.jspoj.czf> References: <000001c87801$bd411a80$6508280a@tocnet28.jspoj.czf> <47C3A89C.5000503@tagnet.ru> <4CB32F5E329F44B2A3A95B20D9AD9675@tocnet28.jspoj.czf> <48722658.4060406@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Sergey, may the problem with "lock pid_file" messages be connected with running = watchquagga daemon ? Here is what I have got in rc.conf file: quagga_enable=3D"YES" quagga_flags=3D"-d" quagga_daemons=3D"zebra ospfd ospf6d bgpd" <<<<<<<<<<<< Is this order = okay ? quagga_extralibs_path=3D"" quagga_delay=3D"10" watchquagga_enable=3D"YES" watchquagga_flags=3D"-dz -R '/usr/local/sbin/zebra -d; = /usr/local/sbin/ospfd -d; /usr/local/sbin/ospf6d -d; = /usr/local/sbin/bgpd -d' zebra ospfd ospf6d bgpd" <<<<<<<<<<<<<<<<<<<<< = I hope this syntax is right one. I did upgrading of quagga to the last one and restarting daemons. Error = messages reappeared. Important! Watchquagga daemon was running at that time too. [root@VERSION 0.99.10 /]# egrep lock /var/log/quagga/* /var/log/quagga/ospfd.log:2008/07/01 13:57:21 errors: OSPF: Could not = lock pid_file /var/run/quagga/ospfd.pid, exiting /var/log/quagga/ospfd.log:2008/07/10 17:17:27 errors: OSPF: Could not = lock pid_file /var/run/quagga/ospfd.pid, exiting ^^^^^^^^^^^^^^^^^^^^^^ the last restarting /var/log/quagga/ospf6d.log:2008/07/01 13:57:21 errors: OSPF6: Could not = lock pid_file /var/run/quagga/ospf6d.pid, exiting /var/log/quagga/ospf6d.log:2008/07/10 17:17:27 errors: OSPF6: Could not = lock pid_file /var/run/quagga/ospf6d.pid, exiting ^^^^^^^^^^^^^^^^^^^^^^ the last restarting /var/log/quagga/zebra.log:2008/07/01 13:57:21 errors: ZEBRA: Could not = lock pid_file /var/run/quagga/zebra.pid, exiting /var/log/quagga/zebra.log:2008/07/10 17:17:27 errors: ZEBRA: Could not = lock pid_file /var/run/quagga/zebra.pid, exiting ^^^^^^^^^^^^^^^^^^^^^^ the last restarting [root@VERSION 0.99.10 /]# It is interesting that the bgp daemon runs without these errors. Important! After that, I stopped watchquagga daemon and I restarted = quagga daemons, no wunder that error messages haven=C2=B4t been = appearing anymore. Voila! IMHO, the problem is connected with watchquagga daemon deffinitely. Daniel -----Original Message----- From: Daniel Dvo=C5=99=C3=A1k [mailto:dandee@hellteam.net]=20 Sent: Monday, July 07, 2008 4:44 PM To: 'Sergey Matveychuk' Cc: 'Boris Kovalenko'; 'ports@FreeBSD.org' Subject: RE: FreeBSD Port: quagga-0.99.9_7 And do you use watchquagga in rc.conf ? I do. Daniel -----Original Message----- From: Sergey Matveychuk [mailto:sem@FreeBSD.org] Sent: Monday, July 07, 2008 4:21 PM To: dandee@hellteam.net Cc: 'Boris Kovalenko'; ports@FreeBSD.org Subject: Re: FreeBSD Port: quagga-0.99.9_7 Daniel Dvo=C5=99=C3=A1k wrote: > VERSION 0.99.10# egrep lock /var/log/quagga/zebra.log ^^^^^^^^^^^^^^^=20 > 2008/06/30 01:38:59 errors: ZEBRA: Could not lock pid_file=20 > /var/run/quagga/zebra.pid, exiting > 2008/07/01 13:57:21 errors: ZEBRA: Could not lock pid_file=20 > /var/run/quagga/zebra.pid, exiting >=20 > VERSION 0.99.10# egrep lock /var/log/quagga/ospfd.log 2008/06/30 > 01:38:59 errors: OSPF: Could not lock pid_file=20 > /var/run/quagga/ospfd.pid, exiting > 2008/07/01 13:57:21 errors: OSPF: Could not lock pid_file=20 > /var/run/quagga/ospfd.pid, exiting >=20 > VERSION 0.99.10# egrep lock /var/log/quagga/ospf6d.log > 2008/07/01 13:57:21 errors: OSPF6: Could not lock pid_file=20 > /var/run/quagga/ospf6d.pid, exiting >=20 Looks like the daemons tried to run twice and fault. But I can see the = problem on my boxes. -- Dixi. Sem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56874B070CEF4FA5B60B2D158D5A9113>