date:20170210

Re: 3.4: eject-volume=yes with interactivity keeps tape device open

2017-02-10 Thread Jean-Louis Martineau


I committed both patches.

Let me know if you have other issues or if it succeed!

Jean-Louis

On 10/02/17 09:37 AM, ts...@portrix-systems.de wrote:
A quick test with amflush on previous holding-disk content didn't show 
the issue anymore. Tape was ejected, no more locking, flushing was 
able to finish both tapes. Will try a real backup next week.


Thanks alot,
Thilo


On 09/02/17 17:33, Jean-Louis Martineau wrote:

This patch is also needed.

Please try them and let me know if they works.

Jean-Louis

On 09/02/17 10:58 AM, Jean-Louis Martineau wrote:

Hi,

Can you try the attached patch.

Jean-Louis

On 08/02/17 12:58 PM, ts...@portrix-systems.de
 wrote:
> Hi,
>
> tried this with:
>
http://www.zmanda.com/downloads/community/Amanda/3.4.2/Redhat_Enterprise_6.0/amanda-backup_server-3.4.2-1.rhel6.x86_64.rpm 


> (and also 3.4.1)
>
> Oracle Linux Server release 6.8
> # uname -rsv
> Linux 4.1.12-61.1.23.el6uek.x86_64 #2 SMP Tue Dec 20 16:51:41 PST 
2016

>
>
> Tapeinfo:
> Vendor ID: 'HP '
> Product ID: 'Ultrium 4-SCSI '
> Revision: 'H63Z'
>
>
> The test backup doesn't fit on one tape. After I get the E-Mail from
> the interactivity module, I can see with lsof that the taper still 
has

> a lock on /dev/nst1:
>
> > # lsof /dev/nst1
>> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
>> taper 1168 amandabackup 5u CHR 9,129 0t0 1812371 /dev/nst1
>
> touching the check-file looks like this in
> /var/log/amanda/server/ptxhamtest/taper.20170208122530.debug:
>
>> Wed Feb 08 16:21:12.035824026 2017: pid 1168: thd-0x240ad70: taper:
>> xfer_queue_message: MSG: > elt= version=0>
>> Wed Feb 08 16:21:12.036846793 2017: pid 1168: thd-0x240ad70: taper:
>> Building type SPLIT_FILE header of 32768-32768 bytes with
>> name='localhost' disk='/amanda/testbackupsrc' dumplevel=0 and
>> blocksize=32768
>> Wed Feb 08 16:22:52.113249836 2017: pid 1168: thd-0x240ad70: taper:
>> Device tape:/dev/nst1 error = 'No space left on device'
>> Wed Feb 08 16:22:52.113278102 2017: pid 1168: thd-0x240ad70: taper:
>> Device tape:/dev/nst1 setting status flag(s):
DEVICE_STATUS_VOLUME_ERROR
>> Wed Feb 08 16:22:53.101250403 2017: pid 1168: thd-0x240ad70: taper:
>> xfer_queue_message: MSG: > elt= version=0>
>> Wed Feb 08 16:23:19.976805822 2017: pid 1168: thd-0x1454d20: taper:
>> Will request retry of failed split part.
>> Wed Feb 08 16:23:19.977170240 2017: pid 1168: thd-0x1454d20: taper:
>> tape HAM-M-029-L4 kb 754974720 fm 73 [OK]
>> Wed Feb 08 16:23:19.980883703 2017: pid 1168: thd-0x1454d20: taper:
>> Device is in variable block size
>> Wed Feb 08 16:23:40.882859608 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 16:23:40.882974991 2017: pid 1168: thd-0x1454d20: taper:
>> cmd: /usr/bin/Mail -s AMANDA VOLUME REQUEST: new volume x...@xxx.xxx

>>
>> Wed Feb 08 16:23:50.888937917 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 16:24:00.960351367 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 16:24:10.960959061 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
> ...
>> Wed Feb 08 17:20:55.510368422 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 17:21:05.512939917 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 17:21:15.515187884 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 17:21:25.517437824 2017: pid 1168: thd-0x1454d20: taper:
>> Device tape:/dev/nst1 error = 'Can't open tape device /dev/nst1:
>> Device or resource busy'
>> Wed Feb 08 17:21:25.517455484 2017: pid 1168: thd-0x1454d20: taper:
>> Device tape:/dev/nst1 setting status flag(s): 
DEVICE_STATUS_DEVICE_BUSY

>> Wed Feb 08 17:21:25.517680908 2017: pid 1168: thd-0x1454d20: taper:
>> Slot 1 without label can be labeled
>> Wed Feb 08 17:21:25.517775016 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='fatal', message='Can't open tape
>> device /dev/nst1: Device or resource busy'
>> Wed Feb 08 17:21:25.518772880 2017: pid 1168: thd-0x1454d20: taper:
>> cmd: /usr/bin/Mail -s AMANDA VOLUME REQUEST: new volume x...@xxx.xxx

>
>
>
>
> if I remove "eject-volume yes" from amanda.conf, lsof doesn't show
>

Re: recent amanda on Debian?

2017-02-10 Thread Jean-Francois Malouin

* Jean-Louis Martineau <jmartin...@carbonite.com> [20170210 11:10]:
> valgrind is a useful tool to find memory corruption.
> 
> Try the attached patch.

Thanks Jean-Louis.

I'll try as soon as the server finishes a flush run. 
Should take a few more hours to complete.

Thanks,
jf

> 
> Jean-Louis
> 
> On 10/02/17 09:35 AM, Jean-Francois Malouin wrote:
> > * Jean-Louis Martineau <jmartin...@carbonite.com> [20170210 07:54]:
> >> Jean-Francois,
> >>
> >> I was not able to find the problem with the stacktrace.
> >>
> >> Do you have valgrind installed on your system?, if yes, can you run the
> >> following command:
> >> G_DEBUG=gc-friendly G_SLICE=always-malloc valgrind --trace-children=yes
> >> --log-file=valgrind.amtape.output --leak-check=full
> >> --leak-resolution=high --track-origins=yes amadmin top tape
> >>
> >> And send me the resulting valgrind.amtape.output file.
> > The output from valgrind file is attached.
> >
> > cheers,
> > jf
> >
> >> Jean-Louis
> >>
> >> On 09/02/17 02:19 PM, Jean-Francois Malouin wrote:
> >>> * Jean-Louis Martineau <jmartin...@carbonite.com> [20170209 14:09]:
> >>>> Jean-Francois,
> >>>>
> >>>> Can you run amadmin in gdb and get a stacktrace?
> >>>>
> >>>> $ gdb ~amanda/sbin/amadmin
> >>>> (gdb) run top tape
> >>>> (gdb) bt
> >>>> (gdb) quit
> >>>>
> >>>> Jean-Louis
> >>> Here you go:
> >>>
> >>> amanda@dow:~$ gdb ~amanda/sbin/amadmin
> >>> GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
> >>> Copyright (C) 2014 Free Software Foundation, Inc.
> >>> License GPLv3+: GNU GPL version 3 or later
> >>> <http://gnu.org/licenses/gpl.html>
> >>> This is free software: you are free to change and redistribute it.
> >>> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> >>> and "show warranty" for details.
> >>> This GDB was configured as "x86_64-linux-gnu".
> >>> Type "show configuration" for configuration details.
> >>> For bug reporting instructions, please see:
> >>> <http://www.gnu.org/software/gdb/bugs/>.
> >>> Find the GDB manual and other documentation resources online at:
> >>> <http://www.gnu.org/software/gdb/documentation/>.
> >>> For help, type "help".
> >>> Type "apropos word" to search for commands related to "word"...
> >>> Reading symbols from /opt/amanda/sbin/amadmin...(no debugging symbols
> >>> found)...done.
> >>> (gdb) run top tape
> >>> Starting program: /opt/amanda-3.4.2/sbin/amadmin top tape
> >>> [Thread debugging using libthread_db enabled]
> >>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> >>> The next Amanda should go onto 3 new tapes.
> >>> *** Error in `/opt/amanda-3.4.2/sbin/amadmin': corrupted double-linked 
> >>> list: 0x006f4710 ***
> >>> The next 3 new tapes already labelled are: NEO-T48-B00022,
> >>> NEO-T48-B00023, NEO-T48-B00024
> >>> Program received signal SIGABRT, Aborted.
> >>> 0x750ee067 in __GI_raise (sig=sig@entry=6) at 
> >>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> >>> 56  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> >>> (gdb) bt
> >>> #0  0x750ee067 in __GI_raise (sig=sig@entry=6) at 
> >>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> >>> #1  0x750ef448 in __GI_abort () at abort.c:89
> >>> #2  0x7512c1b4 in __libc_message (do_abort=do_abort@entry=1, 
> >>> fmt=fmt@entry=0x75221210 "*** Error in `%s': %s: 0x%s ***\n") at 
> >>> ../sysdeps/posix/libc_fatal.c:175
> >>> #3  0x7513198e in malloc_printerr (action=1, str=0x7521d2ec 
> >>> "corrupted double-linked list", ptr=) at malloc.c:4996
> >>> #4  0x75131c4c in malloc_consolidate (av=av@entry=0x7545e620 
> >>> ) at malloc.c:4165
> >>> #5  0x75132e98 in _int_malloc (av=0x7545e620 , 
> >>> bytes=32816) at malloc.c:3423
> >>> #6  0x75135020 in __GI___libc_malloc (bytes=32816) at 
> >>> malloc.c:2891
> >>> #7  0x7516ee31 in __alloc_dir (fd=3, close_fd=, 
> >>>

Re: recent amanda on Debian?

2017-02-10 Thread Jean-Louis Martineau

valgrind is a useful tool to find memory corruption.

Try the attached patch.

Jean-Louis

On 10/02/17 09:35 AM, Jean-Francois Malouin wrote:
> * Jean-Louis Martineau <jmartin...@carbonite.com> [20170210 07:54]:
>> Jean-Francois,
>>
>> I was not able to find the problem with the stacktrace.
>>
>> Do you have valgrind installed on your system?, if yes, can you run the
>> following command:
>> G_DEBUG=gc-friendly G_SLICE=always-malloc valgrind --trace-children=yes
>> --log-file=valgrind.amtape.output --leak-check=full
>> --leak-resolution=high --track-origins=yes amadmin top tape
>>
>> And send me the resulting valgrind.amtape.output file.
> The output from valgrind file is attached.
>
> cheers,
> jf
>
>> Jean-Louis
>>
>> On 09/02/17 02:19 PM, Jean-Francois Malouin wrote:
>>> * Jean-Louis Martineau <jmartin...@carbonite.com> [20170209 14:09]:
>>>> Jean-Francois,
>>>>
>>>> Can you run amadmin in gdb and get a stacktrace?
>>>>
>>>> $ gdb ~amanda/sbin/amadmin
>>>> (gdb) run top tape
>>>> (gdb) bt
>>>> (gdb) quit
>>>>
>>>> Jean-Louis
>>> Here you go:
>>>
>>> amanda@dow:~$ gdb ~amanda/sbin/amadmin
>>> GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
>>> Copyright (C) 2014 Free Software Foundation, Inc.
>>> License GPLv3+: GNU GPL version 3 or later
>>> <http://gnu.org/licenses/gpl.html>
>>> This is free software: you are free to change and redistribute it.
>>> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
>>> and "show warranty" for details.
>>> This GDB was configured as "x86_64-linux-gnu".
>>> Type "show configuration" for configuration details.
>>> For bug reporting instructions, please see:
>>> <http://www.gnu.org/software/gdb/bugs/>.
>>> Find the GDB manual and other documentation resources online at:
>>> <http://www.gnu.org/software/gdb/documentation/>.
>>> For help, type "help".
>>> Type "apropos word" to search for commands related to "word"...
>>> Reading symbols from /opt/amanda/sbin/amadmin...(no debugging symbols
>>> found)...done.
>>> (gdb) run top tape
>>> Starting program: /opt/amanda-3.4.2/sbin/amadmin top tape
>>> [Thread debugging using libthread_db enabled]
>>> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
>>> The next Amanda should go onto 3 new tapes.
>>> *** Error in `/opt/amanda-3.4.2/sbin/amadmin': corrupted double-linked 
>>> list: 0x006f4710 ***
>>> The next 3 new tapes already labelled are: NEO-T48-B00022,
>>> NEO-T48-B00023, NEO-T48-B00024
>>> Program received signal SIGABRT, Aborted.
>>> 0x750ee067 in __GI_raise (sig=sig@entry=6) at 
>>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
>>> 56  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
>>> (gdb) bt
>>> #0  0x750ee067 in __GI_raise (sig=sig@entry=6) at 
>>> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
>>> #1  0x750ef448 in __GI_abort () at abort.c:89
>>> #2  0x7512c1b4 in __libc_message (do_abort=do_abort@entry=1, 
>>> fmt=fmt@entry=0x75221210 "*** Error in `%s': %s: 0x%s ***\n") at 
>>> ../sysdeps/posix/libc_fatal.c:175
>>> #3  0x7513198e in malloc_printerr (action=1, str=0x7521d2ec 
>>> "corrupted double-linked list", ptr=) at malloc.c:4996
>>> #4  0x75131c4c in malloc_consolidate (av=av@entry=0x7545e620 
>>> ) at malloc.c:4165
>>> #5  0x75132e98 in _int_malloc (av=0x7545e620 , 
>>> bytes=32816) at malloc.c:3423
>>> #6  0x75135020 in __GI___libc_malloc (bytes=32816) at malloc.c:2891
>>> #7  0x7516ee31 in __alloc_dir (fd=3, close_fd=, 
>>> flags=, statp=) at 
>>> ../sysdeps/posix/opendir.c:207
>>> #8  0x774a5d19 in debug_unlink_old () from 
>>> /opt/amanda/lib/amanda/libamanda-3.4.2.so
>>> #9  0x774a6cf2 in debug_close () from 
>>> /opt/amanda/lib/amanda/libamanda-3.4.2.so
>>> #10 0x004038b7 in main ()
>>> (gdb) quit
>>> A debugging session is active.
>>>
>>>   Inferior 1 [process 4173] will be killed.
>>>
>>> Quit anyway? (y or n) y
>>>
>>> cheers,
>>> jf
>>>
>>>> On 09/02/17 01:56 PM, Jean-Francois Malouin wr

Re: recent amanda on Debian?

2017-02-10 Thread Stefan G. Weichinger

Am 2017-02-10 um 16:43 schrieb Jose M Calhariz:
> On Fri, Feb 10, 2017 at 04:23:29PM +0100, Stefan G. Weichinger
> wrote:
>> btw: I wrote to you on january 31 personally asking for
>> amanda-packages in debian.
>> 
>> my email might have been filtered to spam or so ...
>> 
> 
> I have replied to you, so maybe was my reply that was tagged as
> spam.

seems like. But this mail came in via both ml and directly.
And your spam score is low ;-) good!

my postfix-logs don't show any rejected mails from you.

the amanda.org mailserver is a bit strange (sorry, Todd ;-)), so pls
use li...@xunil.at for direct mail. my fault to write to you via
s...@amanda.org (I am subscribed to the ml with that address, though)

thanks

Re: recent amanda on Debian?

2017-02-10 Thread Jose M Calhariz

On Fri, Feb 10, 2017 at 04:23:29PM +0100, Stefan G. Weichinger wrote:
> Am 2017-02-10 um 16:13 schrieb Jose M Calhariz:
> > I have started on creating the official Debian packages of amanda
> > 3.4.2, and I would like to have beta testers, in case you are
> > interested.
> 
> sure, yes
> 
> btw: I wrote to you on january 31 personally asking for amanda-packages
> in debian.
> 
> my email might have been filtered to spam or so ...
> 

I have replied to you, so maybe was my reply that was tagged as spam.


-- 
--
Sucrilhos Multi I/O. Com saída Cereal.


signature.asc
Description: Digital signature

Re: recent amanda on Debian?

2017-02-10 Thread Jean-Francois Malouin

* Jose M Calhariz <jose.calha...@tecnico.ulisboa.pt> [20170210 10:14]:
> I have started on creating the official Debian packages of amanda
> 3.4.2, and I would like to have beta testers, in case you are
> interested.

no problem, count me in.

jf

> 
> On Thu, Feb 09, 2017 at 07:35:58PM +0100, Stefan G. Weichinger wrote:
> > 
> > Does anyone use amanda 3.4.2 packages on debian jessie already?
> > Which one, do they work?
> > 
> > I have to switch OS on a backup server and want to stay with
> > amanda-3.4.x because I need some of the latest features ...
> > 
> > self-compile, you know ... I can do but I'd like to avoid.
> > lower maintenance.
> > 
> 
> Kind regards
> Jose M Calhariz
> 
> 
> -- 
> --
> Sucrilhos Multi I/O. Com saída Cereal.

Re: recent amanda on Debian?

2017-02-10 Thread Stefan G. Weichinger

Am 2017-02-10 um 16:13 schrieb Jose M Calhariz:
> I have started on creating the official Debian packages of amanda
> 3.4.2, and I would like to have beta testers, in case you are
> interested.

sure, yes

btw: I wrote to you on january 31 personally asking for amanda-packages
in debian.

my email might have been filtered to spam or so ...

Re: recent amanda on Debian?

2017-02-10 Thread Jose M Calhariz

I have started on creating the official Debian packages of amanda
3.4.2, and I would like to have beta testers, in case you are
interested.

On Thu, Feb 09, 2017 at 07:35:58PM +0100, Stefan G. Weichinger wrote:
> 
> Does anyone use amanda 3.4.2 packages on debian jessie already?
> Which one, do they work?
> 
> I have to switch OS on a backup server and want to stay with
> amanda-3.4.x because I need some of the latest features ...
> 
> self-compile, you know ... I can do but I'd like to avoid.
> lower maintenance.
> 

Kind regards
Jose M Calhariz


-- 
--
Sucrilhos Multi I/O. Com saída Cereal.


signature.asc
Description: Digital signature

Re: 3.4: eject-volume=yes with interactivity keeps tape device open

2017-02-10 Thread tstml

A quick test with amflush on previous holding-disk content didn't show 
the issue anymore. Tape was ejected, no more locking, flushing was able 
to finish both tapes. Will try a real backup next week.


Thanks alot,
Thilo


On 09/02/17 17:33, Jean-Louis Martineau wrote:

This patch is also needed.

Please try them and let me know if they works.

Jean-Louis

On 09/02/17 10:58 AM, Jean-Louis Martineau wrote:

Hi,

Can you try the attached patch.

Jean-Louis

On 08/02/17 12:58 PM, ts...@portrix-systems.de
 wrote:
> Hi,
>
> tried this with:
>
http://www.zmanda.com/downloads/community/Amanda/3.4.2/Redhat_Enterprise_6.0/amanda-backup_server-3.4.2-1.rhel6.x86_64.rpm
> (and also 3.4.1)
>
> Oracle Linux Server release 6.8
> # uname -rsv
> Linux 4.1.12-61.1.23.el6uek.x86_64 #2 SMP Tue Dec 20 16:51:41 PST 2016
>
>
> Tapeinfo:
> Vendor ID: 'HP '
> Product ID: 'Ultrium 4-SCSI '
> Revision: 'H63Z'
>
>
> The test backup doesn't fit on one tape. After I get the E-Mail from
> the interactivity module, I can see with lsof that the taper still has
> a lock on /dev/nst1:
>
> > # lsof /dev/nst1
>> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
>> taper 1168 amandabackup 5u CHR 9,129 0t0 1812371 /dev/nst1
>
> touching the check-file looks like this in
> /var/log/amanda/server/ptxhamtest/taper.20170208122530.debug:
>
>> Wed Feb 08 16:21:12.035824026 2017: pid 1168: thd-0x240ad70: taper:
>> xfer_queue_message: MSG: > elt= version=0>
>> Wed Feb 08 16:21:12.036846793 2017: pid 1168: thd-0x240ad70: taper:
>> Building type SPLIT_FILE header of 32768-32768 bytes with
>> name='localhost' disk='/amanda/testbackupsrc' dumplevel=0 and
>> blocksize=32768
>> Wed Feb 08 16:22:52.113249836 2017: pid 1168: thd-0x240ad70: taper:
>> Device tape:/dev/nst1 error = 'No space left on device'
>> Wed Feb 08 16:22:52.113278102 2017: pid 1168: thd-0x240ad70: taper:
>> Device tape:/dev/nst1 setting status flag(s):
DEVICE_STATUS_VOLUME_ERROR
>> Wed Feb 08 16:22:53.101250403 2017: pid 1168: thd-0x240ad70: taper:
>> xfer_queue_message: MSG: > elt= version=0>
>> Wed Feb 08 16:23:19.976805822 2017: pid 1168: thd-0x1454d20: taper:
>> Will request retry of failed split part.
>> Wed Feb 08 16:23:19.977170240 2017: pid 1168: thd-0x1454d20: taper:
>> tape HAM-M-029-L4 kb 754974720 fm 73 [OK]
>> Wed Feb 08 16:23:19.980883703 2017: pid 1168: thd-0x1454d20: taper:
>> Device is in variable block size
>> Wed Feb 08 16:23:40.882859608 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 16:23:40.882974991 2017: pid 1168: thd-0x1454d20: taper:
>> cmd: /usr/bin/Mail -s AMANDA VOLUME REQUEST: new volume x...@xxx.xxx

>>
>> Wed Feb 08 16:23:50.888937917 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 16:24:00.960351367 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 16:24:10.960959061 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
> ...
>> Wed Feb 08 17:20:55.510368422 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 17:21:05.512939917 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 17:21:15.515187884 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='failed', reason='notfound',
>> message='No acceptable volumes found'
>> Wed Feb 08 17:21:25.517437824 2017: pid 1168: thd-0x1454d20: taper:
>> Device tape:/dev/nst1 error = 'Can't open tape device /dev/nst1:
>> Device or resource busy'
>> Wed Feb 08 17:21:25.517455484 2017: pid 1168: thd-0x1454d20: taper:
>> Device tape:/dev/nst1 setting status flag(s): DEVICE_STATUS_DEVICE_BUSY
>> Wed Feb 08 17:21:25.517680908 2017: pid 1168: thd-0x1454d20: taper:
>> Slot 1 without label can be labeled
>> Wed Feb 08 17:21:25.517775016 2017: pid 1168: thd-0x1454d20: taper:
>> new Amanda::Changer::Error: type='fatal', message='Can't open tape
>> device /dev/nst1: Device or resource busy'
>> Wed Feb 08 17:21:25.518772880 2017: pid 1168: thd-0x1454d20: taper:
>> cmd: /usr/bin/Mail -s AMANDA VOLUME REQUEST: new volume x...@xxx.xxx

>
>
>
>
> if I remove "eject-volume yes" from amanda.conf, lsof doesn't show
> /dev/nst1 as open after the mail and logfile looks like this when
> touching the check-file:
>
>> Sun Feb 05 22:01:45.892621331 2017: pid 14498: thd-0x36592a0:

Re: recent amanda on Debian?

2017-02-10 Thread Jean-Louis Martineau

Jean-Francois,

I was not able to find the problem with the stacktrace.

Do you have valgrind installed on your system?, if yes, can you run the 
following command:
G_DEBUG=gc-friendly G_SLICE=always-malloc valgrind --trace-children=yes 
--log-file=valgrind.amtape.output --leak-check=full 
--leak-resolution=high --track-origins=yes amadmin top tape

And send me the resulting valgrind.amtape.output file.

Jean-Louis

On 09/02/17 02:19 PM, Jean-Francois Malouin wrote:
> * Jean-Louis Martineau  [20170209 14:09]:
>> Jean-Francois,
>>
>> Can you run amadmin in gdb and get a stacktrace?
>>
>> $ gdb ~amanda/sbin/amadmin
>> (gdb) run top tape
>> (gdb) bt
>> (gdb) quit
>>
>> Jean-Louis
> Here you go:
>
> amanda@dow:~$ gdb ~amanda/sbin/amadmin
> GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
> Copyright (C) 2014 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> 
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> .
> Find the GDB manual and other documentation resources online at:
> .
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from /opt/amanda/sbin/amadmin...(no debugging symbols
> found)...done.
> (gdb) run top tape
> Starting program: /opt/amanda-3.4.2/sbin/amadmin top tape
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> The next Amanda should go onto 3 new tapes.
> *** Error in `/opt/amanda-3.4.2/sbin/amadmin': corrupted double-linked list: 
> 0x006f4710 ***
> The next 3 new tapes already labelled are: NEO-T48-B00022,
> NEO-T48-B00023, NEO-T48-B00024
> Program received signal SIGABRT, Aborted.
> 0x750ee067 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> 56  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> (gdb) bt
> #0  0x750ee067 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1  0x750ef448 in __GI_abort () at abort.c:89
> #2  0x7512c1b4 in __libc_message (do_abort=do_abort@entry=1, 
> fmt=fmt@entry=0x75221210 "*** Error in `%s': %s: 0x%s ***\n") at 
> ../sysdeps/posix/libc_fatal.c:175
> #3  0x7513198e in malloc_printerr (action=1, str=0x7521d2ec 
> "corrupted double-linked list", ptr=) at malloc.c:4996
> #4  0x75131c4c in malloc_consolidate (av=av@entry=0x7545e620 
> ) at malloc.c:4165
> #5  0x75132e98 in _int_malloc (av=0x7545e620 , 
> bytes=32816) at malloc.c:3423
> #6  0x75135020 in __GI___libc_malloc (bytes=32816) at malloc.c:2891
> #7  0x7516ee31 in __alloc_dir (fd=3, close_fd=, 
> flags=, statp=) at 
> ../sysdeps/posix/opendir.c:207
> #8  0x774a5d19 in debug_unlink_old () from 
> /opt/amanda/lib/amanda/libamanda-3.4.2.so
> #9  0x774a6cf2 in debug_close () from 
> /opt/amanda/lib/amanda/libamanda-3.4.2.so
> #10 0x004038b7 in main ()
> (gdb) quit
> A debugging session is active.
>
>  Inferior 1 [process 4173] will be killed.
>
> Quit anyway? (y or n) y
>
> cheers,
> jf
>
>> On 09/02/17 01:56 PM, Jean-Francois Malouin wrote:
>>> * Stefan G. Weichinger  [20170209 13:36]:
 Does anyone use amanda 3.4.2 packages on debian jessie already?
 Which one, do they work?
>>> I only see amanda 3.3.6 on Debian/Jessie stable repos at the moment:
>>>
>>> Inst amanda-common (1:3.3.6-4 Debian:8.7/stable [amd64])
>>> Inst amanda-server (1:3.3.6-4 Debian:8.7/stable [amd64])
>>> Inst amanda-client (1:3.3.6-4 Debian:8.7/stable [amd64])
>>>
>>> I've been running a self-compiled amanda-3.4.1 on a Jessie host for a
>>> month now with little problems so far, except this
>>>
>>> :~# su amanda -c "~amanda/sbin/amadmin top tape"
>>> The next Amanda should go onto 3 new tapes.
>>> *** Error in `/opt/amanda/sbin/amadmin': corrupted double-linked list: 
>>> 0x01153710 ***
>>> The next 3 new tapes already labelled are: NEO-T48-B00022, NEO-T48-B00023, 
>>> NEO-T48-B00024
>>>
>>> I have seen this on 3.4.1 and 3.4.2 (I just upgraded).
>>>
>>> cheers,
>>> jf
>>>
>>>
 I have to switch OS on a backup server and want to stay with
 amanda-3.4.x because I need some of the latest features ...

 self-compile, you know ... I can do but I'd like to avoid.
 lower maintenance.

Re: 3.4: eject-volume=yes with interactivity keeps tape device open

Re: recent amanda on Debian?

Re: recent amanda on Debian?

Re: recent amanda on Debian?

Re: recent amanda on Debian?

Re: recent amanda on Debian?

Re: recent amanda on Debian?

Re: recent amanda on Debian?

Re: 3.4: eject-volume=yes with interactivity keeps tape device open

Re: recent amanda on Debian?

10 matches

Site Navigation

Mail list logo

Footer information