Aw: Re: Re: sendbackup: critical (fatal): error [no backup size line]
It seems like another problem with newer smbclient versions. Have a look at: http://osdir.com/ml/backuppc/2015-12/msg00114.html Don´t know how to proceed. Greetings
Re: Re: sendbackup: critical (fatal): error [no backup size line]
Im getting errors like this one: FAILED DUMP DETAILS: /-- BACKUP02 //DC03/PUBLIC lev 0 FAILED [smbclient returned error] sendbackup: info BACKUP=APPLICATION sendbackup: info APPLICATION=amsamba sendbackup: info RECOVER_CMD=/bin/gzip -dc |/usr/lib/amanda/application/amsamba restore [./file-to-restore]+ sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? smbclient: tar:948 Fatal: Can't translate pathname './Allgemein/PDF/2016-04-22 08-03-58chäftsverteilungsplan.pdf' to UTF-8 ? smbclient: NT_STATUS_UNSUCCESSFUL listing \Allgemein\PDF\* ? smbclient: tar:948 Fatal: Can't translate pathname './lanzeige.dot' to UTF-8 ? smbclient: NT_STATUS_UNSUCCESSFUL listing \\* ? smbclient: tar:705 do_list fail NT_STATUS_UNSUCCESSFUL ? smbclient: tar:370 tar_process failed sendbackup: size 98498.5791015625 sendbackup: end sendbackup: error [smbclient returned error] ? Application (1359) amsamba returned 1 Im trying to back up shares from a Windows Server 2008 R2, maybe the UTF-8 problem is related to that then? What does your smb.conf looks like? Greetings!
Re: sendbackup: critical (fatal): error [no backup size line]
Am 2016-06-13 um 09:11 schrieb Traugott Simon: > Hello List, > Hello Stefan, > > how did it went out? the amsamba provided by JLM works fine here so far!
Re: Re: sendbackup: critical (fatal): error [no backup size line]
Hello List, Hello Stefan, how did it went out? Greetings
Re: sendbackup: critical (fatal): error [no backup size line]
Am 2016-06-09 um 14:11 schrieb Jean-Louis Martineau: > Attaching it again. > > You might need to change the first and the 'use lib' line to match your > installation. thanks a lot, the attachment got caught in my spam-filtering. amcheck looks good now, first amdump test running now.
Re: sendbackup: critical (fatal): error [no backup size line]
Am 2016-06-09 um 13:42 schrieb Jean-Louis Martineau: > On 09/06/16 03:00 AM, Stefan G. Weichinger wrote: >> Am 2016-05-27 um 09:23 schrieb Traugott Simon: >>> Hello again, >>> here you have the full anonymized report from amreport >>> >>> http://pastebin.com/MXgVFfb6 >> I hit this as well with a Debian Jessie client. >> Any news or fixes ahead for this? >> >> > Do you tried the latest amsamba I sent to the list? No, and I don't see it in my list-folder. Will dig gmane or so. Although it is a bit complicated to apply patches in debian (without manual installation of amanda). thx, stefan
Re: sendbackup: critical (fatal): error [no backup size line]
Am 2016-06-09 um 09:00 schrieb Stefan G. Weichinger: > Am 2016-05-27 um 09:23 schrieb Traugott Simon: >> Hello again, >> here you have the full anonymized report from amreport >> >> http://pastebin.com/MXgVFfb6 > > I hit this as well with a Debian Jessie client. > Any news or fixes ahead for this? On a gentoo client a downgrade to samba-4.2.9 helped (although this introduces other issues again ... badlock etc).
Re: sendbackup: critical (fatal): error [no backup size line]
Am 2016-05-27 um 09:23 schrieb Traugott Simon: > Hello again, > here you have the full anonymized report from amreport > > http://pastebin.com/MXgVFfb6 I hit this as well with a Debian Jessie client. Any news or fixes ahead for this?
AW: AW: Aw: AW: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hello again, here you have the full anonymized report from amreport http://pastebin.com/MXgVFfb6 Greetings
AW: AW: Aw: AW: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hello again, so i have tried it now with the amsamba you provided. amcheck doesn´t come up with an error anymore, so far so good. A real run gives me out these errors: MYSERVER://MYSERVER02/ASDPC320 105m dump failed: dumper: [/bin/tar: Ignoring unknown extended header keyword 'hdrcharset'], finished (8:54:30) MYSERVER://MYSERVER02/Backup$016m dump failed: dumper: [missing size line from sendbackup], finished (8:56:20) MYSERVER://MYSERVER02/GPC0 1m dump failed: dumper: [/bin/tar: Ignoring unknown extended header keyword 'hdrcharset'], finished (8:51:34) MYSERVER://MYSERVER02/NETLOGON 0 0m dump failed: dumper: [missing size line from sendbackup], finished (8:49:57) MYSERVER://MYSERVER01/BACKUP$0 backup failed: dumper: [missing size line from sendbackup] (8:55:32) MYSERVER://MYSERVER01/GPC0 1m dump failed: dumper: [/bin/tar: Ignoring unknown extended header keyword 'hdrcharset'], finished (8:50:59) MYSERVER://MYSERVER01/Kursverwaltung 025m dump failed: dumper: [/bin/tar: Ignoring unknown extended header keyword 'hdrcharset'], finished (8:52:54) MYSERVER://MYSERVER01/PUBLIC 1 0m dump failed: dumper: [/bin/tar: Ignoring unknown extended header keyword 'hdrcharset'], finished (8:50:11) MYSERVER://MYSERVER01/Schildmedia014m dump failed: dumper: [/bin/tar: Ignoring unknown extended header keyword 'hdrcharset'], finished (8:52:13) MYSERVER://MYSERVER01/USERDIRS 1 0m dump failed: dumper: [/bin/tar: Ignoring unknown extended header keyword 'hdrcharset'], finished (8:50:05) MYSERVER://MYSERVER01/Untis 0 135m dumping2m ( 1.50%) (8:56:37) MYSERVER://MYSERVER01/grafstat4 024m dump failed: dumper: [/bin/tar: Ignoring unknown extended header keyword 'hdrcharset'], finished (8:53:35) As you can see he is trying to transfer on the windows DLE´s for some time and i can see that on the network traffic as well. But for some reason he´s quitting with the error after some time. So he starts to transfer on all DLE´s but that breaks up after a short time. I hope that this helps somehow. Greetings
AW: AW: Aw: AW: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hello again, Well i have tried it first with the amsamba that comes with Amanda 3.3.8, after that failed i have tried it with this one http://pastebin.com/CADU9NKE I have not applied the patches you have send to Tobias in this try with Debian Stretch because i got some errors when i tried to apply them. But i tried to test it with Amanda 3.3.6 and Debian Jessie before. As i have cloned my backup server it´s no problem for me at all to try that out again. Could you please post an amsamba version with all the patches and fixes included to the list, so i can try it again? Greetings!
AW: Aw: AW: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
It was testet with an amsamba including your patches.
-Ursprüngliche Nachricht-
Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com]
Gesendet: Dienstag, 24. Mai 2016 15:41
An: Traugott Simon; Tobias Köck
Cc: AMANDA users
Betreff: Re: Aw: AW: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal):
error [no backup size line]
Do these errors are with the amsamba script you posted last week? or the
amsamba that come with 3.3.8?
Jean-Louis
On 23/05/16 09:02 AM, Traugott Simon wrote:
> Hello list!
>
> so im doing a few more tests right now and for this i have cloned and
> upgraded my backup machine from Jessie to Stretch.
>
> Here is what i have now:
>
> $ smbclient --version Version 4.4.3-Debian, amadmin-3.3.8
>
>
>
> Amanda Backup Client Hosts Check
>
> ERROR: MYSERVER: smbclient: WARNING: The "syslog" option is deprecated
> ERROR: MYSERVER: smbclient: Error reading password from file
> descriptor 3: empty password
> ERROR: MYSERVER: smbclient:
> ERROR: MYSERVER: Application 'amsamba': exited with status 1
> ERROR: MYSERVER: smbclient: WARNING: The "syslog" option is deprecated
> ERROR: MYSERVER: smbclient: Error reading password from file
> descriptor 3: empty password
> ERROR: MYSERVER: smbclient:
> ERROR: MYSERVER: Application 'amsamba': exited with status 1
> ERROR: MYSERVER: smbclient: WARNING: The "syslog" option is deprecated
> ERROR: MYSERVER: smbclient: Error reading password from file
> descriptor 3: empty password
> ERROR: MYSERVER: smbclient:
> ERROR: MYSERVER: Application 'amsamba': exited with status 1
> ERROR: MYSERVER: smbclient: WARNING: The "syslog" option is deprecated
> ERROR: MYSERVER: smbclient: Error reading password from file
> descriptor 3: empty password
>
>
> The interesting thing is that a plain and normal transfer with the smbclient
> just works out of the box:
>
> backup@MYSERVER:/home/backup$ smbclient "MYSERVER2\\Backup$" -U
> backup -E -W SN2.local -Tc Ziel.tar
> WARNING: The "syslog" option is deprecated Enter backup's password:
> Domain=[SN2] OS=[Windows Server 2008 R2 Standard 7601 Service Pack 1]
> Server=[Windows Server 2008 R2 Standard 6.1]
> tar:712 Total bytes received: 110498217
>
> So im going to update the bug reports now, maybe someone can help us out
> here, or is here any Amanda developer around who could have an eye on this?
>
>
> Greetings
>
>
>
>
>
>> Gesendet: Montag, 23. Mai 2016 um 11:21 Uhr
>> Von: "Tobias Köck" <tobias.ko...@qudosoft.de>
>> An: "Traugott Simon" <sauro...@gmx.de>, "AMANDA users"
>> <amanda-users@amanda.org>
>> Betreff: AW: Aw: AW: AW: AW: AW: AW: AW: sendbackup: critical
>> (fatal): error [no backup size line]
>>
>> Thanks for your answer. Unfortunately there doesn't seem to be so much
>> movement to fix the Samba problem right now ...
>>
>> I'm still on the old Samba version.
>>
>> Greetings
>> Tobias
>>
>> -Ursprüngliche Nachricht-
>> Von: owner-amanda-us...@amanda.org
>> [mailto:owner-amanda-us...@amanda.org] Im Auftrag von Traugott Simon
>> Gesendet: Donnerstag, 19. Mai 2016 15:47
>> An: AMANDA users
>> Betreff: AW: Aw: AW: AW: AW: AW: AW: AW: sendbackup: critical
>> (fatal): error [no backup size line]
>>
>> Hello list,
>>
>> so i have done some tests and here are my results.
>>
>> First i have upgraded samba to the version Debian ist coming with after
>> badlock (4.2), then i have replaced the amsamba file with this one:
>>
>> http://pastebin.com/8MaBfRqZ
>>
>> I believe that there is a small error in this file on line 786
>>
>> if ($line !~ /Ignoring unknown extended header keyword/( {
>>
>> should that be this instead??
>>
>> if ($line !~ /Ignoring unknown extended header keyword/) {
>>
>> After changing this line a dry run with perl
>> /usr/lib/amanda/applications/amsamba given me a check as result.
>>
>> When i now try to run an amcheck with this changed file, this is what i get:
>>
>> Amanda Backup Client Hosts Check
>>
>> ": No such file or directorytion 'amsamba': Can't open perl script"
>> ERROR: BACKUP02: Application 'amsamba': exited with status 2
>> ERROR: BACKUP02: Application 'amsamba': can't run support command
>> ": No such file or directorytion 'amsamba': Can't open perl script"
>> ERROR: BACKUP02: Application 'amsamba': exited with status 2
>> ERROR: BACKUP02: Application 'amsamba': can't
Aw: AW: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hello list!
so im doing a few more tests right now and for this i have cloned and upgraded
my backup machine from Jessie to Stretch.
Here is what i have now:
$ smbclient --version Version 4.4.3-Debian, amadmin-3.3.8
Amanda Backup Client Hosts Check
ERROR: MYSERVER: smbclient: WARNING: The "syslog" option is deprecated
ERROR: MYSERVER: smbclient: Error reading password from file descriptor 3:
empty password
ERROR: MYSERVER: smbclient:
ERROR: MYSERVER: Application 'amsamba': exited with status 1
ERROR: MYSERVER: smbclient: WARNING: The "syslog" option is deprecated
ERROR: MYSERVER: smbclient: Error reading password from file descriptor 3:
empty password
ERROR: MYSERVER: smbclient:
ERROR: MYSERVER: Application 'amsamba': exited with status 1
ERROR: MYSERVER: smbclient: WARNING: The "syslog" option is deprecated
ERROR: MYSERVER: smbclient: Error reading password from file descriptor 3:
empty password
ERROR: MYSERVER: smbclient:
ERROR: MYSERVER: Application 'amsamba': exited with status 1
ERROR: MYSERVER: smbclient: WARNING: The "syslog" option is deprecated
ERROR: MYSERVER: smbclient: Error reading password from file descriptor 3:
empty password
The interesting thing is that a plain and normal transfer with the smbclient
just works out of the box:
backup@MYSERVER:/home/backup$ smbclient "MYSERVER2\\Backup$" -U backup -E
-W SN2.local -Tc Ziel.tar
WARNING: The "syslog" option is deprecated
Enter backup's password:
Domain=[SN2] OS=[Windows Server 2008 R2 Standard 7601 Service Pack 1]
Server=[Windows Server 2008 R2 Standard 6.1]
tar:712 Total bytes received: 110498217
So im going to update the bug reports now, maybe someone can help us out here,
or is here any Amanda developer around who could have an eye on this?
Greetings
> Gesendet: Montag, 23. Mai 2016 um 11:21 Uhr
> Von: "Tobias Köck" <tobias.ko...@qudosoft.de>
> An: "Traugott Simon" <sauro...@gmx.de>, "AMANDA users"
> <amanda-users@amanda.org>
> Betreff: AW: Aw: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error
> [no backup size line]
>
> Thanks for your answer. Unfortunately there doesn't seem to be so much
> movement to fix the Samba problem right now ...
>
> I'm still on the old Samba version.
>
> Greetings
> Tobias
>
> -Ursprüngliche Nachricht-
> Von: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] Im
> Auftrag von Traugott Simon
> Gesendet: Donnerstag, 19. Mai 2016 15:47
> An: AMANDA users
> Betreff: AW: Aw: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error
> [no backup size line]
>
> Hello list,
>
> so i have done some tests and here are my results.
>
> First i have upgraded samba to the version Debian ist coming with after
> badlock (4.2), then i have replaced the amsamba file with this one:
>
> http://pastebin.com/8MaBfRqZ
>
> I believe that there is a small error in this file on line 786
>
> if ($line !~ /Ignoring unknown extended header keyword/( {
>
> should that be this instead??
>
> if ($line !~ /Ignoring unknown extended header keyword/) {
>
> After changing this line a dry run with perl
> /usr/lib/amanda/applications/amsamba given me a check as result.
>
> When i now try to run an amcheck with this changed file, this is what i get:
>
> Amanda Backup Client Hosts Check
>
> ": No such file or directorytion 'amsamba': Can't open perl script "
> ERROR: BACKUP02: Application 'amsamba': exited with status 2
> ERROR: BACKUP02: Application 'amsamba': can't run support command
> ": No such file or directorytion 'amsamba': Can't open perl script "
> ERROR: BACKUP02: Application 'amsamba': exited with status 2
> ERROR: BACKUP02: Application 'amsamba': can't run support command
> ": No such file or directorytion 'amsamba': Can't open perl script "
> ERROR: BACKUP02: Application 'amsamba': exited with status 2
> ERROR: BACKUP02: Application 'amsamba': can't run support command
> ": No such file or directorytion 'amsamba': Can't open perl script "
> ERROR: BACKUP02: Application 'amsamba': exited with status 2 .
>
>
> /usr/lib/amanda/application$ ls -lisa
> insgesamt 296
> 1190971 4 drwxr-xr-x 2 root root4096 Mai 19 15:26 .
> 1190367 4 drwxr-xr-x 4 root root4096 Dez 19 2014 ..
> 1191151 44 -rwxr-xr-x 1 root root 44144 Dez 8 2014 ambsdtar
> 1191152 40 -rwsr-xr-- 1 root backup 40328 Dez 8 2014 amgtar
> 1191153 8 -rwxr-xr-x 1 root root7097 Dez 8 2014 amlog-script
> 1191154 36 -rwxr-xr-x 1 root root 34738 Dez 8 2014 ampgsql
> 1191156 12 -rwxr-xr-x 1 root root8926 Dez 8 2014 amraw
>
AW: Aw: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Thanks for your answer. Unfortunately there doesn't seem to be so much movement
to fix the Samba problem right now ...
I'm still on the old Samba version.
Greetings
Tobias
-Ursprüngliche Nachricht-
Von: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] Im
Auftrag von Traugott Simon
Gesendet: Donnerstag, 19. Mai 2016 15:47
An: AMANDA users
Betreff: AW: Aw: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error
[no backup size line]
Hello list,
so i have done some tests and here are my results.
First i have upgraded samba to the version Debian ist coming with after badlock
(4.2), then i have replaced the amsamba file with this one:
http://pastebin.com/8MaBfRqZ
I believe that there is a small error in this file on line 786
if ($line !~ /Ignoring unknown extended header keyword/( {
should that be this instead??
if ($line !~ /Ignoring unknown extended header keyword/) {
After changing this line a dry run with perl
/usr/lib/amanda/applications/amsamba given me a check as result.
When i now try to run an amcheck with this changed file, this is what i get:
Amanda Backup Client Hosts Check
": No such file or directorytion 'amsamba': Can't open perl script "
ERROR: BACKUP02: Application 'amsamba': exited with status 2
ERROR: BACKUP02: Application 'amsamba': can't run support command
": No such file or directorytion 'amsamba': Can't open perl script "
ERROR: BACKUP02: Application 'amsamba': exited with status 2
ERROR: BACKUP02: Application 'amsamba': can't run support command
": No such file or directorytion 'amsamba': Can't open perl script "
ERROR: BACKUP02: Application 'amsamba': exited with status 2
ERROR: BACKUP02: Application 'amsamba': can't run support command
": No such file or directorytion 'amsamba': Can't open perl script "
ERROR: BACKUP02: Application 'amsamba': exited with status 2 .
/usr/lib/amanda/application$ ls -lisa
insgesamt 296
1190971 4 drwxr-xr-x 2 root root4096 Mai 19 15:26 .
1190367 4 drwxr-xr-x 4 root root4096 Dez 19 2014 ..
1191151 44 -rwxr-xr-x 1 root root 44144 Dez 8 2014 ambsdtar
1191152 40 -rwsr-xr-- 1 root backup 40328 Dez 8 2014 amgtar
1191153 8 -rwxr-xr-x 1 root root7097 Dez 8 2014 amlog-script
1191154 36 -rwxr-xr-x 1 root root 34738 Dez 8 2014 ampgsql
1191156 12 -rwxr-xr-x 1 root root8926 Dez 8 2014 amraw
1182688 32 -rwxr-xr-x 1 root root 30155 Mai 19 15:22 amsamba
1182690 32 -rwxr-xr-x 1 root root 28804 Mai 19 14:25 amsamba.orig
1191158 32 -rwsr-xr-- 1 root backup 31968 Dez 8 2014 amstar
1191159 20 -rwxr-xr-x 1 root root 18098 Dez 8 2014 amsuntar
1191160 16 -rwxr-xr-x 1 root root 14176 Dez 8 2014 amzfs-sendrecv
1191161 8 -rwxr-xr-x 1 root root6271 Dez 8 2014 amzfs-snapshot
1191162 8 -rwxr-xr-x 1 root root5732 Dez 8 2014 script-email
Well i don´t know what i should test as next step.
Greetings
AW: Aw: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hello list,
so i have done some tests and here are my results.
First i have upgraded samba to the version Debian ist coming with after badlock
(4.2), then i have replaced the amsamba file with this one:
http://pastebin.com/8MaBfRqZ
I believe that there is a small error in this file on line 786
if ($line !~ /Ignoring unknown extended header keyword/( {
should that be this instead??
if ($line !~ /Ignoring unknown extended header keyword/) {
After changing this line a dry run with perl
/usr/lib/amanda/applications/amsamba given me a check as result.
When i now try to run an amcheck with this changed file, this is what i get:
Amanda Backup Client Hosts Check
": No such file or directorytion 'amsamba': Can't open perl script "
ERROR: BACKUP02: Application 'amsamba': exited with status 2
ERROR: BACKUP02: Application 'amsamba': can't run support command
": No such file or directorytion 'amsamba': Can't open perl script "
ERROR: BACKUP02: Application 'amsamba': exited with status 2
ERROR: BACKUP02: Application 'amsamba': can't run support command
": No such file or directorytion 'amsamba': Can't open perl script "
ERROR: BACKUP02: Application 'amsamba': exited with status 2
ERROR: BACKUP02: Application 'amsamba': can't run support command
": No such file or directorytion 'amsamba': Can't open perl script "
ERROR: BACKUP02: Application 'amsamba': exited with status 2
.
/usr/lib/amanda/application$ ls -lisa
insgesamt 296
1190971 4 drwxr-xr-x 2 root root4096 Mai 19 15:26 .
1190367 4 drwxr-xr-x 4 root root4096 Dez 19 2014 ..
1191151 44 -rwxr-xr-x 1 root root 44144 Dez 8 2014 ambsdtar
1191152 40 -rwsr-xr-- 1 root backup 40328 Dez 8 2014 amgtar
1191153 8 -rwxr-xr-x 1 root root7097 Dez 8 2014 amlog-script
1191154 36 -rwxr-xr-x 1 root root 34738 Dez 8 2014 ampgsql
1191156 12 -rwxr-xr-x 1 root root8926 Dez 8 2014 amraw
1182688 32 -rwxr-xr-x 1 root root 30155 Mai 19 15:22 amsamba
1182690 32 -rwxr-xr-x 1 root root 28804 Mai 19 14:25 amsamba.orig
1191158 32 -rwsr-xr-- 1 root backup 31968 Dez 8 2014 amstar
1191159 20 -rwxr-xr-x 1 root root 18098 Dez 8 2014 amsuntar
1191160 16 -rwxr-xr-x 1 root root 14176 Dez 8 2014 amzfs-sendrecv
1191161 8 -rwxr-xr-x 1 root root6271 Dez 8 2014 amzfs-snapshot
1191162 8 -rwxr-xr-x 1 root root5732 Dez 8 2014 script-email
Well i don´t know what i should test as next step.
Greetings
Aw: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hello list, im looking forward to your test results, i hope it will fix my problems too. Greetings > Gesendet: Montag, 25. April 2016 um 10:48 Uhr > Von: "Tobias Köck" <tobias.ko...@qudosoft.de> > An: "Jean-Louis Martineau" <jmartin...@carbonite.com> > Cc: "amanda-users@amanda.org" <amanda-users@amanda.org> > Betreff: AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no > backup size line] > > Hi Jean-Louis, > > thanks. I will try it out earliest on this weekend. Productive backups are a > priority right now. :) > > Greetings > Tobias > > > > -Ursprüngliche Nachricht- > Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] > Gesendet: Freitag, 22. April 2016 19:14 > An: Tobias Köck > Cc: amanda-users@amanda.org > Betreff: Re: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no > backup size line] > > Hi Tobias, > > amsamba is tested and is working with previous samba release. > The problem is with the new samba, amsamba is not test with it. > I do not have setup to run amsamba so I need your help to fix it. > > Can you try the attached patch? it should fix the 'Ignoring unknown extended > header keyword' error. > > Jean-Louis > > On 22/04/16 12:39 PM, Tobias Köck wrote: > > Hi Jean-Louis, > > > > Now I get two other error messages > > > > - dump failed: dumper: [/bin/tar: Ignoring unknown extended header > > keyword 'hdrcharset'], finished (17:41:11) > > localhost://monster.qudosoft.de/software > > > > - dump failed: dumper: [missing size line from sendbackup], finished > > (17:38:08) > > > > which lets the dump fail completely. I haven't found the strings in the log > > files so I haven't attached the logs at the moment. > > > > Anyway, it seems that the amsamba script is still a little bit buggy. Maybe > > I'll revert to the previous tar configuration with an earlier smbclient > > version to have working backups. > > > > Is the amsamba application tested and in use after all? > > > > Greetings and thanks > > Tobias > > > > -Ursprüngliche Nachricht- > > Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] > > Gesendet: Mittwoch, 20. April 2016 19:34 > > An: Tobias Köck > > Cc: amanda-users@amanda.org > > Betreff: Re: AW: AW: AW: AW: sendbackup: critical (fatal): error [no > > backup size line] > > > > Tobias, > > > > This patch should make amsamba ignore the WARNING line from smbclient. > > > > Jean-Louis > > > > On 20/04/16 01:26 PM, Tobias Köck wrote: > >> Hi Jean-Louis, > >> > >> my smb.conf already has the entry syslog = 0 so I don't know where that > >> came from. > >> > >> Still the amsamba application exits with 1 > >> > >> localhost: Application 'amsamba': exited with status 1 > >> > >> Shouldn't it be something else? It still is 'just' a warning? > >> > >> Anyway, thanks for your help. I'll check out if it runs through. :) > >> > >> Greetings and thanks > >> Tobias > >> > >> -Ursprüngliche Nachricht- > >> Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] > >> Gesendet: Mittwoch, 20. April 2016 19:06 > >> An: Tobias Köck > >> Cc: AMANDA users > >> Betreff: Re: AW: AW: AW: sendbackup: critical (fatal): error [no > >> backup size line] > >> > >> Tobias, > >> > >> Amanda do not use the "syslog" option, check your samba configuration > >> (smb.conf, ...) This is a WARNING, you can try a backup. > >> > >> Jean-Louis > >> > >> On 20/04/16 12:55 PM, Tobias Köck wrote: > >>> Hi Jean-Louis, > >>> > >>> I have applied your patch. Unfortunatelly that didn't work either. I > >>> have attached one log and the amcheck -c someconfig output. > >>> > >>> ---amcheck-- > >>> - > >>> - > >>> -- > >>> backup@chronos:~$ amcheck -c someconfig > >>> > >>> Amanda Backup Client Hosts Check > >>> > >>> ... > >>> ERROR: localhost: smbclient: WARNING: The "syslog" option is > >>> deprecated > >>> ERROR: localhost: Application 'amsamba': exited with status 1 > >>> ERROR: localhost: smbclient: WARNING:
AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hi Jean-Louis, thanks. I will try it out earliest on this weekend. Productive backups are a priority right now. :) Greetings Tobias -Ursprüngliche Nachricht- Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] Gesendet: Freitag, 22. April 2016 19:14 An: Tobias Köck Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line] Hi Tobias, amsamba is tested and is working with previous samba release. The problem is with the new samba, amsamba is not test with it. I do not have setup to run amsamba so I need your help to fix it. Can you try the attached patch? it should fix the 'Ignoring unknown extended header keyword' error. Jean-Louis On 22/04/16 12:39 PM, Tobias Köck wrote: > Hi Jean-Louis, > > Now I get two other error messages > > - dump failed: dumper: [/bin/tar: Ignoring unknown extended header > keyword 'hdrcharset'], finished (17:41:11) > localhost://monster.qudosoft.de/software > > - dump failed: dumper: [missing size line from sendbackup], finished > (17:38:08) > > which lets the dump fail completely. I haven't found the strings in the log > files so I haven't attached the logs at the moment. > > Anyway, it seems that the amsamba script is still a little bit buggy. Maybe > I'll revert to the previous tar configuration with an earlier smbclient > version to have working backups. > > Is the amsamba application tested and in use after all? > > Greetings and thanks > Tobias > > -Ursprüngliche Nachricht- > Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] > Gesendet: Mittwoch, 20. April 2016 19:34 > An: Tobias Köck > Cc: amanda-users@amanda.org > Betreff: Re: AW: AW: AW: AW: sendbackup: critical (fatal): error [no > backup size line] > > Tobias, > > This patch should make amsamba ignore the WARNING line from smbclient. > > Jean-Louis > > On 20/04/16 01:26 PM, Tobias Köck wrote: >> Hi Jean-Louis, >> >> my smb.conf already has the entry syslog = 0 so I don't know where that came >> from. >> >> Still the amsamba application exits with 1 >> >> localhost: Application 'amsamba': exited with status 1 >> >> Shouldn't it be something else? It still is 'just' a warning? >> >> Anyway, thanks for your help. I'll check out if it runs through. :) >> >> Greetings and thanks >> Tobias >> >> -Ursprüngliche Nachricht- >> Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] >> Gesendet: Mittwoch, 20. April 2016 19:06 >> An: Tobias Köck >> Cc: AMANDA users >> Betreff: Re: AW: AW: AW: sendbackup: critical (fatal): error [no >> backup size line] >> >> Tobias, >> >> Amanda do not use the "syslog" option, check your samba configuration >> (smb.conf, ...) This is a WARNING, you can try a backup. >> >> Jean-Louis >> >> On 20/04/16 12:55 PM, Tobias Köck wrote: >>> Hi Jean-Louis, >>> >>> I have applied your patch. Unfortunatelly that didn't work either. I have >>> attached one log and the amcheck -c someconfig output. >>> >>> ---amcheck-- >>> - >>> - >>> -- >>> backup@chronos:~$ amcheck -c someconfig >>> >>> Amanda Backup Client Hosts Check >>> >>> ... >>> ERROR: localhost: smbclient: WARNING: The "syslog" option is >>> deprecated >>> ERROR: localhost: Application 'amsamba': exited with status 1 >>> ERROR: localhost: smbclient: WARNING: The "syslog" option is >>> deprecated >>> ERROR: localhost: Application 'amsamba': exited with status 1 >>> ERROR: localhost: smbclient: WARNING: The "syslog" option is >>> deprecated >>> ERROR: localhost: Application 'amsamba': exited with status 1 >>> ERROR: localhost: smbclient: WARNING: The "syslog" option is >>> deprecated >>> ERROR: localhost: Application 'amsamba': exited with status 1 >>> ERROR: localhost: smbclient: WARNING: The "syslog" option is >>> deprecated >>> ERROR: localhost: Application 'amsamba': exited with status 1 >>> ERROR: localhost: smbclient: WARNING: The "syslog" option is >>> deprecated >>> ERROR: localhost: Application 'amsamba': exited with status 1 >>> ERROR: localhost: smbclient: WARNING: The "syslog" option is >>> deprecated >>> ERROR: localhost: Application 'amsamba': exited with status 1 Clie
AW: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hi Rock, thanks for your answer. I have gotten the same error message before the backlock update (still Samba 4.2). So it's probably not directly related to the badlock update but to changes in Samba 4.2. Do you know if the Samba developer are already informed about the problem? Greetings Tobias Von: Rock Strongo [mailto:sauro...@gmx.de] Gesendet: Samstag, 23. April 2016 12:07 An: Tobias Köck Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line] Hello Tobias, thats the same error message i get since the badlock update. And yes amsamba is working fine for me for years now. The badlock update to Version 4.2 is the main problem at the moment. Greetings
Re: AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hello Tobias, thats the same error message i get since the badlock update. And yes amsamba is working fine for me for years now. The badlock update to Version 4.2 is the main problem at the moment. Greetings
AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hi Jean-Louis, Now I get two other error messages - dump failed: dumper: [/bin/tar: Ignoring unknown extended header keyword 'hdrcharset'], finished (17:41:11) localhost://monster.qudosoft.de/software - dump failed: dumper: [missing size line from sendbackup], finished (17:38:08) which lets the dump fail completely. I haven't found the strings in the log files so I haven't attached the logs at the moment. Anyway, it seems that the amsamba script is still a little bit buggy. Maybe I'll revert to the previous tar configuration with an earlier smbclient version to have working backups. Is the amsamba application tested and in use after all? Greetings and thanks Tobias -Ursprüngliche Nachricht- Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] Gesendet: Mittwoch, 20. April 2016 19:34 An: Tobias Köck Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line] Tobias, This patch should make amsamba ignore the WARNING line from smbclient. Jean-Louis On 20/04/16 01:26 PM, Tobias Köck wrote: > Hi Jean-Louis, > > my smb.conf already has the entry syslog = 0 so I don't know where that came > from. > > Still the amsamba application exits with 1 > > localhost: Application 'amsamba': exited with status 1 > > Shouldn't it be something else? It still is 'just' a warning? > > Anyway, thanks for your help. I'll check out if it runs through. :) > > Greetings and thanks > Tobias > > -Ursprüngliche Nachricht- > Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] > Gesendet: Mittwoch, 20. April 2016 19:06 > An: Tobias Köck > Cc: AMANDA users > Betreff: Re: AW: AW: AW: sendbackup: critical (fatal): error [no > backup size line] > > Tobias, > > Amanda do not use the "syslog" option, check your samba configuration > (smb.conf, ...) This is a WARNING, you can try a backup. > > Jean-Louis > > On 20/04/16 12:55 PM, Tobias Köck wrote: >> Hi Jean-Louis, >> >> I have applied your patch. Unfortunatelly that didn't work either. I have >> attached one log and the amcheck -c someconfig output. >> >> ---amcheck--- >> - >> -- >> backup@chronos:~$ amcheck -c someconfig >> >> Amanda Backup Client Hosts Check >> >> ... >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 Client >> check: 55 hosts checked in 9.979 seconds. 15 problems found. >> >> ---log--- >> - >> - >> backup@chronos:/var/log/amanda/client/something$ less >> Amsamba.20160420155143004.debug Wed Apr 20 15:51:43 2016: >> thd-0x1078200: Amsamba: pid 10415 ruid 34 euid 34 version 3.3.8: >> start at Wed Apr 20 15:51:43 2016 Wed Apr 20 15:51:43 2016: thd-0x1078200: >> Amsamba: Arguments: selfcheck Wed Apr 20 15:51:43 2016: thd-0x1078200: >> Amsamba: pid 10415 ruid 34 euid 34 version 3.3.8: rename at Wed Apr >> 20 >> 15:51:43 2016 Wed Apr 20 15:51:43 2016: thd-0x1078200: Amsamba: >> application: Amsamba >> >> Wed Apr 20 15:51:43 2016: thd-0x1078200: Amsamba: warning: Use of >> uninitialized value $regex_match in pattern match (m//) at >> /usr/lib/amanda/application/amsamba line 91. >> >> Wed Apr 20 15:51:43 2016: thd-0x1078200: Amsamba: Arguments: >> selfcheck --message line --config someconfig --host localhost --disk >> //monster.someurl.de/austausch --device >> //monster.someurl
AW: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hi Jean-Louis, thanks. That fixed at least the warnings with amcheck -c someconfig. Greetings Tobias -Ursprüngliche Nachricht- Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] Gesendet: Mittwoch, 20. April 2016 19:34 An: Tobias Köck Cc: amanda-users@amanda.org Betreff: Re: AW: AW: AW: AW: sendbackup: critical (fatal): error [no backup size line] Tobias, This patch should make amsamba ignore the WARNING line from smbclient. Jean-Louis On 20/04/16 01:26 PM, Tobias Köck wrote: > Hi Jean-Louis, > > my smb.conf already has the entry syslog = 0 so I don't know where that came > from. > > Still the amsamba application exits with 1 > > localhost: Application 'amsamba': exited with status 1 > > Shouldn't it be something else? It still is 'just' a warning? > > Anyway, thanks for your help. I'll check out if it runs through. :) > > Greetings and thanks > Tobias > > -Ursprüngliche Nachricht- > Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] > Gesendet: Mittwoch, 20. April 2016 19:06 > An: Tobias Köck > Cc: AMANDA users > Betreff: Re: AW: AW: AW: sendbackup: critical (fatal): error [no > backup size line] > > Tobias, > > Amanda do not use the "syslog" option, check your samba configuration > (smb.conf, ...) This is a WARNING, you can try a backup. > > Jean-Louis > > On 20/04/16 12:55 PM, Tobias Köck wrote: >> Hi Jean-Louis, >> >> I have applied your patch. Unfortunatelly that didn't work either. I have >> attached one log and the amcheck -c someconfig output. >> >> ---amcheck--- >> - >> -- >> backup@chronos:~$ amcheck -c someconfig >> >> Amanda Backup Client Hosts Check >> >> ... >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 >> ERROR: localhost: smbclient: WARNING: The "syslog" option is >> deprecated >> ERROR: localhost: Application 'amsamba': exited with status 1 Client >> check: 55 hosts checked in 9.979 seconds. 15 problems found. >> >> ---log--- >> - >> - >> backup@chronos:/var/log/amanda/client/something$ less >> Amsamba.20160420155143004.debug Wed Apr 20 15:51:43 2016: >> thd-0x1078200: Amsamba: pid 10415 ruid 34 euid 34 version 3.3.8: >> start at Wed Apr 20 15:51:43 2016 Wed Apr 20 15:51:43 2016: thd-0x1078200: >> Amsamba: Arguments: selfcheck Wed Apr 20 15:51:43 2016: thd-0x1078200: >> Amsamba: pid 10415 ruid 34 euid 34 version 3.3.8: rename at Wed Apr >> 20 >> 15:51:43 2016 Wed Apr 20 15:51:43 2016: thd-0x1078200: Amsamba: >> application: Amsamba >> >> Wed Apr 20 15:51:43 2016: thd-0x1078200: Amsamba: warning: Use of >> uninitialized value $regex_match in pattern match (m//) at >> /usr/lib/amanda/application/amsamba line 91. >> >> Wed Apr 20 15:51:43 2016: thd-0x1078200: Amsamba: Arguments: >> selfcheck --message line --config someconfig --host localhost --disk >> //monster.someurl.de/austausch --device >> //monster.someurl.de/austausch --index line --record --amandapass >> /etc/amandapass Wed Apr 20 15:51:43 >> 2016: thd-0x1078200: Amsamba: command: selfcheck Wed Apr 20 15:51:43 >> 2016: thd-0x1078200: Amsamba: disk //monster.someurl.de/austausch Wed >> Apr 20 15:51:43 2016: thd-0x1078200: Amsamba: amsamba version 3.3.8 >> Wed Apr 20 15:51:43 2016: thd-0x1078200: Amsamba: amsamba >> smbclient-version 4.3.8-Debian Wed Apr 20 15:51:43 2016: >> thd-0x1078200: Amsamba: /usr/bin/smbclient Wed Apr 20 15:51:43 2016: >> thd-0x1078200: Amsamba: amand
AW: AW: AW: sendbackup: critical (fatal): error [no backup size line]
15:51:43 2016 -Ursprüngliche Nachricht- Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] Gesendet: Mittwoch, 20. April 2016 15:21 An: Tobias Köck Cc: AMANDA users Betreff: Re: AW: AW: sendbackup: critical (fatal): error [no backup size line] Looks like smbclient expect to read the password twice. Can you try this patch. Jean-Louis On 20/04/16 05:27 AM, Tobias Köck wrote: > Hi Jean-Louis, > > sure. I have adjusted the password and some URLS/IPs. Relevant and activated > for amsama are the monster.someurl.de entries. > > # nas shares > //192.168.210.254/tempstorage backup%somepassword > //192.168.210.254/a2g_it backup%somepassword > //192.168.210.254/a2g_intern backup%somepassword > //192.168.210.254/backupgate backup%somepassword > //192.168.210.254/ftp backup%somepassword > //192.168.210.254/cust backup%somepassword > //192.168.210.254/clusterexp backup%somepassword > > #//charon2.someurl.de/charon2_shares backup%somepassword # > monster.someurl.de //monster.someurl.de/austausch backup%somepassword > //monster.someurl.de/big backup%somepassword > //monster.someurl.de/intern backup%somepassword > //monster.someurl.de/cust backup%somepassword > > # nooby nas > //nooby-nas.someurl.de/blubb-data backup%somepassword > > //monster.someurl.de/software backup%somepassword > //monster.someurl.de/sysadmin backup%somepassword > > -Ursprüngliche Nachricht- > Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] > Gesendet: Dienstag, 19. April 2016 18:12 > An: Tobias Köck > Cc: AMANDA users > Betreff: Re: AW: sendbackup: critical (fatal): error [no backup size > line] > > Can you post your /etc/amandapass file in attachment? > Substitute your password by a random string > > Jean-Louis > > On 19/04/16 11:47 AM, Tobias Köck wrote: >> Hey Jean-Louis, >> >> I tried your patch. If I run amcheck -c blubberdiblibb it gives me >> another error by not finding the password but I am sure I have >> included the password (and it's not empty) in the /etc/amandapass in >> the right format >> >> Logs: >> >> Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: pid 8732 ruid 34 >> euid 34 version 3.3.8: start at Tue Apr 19 17:28:09 2016 Tue Apr 19 >> 17:28:09 2016: thd-0x18e0200: Amsamba: Arguments: selfcheck Tue Apr >> 19 >> 17:28:09 2016: thd-0x18e0200: Amsamba: pid 8732 ruid 34 euid 34 >> version 3.3.8: rename at Tue Apr 19 17:28:09 2016 Tue Apr 19 17:28:09 >> 2016: thd-0x18e0200: Amsamba: application: Amsamba >> >> Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: warning: Use of >> uninitialized value $regex_match in pattern match (m//) at >> /usr/lib/amanda/application/amsamba line 91. >> >> Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: Arguments: >> selfcheck --message line --config blubberdiblubb --host localhost >> --disk //monster.someurl.de/austausch --device >> //monster.someurl.de/austausch --index line --record --amandapass >> /etc/amandapass Tue Apr 19 17:28:09 >> 2016: thd-0x18e0200: Amsamba: command: selfcheck Tue Apr 19 17:28:09 >> 2016: thd-0x18e0200: Amsamba: disk //monster.someurl.de/austausch Tue >> Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: amsamba version 3.3.8 >> Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: amsamba >> smbclient-version 4.3.8-Debian Tue Apr 19 17:28:09 2016: thd-0x18e0200: >> Amsamba: /usr/bin/smbclient Tue Apr 19 17:28:09 2016: thd-0x18e0200: >> Amsamba: amandapass: /etc/amandapass Tue Apr 19 17:28:09 2016: >> thd-0x18e0200: Amsamba: password_rdr 3 Tue Apr 19 17:28:09 2016: >> thd-0x18e0200: Amsamba: warning: close() on unopened filehandle 1 at >> /usr/lib/amanda/application/amsamba line 426. >> >> Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: password_wtr 4 Tue >> Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: warning: close() on unopened >> filehandle 2 at /usr/lib/amanda/application/amsamba line 427. >> >> Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: execute: >> /usr/bin/smbclient /usr/bin/smbclient //monster.someurl.de/austausch >> -U backup -E -c quit Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: >> stderr: WARNING: The "syslog" option is deprecated Tue Apr 19 >> 17:28:09 >> 2016: thd-0x18e0200: Amsamba: smbclient: WARNING: The "syslog" option >> is deprecated Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: stderr: >> Error reading password from file descriptor 3: empty password Tue Apr 19 >> 17:28:09 2016: thd-0x18e0200: Amsamba: smbclient: Error reading password >> from file descriptor 3: empty password Tue Apr 19 1
AW: AW: sendbackup: critical (fatal): error [no backup size line]
For some reason the MUA didn't transfer the newline characters for the entries but the entries are in separate lines. -Ursprüngliche Nachricht- Von: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] Im Auftrag von Tobias Köck Gesendet: Mittwoch, 20. April 2016 11:27 An: Jean-Louis Martineau Cc: AMANDA users Betreff: AW: AW: sendbackup: critical (fatal): error [no backup size line] Hi Jean-Louis, sure. I have adjusted the password and some URLS/IPs. Relevant and activated for amsama are the monster.someurl.de entries. # nas shares //192.168.210.254/tempstorage backup%somepassword //192.168.210.254/a2g_it backup%somepassword //192.168.210.254/a2g_intern backup%somepassword //192.168.210.254/backupgate backup%somepassword //192.168.210.254/ftp backup%somepassword //192.168.210.254/cust backup%somepassword //192.168.210.254/clusterexp backup%somepassword #//charon2.someurl.de/charon2_shares backup%somepassword # monster.someurl.de //monster.someurl.de/austausch backup%somepassword //monster.someurl.de/big backup%somepassword //monster.someurl.de/intern backup%somepassword //monster.someurl.de/cust backup%somepassword # nooby nas //nooby-nas.someurl.de/blubb-data backup%somepassword //monster.someurl.de/software backup%somepassword //monster.someurl.de/sysadmin backup%somepassword -Ursprüngliche Nachricht- Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] Gesendet: Dienstag, 19. April 2016 18:12 An: Tobias Köck Cc: AMANDA users Betreff: Re: AW: sendbackup: critical (fatal): error [no backup size line] Can you post your /etc/amandapass file in attachment? Substitute your password by a random string Jean-Louis On 19/04/16 11:47 AM, Tobias Köck wrote: > Hey Jean-Louis, > > I tried your patch. If I run amcheck -c blubberdiblibb it gives me > another error by not finding the password but I am sure I have > included the password (and it's not empty) in the /etc/amandapass in > the right format > > Logs: > > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: pid 8732 ruid 34 > euid 34 version 3.3.8: start at Tue Apr 19 17:28:09 2016 Tue Apr 19 > 17:28:09 2016: thd-0x18e0200: Amsamba: Arguments: selfcheck Tue Apr 19 > 17:28:09 2016: thd-0x18e0200: Amsamba: pid 8732 ruid 34 euid 34 > version 3.3.8: rename at Tue Apr 19 17:28:09 2016 Tue Apr 19 17:28:09 > 2016: thd-0x18e0200: Amsamba: application: Amsamba > > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: warning: Use of > uninitialized value $regex_match in pattern match (m//) at > /usr/lib/amanda/application/amsamba line 91. > > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: Arguments: selfcheck > --message line --config blubberdiblubb --host localhost --disk > //monster.someurl.de/austausch --device //monster.someurl.de/austausch > --index line --record --amandapass /etc/amandapass Tue Apr 19 17:28:09 > 2016: thd-0x18e0200: Amsamba: command: selfcheck Tue Apr 19 17:28:09 > 2016: thd-0x18e0200: Amsamba: disk //monster.someurl.de/austausch Tue > Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: amsamba version 3.3.8 > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: amsamba > smbclient-version 4.3.8-Debian Tue Apr 19 17:28:09 2016: thd-0x18e0200: > Amsamba: /usr/bin/smbclient Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: > amandapass: /etc/amandapass Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: > password_rdr 3 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: warning: > close() on unopened filehandle 1 at /usr/lib/amanda/application/amsamba line > 426. > > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: password_wtr 4 Tue > Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: warning: close() on unopened > filehandle 2 at /usr/lib/amanda/application/amsamba line 427. > > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: execute: > /usr/bin/smbclient /usr/bin/smbclient //monster.someurl.de/austausch > -U backup -E -c quit Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: > stderr: WARNING: The "syslog" option is deprecated Tue Apr 19 17:28:09 > 2016: thd-0x18e0200: Amsamba: smbclient: WARNING: The "syslog" option > is deprecated Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: stderr: Error > reading password from file descriptor 3: empty password Tue Apr 19 17:28:09 > 2016: thd-0x18e0200: Amsamba: smbclient: Error reading password from file > descriptor 3: empty password Tue Apr 19 17:28:09 2016: thd-0x18e0200: > Amsamba: stderr: > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: smbclient: > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: stderr: Domain=[someurl] > OS=[Unix] Server=[Samba 3.6.24] > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_utime : 0 > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_stime :
AW: AW: sendbackup: critical (fatal): error [no backup size line]
Hi Jean-Louis, sure. I have adjusted the password and some URLS/IPs. Relevant and activated for amsama are the monster.someurl.de entries. # nas shares //192.168.210.254/tempstorage backup%somepassword //192.168.210.254/a2g_it backup%somepassword //192.168.210.254/a2g_intern backup%somepassword //192.168.210.254/backupgate backup%somepassword //192.168.210.254/ftp backup%somepassword //192.168.210.254/cust backup%somepassword //192.168.210.254/clusterexp backup%somepassword #//charon2.someurl.de/charon2_shares backup%somepassword # monster.someurl.de //monster.someurl.de/austausch backup%somepassword //monster.someurl.de/big backup%somepassword //monster.someurl.de/intern backup%somepassword //monster.someurl.de/cust backup%somepassword # nooby nas //nooby-nas.someurl.de/blubb-data backup%somepassword //monster.someurl.de/software backup%somepassword //monster.someurl.de/sysadmin backup%somepassword -Ursprüngliche Nachricht- Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] Gesendet: Dienstag, 19. April 2016 18:12 An: Tobias Köck Cc: AMANDA users Betreff: Re: AW: sendbackup: critical (fatal): error [no backup size line] Can you post your /etc/amandapass file in attachment? Substitute your password by a random string Jean-Louis On 19/04/16 11:47 AM, Tobias Köck wrote: > Hey Jean-Louis, > > I tried your patch. If I run amcheck -c blubberdiblibb it gives me > another error by not finding the password but I am sure I have > included the password (and it's not empty) in the /etc/amandapass in > the right format > > Logs: > > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: pid 8732 ruid 34 > euid 34 version 3.3.8: start at Tue Apr 19 17:28:09 2016 Tue Apr 19 > 17:28:09 2016: thd-0x18e0200: Amsamba: Arguments: selfcheck Tue Apr 19 > 17:28:09 2016: thd-0x18e0200: Amsamba: pid 8732 ruid 34 euid 34 > version 3.3.8: rename at Tue Apr 19 17:28:09 2016 Tue Apr 19 17:28:09 > 2016: thd-0x18e0200: Amsamba: application: Amsamba > > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: warning: Use of > uninitialized value $regex_match in pattern match (m//) at > /usr/lib/amanda/application/amsamba line 91. > > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: Arguments: selfcheck > --message line --config blubberdiblubb --host localhost --disk > //monster.someurl.de/austausch --device //monster.someurl.de/austausch > --index line --record --amandapass /etc/amandapass Tue Apr 19 17:28:09 > 2016: thd-0x18e0200: Amsamba: command: selfcheck Tue Apr 19 17:28:09 > 2016: thd-0x18e0200: Amsamba: disk //monster.someurl.de/austausch Tue > Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: amsamba version 3.3.8 > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: amsamba > smbclient-version 4.3.8-Debian Tue Apr 19 17:28:09 2016: thd-0x18e0200: > Amsamba: /usr/bin/smbclient Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: > amandapass: /etc/amandapass Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: > password_rdr 3 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: warning: > close() on unopened filehandle 1 at /usr/lib/amanda/application/amsamba line > 426. > > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: password_wtr 4 Tue > Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: warning: close() on unopened > filehandle 2 at /usr/lib/amanda/application/amsamba line 427. > > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: execute: > /usr/bin/smbclient /usr/bin/smbclient //monster.someurl.de/austausch > -U backup -E -c quit Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: > stderr: WARNING: The "syslog" option is deprecated Tue Apr 19 17:28:09 > 2016: thd-0x18e0200: Amsamba: smbclient: WARNING: The "syslog" option > is deprecated Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: stderr: Error > reading password from file descriptor 3: empty password Tue Apr 19 17:28:09 > 2016: thd-0x18e0200: Amsamba: smbclient: Error reading password from file > descriptor 3: empty password Tue Apr 19 17:28:09 2016: thd-0x18e0200: > Amsamba: stderr: > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: smbclient: > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: stderr: Domain=[someurl] > OS=[Unix] Server=[Samba 3.6.24] > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_utime : 0 > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_stime : 0 > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_maxrss : 23572 > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_ixrss : 0 > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_idrss : 0 > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_isrss : 0 > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_minflt : 3839 > Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba:
AW: sendbackup: critical (fatal): error [no backup size line]
Hey Jean-Louis, I tried your patch. If I run amcheck -c blubberdiblibb it gives me another error by not finding the password but I am sure I have included the password (and it's not empty) in the /etc/amandapass in the right format Logs: Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: pid 8732 ruid 34 euid 34 version 3.3.8: start at Tue Apr 19 17:28:09 2016 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: Arguments: selfcheck Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: pid 8732 ruid 34 euid 34 version 3.3.8: rename at Tue Apr 19 17:28:09 2016 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: application: Amsamba Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: warning: Use of uninitialized value $regex_match in pattern match (m//) at /usr/lib/amanda/application/amsamba line 91. Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: Arguments: selfcheck --message line --config blubberdiblubb --host localhost --disk //monster.someurl.de/austausch --device //monster.someurl.de/austausch --index line --record --amandapass /etc/amandapass Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: command: selfcheck Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: disk //monster.someurl.de/austausch Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: amsamba version 3.3.8 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: amsamba smbclient-version 4.3.8-Debian Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: /usr/bin/smbclient Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: amandapass: /etc/amandapass Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: password_rdr 3 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: warning: close() on unopened filehandle 1 at /usr/lib/amanda/application/amsamba line 426. Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: password_wtr 4 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: warning: close() on unopened filehandle 2 at /usr/lib/amanda/application/amsamba line 427. Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: execute: /usr/bin/smbclient /usr/bin/smbclient //monster.someurl.de/austausch -U backup -E -c quit Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: stderr: WARNING: The "syslog" option is deprecated Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: smbclient: WARNING: The "syslog" option is deprecated Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: stderr: Error reading password from file descriptor 3: empty password Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: smbclient: Error reading password from file descriptor 3: empty password Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: stderr: Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: smbclient: Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: stderr: Domain=[someurl] OS=[Unix] Server=[Samba 3.6.24] Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_utime : 0 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_stime : 0 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_maxrss : 23572 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_ixrss : 0 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_idrss : 0 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_isrss : 0 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_minflt : 3839 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_majflt : 0 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_nswap : 0 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_inblock : 0 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_oublock : 16 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_msgsnd : 0 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_msgrcv : 0 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_nsignals: 0 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_nvcsw : 10 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: ru_nivcsw : 579 Tue Apr 19 17:28:09 2016: thd-0x18e0200: Amsamba: pid 8732 finish time Tue Apr 19 17:28:09 2016 -Ursprüngliche Nachricht- Von: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] Gesendet: Dienstag, 19. April 2016 12:38 An: Tobias Köck Cc: AMANDA users Betreff: Re: sendbackup: critical (fatal): error [no backup size line] There is no possible fix for the GNUTAR application (it is deprecated). If you switch to the 'amsamba' application, then the attached patch can fix it. Can someone test it? Jean-Louis On 19/04/16 05:50 AM, Tobias Köck wrote: > Hi guys, > > I got the same mentioned problem with the a newer Amanda Server and a > new smbclient > > - Package: amanda-server > Source: amanda > Version: 1:3.3.8-1 > Installed-Size: 890 > > - Package: smbclient > Source: samba > Version: 2:4.3.8+dfsg- > > - amstatus abc status > > sendbackup.20160419005647.debug:Tue Apr 19 00:56:47 2016: > thd-0x5589cc151000: sendbackup: critical (fatal): error [no backup > size line] > > - less sendbackup.20160419005647.debug > > Tue Apr 19 00:56:47 2016: thd-0x5589c
Aw: sendbackup: critical (fatal): error [no backup size line]
Hello Tobias, i have filed a bug report at Debian and Samba as they have mentioned it to be the best way to sort this out. Please feel free to help out on this wherever you can. It believe it´s a thing that must be fixed at Samba. https://bugzilla.samba.org/show_bug.cgi?id=11854 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821801 Greetings!
sendbackup: critical (fatal): error [no backup size line]
Hi guys, I got the same mentioned problem with the a newer Amanda Server and a new smbclient - Package: amanda-server Source: amanda Version: 1:3.3.8-1 Installed-Size: 890 - Package: smbclient Source: samba Version: 2:4.3.8+dfsg- - amstatus abc status sendbackup.20160419005647.debug:Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: critical (fatal): error [no backup size line] - less sendbackup.20160419005647.debug Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: pid 3141 ruid 34 euid 34 version 3.3.8: start at Tue Apr 19 00:56:47 2016 Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: Version 3.3.8 Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: pid 3141 ruid 34 euid 34 version 3.3.8: rename at Tue Apr 19 00:56:47 2016 Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: Parsed request as: program `GNUTAR' Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: disk `//monster.someurl.de/dev' Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: device `//monster.someurl.de/dev' Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: level 0 Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: since NODATE Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: options `' Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: datapath `AMANDA' Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: start: localhost://monster.someurl.de/dev lev 0 Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: gnutar: backup of \\monster.someurl.de\dev Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: Spawning "/usr/bin/smbclient smbclient "monster.someurl.de\\dev" -U backup -E -d0 -Tqca -" in pipeline Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: gnutar: /usr/bin/smbclient: pid 3144 Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: Started backup Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: Started index creator: "/bin/tar -tf - 2>/dev/null | sed -e 's/^\.//'" Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: 118: strange(?): Error reading password from file descriptor 7: empty password Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: 118: strange(?): Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: 114: normal(|): Domain=[someurl] OS=[Unix] Server=[Samba 3.6.24] Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: 118: strange(?): cli_setatr failed: NT_STATUS_ACCESS_DENIED Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: 118: strange(?): tar:712 Total bytes received: 8196 Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: Index created successfully Tue Apr 19 00:56:47 2016: thd-0x5589cc151000: sendbackup: critical (fatal): error [no backup size line] /usr/lib/amanda/libamanda-3.3.8.so(+0x2a0e7)[0x7f6df2f270e7] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_logv+0x1f4)[0x7f6df1c08944] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_log+0x8f)[0x7f6df1c08b6f] /usr/lib/amanda/sendbackup(parse_backup_messages+0x28c)[0x5589ca7352cc] /usr/lib/amanda/sendbackup(main+0x14be)[0x5589ca732c8e] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f6df11e8610] /usr/lib/amanda/sendbackup(_start+0x29)[0x5589ca733d59] - As mentioned before it works with smbclient_4.1.17+dfsg-2+deb8u1_amd64.deb Is there a solution in planing? It's not really a good thing to use a forced downgrade from smbclient. Greetings and thanks Tobias
Error on backup
Hi All. Does any one knows what this error code means FAILURE AND STRANGE DUMP SUMMARY: backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump (22576) /usr/bin/tar returned 2] backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump to tape failed] And how can I troubleshoot that, Thanks Prashant
Re: Error on backup
The DETAIL section of the report list the output of tar, you should see why it failed (exit with code 2). Jean-Louis Prashant Ramhit wrote: Hi All. Does any one knows what this error code means FAILURE AND STRANGE DUMP SUMMARY: backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump (22576) /usr/bin/tar returned 2] backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump to tape failed] And how can I troubleshoot that, Thanks Prashant
Re: Error on backup
No, it's not a system call returning with setting errno to 2. It is tar exiting with an exit status of 2. Check 'man tar' or 'info tar'. Check the DETAIL section of the report, it give the tar error message. Jean-Louis donald.ritc...@comed.com wrote: And error code 2 can be found in either /usr/include/errno.h or /usr/include/sys/errno.h, depending on your particular version of UNIX and how it structures the include files. (On Tru64 UNIX, the code is 'file or directory not found'.) Don Ritchey -Original Message- From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On Behalf Of Jean-Louis Martineau Sent: Thursday, January 29, 2009 06:01 To: Prashant Ramhit Cc: amanda-users Subject: Re: Error on backup The DETAIL section of the report list the output of tar, you should see why it failed (exit with code 2). Jean-Louis Prashant Ramhit wrote: Hi All. Does any one knows what this error code means FAILURE AND STRANGE DUMP SUMMARY: backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump (22576) /usr/bin/tar returned 2] backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump to tape failed] And how can I troubleshoot that, Thanks Prashant - ** This e-mail and any of its attachments may contain Commonwealth Edison Company proprietary information, which is privileged, confidential, or subject to copyright belonging to Commonwealth Edison Company or its affiliates. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. **
error in backup amanda
Greeting, since a number of days Amanda reports: FAILURE AND STRANGE DUMP SUMMARY: fiume.localnet / lev 0 STRANGE The details given below in the backup report are: FAILED AND STRANGE DUMP DETAILS: /-- fiume.localnet / lev 0 STRANGE sendbackup: start [fiume.localnet:/ level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -xpGf - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: ./etc/amanda/daily/index/stremen.localnet/_srv/20071201110501_0.gz.tmp: Warning: Cannot stat: No such file or directory | Total bytes written: 203837440 (195MiB, 7.5MiB/s) sendbackup: size 199060 sendbackup: end Indeed, that file 20071201110501_0.gz.tmp does not exist,although a file with the same name without the .tmp extension does exist in /etc/amanda/daily/index/stremen.localnet/_srv/ and also seems to be correct (it contains the list of files to be backed up). fiume is a client PC, the 2 other DLE's on fiume do not give errors. Is this something to worry about, or can I ignore this? Regards, Charles -- Charles Stroom email: charles at no-spam.stremen.xs4all.nl (remove the no-spam.)
Re: error in backup amanda
On Sun, Dec 02, 2007 at 01:36:15PM +0100, Charles Stroom wrote: Greeting, since a number of days Amanda reports: FAILURE AND STRANGE DUMP SUMMARY: fiume.localnet / lev 0 STRANGE The details given below in the backup report are: FAILED AND STRANGE DUMP DETAILS: /-- fiume.localnet / lev 0 STRANGE sendbackup: start [fiume.localnet:/ level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -xpGf - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: ./etc/amanda/daily/index/stremen.localnet/_srv/20071201110501_0.gz.tmp: Warning: Cannot stat: No such file or directory | Total bytes written: 203837440 (195MiB, 7.5MiB/s) sendbackup: size 199060 sendbackup: end Indeed, that file 20071201110501_0.gz.tmp does not exist,although a file with the same name without the .tmp extension does exist in /etc/amanda/daily/index/stremen.localnet/_srv/ and also seems to be correct (it contains the list of files to be backed up). fiume is a client PC, the 2 other DLE's on fiume do not give errors. Is this something to worry about, or can I ignore this? You are backing up the directory tree that contains the amanda logs and indexes. This is a difficult thing. How does one get a clean backup of something that is actively changing while it is being backed up? The actual message you see arises because of the two step nature of the backup. First a list of files that need to be backed up is created, then in a second step they are actually backed up. What you are seeing is a file has disappeared between the two steps. And probably a new one (with out the .tmp extension) appeared that was not there during the first step of creating the list. You will also see similar messages of the form file changed as we were backing it up. So you need to ask yourself several questions: - how important is a file named xxx.tmp - how important is a file that existed only for a brief time - how annoying are the messages - how much work is it to avoid the messages Ways to avoid them: - tell amanda those are normal messages but you will then miss them when a real problem occurs - create an exclude that eliminates *.tmp files - find a way to create a read-only file system and back that up rather than the live read/write one - find an alternative to backing up the amanda tree -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: error in backup amanda
On Wed, 5 Dec 2007 13:18:37 -0500 Jon LaBadie [EMAIL PROTECTED] wrote: On Sun, Dec 02, 2007 at 01:36:15PM +0100, Charles Stroom wrote: Greeting, since a number of days Amanda reports: FAILURE AND STRANGE DUMP SUMMARY: fiume.localnet / lev 0 STRANGE The details given below in the backup report are: FAILED AND STRANGE DUMP DETAILS: /-- fiume.localnet / lev 0 STRANGE sendbackup: start [fiume.localnet:/ level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -xpGf - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: ./etc/amanda/daily/index/stremen.localnet/_srv/20071201110501_0.gz.tmp: Warning: Cannot stat: No such file or directory | Total bytes written: 203837440 (195MiB, 7.5MiB/s) sendbackup: size 199060 sendbackup: end Indeed, that file 20071201110501_0.gz.tmp does not exist,although a file with the same name without the .tmp extension does exist in /etc/amanda/daily/index/stremen.localnet/_srv/ and also seems to be correct (it contains the list of files to be backed up). fiume is a client PC, the 2 other DLE's on fiume do not give errors. Is this something to worry about, or can I ignore this? You are backing up the directory tree that contains the amanda logs and indexes. This is a difficult thing. How does one get a clean backup of something that is actively changing while it is being backed up? The actual message you see arises because of the two step nature of the backup. First a list of files that need to be backed up is created, then in a second step they are actually backed up. What you are seeing is a file has disappeared between the two steps. And probably a new one (with out the .tmp extension) appeared that was not there during the first step of creating the list. You will also see similar messages of the form file changed as we were backing it up. So you need to ask yourself several questions: - how important is a file named xxx.tmp - how important is a file that existed only for a brief time - how annoying are the messages - how much work is it to avoid the messages Ways to avoid them: - tell amanda those are normal messages but you will then miss them when a real problem occurs - create an exclude that eliminates *.tmp files - find a way to create a read-only file system and back that up rather than the live read/write one - find an alternative to backing up the amanda tree Thanks, you answered my question. I was not sure whether the message only related to the fact that one particular file (20071201110501_0.gz.tmp) was not existing or that that this file was essential to get a correct backup of other files. So, messages ignored! Regards, -- Charles Stroom email: charles at no-spam.stremen.xs4all.nl (remove the no-spam.)
Error in backup
Title: Message Hi, I received the following error in backup today: NOTES: planner: online.intranet.vicscouts.asn.au / 20040518 0 [dumps too big, 2897508 KB, full dump delayed] taper: tape Online-DailySet1-Tuesday kb 9021344 fm 3 [OK] Is there anything that I need to do. Will it cause any errors when I do backup today? Also, I just wanted to ask what gets excluded in the backup given the exclude file attached. Ifmy disklists are / and /online/backup/storage what gets excluded. I read in documentation somewhere that a ./diretory in the exclude list means that its the directory relative to the disk that gets backed up. Thanks, Tu ./tmp ./lib/mysql/mysql.sock ./log/messages ./log/maillog ./spool/* ./mysql/ib_logfile1 ./mysql/ibdata1 ./backup/amanda ./backup/spool
Re: samba backup error [no backup size line]
Still getting the same error message. (This happens every day during our regular backups) I'm not going to spend any time debugging or testing it as we're planning to replace Amanda by something that can handle Windows boxes better and thus it would be a wasted effort. Just wanted to make you aware that this problem apparently still exists even in the latest snapshots. Greetings, Michel - Original Message - From: Geoff Austin [EMAIL PROTECTED] Sent: Monday, December 08, 2003 20:11 Subject: Re: samba backup error [no backup size line] For various reasons too boring to go into, I have delayed making the test until next weekend, but would be very interested to know how you get on... On Mon, 2003-12-08 at 08:49, Michel Meyers wrote: I'm running Amanda 2.4.4p1-20031120 and also getting this error. (Samba version 3.0.0-Debian from Debian testing) I'll try upgrading to 2.4.4p1-20031202 to see what that gives. Greetings, Michel
Re: samba backup error [no backup size line]
On Tuesday 09 December 2003 08:38, Michel Meyers wrote: Still getting the same error message. (This happens every day during our regular backups) I'm not going to spend any time debugging or testing it as we're planning to replace Amanda by something that can handle Windows boxes better and thus it would be a wasted effort. Just wanted to make you aware that this problem apparently still exists even in the latest snapshots. Greetings, Michel I see no indication that you replaced your samba with the newest one, which is supposed to fix that problem as another poster related, the fix having gone into samba on 10-30-03. I think you are unfairly blaming amanda for what is basicly a windows problem. There are quite a few file attributes that make amanda's job relatively easy on *nix-like systems. Attributes that are not in the windows filesystem architecture in the first place. Samba does it best to invent sane substitutes for the missing data and sometimes misses the mark a bit. Thats NOT amanda's fault. - Original Message - From: Geoff Austin [EMAIL PROTECTED] Sent: Monday, December 08, 2003 20:11 Subject: Re: samba backup error [no backup size line] For various reasons too boring to go into, I have delayed making the test until next weekend, but would be very interested to know how you get on... On Mon, 2003-12-08 at 08:49, Michel Meyers wrote: I'm running Amanda 2.4.4p1-20031120 and also getting this error. (Samba version 3.0.0-Debian from Debian testing) I'll try upgrading to 2.4.4p1-20031202 to see what that gives. Greetings, Michel -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: samba backup error [no backup size line]
Sorry, I didn't know a new Samba version was required, all I read to date was that latest Amanda snapshots fix this. Must have missed the rest. And I'm not blaming Amanda for anything. I'm merely saying that we know of a solution that happens to work better and that we have decided to go there, (support for Windows not being the only feature where it offers advantages over Amanda, it can also span backups over multiple tapes, ...) and given that, I won't be able to do any further testing on this issue. Greetings, Michel - Original Message - From: Gene Heskett [EMAIL PROTECTED] Sent: Tuesday, December 09, 2003 15:41 Subject: Re: samba backup error [no backup size line] I see no indication that you replaced your samba with the newest one, which is supposed to fix that problem as another poster related, the fix having gone into samba on 10-30-03. I think you are unfairly blaming amanda for what is basicly a windows problem.
Re: samba backup error [no backup size line]
GA Samba: 3.0.0-15 GA Amanda: 2.4.4p1 I'm running Amanda 2.4.4p1-20031120 and also getting this error. (Samba version 3.0.0-Debian from Debian testing) I'll try upgrading to 2.4.4p1-20031202 to see what that gives. Greetings, Michel
Re: samba backup error [no backup size line]
Hi, Michel, on 08. Dezember 2003 at 09:49 you wrote to amanda-users: MM I'm running Amanda 2.4.4p1-20031120 and also getting this error. (Samba MM version 3.0.0-Debian from Debian testing) I'll try upgrading to MM 2.4.4p1-20031202 to see what that gives. The patch for samba3 went in on 2003-10-30. This error can occur due to other issues, too. Let us know if problems persist. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: samba backup error [no backup size line]
For various reasons too boring to go into, I have delayed making the test until next weekend, but would be very interested to know how you get on... On Mon, 2003-12-08 at 08:49, Michel Meyers wrote: I'm running Amanda 2.4.4p1-20031120 and also getting this error. (Samba version 3.0.0-Debian from Debian testing) I'll try upgrading to 2.4.4p1-20031202 to see what that gives. Greetings, Michel
samba backup error [no backup size line]
Hi, I'm new to Amanda and I'm having trouble getting a samba dump to work, I hope somebody can help me, please... My amanda server is a Redhat fedora core-1 intel, linux server. I'm able to backup linux client machines OK. I am not able to successfully backup a samba share. From reading the log file, It looks like the actual tar is running OK, but there appears to be a problem in the reporting back to the dump server. I've included the log from the samba server: [EMAIL PROTECTED] gaustin]$ cat sendbackup.20031207115510.debug sendbackup: debug 1 pid 23696 ruid 33 euid 33: start at Sun Dec 7 11:55:10 2003 /usr/lib/amanda/sendbackup: version 2.4.4p1 parsed request as: program `GNUTAR' disk `//fnp/geoff' device `//fnp/geoff' level 0 since 1970:1:1:0:0:0 options `|;auth=bsd;index;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.33162 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.33163 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.33164 sendbackup: time 0.001: waiting for connect on 33162, then 33163, then 33164 sendbackup: time 0.002: stream_accept: connection from 192.168.2.4.33165 sendbackup: time 0.002: stream_accept: connection from 192.168.2.4.33166 sendbackup: time 0.002: stream_accept: connection from 192.168.2.4.33167 sendbackup: time 0.002: got all connections sendbackup-gnutar: time 0.006: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup-gnutar: time 0.008: backup of \\fnp\geoff sendbackup: time 0.009: spawning /usr/bin/smbclient in pipeline sendbackup: argument list: smbclient \\fnp\geoff -U gaustin -E -d0 -Tqca - sendbackup: time 0.014: started index creator: /bin/tar -tf - 2/dev/null | sed -e 's/^\.//' sendbackup-gnutar: time 0.019: /usr/bin/smbclient: pid 23701 sendbackup: time 9.627: 126: strange(?): [2003/12/07 11:55:20, 0] client/clitar.c:process_tar(1433) sendbackup: time 9.628: 126: strange(?): tar: dumped 18 files and directories sendbackup: time 9.628: 126: strange(?): [2003/12/07 11:55:20, 0] client/clitar.c:process_tar(1434) sendbackup: time 9.629: 126: strange(?): Total bytes written: 31640576 sendbackup: time 9.630: index created successfully sendbackup: time 9.632: error [no backup size line] sendbackup: time 9.632: pid 23696 finish time Sun Dec 7 11:55:20 2003 [EMAIL PROTECTED] gaustin]$ Many Thanks, Geoff
Re: samba backup error [no backup size line]
Hi, Geoff Austin, on Sonntag, 07. Dezember 2003 at 14:52 you wrote to amanda-users: GA Hi, GA I'm new to Amanda and I'm having trouble getting a samba dump to work, GA I hope somebody can help me, please... GA My amanda server is a Redhat fedora core-1 intel, linux server. GA I'm able to backup linux client machines OK. GA I am not able to successfully backup a samba share. From reading the log file, It looks like the actual tar is running OK, GA but there appears to be a problem in the reporting back to the dump GA server. Which versions of AMANDA and Samba? You have to use one of the latest AMANDA-snapshots to be able to use Samba 3. This combination is well known to behave the way you reported. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: samba backup error [no backup size line]
Hi Stefan, On Sun, 2003-12-07 at 15:22, Stefan G. Weichinger wrote: Which versions of AMANDA and Samba? You have to use one of the latest AMANDA-snapshots to be able to use Samba 3. This combination is well known to behave the way you reported. Samba: 3.0.0-15 Amanda: 2.4.4p1 I'll have a look at the snapshot. Many Thanks for your help Stefan, Geoff
Re: samba backup error [no backup size line]
Hi, Geoff, on Sonntag, 07. Dezember 2003 at 19:03 you wrote to amanda-users: GA Samba: 3.0.0-15 GA Amanda: 2.4.4p1 GA I'll have a look at the snapshot. That´s the way to go in your case. GA Many Thanks for your help Stefan, You´re welcome. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
