I've received the following message twice now:
FAILURE DUMP SUMMARY:
planner: ERROR badly formatted response from unity.med.utah.edu
unity.med.utah.edu /home2/raid7/gen25 lev 0 FAILED [badly formatted response
from unity.med.utah.edu]
The amandad debug file says:
OPTIONS features
.
The next 2 tapes Amanda expects to use are: Curie15, Curie16.
FAILURE DUMP SUMMARY:
finsen /lev 0 FAILED [disk /, all estimate timed out]
everest /images3 RESULTS MISSING
planner: ERROR badly formatted response from finsen
planner: ERROR badly formatted response from finsen
formatted response from finsen
planner: ERROR badly formatted response from finsen
planner: ERROR Request to everest failed: timeout waiting for ACK
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min
are: Curie15, Curie16.
FAILURE DUMP SUMMARY:
finsen /lev 0 FAILED [disk /, all estimate timed out]
everest /images3 RESULTS MISSING
planner: ERROR badly formatted response from finsen
planner: ERROR badly formatted response from finsen
planner: ERROR Request to everest
Great, thank you very much!
Brian
On Thu, Oct 29, 2009 at 11:07:09AM -0400, Jean-Louis Martineau wrote:
Brian Cuttler wrote:
Jean-Louis,
On Thu, Oct 29, 2009 at 10:50:43AM -0400, Jean-Louis Martineau wrote:
With this patch, you will get the error reported by sendsize.
So the
Brian Cuttler wrote:
Jean-Louis,
On Thu, Oct 29, 2009 at 10:50:43AM -0400, Jean-Louis Martineau wrote:
With this patch, you will get the error reported by sendsize.
So the error will be more explicite - or will the additional info
help amanda development ?
The error will be more
FAILED [disk /, all estimate timed out]
everest /images3 RESULTS MISSING
planner: ERROR badly formatted response from finsen
planner: ERROR badly formatted response from finsen
planner: ERROR Request to everest failed: timeout waiting for ACK
STATISTICS:
Total Full
Stefan Noll wrote:
Paul Bijnens wrote:
Also interesting is the sendsize..debug file on the client.
Can you post that one?
Sorry it's about 220KBytes.
There are 100 different entries in the disklist for client neptun.
We had some offline conversation, and probably Stefan hit a bug
due to the
Hallo Paul,
thank you for your help.
I think, it would be good to document this at
http://www.amanda.org FAQ-O-Matic
Greetings
Stefan Noll
Paul Bijnens wrote:
Stefan Noll wrote:
Hallo from Germany,
OK.
I found the cause.
It is a bug that was solved only recently (dd. 14 april 2004):
FAILED [badly formatted response from neptun]
neptun /home lev 0 FAILED [badly formatted response from neptun]
The first question is the very obscure path:
/var/samba/projojekte/Laufende/Klingelnberg
The entry in the disklist is
neptun /var/samba/projekte/Laufende/Klingelnberg comp-root-tar
/etc lev 0 FAILED [badly formatted response from neptun]
neptun /home lev 0 FAILED [badly formatted response from neptun]
The first question is the very obscure path:
/var/samba/projojekte/Laufende/Klingelnberg
The entry in the disklist is
neptun /var/samba/projekte/Laufende/Klingelnberg comp
: got result for host neptun disk /: 0 - 457710K, 1
- 2980K, -1 - -1K
Is the name now mangled to projojeke?
You get the badly formatted response from error when one of these
things happen:
- The datagram line could not be parsed by
(sscanf(t - 1, %d SIZE %ld, level, size) != 2)
- The estimate
:
command 0, options:
last_level 1 next_level0 -5 level_days 3
getting estimates 0 (45620) 1 (60) -1 (-1)
You get the badly formatted response from error when one of these
things happen:
- The datagram line could not be parsed by
(sscanf(t - 1, %d SIZE %ld, level, size) != 2
only the setup for estimate. What does the result show?
It looks like:
planner: time 80.851: got result for host neptun disk /: 0 - 45620K, 1
- 60K, -1 - -1K
You get the badly formatted response from error when one of these
things happen:
- The datagram line could not be parsed by
(sscanf(t
, 1
- 60K, -1 - -1K
I found in amdump.1 long
planner: time 1780.198: error result for host neptun disk
/var/samba/projekte/Laufende/Klingelnberg: badly formatted response from
neptun
What the client sent, yes, but what the server received, we don't know.
The problem is, where to look
Title: Nachricht
Hello,
on my SUSE 8,0 Backupserver runs Amanda 2.4.4. Unix
Clients become
also perfectly secured. Problems emerge with files on
the server.
After dump appears the following message:
localhost /etc/test lev 0 FAILED [badly formatted
response from
localhost]
What does
Due to the size of some of my volume mount points, I have 56 volume
entries in my disk list for this server (out of 183 total). ...
I assume you meant 56 entries for this *client*?
I am having amdump fail with the message:
client /d4 lev 0 FAILED [badly formatted response from client
:
client /d4 lev 0 FAILED [badly formatted response from client]
Where is the best place to figure out what is going on? Known bug?
thanks
On 29 Oct 2000, Alexandre Oliva wrote:
amandad.debug should contain the REQ packet.
Here is that portion of the amandad.debug file from amdump.
got packet:
Amanda 2.4 REQ HANDLE 000-00540508 SEQ 972857686
SECURITY USER operator
SERVICE sendsize
OPTIONS
On Oct 29, 2000, "Jason C. Wells" [EMAIL PROTECTED] wrote:
GNUTAR /home 0 1970:1:1:0:0:0 -1 exclude-file=
GNUTAR /home 1 2000:9:23:7:39:57 -1 exclude-file=
Hmmm... These look odd. I don't recall having seen `exclude-file='
followed by an empty string before, and I would bet this is the
Amcheck runs fine. I just rebuilt amanda2.4.1 on FreeBSD 4.0 to try to
clear up this problem. The problem remains.
I am getting these errors:
server /var lev 0 FAILED [badly formatted response from server]
server /usr lev 0 FAILED [badly formatted response from server]
server
21 matches
Mail list logo
