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
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!
Re: amreport claims tape is full but it is not
I attempted Alan's suggestion and dd'd to the tape. /dev/md0 is > 130G and dd borked almost immediately: root@scriptor:/home/manager dd if=/dev/md0 of=/dev/st0 dd: writing to ‘/dev/st0’: Input/output error 3+0 records in 2+0 records out 1024 bytes (1.0 kB) copied, 15.2882 s, 0.1 kB/s Funny thing is that the Superloader passes all of its internal diagnostics as far as I can tell. Suggestions on how to verify which piece of hardware is causing the problem would be greatly appreciated. Kind regards, Chris On Fri, Apr 15, 2016 at 1:03 PM, Chris Nighswonger < cnighswon...@foundations.edu> wrote: > Well, perhaps it is a bad device. A run of amflush CONFIG resulted in > another failure: > > Fri Apr 15 11:52:31 2016: thd-0x18bae00: taper: > Quantum-Superloader3-LTO-V4: updating state > Fri Apr 15 11:52:31 2016: thd-0x18bae00: taper: > Amanda::Taper::Scan::traditional stage 2: scan for any reusable volume > Fri Apr 15 11:52:31 2016: thd-0x18bae00: taper: > Quantum-Superloader3-LTO-V4: too early for another 'status' invocation > Fri Apr 15 11:52:31 2016: thd-0x18bae00: taper: > Quantum-Superloader3-LTO-V4: loading next relative to 5: 6 > Fri Apr 15 11:52:31 2016: thd-0x18bae00: taper: > Quantum-Superloader3-LTO-V4: using drive 0 > Fri Apr 15 11:52:31 2016: thd-0x18bae00: taper: > Quantum-Superloader3-LTO-V4: unloading drive 0 > Fri Apr 15 11:52:31 2016: thd-0x18bae00: taper: invoking /usr/sbin/mtx -f > /dev/sg4 unload 5 0 > Fri Apr 15 11:53:41 2016: thd-0x18bae00: taper: > Quantum-Superloader3-LTO-V4: unload complete > Fri Apr 15 11:53:41 2016: thd-0x18bae00: taper: invoking /usr/sbin/mtx -f > /dev/sg4 load 6 0 > Fri Apr 15 11:55:01 2016: thd-0x18bae00: taper: > Quantum-Superloader3-LTO-V4: polling 'tape:/dev/nst0' to see if it's ready > Fri Apr 15 11:55:04 2016: thd-0x18bae00: taper: > Quantum-Superloader3-LTO-V4: setting current slot to 6 > Fri Apr 15 11:55:04 2016: thd-0x18bae00: taper: Slot 6 with label > campus-NGH874L4 is usable > Fri Apr 15 11:55:04 2016: thd-0x18bae00: taper: > Amanda::Taper::Scan::traditional result: 'campus-NGH874L4' on > tape:/dev/nst0 slot 6, mode 2 > Fri Apr 15 11:55:04 2016: thd-0x18bae00: taper: Amanda::Taper::Scribe > preparing to write, part size 0, using LEOM (falling back to holding disk > as cache) (splitter) (LEOM supported) > Fri Apr 15 11:55:04 2016: thd-0x18bae00: taper: Starting ( -> )> > Fri Apr 15 11:55:04 2016: thd-0x18bae00: taper: Final linkage: > -(PULL_BUFFER)-> > -(PUSH_BUFFER)-> > Fri Apr 15 11:55:09 2016: thd-0x18bae00: taper: Building type TAPESTART > header of 32768-32768 bytes with name='campus-NGH874L4' disk='' dumplevel=0 > and blocksize=32768 > Fri Apr 15 11:55:11 2016: thd-0x18bae00: taper: Device tape:/dev/nst0 > error = 'Error writing filemark: Input/output error' > Fri Apr 15 11:55:11 2016: thd-0x18bae00: taper: Device tape:/dev/nst0 > setting status flag(s): DEVICE_STATUS_DEVICE_ERROR, and > DEVICE_STATUS_VOLUME_ERROR > Fri Apr 15 11:55:27 2016: thd-0x18bae00: taper: tape campus-NGH874L4 kb 0 > fm -1 [OK] > >
Re: amreport claims tape is full but it is not
On Tuesday, April 19, 2016 09:57:32 AM Chris Nighswonger wrote: > I attempted Alan's suggestion and dd'd to the tape. /dev/md0 is > 130G and > dd borked almost immediately: > > root@scriptor:/home/manager dd if=/dev/md0 of=/dev/st0 > dd: writing to ‘/dev/st0’: Input/output error > 3+0 records in > 2+0 records out > 1024 bytes (1.0 kB) copied, 15.2882 s, 0.1 kB/s > > Funny thing is that the Superloader passes all of its internal diagnostics > as far as I can tell. > > Suggestions on how to verify which piece of hardware is causing the problem > would be greatly appreciated. > That's kind of tough unless you have either a separate tape drive, or a separate server/SAS controller/cable combination to test. It seems to be talking OK to the loader, though, so odds are it's the drive. Quantum's pretty good about taking RMA's on the Superloaders without too much fuss, as long as you have a maintenance contract in place.
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-0x5589cc151000: sendbackup: pid 3141 > ruid 34 euid 34 version 3.3.8: start at Tue Apr 19 00:56:
Re: Problems with amsamba on Debian Jessie since upgrade
Am 2016-04-15 um 11:41 schrieb Tobias Köck: > Hi there, > > as reported before I have the same problem. > > I have tried the newest update it didn't work, too. > > At the moment I have reverted to Samba version > > 4.1.17+dfsg-2 I try to use amsamba-application with amanda 3.3.9 on gentoo. Could someone provide a working example of the definition of the application using the amsamba-plugin, plus dumptype plus example DLE? To me it looks like the amsamba-manpage isn't fully correct, at least I had to specify additional stuff to make it even amcheck. Now it tells me it can't find amandapass, even when I double-checked the server/path/permissions ...