Re: PARTIAL dump on my Fedora 26

2017-10-17 Thread Jean-Louis Martineau

On 10/10/17 03:27 AM, Henrik Johansson wrote:

Hi,

JT> If amanda-3.4.5 are OK I wait for Fedora 27, plan to upgrade 
Fedora in dec-jan.


Are there any known release-plans for amanda on CentOS-7?

Thanks,
Henrik

On 2017-10-10 00:11, Jason L Tibbitts III wrote:

"HJ" == Henrik Johansson  writes:

HJ> How old are version 3.3.3?

It's pretty old, but Red Hat is incredibly conservative regarding
updates.  It was released on January 10, 2013 but Red Hat has almost
certainly applied multiple patches to it.

HJ> The version in Fedora 26 are 3.4.5 and version 3.5 was released
HJ> 2017-09-28?

Yes.  3.5 is in Fedora rawhide and will hopefully be in Fedora 27 when
it is released.  (I have been out of town for a week and haven't had a
chance to do much testing on it but I will try to get an update
generated tomorrow.)  If you want 3.5 for Fedora 26 then I can give you
packages, but I don't think we'll be upgrading F26 (or F25) because of
the requirement for tcp_port_range in amanda-security.conf. It's not
nice when an update causes your machine to start spamming you.
They are not required in the amanda-security.conf if you configure 
amanda with --with-low-tcpportrange= and --with-udpportrange=


Jean-Louis
This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail


Re: PARTIAL dump on my Fedora 26

2017-10-10 Thread Jon LaBadie
On Tue, Oct 10, 2017 at 09:52:38AM -0500, Jason L Tibbitts III wrote:
> > "HJ" == Henrik Johansson  writes:
> 
> HJ> Are there any known release-plans for amanda on CentOS-7?
> 
> That is up to Red Hat (since CentOS almost certainly won't diverge from
> them in this instance).  They will not disclose any future plans, and
> honestly I doubt they would ever push an update to a more recent
> version.  They're not completely compatible so someone would need to 
> 
> You can, of course, build your own packages or just build from source.
> The Fedora packages will build fine; I just did a test build of the
> rawhide package on EL7.  The server package can't be installed due to a
> missing dependency on the Perl Dancer2 package, but the client packages
> should install without error.  I haven't tested any further than that,
> though.

Another alternative is the Zamanda pre-built rpm's for RHEL7.
I'm running them on CentOS7.

jl
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)


Re: PARTIAL dump on my Fedora 26

2017-10-10 Thread Jason L Tibbitts III
> "HJ" == Henrik Johansson  writes:

HJ> Are there any known release-plans for amanda on CentOS-7?

That is up to Red Hat (since CentOS almost certainly won't diverge from
them in this instance).  They will not disclose any future plans, and
honestly I doubt they would ever push an update to a more recent
version.  They're not completely compatible so someone would need to 

You can, of course, build your own packages or just build from source.
The Fedora packages will build fine; I just did a test build of the
rawhide package on EL7.  The server package can't be installed due to a
missing dependency on the Perl Dancer2 package, but the client packages
should install without error.  I haven't tested any further than that,
though.

 - J<


Re: PARTIAL dump on my Fedora 26

2017-10-10 Thread Henrik Johansson

Hi,

JT> If amanda-3.4.5 are OK I wait for Fedora 27, plan to upgrade Fedora 
in dec-jan.


Are there any known release-plans for amanda on CentOS-7?

Thanks,
Henrik

On 2017-10-10 00:11, Jason L Tibbitts III wrote:

"HJ" == Henrik Johansson  writes:

HJ> How old are version 3.3.3?

It's pretty old, but Red Hat is incredibly conservative regarding
updates.  It was released on January 10, 2013 but Red Hat has almost
certainly applied multiple patches to it.

HJ> The version in Fedora 26 are 3.4.5 and version 3.5 was released
HJ> 2017-09-28?

Yes.  3.5 is in Fedora rawhide and will hopefully be in Fedora 27 when
it is released.  (I have been out of town for a week and haven't had a
chance to do much testing on it but I will try to get an update
generated tomorrow.)  If you want 3.5 for Fedora 26 then I can give you
packages, but I don't think we'll be upgrading F26 (or F25) because of
the requirement for tcp_port_range in amanda-security.conf.  It's not
nice when an update causes your machine to start spamming you.

(In case it isn't obvious, I help maintain Amanda in Fedora.)

  - J<



--

Henrik Johansson

E-mail:   henrik.johansson.k...@mail.se
Voice:+46 924 50129
Mobile:   +46 70 555 9998
S Prästholm 799, S-955 91 Råneå, Sweden



Re: PARTIAL dump on my Fedora 26

2017-10-10 Thread Henrik Johansson

Hi,

The backups last night was OK :)

One minor question:
- Are my installation misconfigured, I have to change owner on 
directory-tree '/etc/amanda/DailySet1', after upgrades?


Thanks,
Henrik

On 2017-10-09 11:51, Henrik Johansson wrote:

Hi,

Extract some lines from the report:
...
*** A TAPE ERROR OCCURRED: [/usr/lib64/amanda/chg-disk: need 'rwx' 
access to '/etc/amanda/DailySet1'].

There are 76842540K of dumps left in the holding disk.
Run amflush to flush them to tape.

The next tape Amanda expects to use is: DailySet1-18.
STRANGE DUMP SUMMARY:
  uw000140.kank.se / lev 1  STRANGE (see below)
  uw000140.kank.se /home lev 1  STRANGE (see below)

uw000140.kank.se    /   1  3703760  3703760 --    8:12 7525.0
uw000140.kank.se    /boot   1   40   40 --    0:00 347.0
uw000140.kank.se    /home   1 72334740 72334740 --  136:56 8803.9

I've changed owner and group of /etc/amanda/DailySet1, and started 
'amflush DailySet1'.

'amflush DailySet1' moved 46 GB to DailySet1-18.

Henrik


On 2017-10-08 22:33, Jon LaBadie wrote:

On Sun, Oct 08, 2017 at 10:53:35AM +0200, Henrik Johansson wrote:

Hi again,

I checked this list once again and a similar problem (attached).
My server has CentOS-7 and the problem started after the upgrade:
 Updated 
amanda-3.3.3-17.el7.x86_64   @base

 Update 3.3.3-18.el7.x86_64 @base
 Updated 
amanda-client-3.3.3-17.el7.x86_64    @base

 Update 3.3.3-18.el7.x86_64    @base
 Updated 
amanda-libs-3.3.3-17.el7.x86_64  @base

 Update 3.3.3-18.el7.x86_64  @base
 Updated 
amanda-server-3.3.3-17.el7.x86_64    @base

 Update 3.3.3-18.el7.x86_64    @base

I've tried to downgrade, but the old package aren't available.

Henrik,

I too am running my amanda server on CentOS7.

I do not remember the symptoms but I could not get the CentOS
packages running to my satisfaction.  It may have been that
I could not get "on demand" backup from laptops with the
CentOS packages.

I elected to remove the CentOS packages and install a package
from the Zamanda website built for RHEL7.  The version I
installed was 3.4.1-1 and there are several newer versions
available now.

The changeover for me was painless.  I don't think I had to
make a single configuration change.  YMMV.

BTW I run with both user "amanda" and "amandabackup".  I.e.
separate /etc/{passwd,group} entries but same user data.
I started this at a time when the OS packages used amanda
and the Zmanda packages used amandabackup.  Now it is just
easier to "su amanda" rather than "su amandabackup"  :))

Jon




--

Henrik Johansson

E-mail:   henrik.johansson.k...@mail.se
Voice:+46 924 50129
Mobile:   +46 70 555 9998
S Prästholm 799, S-955 91 Råneå, Sweden



Re: PARTIAL dump on my Fedora 26

2017-10-09 Thread Jason L Tibbitts III
> "HJ" == Henrik Johansson  writes:

HJ> How old are version 3.3.3?

It's pretty old, but Red Hat is incredibly conservative regarding
updates.  It was released on January 10, 2013 but Red Hat has almost
certainly applied multiple patches to it.

HJ> The version in Fedora 26 are 3.4.5 and version 3.5 was released
HJ> 2017-09-28?

Yes.  3.5 is in Fedora rawhide and will hopefully be in Fedora 27 when
it is released.  (I have been out of town for a week and haven't had a
chance to do much testing on it but I will try to get an update
generated tomorrow.)  If you want 3.5 for Fedora 26 then I can give you
packages, but I don't think we'll be upgrading F26 (or F25) because of
the requirement for tcp_port_range in amanda-security.conf.  It's not
nice when an update causes your machine to start spamming you.

(In case it isn't obvious, I help maintain Amanda in Fedora.)

 - J<


Re: PARTIAL dump on my Fedora 26

2017-10-09 Thread Henrik Johansson

Hi,

Extract some lines from the report:
...
*** A TAPE ERROR OCCURRED: [/usr/lib64/amanda/chg-disk: need 'rwx' 
access to '/etc/amanda/DailySet1'].

There are 76842540K of dumps left in the holding disk.
Run amflush to flush them to tape.

The next tape Amanda expects to use is: DailySet1-18.
STRANGE DUMP SUMMARY:
  uw000140.kank.se / lev 1  STRANGE (see below)
  uw000140.kank.se /home lev 1  STRANGE (see below)

uw000140.kank.se    /   1  3703760  3703760 --    8:12 7525.0
uw000140.kank.se    /boot   1   40   40 --    0:00 347.0
uw000140.kank.se    /home   1 72334740 72334740 --  136:56 8803.9

I've changed owner and group of /etc/amanda/DailySet1, and started 
'amflush DailySet1'.

'amflush DailySet1' moved 46 GB to DailySet1-18.

Henrik


On 2017-10-08 22:33, Jon LaBadie wrote:

On Sun, Oct 08, 2017 at 10:53:35AM +0200, Henrik Johansson wrote:

Hi again,

I checked this list once again and a similar problem (attached).
My server has CentOS-7 and the problem started after the upgrade:
     Updated amanda-3.3.3-17.el7.x86_64   @base
     Update 3.3.3-18.el7.x86_64   @base
     Updated amanda-client-3.3.3-17.el7.x86_64    @base
     Update 3.3.3-18.el7.x86_64    @base
     Updated amanda-libs-3.3.3-17.el7.x86_64  @base
     Update 3.3.3-18.el7.x86_64  @base
     Updated amanda-server-3.3.3-17.el7.x86_64    @base
     Update 3.3.3-18.el7.x86_64    @base

I've tried to downgrade, but the old package aren't available.

Henrik,

I too am running my amanda server on CentOS7.

I do not remember the symptoms but I could not get the CentOS
packages running to my satisfaction.  It may have been that
I could not get "on demand" backup from laptops with the
CentOS packages.

I elected to remove the CentOS packages and install a package
from the Zamanda website built for RHEL7.  The version I
installed was 3.4.1-1 and there are several newer versions
available now.

The changeover for me was painless.  I don't think I had to
make a single configuration change.  YMMV.

BTW I run with both user "amanda" and "amandabackup".  I.e.
separate /etc/{passwd,group} entries but same user data.
I started this at a time when the OS packages used amanda
and the Zmanda packages used amandabackup.  Now it is just
easier to "su amanda" rather than "su amandabackup"  :))

Jon


--

Henrik Johansson

E-mail:   henrik.johansson.k...@mail.se
Voice:+46 924 50129
Mobile:   +46 70 555 9998
S Prästholm 799, S-955 91 Råneå, Sweden



Re: PARTIAL dump on my Fedora 26

2017-10-08 Thread Henrik Johansson

Hi,

I found previous version 3.3.3-17 for CentOS-7, downloaded and 
downgraded on my backup-server.

If it doesn't work to night, I have to find and download amanda sources.

How old are version 3.3.3?
The version in Fedora 26 are 3.4.5 and version 3.5 was released 2017-09-28?

Thanks,
Henrik

On 2017-10-08 16:06, Jean-Louis Martineau wrote:

On 08/10/17 04:53 AM, Henrik Johansson wrote:

Hi again,

I checked this list once again and a similar problem (attached).


Mathias reported that the patch I posted fixed the issue.
Have you tried the patch that was posted on that thread?

Jean-Louis


My server has CentOS-7 and the problem started after the upgrade:
    Updated amanda-3.3.3-17.el7.x86_64   
@base

    Update 3.3.3-18.el7.x86_64 @base
    Updated amanda-client-3.3.3-17.el7.x86_64    
@base

    Update 3.3.3-18.el7.x86_64    @base
    Updated amanda-libs-3.3.3-17.el7.x86_64  
@base

    Update 3.3.3-18.el7.x86_64  @base
    Updated amanda-server-3.3.3-17.el7.x86_64    
@base

    Update 3.3.3-18.el7.x86_64    @base

I've tried to downgrade, but the old package aren't available.

Regards,
Henrik

On 2017-10-04 23:11, Henrik Johansson wrote:
> Hi,
>
> Backup of my workstation are only partial, I  need som help where to
> check.
> Are there a combination of more than one problem?
>
> Extract from the email-report:
> FAILURE DUMP SUMMARY:
> centos7.opistogo.se  / lev 1  FAILED 
[data read: recv error: Resource

> temporarily unavailable]
> centos7.opistogo.se  / lev 1  was 
successfully retried
> uw000140.kank.se  /boot lev 0  FAILED 
[data read: recv error:

> Resource temporarily unavailable]
> uw000140.kank.se  /boot lev 0  FAILED 
[data read: recv error:

> Resource temporarily unavailable]
> uw000140.kank.se  /boot lev 0  partial 
taper: successfully taped a

> partial dump
> The client centos7 are on same subnet as the backup-server.
> The client uw000140 are on an other subnet with a firewall between
> backup-server and client.
>
> In the debug-files on uw000140, i found lots of "write error
> to"-messages:
> [root@uw000140 ~]# egrep -c " write error to: Bad file descriptor"
> /var/log/amanda/amandad/amandad.201710040*
> /var/log/amanda/client/DailySet1/*.201710040* | egrep -v ':0$'
> /var/log/amanda/amandad/amandad.20171004004901.debug:743574
> /var/log/amanda/amandad/amandad.20171004005007.debug:8695
> /var/log/amanda/amandad/amandad.20171004005033.debug:8530
> /var/log/amanda/amandad/amandad.20171004005055.debug:746479
> /var/log/amanda/amandad/amandad.20171004005250.debug:2259690
> /var/log/amanda/amandad/amandad.20171004005346.debug:2259069
> [root@uw000140 ~]# egrep -c " write error to: Connection reset by
> peer" /var/log/amanda/amandad/amandad.201710040*
> /var/log/amanda/client/DailySet1/*.201710040* | egrep -v ':0$'
> /var/log/amanda/amandad/amandad.20171004004901.debug:1
> /var/log/amanda/amandad/amandad.20171004005007.debug:1
> /var/log/amanda/amandad/amandad.20171004005033.debug:1
> /var/log/amanda/amandad/amandad.20171004005346.debug:1
> [root@uw000140 ~]# egrep -c " write error to: Broken pipe"
> /var/log/amanda/amandad/amandad.201710040*
> /var/log/amanda/client/DailySet1/*.201710040* | egrep -v ':0$'
> /var/log/amanda/amandad/amandad.20171004004901.debug:2
> /var/log/amanda/amandad/amandad.20171004005007.debug:12
> /var/log/amanda/amandad/amandad.20171004005033.debug:14
> /var/log/amanda/amandad/amandad.20171004005055.debug:1
> /var/log/amanda/amandad/amandad.20171004005250.debug:1
> /var/log/amanda/amandad/amandad.20171004005346.debug:8
>
> Regards,
> Henrik
>

--

Henrik Johansson

E-mail: henrik.johansson.k...@mail.se
Voice: +46 924 50129
Mobile: +46 70 555 9998
S Prästholm 799, S-955 91 Råneå, Sweden





*Disclaimer*

This message is the property of *CARBONITE, INC.* 
 and may contain confidential or privileged 
information.


If this message has been delivered to you by mistake, then do not copy 
or deliver this message to anyone. Instead, destroy it and notify me 
by reply e-mail.




--

Henrik Johansson

E-mail:   henrik.johansson.k...@mail.se
Voice:+46 924 50129
Mobile:   +46 70 555 9998
S Prästholm 799, S-955 91 Råneå, Sweden



Re: PARTIAL dump on my Fedora 26

2017-10-08 Thread Jean-Louis Martineau

On 08/10/17 04:53 AM, Henrik Johansson wrote:

Hi again,

I checked this list once again and a similar problem (attached).


Mathias reported that the patch I posted fixed the issue.
Have you tried the patch that was posted on that thread?

Jean-Louis


My server has CentOS-7 and the problem started after the upgrade:
Updated amanda-3.3.3-17.el7.x86_64   @base
Update 3.3.3-18.el7.x86_64   @base
Updated amanda-client-3.3.3-17.el7.x86_64@base
Update 3.3.3-18.el7.x86_64@base
Updated amanda-libs-3.3.3-17.el7.x86_64  @base
Update 3.3.3-18.el7.x86_64  @base
Updated amanda-server-3.3.3-17.el7.x86_64@base
Update 3.3.3-18.el7.x86_64@base

I've tried to downgrade, but the old package aren't available.

Regards,
Henrik

On 2017-10-04 23:11, Henrik Johansson wrote:
> Hi,
>
> Backup of my workstation are only partial, I  need som help where to
> check.
> Are there a combination of more than one problem?
>
> Extract from the email-report:
> FAILURE DUMP SUMMARY:
> centos7.opistogo.se 
 
/ lev 1  FAILED [data read: recv error: Resource

> temporarily unavailable]
> centos7.opistogo.se 
 
/ lev 1  was successfully retried
> uw000140.kank.se 
 
/boot lev 0  FAILED [data read: recv error:

> Resource temporarily unavailable]
> uw000140.kank.se 
 
/boot lev 0  FAILED [data read: recv error:

> Resource temporarily unavailable]
> uw000140.kank.se 
 
/boot lev 0  partial taper: successfully taped a

> partial dump
> The client centos7 are on same subnet as the backup-server.
> The client uw000140 are on an other subnet with a firewall between
> backup-server and client.
>
> In the debug-files on uw000140, i found lots of "write error
> to"-messages:
> [root@uw000140 ~]# egrep -c " write error to: Bad file descriptor"
> /var/log/amanda/amandad/amandad.201710040*
> /var/log/amanda/client/DailySet1/*.201710040* | egrep -v ':0$'
> /var/log/amanda/amandad/amandad.20171004004901.debug:743574
> /var/log/amanda/amandad/amandad.20171004005007.debug:8695
> /var/log/amanda/amandad/amandad.20171004005033.debug:8530
> /var/log/amanda/amandad/amandad.20171004005055.debug:746479
> /var/log/amanda/amandad/amandad.20171004005250.debug:2259690
> /var/log/amanda/amandad/amandad.20171004005346.debug:2259069
> [root@uw000140 ~]# egrep -c " write error to: Connection reset by
> peer" /var/log/amanda/amandad/amandad.201710040*
> /var/log/amanda/client/DailySet1/*.201710040* | egrep -v ':0$'
> /var/log/amanda/amandad/amandad.20171004004901.debug:1
> /var/log/amanda/amandad/amandad.20171004005007.debug:1
> /var/log/amanda/amandad/amandad.20171004005033.debug:1
> /var/log/amanda/amandad/amandad.20171004005346.debug:1
> [root@uw000140 ~]# egrep -c " write error to: Broken pipe"
> /var/log/amanda/amandad/amandad.201710040*
> /var/log/amanda/client/DailySet1/*.201710040* | egrep -v ':0$'
> /var/log/amanda/amandad/amandad.20171004004901.debug:2
> /var/log/amanda/amandad/amandad.20171004005007.debug:12
> /var/log/amanda/amandad/amandad.20171004005033.debug:14
> /var/log/amanda/amandad/amandad.20171004005055.debug:1
> /var/log/amanda/amandad/amandad.20171004005250.debug:1
> /var/log/amanda/amandad/amandad.20171004005346.debug:8
>
> Regards,
> Henrik
>

--

Henrik Johansson

E-mail: henrik.johansson.k...@mail.se
Voice: +46 924 50129
Mobile: +46 70 555 9998
S Prästholm 799, S-955 91 Råneå, Sweden


This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail


Re: PARTIAL dump on my Fedora 26

2017-10-08 Thread Henrik Johansson

Hi again,

I checked this list once again and a similar problem (attached).
My server has CentOS-7 and the problem started after the upgrade:
    Updated amanda-3.3.3-17.el7.x86_64   @base
    Update 3.3.3-18.el7.x86_64   @base
    Updated amanda-client-3.3.3-17.el7.x86_64    @base
    Update 3.3.3-18.el7.x86_64    @base
    Updated amanda-libs-3.3.3-17.el7.x86_64  @base
    Update 3.3.3-18.el7.x86_64  @base
    Updated amanda-server-3.3.3-17.el7.x86_64    @base
    Update 3.3.3-18.el7.x86_64    @base

I've tried to downgrade, but the old package aren't available.

Regards,
Henrik

On 2017-10-04 23:11, Henrik Johansson wrote:

Hi,

Backup of my workstation are only partial, I  need som help where to 
check.

Are there a combination of more than one problem?

Extract from the email-report:
FAILURE DUMP SUMMARY:
  centos7.opistogo.se / lev 1  FAILED [data read: recv error: Resource 
temporarily unavailable]

  centos7.opistogo.se / lev 1  was successfully retried
  uw000140.kank.se /boot lev 0  FAILED [data read: recv error: 
Resource temporarily unavailable]
  uw000140.kank.se /boot lev 0  FAILED [data read: recv error: 
Resource temporarily unavailable]
  uw000140.kank.se /boot lev 0  partial taper: successfully taped a 
partial dump

The client centos7 are on same subnet as the backup-server.
The client uw000140 are on an other subnet with a firewall between 
backup-server and client.


In the debug-files on uw000140, i found lots of "write error 
to"-messages:
[root@uw000140 ~]# egrep -c " write error to: Bad file descriptor" 
/var/log/amanda/amandad/amandad.201710040* 
/var/log/amanda/client/DailySet1/*.201710040* | egrep -v ':0$'

/var/log/amanda/amandad/amandad.20171004004901.debug:743574
/var/log/amanda/amandad/amandad.20171004005007.debug:8695
/var/log/amanda/amandad/amandad.20171004005033.debug:8530
/var/log/amanda/amandad/amandad.20171004005055.debug:746479
/var/log/amanda/amandad/amandad.20171004005250.debug:2259690
/var/log/amanda/amandad/amandad.20171004005346.debug:2259069
[root@uw000140 ~]# egrep -c " write error to: Connection reset by 
peer" /var/log/amanda/amandad/amandad.201710040* 
/var/log/amanda/client/DailySet1/*.201710040* | egrep -v ':0$'

/var/log/amanda/amandad/amandad.20171004004901.debug:1
/var/log/amanda/amandad/amandad.20171004005007.debug:1
/var/log/amanda/amandad/amandad.20171004005033.debug:1
/var/log/amanda/amandad/amandad.20171004005346.debug:1
[root@uw000140 ~]# egrep -c " write error to: Broken pipe" 
/var/log/amanda/amandad/amandad.201710040* 
/var/log/amanda/client/DailySet1/*.201710040* | egrep -v ':0$'

/var/log/amanda/amandad/amandad.20171004004901.debug:2
/var/log/amanda/amandad/amandad.20171004005007.debug:12
/var/log/amanda/amandad/amandad.20171004005033.debug:14
/var/log/amanda/amandad/amandad.20171004005055.debug:1
/var/log/amanda/amandad/amandad.20171004005250.debug:1
/var/log/amanda/amandad/amandad.20171004005346.debug:8

Regards,
Henrik



--

Henrik Johansson

E-mail:   henrik.johansson.k...@mail.se
Voice:+46 924 50129
Mobile:   +46 70 555 9998
S Prästholm 799, S-955 91 Råneå, Sweden

--- Begin Message ---
Hello!

I have a running Amanda 3.3.3 Server. The backup works without
problems. On the clients we use Amanda 3.3.0/3.3.6 and 2.6.x on some
old systems.

After migrating one of the 2.6 Clients to 3.3.0 the backup fails with:

 cl15 /var/lib/jenkins lev 0  FAILED [data read: recv error: Resource 
temporarily unavailable]
 cl15 /var/lib/jenkins lev 0  FAILED [data read: recv error: Resource 
temporarily unavailable]
 cl15 /var/lib/jenkins lev 0  partial taper: successfully taped a partial dump

That would not be a big problem but after the migration other systems
start to fail too.

What does the error message mean? Do I have to remove some old indicies
from the server? Any hints?

Thanks!
Matthias

--- End Message ---