(2012/09/04 15:54), Liu Yuan wrote:
On 09/04/2012 02:41 PM, Hitoshi Mitake wrote:
On my environment, I needed to iterate more than few ten times to
reproduce the bug.
In addition, the crash of sheep on my environment might not be segfault.
Instead of core dump, I could find this output in 026.out.bad:
I am not sure what cause crash, but we will get core file when sheep
crashes.
As I write later, the cause of the problem I met was not crash of sheeps.
QA output created by 026
using backend farm store
[main] do_read(275) failed to read from socket: -1
[main] exec_req(362) failed to read a response
failed to connect to 127.0.0.1:7005
I think this log is from collie, sheep :7000 isn't crashed in your case?
According to the sheep.log, it seems that sheep:7000 didn't crash.
By the way, I am not 100% sure if this is your patch set problem. Do you
meet this problem on 026 without your patch set?
I met this problem without my patch series just now.
# HEAD is 8df7ff4c08500dbe92e01d821a661d8bd1615215
The content of 026.out.bad is same to the above.
I changed eprintf to output errno to log, and the errno was Connection
reset by peer.
But sheep procseses are still running. There might be a possibility that
the bug you met and mine are different things...
Thanks,
Hitoshi
--
sheepdog mailing list
[email protected]
http://lists.wpkg.org/mailman/listinfo/sheepdog
