driver: FATAL reading result from taper: Connection reset by peer

2006-06-09 Thread Geert Uytterhoeven
Hi all,

After upgrading amanda from 2.5.0 to 2.5.0p2 (Debian testing), all backups
fail with:

| *** THE DUMPS DID NOT FINISH PROPERLY!
| 
| The next tape Amanda expects to use is: DAILY18.
| 
| FAILURE AND STRANGE DUMP SUMMARY:
|   anakin /   RESULTS MISSING
   ^^^
|   anakin /boot   RESULTS MISSING
   ^^^
|   ...
|   driver: FATAL reading result from taper: Connection reset by peer
^

There's no indication of the failure in any log file in /tmp/amanda/.

/var/log/amanda/DailySet1/log.20060608.0 has:

| DISK planner anakin /
| DISK planner anakin /boot
| ...
| START planner date 20060608
| START driver date 20060608
| STATS driver startup time 0.003
| FATAL driver reading result from taper: Connection reset by peer
  
| INFO planner Incremental of ... bumped to level 2.
| INFO planner Full dump of ... promoted from 21 days ahead.
| ...
| FINISH planner date 20060608 time 30.445

Anyone with a clue? I'm using vtapes.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds


Re: driver: FATAL reading result from taper: Connection reset by peer

2006-06-09 Thread Paul Bijnens

On 2006-06-09 13:27, Geert Uytterhoeven wrote:

Hi all,

After upgrading amanda from 2.5.0 to 2.5.0p2 (Debian testing), all backups
fail with:

| *** THE DUMPS DID NOT FINISH PROPERLY!
| 
| The next tape Amanda expects to use is: DAILY18.
| 
| FAILURE AND STRANGE DUMP SUMMARY:

|   anakin /   RESULTS MISSING
   ^^^
|   anakin /boot   RESULTS MISSING
   ^^^
|   ...
|   driver: FATAL reading result from taper: Connection reset by peer
^


Seems like taper died suddenly?
Or the TCP connection between driver and taper was broken by a local
firewall rule maybe?





There's no indication of the failure in any log file in /tmp/amanda/.


Taper and driver have their stderr redirected into the amdump file
which gets renamed to amdump.1 (etc.) when finished.
Any clue in there?



--
Paul Bijnens, xplanation Technology ServicesTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  Are you sure?  ...   YES   ...   Phew ...   I'm out  *
***



Re: driver: FATAL reading result from taper: Connection reset by peer

2006-06-09 Thread Geert Uytterhoeven
On Fri, 9 Jun 2006, Paul Bijnens wrote:
 On 2006-06-09 13:27, Geert Uytterhoeven wrote:
  After upgrading amanda from 2.5.0 to 2.5.0p2 (Debian testing), all backups
  fail with:
  
  | *** THE DUMPS DID NOT FINISH PROPERLY!
  | | The next tape Amanda expects to use is: DAILY18.
  | | FAILURE AND STRANGE DUMP SUMMARY:
  |   anakin /   RESULTS MISSING
 ^^^
  |   anakin /boot   RESULTS MISSING
 ^^^
  |   ...
  |   driver: FATAL reading result from taper: Connection reset by peer
  ^
 
 Seems like taper died suddenly?
 Or the TCP connection between driver and taper was broken by a local
 firewall rule maybe?
 
  There's no indication of the failure in any log file in /tmp/amanda/.
 
 Taper and driver have their stderr redirected into the amdump file
 which gets renamed to amdump.1 (etc.) when finished.
 Any clue in there?

Hmm, how could I have missed that file?

| FATAL: Can't find system command 'cdrecord' on search path 
('/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin')!
| Can't use string (0) as a HASH ref while strict refs in use at 
/usr/lib/amanda/taper line 48.
| driver: reading result from taper: Connection reset by peer

(I'm using cdrw-taper, but I'm not actually backing up to CD).

The strange thing is that cdrecord is /usr/bin/cdrecord...

Ah, but it's not accessible for user backup, because backup is not a member of
group cdrom:

| [EMAIL PROTECTED]:~$ ls -l /usr/bin/cdrecord
| -rwsr-xr-- 1 root cdrom 133 Jan  7 19:43 /usr/bin/cdrecord
| [EMAIL PROTECTED]:~$ groups
| backup disk tape
| [EMAIL PROTECTED]:~$

Time to file a bug with Debian's cdrw-taper...

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds