rdump stuck in sbwait state (RELENG_7)
peterjeremy at optushome.com.au
Tue Dec 30 08:10:20 UTC 2008
On 2008-Dec-29 20:28:41 -0500, Terry Kennedy <terry at tmk.com> wrote:
> I upgraded a box (Dell Poweredge 1550, dual PIII processors) from a kernel +
>world of December 8th to one from today (December 29th) and I am experiencing
>a new problem with rdump.
> A tcpdump on both the sending and receiving systems shows no packets
>between them from the rdump processes. However, I can rshell both ways
>and get the expected output, so the link isn't down.
This is probably the critical piece of information - the TCP connection
has stopped transferring data for some reason and the rdump is blocked
waiting to send.
Unfortunately, you need the last packets that were exchanged in order
to identify which end has the problem (and hopefully provide some
pointers as to why). If possible, can you repeat the dump whilst you
run a tcpdump on the rdump flow and then post the last dozen or so
packets in each direction.
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20081230/d9ca1b32/attachment.pgp
More information about the freebsd-stable