On Wed, 27 Nov 2013 15:31:49 +0000, "C. L. Martinez" <carlopm...@gmail.com> wrote: > On Wed, Nov 27, 2013 at 3:25 PM, andy <a...@brandwatch.com> wrote: >> On Wed, 27 Nov 2013 15:08:33 +0000, "C. L. Martinez" >> <carlopm...@gmail.com> >> wrote: >>> Hi all, >>> >>> I am doing some tests with two openBSD 5.4 hosts configuring carp >>> features. All it is ok, except for pfsync0 interface: it doesn't >>> starts up at system boot or when both are rebooted. I need to start it >>> manually every time. >>> >>> cat /etc/hostname.pfsync0 >>> up syncdev em3 >> >> Do you also have; >> cat /etc/hostname.em3 >> inet 192.168.0.252 255.255.255.0 >> up >> >>> > > Yes, interface em3 is up ..
If you have an 'up' in your /etc/hostname.em3 file, and your pfsync0 looks right, have you try running /etc/netstart to correct the permissions on your files. Other than that I don't know.. I've not heard of pfsync not starting at all before. It always starts without issue for us (albeit slowly). I have known it to take over 60 seconds after rebooting a box for pfsync to go up properly and for the carp demotion counters to come all the way down. I figured that was just due to various pfsync timers and the time taken to get the boxes in sync.
