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).
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.
-Maxim
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
