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
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
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!
Hello List,
Hello Stefan,
how did it went out?
Greetings
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.
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
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
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?
Hello again,
here you have the full anonymized report from amreport
http://pastebin.com/MXgVFfb6
Greetings
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
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
: 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 ha
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-use
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
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
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
> prior
: 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
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
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
: 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 cam
: 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 k
endet: 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
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
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
>
> -
mba: 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]
Ther
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
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
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
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
...@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
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]
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:
/--
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
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
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
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
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
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
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
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
(?): 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
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
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
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
44 matches
Mail list logo
