>> From: Gunnarsson, Gunnar
>> Sent: Tuesday, March 22, 2022 9:30 AM
>> To: Chris Hassell ; li...@xunil.at; ? amanda users
>>
>> Subject: SV: Sent out a pull-request to upgrade the packaging system
>>
>> WARNING: This email originated from
Hassell ; li...@xunil.at; ? amanda users
>
> Subject: SV: Sent out a pull-request to upgrade the packaging system
>
> WARNING: This email originated from outside of BETSOL. Do not click links or
> open attachments unless you recognize the sender and know the content is safe
Hi,
I'm testing the amanda-3_5-packaging-upgrade-wip and now it builds on my
solaris 11.4 system.
Amrecover fails to connect to the amindexd server see trace from below.
Complains about too big message size see trace below.
Server works if the amrecover client is 3.4.5 and the backup
da.org>
> Subject: Re: Sent out a pull-request to upgrade the packaging system
>
> WARNING: This email originated from outside of BETSOL. Do not click links or
> open attachments unless you recognize the sender and know the content is safe.
>
>
> Am 17.03.22 um 2
> Sent: Friday, March 18, 2022 3:31 AM
> To: Chris Hassell ; ? amanda users us...@amanda.org>
> Subject: Re: Sent out a pull-request to upgrade the packaging system
>
> WARNING: This email originated from outside of BETSOL. Do not click links or
> open attachments unle
collect2: error: ld returned 1 exit status
gmake[3]: *** [Makefile:2371: amflock-test] Error 1
gmake[3]: Leaving directory
'/root/amanda_compile/amanda-3_5-packaging-upgrade-wip/amanda/common-src'
gmake[2]: *** [Makefile:2171: all] Error 2
gmake[2]: Leaving directory
'/root/amanda_compile/amanda-3
Hi,
git clone -b 3_5-packaging-upgrade-wip https://github.com/zmanda/amanda.git
git branch
* 3_5-packaging-upgrade-wip
On solaris these packages are needed
pkg install git automake autoconf pkg:/developer/build/libtool gcc
cd Amanda
./autogen
+ set -x
+ /usr/bin/autoconf
configure.ac:25
Am 17.03.22 um 22:28 schrieb Chris Hassell:
First of many. It is not configured-and-tested as is but it is very
close to our working version.
-Versioning based on tags from git
-An in-directory build as well as below-directory package build
-Solaris 10 and Solaris 11 packages
-Better
First of many. It is not configured-and-tested as is but it is very close to
our working version.
-Versioning based on tags from git
-An in-directory build as well as below-directory package build
-Solaris 10 and Solaris 11 packages
-Better handling of pre/post
I've upgraded our backup server from Ubuntu 16.04.5 to 18.04.1.
This gave us amanda 3.5.1-1build2 (before upgrade: 3.3.6-4.1).
Our daily routine is:
amdump to disk
amvault to tape library
amcheckdump the tapes
The new amcheckdump 3.5.1 is giving us trouble: It's using 100% cpu
----
> >> From: Seann [mailto:nombran...@tsukinokage.net]
> >> Sent: Thursday, September 24, 2015 06:35 PM
> >> To: Debra S Baddorf ; Joi L. Ellis
> >>
> >> Cc: amanda-users@amanda.org
> >> Subject: Re: Upgrade woes and eternal hanging of dumps
&
Am 2016-04-22 um 08:08 schrieb Traugott Simon:
> I have filed a bug report about this at Samba and Debian:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821801
> https://bugzilla.samba.org/show_bug.cgi?id=11854
Thanks for doing that. bug-reports lead to bug-fixing. Sometimes ;)
I have filed a bug report about this at Samba and Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821801
https://bugzilla.samba.org/show_bug.cgi?id=11854
Greetings
Hello together,
here you have a sample of my confi which used to work for several years.
DLE:
BACKUP02//DC03/USERDIRS root-samba
dumptype from amanda.conf
define dumptype root-samba {
program "APPLICATION"
application{
plugin "amsamba"
}
comment
Am 20.04.2016 um 15:30 schrieb Jean-Louis Martineau:
> It's hard to fix documentation when user don't tell how to improve it.
> Can you tell us the additional stuff?
You are right, sorry.
I just wanted to wait for an example, maybe I misunderstood something etc
My definitions so far, note
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.
: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] Im
Auftrag von Traugott Simon
Gesendet: Freitag, 15. April 2016 10:39
An: amanda-users@amanda.org
Betreff: Problems with amsamba on Debian Jessie since upgrade
Hello guys,
since the cirtical security update a few days ago i have
Hello guys,
since the cirtical security update a few days ago i have huge problems with
amsamba backing up Windows shares.
This is what i get for example:
FAILED DUMP DETAILS:
/-- BACKUP02 //DC03/PUBLIC lev 0 FAILED [/bin/tar: Ignoring unknown extended
header keyword 'hdrcharset']
?
Idea two: If any of the involved machines are running iptables or
ufw firewalls, verify the new configuration is still loading the
correct kernel modules. At one point the /etc/default/ufw.conf
file named kernel modules incorrectly after an upgrade, and/or the
nf_conntrack_amanda module itself
cp if you don't provide it. Does your new configuration specify
>>> that those clients must be reached with -auth=bsd from the new server,
>>> rather than the server's new default of -auth=bsdctp?
>>>
>>> Idea two: If any of the involved machines are running iptable
r 24, 2015 06:35 PM
> To: Debra S Baddorf <badd...@fnal.gov>; Joi L. Ellis
> <jlel...@pavlovmedia.com>
> Cc: amanda-users@amanda.org
> Subject: Re: Upgrade woes and eternal hanging of dumps
>
> On 9/21/2015 11:36 AM, Debra S Baddorf wrote:
> > YES!I agree with t
.net]
Sent: Thursday, September 24, 2015 06:35 PM
To: Debra S Baddorf <badd...@fnal.gov>; Joi L. Ellis
<jlel...@pavlovmedia.com>
Cc: amanda-users@amanda.org
Subject: Re: Upgrade woes and eternal hanging of dumps
On 9/21/2015 11:36 AM, Debra S Baddorf wrote:
YES!I agree wi
are running iptables or ufw
firewalls, verify the new configuration is still loading the correct kernel
modules. At one point the /etc/default/ufw.conf file named kernel modules
incorrectly after an upgrade, and/or the nf_conntrack_amanda module itself went
missing. (Some kernels cha
named kernel modules
incorrectly after an upgrade, and/or the nf_conntrack_amanda module itself went
missing. (Some kernels change the name of this module, usually it's the first
two characters.) The symptom here is that amcheck thinks everything is fine,
yet the actual amdump process fails b
are running iptables or ufw
firewalls, verify the new configuration is still loading the correct kernel
modules. At one point the /etc/default/ufw.conf file named kernel modules
incorrectly after an upgrade, and/or the nf_conntrack_amanda module itself went
missing. (Some kernels change the name
tc/default/ufw.conf file named kernel modules
> incorrectly after an upgrade, and/or the nf_conntrack_amanda module itself
> went missing. (Some kernels change the name of this module, usually it's the
> first two characters.) The symptom here is that amcheck thinks everything is
> fine, yet
-Ursprungligt meddelande-
Från: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] För
Gunnarsson, Gunnar
Skickat: den 3 september 2015 22:11
Till: Jean-Francois Malouin; amanda-users@amanda.org
Ämne: SV: Tape write rate much slower efter upgrade
I'm doing amvault from disk
Gunnar,
Do the number by DLE always differ?
Are you using a holding disk?
Can you monitor the server to find some bottleneck, memory, cpu,
network, disk I/O, ...
Jean-Louis
On 03/09/15 02:49 PM, Gunnarsson, Gunnar wrote:
Hi,
See below slow down in avg tp write rate after having upgraded
Hi,
See below slow down in avg tp write rate after having upgraded amanda from
3.2.0 to 3.3.7p1 nothing else is changed.
We are using DLT drivers SCSI and fiber connected.
Thanks Gunnar
Tape Time (hrs:min) 2:37 2:37 0:00
Tape Size (meg) 382968.9 382968.9
f my amanda server from 3.3.5 to 3.3.7.
Right away I noticed a ~25% tape write performance degradation to a LTO4
tape drive. I've attached 2 pics showing the xfer IO rate to/from the
holddisk: one shows a snapshot of the week after the upgrade with the
10th of Feb still at 3.3.5 (and a xfer rate of
-Francois Malouin
Skickat: den 3 september 2015 21:37
Till: amanda-users@amanda.org
Ämne: Re: Tape write rate much slower efter upgrade
Hi,
* Jean-Louis Martineau <martin...@zmanda.com> [20150903 15:21]:
> Gunnar,
>
> Do the number by DLE always differ?
> Are you using a holdi
On Aug 23, 2015, at 5:45 PM, Seann nombran...@tsukinokage.net wrote:
On 8/19/2015 11:12 PM, Gerrit A. Smit wrote:
Debra S Baddorf schreef op 18-08-15 om 23:21:
Thank you, Mr Troll, for complaining about our posting techniques (is
this better?) but
giving no actual help.
And you think
On 8/24/2015 11:57 AM, Debra S Baddorf wrote:
On Aug 23, 2015, at 5:45 PM, Seann nombran...@tsukinokage.net wrote:
On 8/19/2015 11:12 PM, Gerrit A. Smit wrote:
Debra S Baddorf schreef op 18-08-15 om 23:21:
Thank you, Mr Troll, for complaining about our posting techniques (is this
better?)
On Aug 24, 2015, at 1:49 PM, Seann nombran...@tsukinokage.net wrote:
On 8/24/2015 11:57 AM, Debra S Baddorf wrote:
On Aug 23, 2015, at 5:45 PM, Seann nombran...@tsukinokage.net wrote:
On 8/19/2015 11:12 PM, Gerrit A. Smit wrote:
Debra S Baddorf schreef op 18-08-15 om 23:21:
Thank you, Mr
On Mon, Aug 24, 2015 at 01:49:46PM -0500, Seann wrote:
...
The only errors for the manual run are 'Strange' errors, related to files
that either have been removed during backup, or files (log files mainly)
that have changed during the tar process.
I updated my cron tasks last night, to run
On 8/19/2015 11:12 PM, Gerrit A. Smit wrote:
Debra S Baddorf schreef op 18-08-15 om 23:21:
Thank you, Mr Troll, for complaining about our posting techniques
(is this better?) but
giving no actual help.
And you think this is appropiate?
With regards to the posting style, as 90% of my
Deb,
The CRON issue happens with, and without the two clients who fail.
All of my normal testing, and manual runs are done with the two problem
hosts disabled, because they are known problems, and I figure it is due
to large amounts of files on both of them causing a timeout.
I am working
All,
I am looking for a little direction on a problem that has cropped up for
me recently.
I have a backup set, that was created using Amanda 2.5 (default on
CentOS 5.11) and ran very well, both manually and from the cron job I
had set for it.
It has approximately 13 hosts to backup, from
Check that the parts in /etc/xinetd.d(or similar … I’m on linux) are
ALSO using amandabackup
and not your previous backup name. The services have auser=X line
in them.
Grep a bit (or maybe somebody else will join the conversation!)
My files to start the services look
Ahh. So are you saying that the other nodes work when the backup is run
manually, but hang forever when it is run from a CRON job?
That might imply permissions when run as a cron job vs live….
Deb
On Aug 17, 2015, at 3:25 PM, Seann nombran...@tsukinokage.net wrote:
Deb,
The CRON issue
Does this include the two clients who fail — do THEY also say that their
estimates are complete? Or are they still working on estimates, and thus
holding up the whole works? All of the estimates seem to need to finish,
before anybody gets to start.
Deb Baddorf
Fermilab
On Aug 17, 2015, at
Deb,
That would make sense.
On the new install, the process is using amandabackup as the user.
When I run the process manually, I run it as follows:
sudo -u amandabackup amdump DailySet1
I have the CRON scheduled in the amandabackup user CRON
Editing it using this command:
crontab -u
On Mon, Jul 18, 2011 at 09:39:15AM -0400, Brian Cuttler wrote:
It is not enough to backup different DLEs on a single client from
a single server, you the client will only communicate with a single
server at any give time.
This sounds like the answer to a question I have. Just checking:
On Fri, Aug 05, 2011 at 01:59:26PM -0400, Bryan Hodgson wrote:
On Mon, Jul 18, 2011 at 09:39:15AM -0400, Brian Cuttler wrote:
It is not enough to backup different DLEs on a single client from
a single server, you the client will only communicate with a single
server at any give time.
Jon LaBadie wrote at 18:49 -0400 on Jul 15, 2011:
On Fri, Jul 15, 2011 at 05:08:24PM -0400, Chris Hoogendyk wrote:
Thanks, Brian. So, basically, the upgrade in general is pretty
straightforward.
The key point, though, is that I am promoting an important Amanda
client
On Sat, Jul 16, 2011 at 10:43:25PM -0700, Christ Schlacta wrote:
On 7/16/2011 17:04, Chris Hoogendyk wrote:
That's perfect. I can gradually shuffle tapes over to the new system,
and, eventually, all the tapes and all the clients will be there.
During the transition, I can recover stuff from
On Fri, Jul 15, 2011 at 05:08:24PM -0400, Chris Hoogendyk wrote:
Thanks, Brian. So, basically, the upgrade in general is pretty
straightforward.
The key point, though, is that I am promoting an important Amanda client to
be the new Amanda server. During that process, there may be a period
On 7/18/11 9:39 AM, Brian Cuttler wrote:
On Sat, Jul 16, 2011 at 10:43:25PM -0700, Christ Schlacta wrote:
On 7/16/2011 17:04, Chris Hoogendyk wrote:
That's perfect. I can gradually shuffle tapes over to the new system,
and, eventually, all the tapes and all the clients will be there.
During
On Mon, 18 Jul 2011 11:32:01 -0400
Chris Hoogendyk hoogen...@bio.umass.edu wrote:
On 7/18/11 9:39 AM, Brian Cuttler wrote:
It is ALWAYS a good idea to test your restores.
A good argument can be made that you are not so much interested in
backing up your system as in being able to
On Mon, Jul 18, 2011 at 10:30:44AM -0600, Charles Curley wrote:
On Mon, 18 Jul 2011 11:32:01 -0400
Chris Hoogendyk hoogen...@bio.umass.edu wrote:
On 7/18/11 9:39 AM, Brian Cuttler wrote:
It is ALWAYS a good idea to test your restores.
A good argument can be made that you are not
On 7/18/11 12:58 PM, Brian Cuttler wrote:
On Mon, Jul 18, 2011 at 10:30:44AM -0600, Charles Curley wrote:
On Mon, 18 Jul 2011 11:32:01 -0400
Chris Hoogendykhoogen...@bio.umass.edu wrote:
On 7/18/11 9:39 AM, Brian Cuttler wrote:
It is ALWAYS a good idea to test your restores.
A good argument
On 7/15/11 6:49 PM, Jon LaBadie wrote:
On Fri, Jul 15, 2011 at 05:08:24PM -0400, Chris Hoogendyk wrote:
Thanks, Brian. So, basically, the upgrade in general is pretty straightforward.
The key point, though, is that I am promoting an important Amanda
client to be the new Amanda server. During
On 7/16/2011 17:04, Chris Hoogendyk wrote:
That's perfect. I can gradually shuffle tapes over to the new system,
and, eventually, all the tapes and all the clients will be there.
During the transition, I can recover stuff from either server
according to which was covering the period of time in
I'm in the process of doing an upgrade and thought I should check with the list before plunging
forward to see if anyone else has done it quite like this or has any comments or suggestions.
Original set up: Amanda 2.5.1p3 on a collection of E250's running Solaris 9. Spare E250 set up
, but I think I'd upgrade the
amanda version on the new server first, that way I'd potentially
put backups off-line for a single system, where as a server upgrade
might off-line backups for multiple clients.
The 3.3.0, up from 3.1.2 on the x86 and from 2.4.x (I think, it was
all of two weeks ago you
Thanks, Brian. So, basically, the upgrade in general is pretty straightforward.
The key point, though, is that I am promoting an important Amanda client to be the new Amanda
server. During that process, there may be a period of time when the old server (running 2.5.1p3)
will be talking
On Fri, Jul 15, 2011 at 05:08:24PM -0400, Chris Hoogendyk wrote:
Thanks, Brian. So, basically, the upgrade in general is pretty
straightforward.
The key point, though, is that I am promoting an important Amanda
client to be the new Amanda server. During that process, there may
be a period
Hello!
I just finished a major system upgrade on a small one-machine setup
(client=server). This involved upgrading the OS from FreeBSD 6.4 to
8.1 and also upgrading or at least rebuilding all the installed
applications. Amanda was upgraded from 2.5.1 to 3.2.0, and GNU tar
from 1.15.1
Do all tapes are listed in the tapelist file?
Do all log.dataestamp are in logdir?
What's the output of: amadmin BACKUP find
Toomas Aas wrote:
Hello!
I just finished a major system upgrade on a small one-machine setup
(client=server). This involved upgrading the OS from FreeBSD 6.4 to
8.1
On Tue, 30 Nov 2010 22:50:54 -0500, Jon LaBadie j...@jgcomp.com wrote:
On Tue, Nov 30, 2010 at 08:58:08AM -0700, Charles Curley wrote:
On Mon, 29 Nov 2010 07:08:23 -0700
m...@imparisystems.com wrote:
Basically, it appears that the executables were moved after the
upgrade - I'm doing
Basically, it appears that the executables were moved after the upgrade -
I'm doing this from memory, but I think amandad no longer is on my machine
when it used to be in /etc/amanda directory.
Has anyone else heard about this? I've been running amanda for about 2
1/2 years. What's my next
On Mon, 29 Nov 2010 07:08:23 -0700
m...@imparisystems.com wrote:
Basically, it appears that the executables were moved after the
upgrade - I'm doing this from memory, but I think amandad no longer
is on my machine when it used to be in /etc/amanda directory.
amandad as installed from
We're trying to upgrade Zmanda Client for Windows from 2.6.1.2 (At revision:
20180, Jan 8, 2010) to Version 3.1.3 (64 bit) and having problems with the
installer. Any ideas?
I did not Uninstall the current version before running Setup to upgrade the
client to ZWC-Community-3.1.3-64bit
...@yahoo.com wrote:
We're trying to upgrade Zmanda Client for Windows from 2.6.1.2 (At
revision:
20180, Jan 8, 2010) to Version 3.1.3 (64 bit) and having problems with the
installer. Any ideas?
I did not Uninstall the current version before running Setup to upgrade the
client to ZWC
On Tue, Nov 09, 2010 at 10:39:36PM +0530, Prashant Joshi wrote:
Hi Debbie,
I would need the following information to debug the issue:
1. Please send us the ZWCInstall.log located at %temp% LogFile.txt under
the ZWC install dir\Debug to debug the issue.
2. What OS is ZWC installed on?
) upgrade has installer error
Hi Debbie,
I would need the following information to debug the issue:
1. Please send us the ZWCInstall.log located at %temp% LogFile.txt under
the
ZWC install dir\Debug to debug the issue.
2. What OS is ZWC installed on?
Regards,
Prashant
On Tue, Nov 9, 2010 at 9:57 PM
-3.1.3, which is released today. It is
a patch
release in the 3.1.x series, and contains the fix for this security
vulnerability as well as fixes for several other significant bugs in
3.1.2.
This upgrade should be considered a high priority upgrade.
Updated images and tarballs are available
On Wed, Sep 15, 2010 at 12:53 AM, Marc Muehlfeld
marc.muehlf...@medizinische-genetik.de wrote:
since switching to 3.2.1, I have every day at least one (sometimes two)
Can't open data output stream: Connection refused messages in my amanda
mail. Which server is concerned differs. And it allways
Hello,
since switching to 3.2.1, I have every day at least one (sometimes two) Can't
open data output stream: Connection refused messages in my amanda mail. Which
server is concerned differs. And it allways was successfully retried. But it
came up after switching the server to 3.2.1. All
Hi All.
I am plannig to upgrade amanda version of my machines from 2.4 to 2.6.
On server side, I can find an article on amanda wiki.
(http://wiki.zmanda.com/index.php/How_To:Upgrade_from_Amanda-2.4_to_Amanda-2.6)
But I cannot find a one for client side.
Will I need to change any of amanda
Hi,
Am 09.08.2010 08:53, schrieb purpleshadow livedoor:
On server side, I can find an article on amanda wiki.
(http://wiki.zmanda.com/index.php/How_To:Upgrade_from_Amanda-2.4_to_Amanda-2.6)
But I cannot find a one for client side.
Will I need to change any of amanda clients configuration
I have tried to find this answer but cannot so I will ask here.
I am a bit behind on versions, running 2.6.0p1, and want to upgrade to 2.6.1p2.
I have downloaded, configured and made 2.6.1p2 with no problems. Before I
install it I would like to know if there is a way to test it to be sure
. Mitchell
Skickat: den 2 juli 2010 23:56
Till: Gunnarsson, Gunnar
Kopia: amanda-users@amanda.org
Ämne: Re: upgrade to 3.1.1
On Fri, Jul 2, 2010 at 4:34 PM, Gunnarsson, Gunnar gunnar.gunnars...@svk.se
wrote:
Perms are okay, it was working for versions 3.1.0.
# ls -l /etc/opt/amanda/orabck/tapelist
On Mon, Jul 5, 2010 at 6:06 AM, Gunnarsson, Gunnar
gunnar.gunnars...@svk.se wrote:
The issue is resolved it needs to have write permission in the sysconfdir
directory as well. I my case its /etc/opt/amanda which this differs from
previous versions.
I'll check this out - Amanda should at least
On Monday 05 July 2010, Dustin J. Mitchell wrote:
On Mon, Jul 5, 2010 at 6:06 AM, Gunnarsson, Gunnar
gunnar.gunnars...@svk.se wrote:
The issue is resolved it needs to have write permission in the
sysconfdir directory as well. I my case its /etc/opt/amanda which this
differs from previous
Hi,
I got this error while I upgraded from 3.1.0beta2 to 3.1.1 ?
File is ownered by the backup user.
The next tape Amanda expects to use is: 1 new tape.
FAILURE DUMP SUMMARY:
taper: FATAL Could not open '/etc/opt/amanda/orabck/tapelist'
for writing: Permission denied at
On Fri, Jul 2, 2010 at 2:44 PM, Gunnarsson, Gunnar
gunnar.gunnars...@svk.se wrote:
The next tape Amanda expects to use is: 1 new tape.
FAILURE DUMP SUMMARY:
taper: FATAL Could not open '/etc/opt/amanda/orabck/tapelist'
for writing: Permission denied at
Skickat: den 2 juli 2010 22:59
Till: Gunnarsson, Gunnar
Kopia: amanda-users@amanda.org
Ämne: Re: upgrade to 3.1.1
On Fri, Jul 2, 2010 at 2:44 PM, Gunnarsson, Gunnar gunnar.gunnars...@svk.se
wrote:
The next tape Amanda expects to use is: 1 new tape.
FAILURE DUMP SUMMARY:
taper: FATAL Could not open
] För Dustin J. Mitchell
Skickat: den 2 juli 2010 23:56
Till: Gunnarsson, Gunnar
Kopia: amanda-users@amanda.org
Ämne: Re: upgrade to 3.1.1
On Fri, Jul 2, 2010 at 4:34 PM, Gunnarsson, Gunnar gunnar.gunnars...@svk.se
wrote:
Perms are okay, it was working for versions 3.1.0.
# ls -l /etc/opt/amanda
On Fri, Jul 2, 2010 at 4:34 PM, Gunnarsson, Gunnar
gunnar.gunnars...@svk.se wrote:
Perms are okay, it was working for versions 3.1.0.
# ls -l /etc/opt/amanda/orabck/tapelist
-rw-r--r-- 1 amanda amanda 259 Jun 28 20:26
/etc/opt/amanda/orabck/tapelist
How about for the enclosing
I just upgraded from debian etch to lenny, with the upgrade
came an upgrade from amanda-server 2.5.1p1-2.1 to
amanda server 2.5.2p1-4.
There were a few permissions issues that were noted in
bug reports. However there were errors when running amcheck
that I could not find any reason
Sorry all, I just realized that I had turned off
IPv6 off in /etc/modprob.d/aliases
I turned back on only on the server and it seems
to work..
Sorry again for the known problem.
On Mon, 16 Mar 2009, Tim Johnson J. wrote:
I just upgraded from debian etch to lenny, with the upgrade
Is there anything special you have to do to upgrade from amanda 2.5.0p2-1.fc5
to the latest version?
On Mon, Aug 11, 2008 at 04:34:17PM -0400, stan wrote:
On Mon, Aug 11, 2008 at 10:24:59AM -0400, Dustin J. Mitchell wrote:
On Mon, Aug 11, 2008 at 9:26 AM, stan [EMAIL PROTECTED] wrote:
Since I install each application in /opt/{APP_NAME}, I'd prefer not to
have
the 2n'r amanda levels.
--with-sbindir=/opt/amanda2/sbin \
--with-libexecdir=/opt/amanda2/libexec \
--with-libdir=/opt/amanda2/lib \
--with-mandir=/opt/amanda2/man \
These four lines are being ignored -- thes options should not include
with-. Check the configure --help.
164 ./perlib/Amanda
This has to be
might find the time to do that. If I do, I'll ask how to submit
the patch. In the menatime, isn't AMANDA_HOME/var/lib where index files are
stored? So if I am correct, then won't this change break working systems on
an upgrade? At least untill an entire dumpcycle has been run, and new
indexes have
On Fri, Aug 08, 2008 at 10:27:30AM -0400, Dustin J. Mitchell wrote:
On Fri, Aug 8, 2008 at 9:11 AM, stan [EMAIL PROTECTED] wrote:
But 2.6 seems to be installing things in /opt/amanda/lib/amanda
Tjis is resulting in things like it looking for the config file (which is
installed in
On Mon, Aug 11, 2008 at 9:26 AM, stan [EMAIL PROTECTED] wrote:
Since I install each application in /opt/{APP_NAME}, I'd prefer not to have
the 2n'r amanda levels. In the past I used dirctives like:
--sbindir=/opt/amanda/sbin
You'll want to look at --with-amlibdir, --with-amlibexecdir, and
Op ma 11aug08 om 09:26 schreef stan:
Since I install each application in /opt/{APP_NAME}, I'd prefer not to
have the 2n'r amanda levels. In the past I used dirctives like:
--sbindir=/opt/amanda/sbin
Will doing this still work? If so, what all do I need to specif? In
the past it was:
On Mon, Aug 11, 2008 at 03:39:21PM +0200, Gerrit A. Smit -TI- wrote:
Op ma 11aug08 om 09:26 schreef stan:
Since I install each application in /opt/{APP_NAME}, I'd prefer not to
have the 2n'r amanda levels. In the past I used dirctives like:
--sbindir=/opt/amanda/sbin
Will doing
On Mon, Aug 11, 2008 at 10:24:59AM -0400, Dustin J. Mitchell wrote:
On Mon, Aug 11, 2008 at 9:26 AM, stan [EMAIL PROTECTED] wrote:
Since I install each application in /opt/{APP_NAME}, I'd prefer not to have
the 2n'r amanda levels. In the past I used dirctives like:
I am strugling with an upgrade to 2.6,0p1 , and it seems that the default
installation location of various files has changed. I build Amanda with a
little run_configure script, that specifes the various configure options,
and historically it has containde the following lines:
--prefix=/opt
On Fri, Aug 8, 2008 at 9:11 AM, stan [EMAIL PROTECTED] wrote:
But 2.6 seems to be installing things in /opt/amanda/lib/amanda
Tjis is resulting in things like it looking for the config file (which is
installed in /opt/amanda/etc/DailyDump) in /opt/amanda/etc/amanda/DailyDump
We did move some
I am attempting to upgrade my amanda installation from 2.4.4p1 to
2.5.0 for various reasons
(retiring a server that was giving me trouble, aspiring to membership
in an exclusive
club of AMANDA users, etc),
I'm using CentOS. I may disable SElinux on the machine, although
there were no avc
On Tue, Apr 15, 2008 at 5:55 PM, Dustin J. Mitchell [EMAIL PROTECTED] wrote:
On Tue, Apr 15, 2008 at 5:34 PM, FL [EMAIL PROTECTED] wrote:
Maybe it's time to contribute a rewrite
to chg-zd-mtx--unless there is an explicit inventory command I could
invoke in the changer.conf script)
That
On Tue, Apr 15, 2008 at 5:34 PM, FL [EMAIL PROTECTED] wrote:
Maybe it's time to contribute a rewrite
to chg-zd-mtx--unless there is an explicit inventory command I could
invoke in the changer.conf script)
That would be great! That script doesn't get a lot of attention.
Now with the
On Tue, Apr 15, 2008 at 6:20 PM, Dustin J. Mitchell [EMAIL PROTECTED] wrote:
On Tue, Apr 15, 2008 at 6:15 PM, FL [EMAIL PROTECTED] wrote:
... the wait completes and then
wait4(-1, [{WIFEXITED(s) WEXITSTATUS(s) == 1}], 0, NULL) = 5539
--- SIGCHLD (Child exited) @ 0 (0) ---
wait4(-1,
On Tue, Apr 15, 2008 at 6:15 PM, FL [EMAIL PROTECTED] wrote:
... the wait completes and then
wait4(-1, [{WIFEXITED(s) WEXITSTATUS(s) == 1}], 0, NULL) = 5539
--- SIGCHLD (Child exited) @ 0 (0) ---
wait4(-1,
Does this repeat? It may be running the changer through a number of slots.
If
There is more to this story: after addtressing the selinux issue,
and setting the mode of .amandahosts to 600, I now have the
following:
-sh-3.1$ amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /home/amanda/holding-disk: 104765 MB disk space
available, using
On Tue, Apr 15, 2008 at 8:24 PM, FL [EMAIL PROTECTED] wrote:
*** glibc detected *** amcheck: double free or corruption (fasttop):
0x083bef40 ***
Uh-oh! I could probably come up with 50 bugfixes that this might
correspond to over the last two years. If you're committed to
2.5.0p2, then all
1 - 100 of 268 matches
Mail list logo
