On Mon, 16 Apr 2007, Jean-Louis Martineau wrote:
That's your problem:
---
dumper: connect_port: Try port 585: Available -
-->>dumper: connect_portrange: connect from 0.0.0.0.585 failed: Operation
timed out
-->>dumper: connect_portra
That's your problem:
---
dumper: connect_port: Try port 585: Available -
-->>dumper: connect_portrange: connect from 0.0.0.0.585 failed:
Operation timed out
-->>dumper: connect_portrange: connect to 209.123.46.110.10080 failed:
Opera
On Wed, 11 Apr 2007, Jean-Louis Martineau wrote:
When it say "was successfully retried", that's because the dump succeeded on
the second try.
Yep.
It still give the error of the first try "FAILED [cannot read header: got 0
instead of 32768]"
You should be able to find more about it in the
When it say "was successfully retried", that's because the dump
succeeded on the second try.
It still give the error of the first try "FAILED [cannot read header:
got 0 instead of 32768]"
You should be able to find more about it in the amdump.1 log file and
the dumper.*.debug and chunker.*.debug
On Tue, 10 Apr 2007, Jean-Louis Martineau wrote:
The "seek failed: Illegal seek" are normal error.
The "got partial result" lines are expected.
You have no problem with the estimate phase, don't try to search for bug
there.
Just for my own curiosity, what are those errors telling me? The pa
The "seek failed: Illegal seek" are normal error.
The "got partial result" lines are expected.
You have no problem with the estimate phase, don't try to search for bug
there.
Jean-Louis
Charles Sprickman wrote:
Perhaps the root of the problems I'm having, perhaps not.
I keep saying "I'm do
Perhaps the root of the problems I'm having, perhaps not.
I keep saying "I'm done with this" and then I go back and correlate more
server/client logs.
This is my latest finding.
While backups seem to be mostly working (even though I'm having some
amrecover issues in another thread), I have n
