Re: AIX 5.2 core dumps
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 this ring any bells for anyone? There have certainly been issues related to that patch, though I haven't personally seen any sendsize core dumps. Care to send in a backtrace or two? --Ian -- Zmanda: Open Source Data Protection and Archiving. http://www.zmanda.com
Re: Release of amanda-2.5.1p2
Amanda 2.5.1p2 RPMs, Windows MSI, and source tar ball are available for following platforms at http://www.zmanda.com/downloads.html - Red Hat Enterprise server 4, - Red Hat Enterprise server 3 - Suse Linux Enterprise 9, - Suse Linux Enterprise 10, - Open Suse 10.0, - Fedora Core 3, - Fedora Core 4, - Fedora Core 5 - Windows XP/Windows 2003 server Paddy On 11/9/06, Jean-Louis Martineau <[EMAIL PROTECTED]> wrote: The Amanda core team is pleased to announce the release of Amanda 2.5.1p2. This is a bug fix only release, it fix all known bug in 2.5.1. Source tar ball can be downloaded from http://sourceforge.net/projects/amanda or http://www.amanda.org If you find bugs or have feature requests, please submit a bug report on sourceforge in the group v2.5.1p2. If you successfully use 2.5.1p2, please post your success reports to http://forums.zmanda.com. For list of 2.5.1 features and changes and documentation, see http://wiki.zmanda.com/index.php/2.5.1_features The list of Changes in 2.5.1p2 release: Many bugs fixed amoverview is working dumptype starttime is working Amanda command changes amtape accept the -o arguments amgetconf --list to list all tapetype, dumptype, holdingdisk or interface amgetconf can return a value of a specific tapetype, dumptype, holdingdisk or interface -- Amanda documentation: http://wiki.zmanda.com Amanda forums: http://forums.zmanda.com
Re: amanda-2.5.0p2-1.src.rpm
On 11/9/06, James Wilson <[EMAIL PROTECTED]> wrote: I apologize it seems that I was using the 2.5.0p2.tar.gz file not the sourc rpm. Does this make a difference? This should not matter. Please provide output for "amadmin xx version" Paddy
Wildcards in disklist--revisited, only using exclusions:
Hi, all.
To summarize, I'm trying to back up a hashed spool of mailboxes on our
mailserver at work. The top directory of that spool has five hundred
directories numbered 0-499 and I want to back them up a hundred at a
time over the length of the backup process.
The first time I tried, this was according to a suggestion I found in
the list archive. The backup failed because it was looking for the
"wildcards" as literal parts of the pathname and not actually globbing
as it should. For example, if I give "./[0-9]/",it would look for
pathnames containing "./[0-9]/" actually in them, not expanding them as
the wildcards I expressed them to be. The net result is that the mail
spool does not get backed up at all because it cannot find that
"pathname". The pathnames are in a file passed to the machine in
question, "trillian", then referenced by gtar's --from-file.
This time, I tried using wildcards in exclude lines. Here's my revised
disk list entries (the actual directories to be backed up are commented
out for reference's sake):
trillian /var/spool/PO/mailbox/0-99 /var/spool/PO/mailbox {
user-tar
# include "./[0-9]/" "./[1-9][0-9]/"
exclude "./[1-4][0-9][0-9]/"
} 1
[...]
trillian /var/spool/PO/mailbox/100-199 /var/spool/PO/mailbox {
user-tar
# include "./1[0-9][0-9]/"
exclude "./[0-9]/" "./[1-9][0-9]/" "./[2-4][0-9][0-9]/"
} 1
[...]
trillian /var/spool/PO/mailbox/200-299 /var/spool/PO/mailbox {
user-tar
# include "/.2[0-9][0-9]/"
exclude "./[0-9]/" "./[1-9][0-9]/" "./[1,3-4][0-9][0-9]/"
} 1
[...]
trillian /var/spool/PO/mailbox/300-399 /var/spool/PO/mailbox {
user-tar
# include "./3[0-9][0-9]/"
exclude "./[0-9]/" "./[1-9][0-9]/" "./[1-2,4][0-9][0-9]/"
} 1
[...]
trillian /var/spool/PO/mailbox/400-499 /var/spool/PO/mailbox {
user-tar
# include "./4[0-9][0-9]/"
exclude "./[0-9]/" "./[1-9][0-9]/" "./[1-3][0-9][0-9]/"
} 1
This time, the directories to be excluded end up in the same type of
file as above, but are fed via --exclude-from rather than --from-file.
I looked at the /tmp/amanda/sendbackup.*.exclude files and the
exclusions are getting in as they should.
However, they're not being PARSED as they should be.
For each stanza, it backs up ALL five hundred directories. For the
entire disklist file, it would back up the hierarchy a complete five
times. Apparently because it can't find the specified "pathname
component(s)" I'm specifying. And I suspect that again, you cannot have
wildcards in the --exclude-from file like you can't from the --from-file
file. I can't help thinking it's a gtar bug and I can't be sure whether
if it's a gtar bug or if it's that way by design, i.e. you can only
explicitly give directories or files while forbidding globbing. gtar is
taking those two files and interpreting them literally, not performing
any globbing as specified.
What am I doing wrong here? All I want to do in each case is limit it
to a certain one hundred directories and I'd like to use
well-established wildcards/globbing to enumerate them.
Thanks for any help.
--Ian.
AIX 5.2 core dumps
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
Re: amanda-2.5.0p2-1.src.rpm
I apologize it seems that I was using the 2.5.0p2.tar.gz file not the sourc rpm. Does this make a difference? Paddy Sreenivasan wrote: Did you run ./configure --with-user=amandabackup ? Please provide output of "amadmin XX config" command? Thanks, Paddy On 11/9/06, James Wilson <[EMAIL PROTECTED]> wrote: I did a make uninstall and ran ./configure again but it still comes up with the user amandabacup instead of amandabackup. How can I totally remove the configuration? Stefan G. Weichinger wrote: > James Wilson wrote: > >> I got the source bilt and changed the path to amandad in the >> /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. >> Put when I run amcheck on the server for this host it still times out. >> Any ideas? >> > > faq/doc: restart xinetd, look for /tmp/amanda, permissions, > Stefan > >
chg-scsi used to work then it stopped: details inside.
Amanda Group, I've been running Debian Testing for almost 4 months now without any issues with chg-scsi binary and my quantum superloader 16 tape library LTO-3. Couple of days ago chg-scsi has been unable to access the medium changer. Details of system and software: Kernel 2.6.17.7 with SCSI generic support (worked with this kernel) Debian Linux 3.1 Testing Amanda-server 2.5.1p1-2 Amanda-client 2.5.1p1-2 Amanda-common 2.5.1p1-2 Checking /proc/scsi/sg/device_strs CERTANCE ULTRIUM 31856 QUANTUMUHDL 0031 dmesg output ch 1:0:5:1: Attached scsi changer ch1 ch 1:0:5:1: Attached scsi generic sg7 type 8 ls -al /dev/sg7: crw-rw 1 backup root 21, 7 2005-02-25 22:38 /dev/sg7 mtx -f /dev/sg7 status (works correctly) Storage Changer /dev/sg7:1 Drives, 16 slots ( 0 Import/Export) Data Transfer Element 0: Full (Storage Element 6 Loaded): VolumeTag = MBW.. Storage Element 1: Full :VolumeTag=MBW... ... ... ... Storage Element 16: Full :VolutmeTag=MBW... also mtx -f /dev/sg7 next (works) Unfortunately: Output of chg-scsi -info as follows: chg-scsi: open: /dev/sg7: No such file or directory open: /dev/sg7: No such file or directory I've tried running both as root and the backup user. I've changed user/group permissions. I have another changer device an Exabyte 7 tape changer library at /dev/sg4 and if I change the amanda.conf/changer.conf file to point to SG4 chg-scsi -info reports: 13 16 1 1 This is incorrect, because the changer arm is not at the 13th slot, there isn't a maximum of 16 tape library, tape is not loaded into the drive, and there is no barcode reader on SG4. Any other /dev/sg[0-9] other than 4 and CHG-SCSI seg faults. I have cycled the server, tape drive/changer(s) with no success, changed Kernel to 2.6.18.2 with no success. Has there been any changes to chg-scsi from 2.5.0 to 2.5.1? The only thing I can think of is that I did a package upgrade and that's when things went downhill. Unfortunately none of my logs are reporting software changes. :( Also, no noteable changes in the bootup messages have been found to indicate tape changer behavior. Anyone have a similar issue or am I to now change to chg-zd-mtx and have to recreate the label file of the barcode database (such a drag!) Thanks for any assistance.
Re: amanda-2.5.0p2-1.src.rpm
Yes I ran ./configure --with-user=amandabackup --with-group=disk. Is there a way to remove the ./configure like make uninstall is there a similar command? Paddy Sreenivasan wrote: Did you run ./configure --with-user=amandabackup ? Please provide output of "amadmin XX config" command? Thanks, Paddy On 11/9/06, James Wilson <[EMAIL PROTECTED]> wrote: I did a make uninstall and ran ./configure again but it still comes up with the user amandabacup instead of amandabackup. How can I totally remove the configuration? Stefan G. Weichinger wrote: > James Wilson wrote: > >> I got the source bilt and changed the path to amandad in the >> /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. >> Put when I run amcheck on the server for this host it still times out. >> Any ideas? >> > > faq/doc: restart xinetd, look for /tmp/amanda, permissions, > Stefan > >
Re: amanda-2.5.0p2-1.src.rpm
Did you run ./configure --with-user=amandabackup ? Please provide output of "amadmin XX config" command? Thanks, Paddy On 11/9/06, James Wilson <[EMAIL PROTECTED]> wrote: I did a make uninstall and ran ./configure again but it still comes up with the user amandabacup instead of amandabackup. How can I totally remove the configuration? Stefan G. Weichinger wrote: > James Wilson wrote: > >> I got the source bilt and changed the path to amandad in the >> /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. >> Put when I run amcheck on the server for this host it still times out. >> Any ideas? >> > > faq/doc: restart xinetd, look for /tmp/amanda, permissions, > Stefan > > -- Amanda documentation: http://wiki.zmanda.com Amanda forums: http://forums.zmanda.com
Re: amanda-2.5.0p2-1.src.rpm
I did a make uninstall and ran ./configure again but it still comes up with the user amandabacup instead of amandabackup. How can I totally remove the configuration? Stefan G. Weichinger wrote: James Wilson wrote: I got the source bilt and changed the path to amandad in the /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. Put when I run amcheck on the server for this host it still times out. Any ideas? faq/doc: restart xinetd, look for /tmp/amanda, permissions, Stefan
Re: amanda-2.5.0p2-1.src.rpm
I changed the permissions on the /tmp/amanda directory and now I get this. ERROR: NAK apexdev.transolutions.net: getpwnam(amandabacup) fails Stefan G. Weichinger wrote: James Wilson wrote: I got the source bilt and changed the path to amandad in the /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. Put when I run amcheck on the server for this host it still times out. Any ideas? faq/doc: restart xinetd, look for /tmp/amanda, permissions, Stefan
Re: amanda-2.5.0p2-1.src.rpm
James, Are you still seeing the problem of selfcheck not being started on this client? Thanks, Paddy On 11/9/06, James Wilson <[EMAIL PROTECTED]> wrote: I got the source bilt and changed the path to amandad in the /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. Put when I run amcheck on the server for this host it still times out. Any ideas? Paddy Sreenivasan wrote: > James, > > libamclient-2.5.0p2.so should be installed in /usr/lib directory and > is part of the binary > rpm. Source rpm (amanda-2.5.0p2-1.src.rpm) will not contain the > libamclient library. > You have to build the source rpm to get the libamclient library. > > Thanks, > Paddy > > On 11/8/06, James Wilson <[EMAIL PROTECTED]> wrote: >> Hey All, >> >> I am installing this on RedHat version 9 and was wondering if there >> were additional steps needed for the source rpm? When I try to manually >> run ./selfcheck I get this error "error while loading shared libraries: >> libamclient-2.5.0p2.so: cannot open shared object file: No such file or >> directory". Do I need to pull libamclient-2.5.0p2.so down from zmandas >> website? And if so do I need anything additional to this? Thanks >> > > -- Amanda documentation: http://wiki.zmanda.com Amanda forums: http://forums.zmanda.com
Re: amanda-2.5.0p2-1.src.rpm
James Wilson wrote: > I got the source bilt and changed the path to amandad in the > /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. > Put when I run amcheck on the server for this host it still times out. > Any ideas? faq/doc: restart xinetd, look for /tmp/amanda, permissions, Stefan
Re: amanda-2.5.0p2-1.src.rpm
I got the source bilt and changed the path to amandad in the /xinetd.d/amandaclient config to point to /usr/local/libexec/amandad. Put when I run amcheck on the server for this host it still times out. Any ideas? Paddy Sreenivasan wrote: James, libamclient-2.5.0p2.so should be installed in /usr/lib directory and is part of the binary rpm. Source rpm (amanda-2.5.0p2-1.src.rpm) will not contain the libamclient library. You have to build the source rpm to get the libamclient library. Thanks, Paddy On 11/8/06, James Wilson <[EMAIL PROTECTED]> wrote: Hey All, I am installing this on RedHat version 9 and was wondering if there were additional steps needed for the source rpm? When I try to manually run ./selfcheck I get this error "error while loading shared libraries: libamclient-2.5.0p2.so: cannot open shared object file: No such file or directory". Do I need to pull libamclient-2.5.0p2.so down from zmandas website? And if so do I need anything additional to this? Thanks
