Does this ring a bell with anyone - on a clean/fresh install of FreeBSD
11.0-RELEASE-p2 with Amanda 3.3.6 (default from Ports) things like
amtapetype -f /dev/nst0
et.al. all started to dump core:
Segmentation fault (core dumped)
With a fairly plain stacktrace:
> (gdb) bt
&
/amanda I'm seeing core files,
I don't think I've ever seen that before.
# cat /tmp/amanda/client/flower/selfcheck.20100723140106.debug
[bioxrs]: /tmp/am-inst/amanda-3.1.1 cat
/tmp/amanda/client/flower/selfcheck.20100723140106.debug
Fri Jul 23 14:01:06 2010: selfcheck: pid 14814 ruid 110 euid
While testing amrecover I got core dump see below on Solaris sparc
amrecover extract
Extracting files from holding disk on host localhost.
The following files are needed: /var/opt/amanda/hd1/20100527211005/generisgaspr0
Extracting from file /var/opt/amanda/hd1/20100527211005/generisgasproddb
Gunnar,
This bug is already fixed in the svn repository.
Thanks for testing and reporting the problem.
Jean-Louis
Gunnarsson, Gunnar wrote:
While testing amrecover I got core dump see below on Solaris sparc
amrecover extract
Extracting files from holding disk on host localhost
All,
We have been experimenting with pigz (a parallel version of gzip which
exploits multiple cores) to try and reduce the amount of time taken
when backing up DLEs using software compression (gzip). We've had
encouraging results, with the backup taking roughly half the time.
Unfortunately, the
is there anyway to reconfigure amanda on fedora core 6? i have to use
diferent user other than default user amanda.
I couldn't find the way to reconfigure, so i uninstalled amanda and
amanda package on the system which serves as client, and configure from
source. But then I always get error
Hello,
I am new to the list, I am using amanda at home (Linux) and it works
very well, it is not very simple to start ...
I want to use at my work with 2 servers on AIX 5.2.
I have downloaded the package from AIXPDSLIB and installed it,
inetd.conf should be OK, amanda.conf should be also OK.
Hi folks,
I've been implementing amanda 2.5.0p2 in our very heterogeneous
environment. One of the clients is AIX 5.2. It compiles correctly but
sendsize always dumps core. It appears to be related the addition of the
AMANDATES_FILE macro. Does this ring any bells for anyone?
Brett
On Thursday 09 November 2006 16:12, Brett Marlowe wrote:
I've been implementing amanda 2.5.0p2 in our very heterogeneous
environment. One of the clients is AIX 5.2. It compiles correctly but
sendsize always dumps core. It appears to be related the addition of the
AMANDATES_FILE macro. Does
Just in case other people hit these problems and don't check the bug
tracker - I believe I've found and fixed (at least for my config) a couple
of problems in 2.5.1p1
1582254 - under some conditions skipping a DLE (because of strategy
skip in the dumptype definition) can cause the in-code
Hello all.
I built 2.5.0p2 on Solaris 8 successfully, and have been slowly
deploying. It worked on the first system, but that was only one small
test. I installed it on another server and it worked for a small (/etc)
filesystem, but core dumped when I tried to backup another system, a
little
On Thursday 28 September 2006 13:52, Bob Kryger wrote:
Hello all.
I built 2.5.0p2 on Solaris 8 successfully, and have been slowly
deploying. It worked on the first system, but that was only one small
test. I installed it on another server and it worked for a small (/etc)
filesystem, but core
I've run amanda for years on various FreeBSD machines. I THINK in days
of old I also backed up at least one Redhat 8 client system, but the
system retired a while back so I have no data and little memory.
I'm now trying to add a Fedora 4 client, with poor results. amcheck
runs fine, but the
On Mon, Feb 20, 2006 at 05:17:16PM -0500, Drew Derbyshire enlightened us:
I've run amanda for years on various FreeBSD machines. I THINK in days
of old I also backed up at least one Redhat 8 client system, but the
system retired a while back so I have no data and little memory.
I'm now
Matt Hyclak wrote:
If I had to guess, I'd say you've got SELinux enabled and it's
interfering.
Anything in /var/log/messages to tell if that's the case?
No messages, but we have a winner anyway. I kicked SELinux down to warn
mode and *poof* now amanda works.
That will teach me to turn
On Monday 20 February 2006 17:17, Drew Derbyshire wrote:
I've run amanda for years on various FreeBSD machines. I THINK in
days of old I also backed up at least one Redhat 8 client system, but
the system retired a while back so I have no data and little memory.
I'm now trying to add a Fedora 4
You're incorrect regarding how I built it, as this was the standard
binary install via YUM. My natural expectation, proven by the
suggestion on SELinux, is that the package was built and installed
properly, but my environment had other issues.
One does not need to build it as the user who
After much digging around I found a way to always have my tape configured for
no hardware compression without my constantly having to turn it off.
Here's what I did.
I create a /etc/stinit.def file with the following entries:
# Quantum SDLT220
manufacturer=QUANTUM model=SuperDLT1 {
timeout=3600
correctly for a LTO 1 drive on a different machine.
I very recently came across this in course materials that I'm preparing
to teach. But I'd not done any testing to report it to the mailing list.
On Fedora Core 3 there is documentation under:
/usr/share/doc/mt-st-*
One file of interest
Jon LaBadie wrote:
On Fedora Core 3 there is documentation under:
/usr/share/doc/mt-st-*
One file of interest there is stinit.def.examples which has several
sample stinit.def examples for things like DDS and DLT and ??? drives.
In addition to the standard nst#/st# devices (mode 0
On Fri, Oct 14, 2005 at 05:39:51PM +0200, Paul Bijnens wrote:
Jon LaBadie wrote:
On Fedora Core 3 there is documentation under:
/usr/share/doc/mt-st-*
One file of interest there is stinit.def.examples which has several
sample stinit.def examples for things like DDS and DLT
If you head to quantum.com and do a seatch for 'linux book' they have a pdf
document that explains some of that.
Chris
-- Original Message --
Received: Fri, 14 Oct 2005 12:28:43 PM MDT
From: Jon LaBadie [EMAIL PROTECTED]
To: amanda-users@amanda.org
Subject: Re: sdlt220 on Fedora Core 4
Hi all,
When executing 'chg-scsi -genconf' a core dump is resulting.
Calling chg-scsi with other parameters is also unsuccessful:
-info: please check your config and use a config file for chg-scsi
-status /dev/lus: please check your config and use a config file for chg-scsi
-scan: gives only
Hi,
on Donnerstag, 20. Jänner 2005 at 22:22 I wrote to amanda-users:
SGW This will be added to the docs:
SGW - configure and make as $AMANDAUSER, make install as root
SGW - run ldconfig afterwards.
I edited the install.xml-file today and tried to take care of the
things mentioned in this
On Fri, Jan 21, 2005 at 11:05:23PM -0500, Gene Heskett wrote:
Most users are not that priviledged, and should not be. And thats the
main justification for a seperate user to run amanda.
Agreed 100%!
erics isn't a member of disk. (Sorry I didn't mention that.
I agree with the above so fully
On Monday 24 January 2005 13:01, Eric Siegerman wrote:
On Fri, Jan 21, 2005 at 11:05:23PM -0500, Gene Heskett wrote:
Most users are not that priviledged, and should not be. And thats
the main justification for a seperate user to run amanda.
Agreed 100%!
erics isn't a member of disk. (Sorry I
On Mon, Jan 24, 2005 at 03:51:13PM -0500, Gene Heskett wrote:
Now become 'amanda' and do an amcheck, which works just fine.
Back out of that and become 'gene' and the permissions are denied, the
user gene, even though he built it, cannot run it.
[...]
So basicly it has to be run by whomever
On Thu, Jan 20, 2005 at 10:22:16PM +0100, Stefan G. Weichinger wrote:
- configure and make as $AMANDAUSER
I don't believe this is necessary. One should avoid building
Amanda as root, but that's not because it'll cause problems for
Amanda; it's for the same reason one should avoid building
--On Friday, January 21, 2005 18:18:52 -0500 Eric Siegerman [EMAIL PROTECTED]
wrote:
On Thu, Jan 20, 2005 at 10:22:16PM +0100, Stefan G. Weichinger wrote:
- configure and make as $AMANDAUSER
I don't believe this is necessary. One should avoid building
Amanda as root, but that's not
On Fri, Jan 21, 2005 at 06:15:28PM -0600, Frank Smith wrote:
--On Friday, January 21, 2005 18:18:52 -0500 Eric Siegerman [EMAIL
PROTECTED] wrote:
On Thu, Jan 20, 2005 at 10:22:16PM +0100, Stefan G. Weichinger wrote:
- configure and make as $AMANDAUSER
I don't believe this is
On Friday 21 January 2005 18:18, Eric Siegerman wrote:
On Thu, Jan 20, 2005 at 10:22:16PM +0100, Stefan G. Weichinger wrote:
- configure and make as $AMANDAUSER
I don't believe this is necessary. One should avoid building
Amanda as root, but that's not because it'll cause problems for
Amanda;
On Friday 21 January 2005 19:15, Frank Smith wrote:
--On Friday, January 21, 2005 18:18:52 -0500 Eric Siegerman
[EMAIL PROTECTED] wrote:
On Thu, Jan 20, 2005 at 10:22:16PM +0100, Stefan G. Weichinger
wrote:
- configure and make as $AMANDAUSER
I don't believe this is necessary. One should
Hi, Gene,
on Donnerstag, 20. Jänner 2005 at 01:46 you wrote to amanda-users:
GH I post it here from time to time, but its short enough I can
GH probably abuse the list again without reaching for my nomex
GH underwear.
GH ---
GH #!/bin/sh
:-)
I will do some grep gene-script
On Thu, Jan 20, 2005 at 10:22:16PM +0100, Stefan G. Weichinger wrote:
This will be added to the docs:
- configure and make as $AMANDAUSER, make install as root
- run ldconfig afterwards.
The latter in an OS-specific manner I trust.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG
I have hard disk backups setup using amanda on Fedora Core 3. Everything is
great except when I use amrecover. Trying to restore an old file I will get tar
errors like this:
tar: ./dir/somefile: invalid sparse archive member
tar: Skipping to next header
tar: Archive contains obsolescent base-64
Matt Lung wrote:
I have hard disk backups setup using amanda on Fedora Core 3. Everything is
great except when I use amrecover. Trying to restore an old file I will get tar
errors like this:
tar: ./dir/somefile: invalid sparse archive member
tar: Skipping to next header
tar: Archive contains
On Wednesday 19 January 2005 08:25, Matt Lung wrote:
I have hard disk backups setup using amanda on Fedora Core 3.
Everything is great except when I use amrecover. Trying to restore
an old file I will get tar errors like this:
tar: ./dir/somefile: invalid sparse archive member
tar: Skipping
Matt Lung wrote:
I have hard disk backups setup using amanda on Fedora Core 3. Everything is
great except when I use amrecover. Trying to restore an old file I will get tar
errors like this:
tar: ./dir/somefile: invalid sparse archive member
tar: Skipping to next header
tar: Archive contains
Quoting Gene Heskett [EMAIL PROTECTED]:
On Wednesday 19 January 2005 08:25, Matt Lung wrote:
I have hard disk backups setup using amanda on Fedora Core 3.
Everything is great except when I use amrecover. Trying to restore
an old file I will get tar errors like this:
tar: ./dir/somefile
Matt Lung wrote:
Quoting Gene Heskett [EMAIL PROTECTED]:
If not that, then back up to 1.13-19 or 1.13-25, both are known good
with amanda.
Roll back to that RPM version build for Fedora, or abandon the RPM and go
with
source?
Personnally, I dislike RPM's. Compiling gnutar from source is easy.
(
Quoting Paul Bijnens [EMAIL PROTECTED]:
Matt Lung wrote:
Quoting Gene Heskett [EMAIL PROTECTED]:
If not that, then back up to 1.13-19 or 1.13-25, both are known good
with amanda.
Roll back to that RPM version build for Fedora, or abandon the RPM and go
with
source?
Personnally, I
Quoting Andreas Sundstrom [EMAIL PROTECTED]:
Matt Lung wrote:
I have hard disk backups setup using amanda on Fedora Core 3. Everything
is
great except when I use amrecover. Trying to restore an old file I will
get tar
errors like this:
tar: ./dir/somefile: invalid sparse archive
On Wednesday 19 January 2005 09:43, Matt Lung wrote:
Quoting Gene Heskett [EMAIL PROTECTED]:
On Wednesday 19 January 2005 08:25, Matt Lung wrote:
I have hard disk backups setup using amanda on Fedora Core 3.
Everything is great except when I use amrecover. Trying to
restore an old file I
Quoting Gene Heskett [EMAIL PROTECTED]:
On Wednesday 19 January 2005 09:43, Matt Lung wrote:
Quoting Gene Heskett [EMAIL PROTECTED]:
On Wednesday 19 January 2005 08:25, Matt Lung wrote:
I have hard disk backups setup using amanda on Fedora Core 3.
Everything is great except when I use
Core 3.
Everything is great except when I use amrecover. Trying to
restore an old file I will get tar errors like this:
tar: ./dir/somefile: invalid sparse archive member
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
Do I need to dump
On Tue, 28 Dec 2004 at 9:43pm, Michael J. Pawlowsky wrote
I keep getting pernission denied while trying to backup a logical volume
in Fedora Core 3.
The problem is that udev is creating the dev as owner root.root with 600
permissions.
I added in /etc/udev/permissions.d/50-udev.permissions
I know nothing of LVM, but I think it should still work. What backup tool
are you using (dump or tar)? If tar, amanda runs it via the setuid root
'runtar' wrapper, so tar will run as root. amcheck may well fail, IIRC,
but amdump should actually work.
I'm using dump. Basically it fails
On Wed, 29 Dec 2004 at 10:15am, Michael J. Pawlowsky wrote
I know nothing of LVM, but I think it should still work. What backup tool
are you using (dump or tar)? If tar, amanda runs it via the setuid root
'runtar' wrapper, so tar will run as root. amcheck may well fail, IIRC,
but
On Wednesday 29 December 2004 10:15, Michael J. Pawlowsky wrote:
I know nothing of LVM, but I think it should still work. What
backup tool are you using (dump or tar)? If tar, amanda runs it
via the setuid root 'runtar' wrapper, so tar will run as root.
amcheck may well fail, IIRC, but
I keep getting pernission denied while trying to backup a logical volume
in Fedora Core 3.
The problem is that udev is creating the dev as owner root.root with 600
permissions.
I added in /etc/udev/permissions.d/50-udev.permissions the line:
mapper/*:root:disk:0660
There are 2 files in /dev
seems to start up okay and all the dumper and sendsize processes seem
to start, but then driver core dumps and the following is reported in the
amdump log file:
HEAPS OF driver, taper and dumper messages here
.and then
driver: adding holding disk 0 dir /amholding2 size 768
reserving
Gene Heskett wrote:
I take it you unpacked, made, and installed amanda as root.
Generally speaking, thats a no-no.
Yes I did. But that's only for a quick test... It should not be relevant
who builds the code (only for security considerations). (Or am I wrong)?
If a segfault occoures the
.
The coredump I don't know about. Here it refuses to run amcheck as
root, returning this:
[root@coyote root]# amcheck DailySet1
amcheck: running as user root instead of amanda
[root@coyote root]#
Now, lets see if I have a fresh core in /root...
No, that was a clean exit. But then it was also
Thanks for all the help. The problem goes away as soon as I
used the following device (in changer.conf).
changerdev /dev/scsi/changer/c1t5d1
This device is created by sgen and not by st. I'll write a summary
with what I did as soon as I got amanda completely up and running.
Sven
I have a very strange problem. chg-scsi (2.4.2p2) does work if it is
called as root. When I call it as user amanda it dumpes core.
By comparing two truss files I found that there is a problem with
the permissions of the device file:
open64(/dev/rmt/1mn, O_RDWR|O_NDELAY) = 4
ioctl(4
On Saturday 10 August 2002 20:46, Sven Kirmess wrote:
I have a very strange problem. chg-scsi (2.4.2p2) does work if it
is called as root. When I call it as user amanda it dumpes core.
By comparing two truss files I found that there is a problem with
the permissions of the device file:
open64
signal 11)
Then it core dumps in the amanda configuration file directory.
Here is some output:
# gdb -n -c core /usr/local/libexec/chg-scsi
GNU gdb 5.0rh-5 Red Hat Linux 7.1
Copyright 2001 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
that is tickling this bug. I had a
segfault in chg-scsi also which in my case turned out to be a power
supply failure on the tape library. I couldn't find a core dump,
though.
Thank you in advance for your help with this matter.
Warm Regards,
Brian
when trying to label tapes on a newly created amanda (2.4.3b1) server,
amlabel does a core dump. This is running on a BSDI 4.1 box. The following
is my gdb output of the core file:
(gdb) core-file amlabel.core
Core was generated by `amlabel
What program generated the core file? Run file core and it should
tell you.
Once you know that, run gdb or dbx on the program that failed and the
core file, then type where at the prompt and post those results.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
ELF 32-bit MSB core file SPARC Version 1, from 'ufsrestore
gdb ufsrestore
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type
ELF 32-bit MSB core file SPARC Version 1, from 'ufsrestore
So this isn't an Amanda problem, but a Solaris one.
Here are some thoughts:
* Go to Sun and look for any patches to ufsdump/ufsrestore, i.e.
make sure you're running the latest version.
* Reload the image to disk by hand
On Jun 1, 2001, Denise Ives [EMAIL PROTECTED] wrote:
gdb ufsrestore
This GDB was configured as sparc-sun-solaris2.8...(no debugging symbols
found)...
(gdb)
If it was ufsrestore that crashed, you should file a bug report to
Sun.
But first, make sure this particular filesystem was dumped
63 matches
Mail list logo
