Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 May 2011 21:07:38 +0200
From:      Daniel Gerzo <danger@FreeBSD.org>
To:        freebsd-current@freebsd.org, Pawel Jakub Dawidek <pjd@FreeBSD.org>,  Mikolaj Golub <to.my.trociny@gmail.com>
Subject:   Re: Weird issue with hastd(8)
Message-ID:  <4DDD537A.7090408@FreeBSD.org>
In-Reply-To: <4DDD4964.7060008@sippysoft.com>
References:  <4DDD4890.70604@FreeBSD.org> <4DDD4964.7060008@sippysoft.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 25.5.2011 20:24, Maxim Sobolev wrote:
> On 5/25/2011 11:21 AM, Maxim Sobolev wrote:
>> Hi Pawel,
>>
>> I am observing strange errors while synchronizing the data between
>> primary and secondary. I keep getting the following error messages:
>>
>> May 25 11:09:19 eights hastd[10113]: [test] (secondary) Unable to
>> receive request header: Socket is not connected.
>> May 25 11:09:24 eights hastd[37571]: [test] (secondary) Worker process
>> exited ungracefully (pid=10113, exitcode=75).
>> May 25 11:10:17 eights hastd[12109]: [test] (secondary) Unable to
>> receive request header: Socket is not connected.
>> May 25 11:10:18 eights hastd[37571]: [test] (secondary) Worker process
>> exited ungracefully (pid=12109, exitcode=75).
>> May 25 11:10:39 eights hastd[14685]: [test] (secondary) Unable to
>> receive request header: Socket is not connected.
>> May 25 11:10:44 eights hastd[37571]: [test] (secondary) Worker process
>> exited ungracefully (pid=14685, exitcode=75).

I can only confirm this behavior. I have already reported this to 
Mikolaj and we are trying to hunt down the problem. I have started 
observing suddenly after some update. Unfortunately I haven't noted 
which revision I started to observe this bug ;(

Do you happen to use some net.inet sysctls/tunables?


>>
>> The synchronization steel proceeds, but it's slow due to the need to
>> re-negotiate and re-spawn the secondary worker. I have tried to ktrace
>> both server and client at the same time. For some reason the primary
>> keeps sending data, while client gets 0-read from the recvfrom at some
>> point, while the primary keeps sending more data. This is 8-STABLE code
>> on both ends.
>>
>> Any ideas of what could be wrong here are appreciated.
>
> Sorry, forgot the traces.
>
> Regards,
>
>
>
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"



-- 
S pozdravom / Best regards
   Daniel Gerzo, FreeBSD committer



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DDD537A.7090408>