View Full Version : strange error: «chunker: FATAL error [chunker PORT-WRITE: too many args: 15 !»

November 18th, 2008, 04:47 AM

This is my first post here.
I'm encountering an error I don't/can't understand. Googling this was not very helpfull.

I'm trying to backup data on a LTO-3 tape changer. Everytime I try to, this ends up with this failure summary:

lserver /home/archive/mail RESULTS MISSING
chunker: FATAL error [chunker PORT-WRITE: too many args: 15 != 13]
chunker: FATAL error [chunker PORT-WRITE: too many args: 15 != 13]

I'm using Amanda 2.6.0p2 to backup servers running Debian GNU/Linux (mainly
stable version, some old-stable version, in both 64bits and 32bits
environments) and Windows (2000 server and 2003 server).
amcheck runs fine, without a single warning, I can access my tape changer
with mt/mtx.

The "amanda server" (name: iznogoud) is a bi Quad Core with 4 GB of RAM. It runs a 64bits Debian stable.
I have 3 amanda configs on this server:
- daily: backup on disk (works fine) ;
- weekly: backup on tape ;
- mails: another backup on tape.
Only «weekly» and «mails» are concerned by my problem.
These 3 configs share a common part.

Here is the log of chunker on the client when running «amdump mails»:

1227004375.844391: chunker: pid 16471 ruid 34 euid 34: start at Tue Nov 18 11:32:55 2008
1227004375.845252: chunker: pid 16471 ruid 34 euid 34: rename at Tue Nov 18 11:32:55 2008
1227004375.845334: chunker: getcmd: START 20081118112701
1227004375.845363: chunker: getcmd: PORT-WRITE 00-00002 /mnt/backup/hold/20081118112701/lserver._home_archive_mail.0 lserver ffffffff9ffeffffffff00 /home/archive/mail 0 1970:1:1:0:0:0 524288 GNUTAR 8492320 |;auth=bsd;comp-cust=/bin/tar --ignore-failed-read --bzip2;index;
1227004375.845410: chunker: critical (fatal): error [chunker PORT-WRITE: too many args: 15 != 13]

For your information, I join to this post my amanda config.

Thanks a lot for your help.

November 18th, 2008, 07:03 AM
I'm guessing that you have two different versions of Amanda installed, and the driver is, for some reason, running and older version of the chunker. These components are not intended to be compatible across versions.

November 18th, 2008, 08:12 AM
In the weekly config, I have a few clients that are still running an older version of Amanda (2.5).
In the mails config, both client and server use the same version.
The amanda server is newly installed (the old one died), but clients were upgraded from version 2.5 to 2.6.
Anyway, I will check my clients and upgrade the last one which have the version 2.5 installed.

November 18th, 2008, 08:31 AM
In this case, it looks like your server somehow has a mix of versions installed -- clients are completely separate.

On the other hand, this is weird:

comp-cust=/bin/tar --ignore-failed-read --bzip2

tar is not a compression program! Your custom compression program should be something like 'bzip2'.

Jean-Louis, this parameter should probably be quoted, right?

November 18th, 2008, 08:38 AM
Older client doesn't accept quoted text, so it should not be quoted. In is quoted in the new XML protocol.

November 18th, 2008, 09:50 AM
I changed my «/bin/tar ...» to «/bin/bzip2». It seems to work better (amdump didn't fail after 5 or 10 minutes).
The thing I don't understand is: I use the same "tar thing" in my daily config, and it works fine :-(
I'll tell when the test is over if everything went OK.

November 18th, 2008, 11:03 PM
Everything went OK after I changed the «tar ...» to «bzip2».
The only point I don't understand is: I use the same custom compress program (tar --ignore-failed-read --bzip2) in another config on the same server, and there are no trouble.
The only differences between these config are:
- daily uses a hard drive to backup, and is supposed to do only incremental backup ;
- mails and weekly use a tape changer and are supposed to do only full backup.

Anyway, thanks a lot for your help, no my backup on tape are functionnal.