Re: upd port restictions
With bsd auth, the client choose the ports, they are in the range set by --with-tcpportrange, which default to 1025-65536, you can set 'unreserved-tcp-port' in amanda-client.conf to change it. You can also switch to the bsdtcp auth which require less port and is easier to configure. Jean-Louis Glenn Gillis wrote: Brian Cuttler wrote, On 3/24/2009 7:42 AM: Jean-Louis, On Tue, Mar 24, 2009 at 10:37:22AM -0400, Jean-Louis Martineau wrote: Hi, Server use tcp port between 10084 and 10100 to connect to client trel.wadsworth.org on port 56446. It looks good. Do you have firewall on server or client? Disable them while you test amanda. Can you post server and client debug files? We've opened the ports that we expected to use on the client, the server is not running a FW. I'd thought that the amanda TCP ports where well known and had assumed it was the dump on the client that was choosing a upd port that the server was not listening to because of --with-udpportrange=932,948. We will disable FW on the MAC for further testing, but I know that there is a preference to keep it running. Are the ports predictable so that we can at least somewhat restrict the range ? I believe the ports *are* predictable to an extent, Jean-Louis. I've successfully configured a FreeBSD Amanda server to backup another FreeBSD server running a firewall in the past. I used: http://wiki.zmanda.com/index.php/Configuration_with_iptables#IP_Traffic and http://wiki.zmanda.com/index.php/TCP/UDP_ports for guidance.
Re: zfs backup failure
Post the output of: amadmin config disklist grifserv /griffyp/hiu and the client amandad.*.debug, sendbackup.*.debug and zfs*.*.debug Jean-Louis Brian Cuttler wrote: Ok, scratched my head a little and thought about was what different between testing in-preproduction and now, we changed the system name and we ADDED quotas to the zfs file systems!! Checking # df output I realized that the file system with the error was the clostest to capacity. It was sitting at about 92% of its quota limit, with the next nearest capacity (size issues asside) at 89% capacity. I increased the disk quota so it fell below 90% and tried amdump again. We failed, I believe, on etimeout, which was set to only 300 or 600 seconds. We failed again at 2600 seconds, I uppped it to 4200 and left it for the nightly run to test. We produced the following error FAILURE DUMP SUMMARY: grifserv /griffyp/hiu lev 0 FAILED [too many dumper retry: [request failed: timeout waiting for REP]] Currently my timeouts are set etimeout 4200 # number of seconds per filesystem for estimates. dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host The particular file system (underlie a single samba share) is 61 Gig. griffyp/hiu 70G61G 8.9G88%/griffyp/hiu Don't know if I misconfigured something, had not expected issues when moving from testing to production. Did not experience this issue on the older/slower server, but that was a UFS file system running DUMP rather than tar. Any suggestions much apreciated, I really want to get this file system back under backups. If there are no ideas, I'll try to do a straight tar of the system tonight and skip the snapshot for it. If there is a limit for quota'd zfs file systems to produce snapshots, how do I both produce snapshots and keep a lid on usage ?? thanks, Brian On Thu, Mar 26, 2009 at 03:09:16PM -0400, Brian Cuttler wrote: I really am confused... When we set up amanda I configured amanda to have priv to perform snapshots. That is, as root I issued this command. /usr/sbin/usermod -P ZFS File System Management,ZFS Storage Management amanda We are able to perform 9 out of 10 ZFS dumps each night on this system, one fails with an apparently planner error, but I think it goes a little deeper. I had expected that as user amanda I could manually create a snapshot, but I can't, not on any zfs mount point, even though we seem to be able to do so when we perfrom nightly dumps. id uid=110(amanda) gid=3(sys) zfs snapshot griffyp/h...@amanda cannot create snapshot 'griffyp/h...@amanda': permission denied I'm clearly missing a step in the methodology. Only fileysstem /griffyp/hiu fails to backup, griffyp being the name of the amanda pool. Can anyone help me ? thanks, Brian df -kl Filesystemkbytesused avail capacity Mounted on /dev/dsk/c1t0d0s08262413 7067795 99487%/ /devices 0 0 0 0%/devices ctfs 0 0 0 0%/system/contract proc 0 0 0 0%/proc mnttab 0 0 0 0%/etc/mnttab swap 86608321632 8659200 1%/etc/svc/volatile objfs 0 0 0 0%/system/object sharefs0 0 0 0%/etc/dfs/sharetab /platform/sun4u-us3/lib/libc_psr/libc_psr_hwcap1.so.1 8262413 7067795 99487% /platform/sun4u-us3/lib/libc_psr.so.1 /platform/sun4u-us3/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1 8262413 7067795 99487% /platform/sun4u-us3/lib/sparcv9/libc_psr.so.1 fd 0 0 0 0%/dev/fd /dev/dsk/c1t0d0s68262413 1636317 654347221%/var swap 20971521624 2095528 1%/tmp swap 8659264 64 8659200 1%/var/run griffyp 173182464 475 44829887 1%/griffyp griffyp/amanda 173182464 74 44829887 1%/griffyp/amanda griffyp/climsgl 1048576 245576 80299924%/griffyp/climsgl griffyp/connlab 5242880 4574973 66790688%/griffyp/connlab griffyp/csssoft 1048576 38 1048537 1%/griffyp/csssoft griffyp/dew 2097152 1324984 77216764%/griffyp/dew griffyp/encphrev 10485761197 1047379 1%/griffyp/encphrev griffyp/export 5242880 4433533 80934785%/griffyp/export griffyp/grifadmin2097152 1548594 54855874%/griffyp/grifadmin griffyp/hiu
Re: Strange FORMAT ERROR with 2.6.1
Stefan,
This bug is already fixed and is available in the latest snaphot.
I attach the patch.
Jean-Louis
Stefan G. Weichinger wrote:
Greets,
I have to debug some backup-related problems for a customer ...
Running amanda 2.6.1 on gentoo linux there (my own ebuild).
For some DLEs I get:
samba01.xy.at christian_home lev 1 FAILED [FORMAT ERROR IN REQUEST
PACKET 'Error on line 1 char 202: Odd character 'r', expected an open
quote mark after the equals sign when giving value for attribute
'encoding' of element 'file'']
Corresponding lines in amdump.1 (afaik):
driver: send-cmd time 3904.615 to dumper4: PORT-DUMP 04-00020 11635
samba01.lietz.at 9ffe7f christian_home /home 1
2009:3:13:21:32:27 GNUTAR X X X BSD | authBSD/auth\n
recordYES/record\n indexYES/index\n exclude\nfile
encoding=\raw\
raw=\Li9jaHJpc3RpYW4vRWlnZW5lIERhdGVpZW4=\./christian/Eigene_Dateien/file\n
list/usr/local/etc/amanda/daily/excludes/root-excludes/list\n
/exclude\n include\nfile./christian/file\n /include\n
driver: state time 3904.615 free kps: 3335 space: 26304680 taper: DOWN
idle-dumpers: 3 qlen tapeq: 46 runq: 32 roomq: 0 wakeup: 0 driver-idle:
no-bandwidth
driver: interface-state time 3904.615 if default: free 3335
driver: hdisk-state time 3904.615 hdisk 0: free 26304680 dumpers 5
driver: state time 3904.629 free kps: 3335 space: 26304680 taper: DOWN
idle-dumpers: 3 qlen tapeq: 46 runq: 32 roomq: 0 wakeup: 15 driver-idle:
no-bandwidth
driver: interface-state time 3904.629 if default: free 3335
driver: hdisk-state time 3904.629 hdisk 0: free 26304680 dumpers 5
driver: result time 3904.629 from dumper4: FAILED 04-00020 FORMAT ERROR
IN REQUEST PACKET 'Error on line 1 char 202: Odd character 'r', expected
an open quote mark after the equals sign when giving value for attribute
'encoding' of element 'file''
driver: send-cmd time 3904.629 to chunker4: FAILED 04-00020
driver: state time 3904.629 free kps: 3335 space: 26304680 taper: DOWN
idle-dumpers: 3 qlen tapeq: 46 runq: 32 roomq: 0 wakeup: 15 driver-idle:
no-bandwidth
driver: interface-state time 3904.629 if default: free 3335
driver: hdisk-state time 3904.629 hdisk 0: free 26304680 dumpers 5
driver: result time 3904.629 from chunker4: FAILED 04-00020 [cannot
read header: got 0 bytes instead of 32768]
--
The client here is running the zmanda-rpm
amanda-backup_server-2.6.1-1.suse10 on a Suse 10.0 (yes, old, all this
is part of migration and removal of the old client ...)
--
I'd be happy to provide any more logs offlist, if needed ...
Thanks, Stefan
Index: ChangeLog
===
--- ChangeLog (revision 1648)
+++ ChangeLog (revision 1649)
@@ -1,3 +1,7 @@
+2009-02-06 Jean-Louis Martineau martin...@zmanda.com
+ * server-src/dumper.c: options is already unquoted.
+ * common-src/util.c: argument should not be quoted when added to argv.
+
2009-02-06 Dustin J. Mitchell dus...@zmanda.com
* installcheck/Amanda_Changer_compat.pl: remove debugging code
Index: server-src/dumper.c
===
--- server-src/dumper.c (revision 1648)
+++ server-src/dumper.c (revision 1649)
@@ -260,9 +260,8 @@
char *errmsg = NULL;
dle_t *dle;
-char *uoptionstr = unquote_string(optionstr);
-o = oo = vstralloc(dle, strchr(uoptionstr,''), /dle, NULL);
-
+o = oo = vstralloc(dle, strchr(optionstr,''), /dle, NULL);
+
dle = amxml_parse_node_CHAR(o, errmsg);
if (dle == NULL) {
error(amxml_parse_node_CHAR failed: %s\n, errmsg);
@@ -2048,9 +2047,8 @@
amfree(dle_str);
if (am_has_feature(their_features, fe_req_xml)) {
- char *o, *p = NULL;
+ char *p = NULL;
char *pclean;
- o = unquote_string(options+1);
vstrextend(p, dle\n, NULL);
if (*application_api != '\0') {
vstrextend(p, programAPPLICATION/program\n, NULL);
@@ -2063,8 +2061,7 @@
NULL);
}
vstrextend(p, level, level_string, /level\n, NULL);
- vstrextend(p, o, /dle\n, NULL);
- amfree(o);
+ vstrextend(p, options+1, /dle\n, NULL);
pclean = clean_dle_str_for_client(p);
vstrextend(req, pclean, NULL);
amfree(pclean);
Index: common-src/util.c
===
--- common-src/util.c (revision 1648)
+++ common-src/util.c (revision 1649)
@@ -1044,9 +1044,9 @@
property_t *value_s = value_p;
char ***argv = user_data_p;
GSList *value;
-char *q, *w, *qprop, *qvalue;
+char *q, *w, *qprop;
-q = quote_string(property_s);
+q = stralloc(property_s);
/* convert to lower case */
for (w=q; *w != '\0'; w++) {
*w = tolower(*w);
@@ -1056,10 +1056,9 @@
qprop = stralloc2(--, q);
amfree(q);
for(value=value_s-values; value != NULL; value = value-next) {
- qvalue = quote_string((char *)value-data);
**argv = stralloc(qprop);
(*argv)++;
- **argv = qvalue;
+ **argv = stralloc((char *)value-data);
(*argv
Re: Is partial taper Expected?
The 4 DLEs are already flushed. There is a bug in 2.6.1 that don't erase them from holding disk, this bug is already fixed in SVN. You can securely remove the files from holding disk. Jean-Louis Steven Backus wrote: Jean-Louis Martineau martin...@zmanda.com wrote: You get this message if the dump is not complete. The taper successfully wrote an incomplete image to tape. Since they are autoflushed image, check in previous report to know why the dump failed. The night before one of the machines was down. Other machines auto-mounted some partitions on this machine leading to problems like: ? gtar: ./gen17: Cannot savedir: No such file or directory Since I had autoflush in amanda.conf I would expect the holding disks to be drained regardless of what errors happened. Not so? Will they ever be flushed or should I just delete them? Steve
Re: increasing tar failures
The email report should give you the complete output of tar, check the DETAIL section of the report. Jean-Louis Steve Wray wrote: Hi there, over the last month or so I've been seeing increasing amounts of disk list entries showing this in the amanda report: FAILED [/bin/tar returned 1] I've gone to the hosts involved and checked their logs and really thats about as informative as it gets. I've checked the tar command used on these hosts and run that to hand (sending to /dev/null) and have never seen tar fail yet. Amanda versions vary a lot here, we have Debian Sarge, Etch and Lenny hosts. Nothing major has changed with the hosts which have started to show this problem. There have been no network changes in the form of routers, switches or firewalls. Can someone please suggest some further diagnostics? Thanks!
Re: upd port restictions
Hi, Server use tcp port between 10084 and 10100 to connect to client trel.wadsworth.org on port 56446. It looks good. Do you have firewall on server or client? Disable them while you test amanda. Can you post server and client debug files? Jean-Louis Brian Cuttler wrote: I am running Amanda 2.6.1-20090227 on Solaris 10 with ZFS and snapshots !! to an LTO4 in a SL24 jukebox. I'm trying to add some remote clients, starting with the one that gives me the most trouble. Moving the MAC with 300 Gig of storage to the x4500 amanda platform with the Gig interface and off of the SF280 with the 100 Meg interface and the LTO3... However we find the following error on the server FAILURE DUMP SUMMARY: trel / lev 0 FAILED [too many dumper retry: [could not connect DATA stream: can't connect stream to trel.wadsworth.org port 56446: Connection timed out]] We did build the server with port restrictions, because that is the way we are going. --with-udpportrange=932,948 --with-tcpportrange=10084,10100 We seem to have build the amand client on the MAC without port restrictions, the client is 2.4.5p1. Is there any magic, short of a client rebuild to resolve the error ? I am on the correct path ? My mac expert is hoping he doesn't have to relearn how to rebuild, or is there a current MAC build with port restriction in use available ? thank you, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: BUILT_MACH wrong ?
BUILT_MACH is set from the output of ./config/config.guess What is the ouput? Jean-Louis Peter Kunst wrote: Hi there, just noticed in another Solaris10/sparc machine's amandad debug file: 1237478934.669711: amandad: BUILT_MACH=x86_64-unknown-linux-gnu BUILT_REV=1609 This amandad 2.6.1 binary was built from the official 2.6.1 tarball on Solaris10/sparc. This is neither x86, nor Linux, and i never run any builds for x86 here in this amanda's src tree. Cheers, Peter
Re: More ranting about issues compiling 2.6.1 on older machines
I have numerous clients still running amanda 2.4.x clients and talking to my 2.6.1 server. I would think that maintaining backward compatibility within the amanda server is a more fruitful path than trying to build the latest version on all sorts of older platforms. Is there reason to believe that older clients will become unsupported sometime soon? No, compatibility with older client is a priority. Have you tried restoring? I have a contractor whose assignment is to prove that we can estore on evey machine in the backup system. She assures me that earlier cliets cannot do this, and that we must move foward. I have 2 reasons to beleive her. 1. I trust her, and have worked with her for years. 2. It's a fixed price job for here, and the answer she came up will definatley cost her money. Make a bug report if you have problem using amrecover on older client with newer server. We try to make them compatible but we haven't the time to test all features combination. Jean-Louis
Re: [Amanda-users] how to use amrestore
Why you can't open the file? Jean-Louis ay4you wrote: Hi Can anyone tell me how to use amrestore i have done amrestore tapefile host now i have a big file which i cant open how do i extract the files there +-- |This was sent by mahmoudh...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: amstatus error on 2.6.1
Stan, It's known bug, remove the line 1042. Jean-Louis stan wrote: When I ran amstatus to check on last nights run, I got a serries of the follwing error messages: :Use of uninitialized value in addition (+) at /opt/amanda/sbin/amstatus line 1042. Looking at that line of the script makes me suspect that the acumulation that's going on here needs to have (if defined) protecting it. Does this make sense?
Re: amstatus error on 2.6.1
stan wrote: On Thu, Feb 26, 2009 at 07:31:44AM -0500, Jean-Louis Martineau wrote: Stan, It's known bug, remove the line 1042. So, that element of the structure does not need to get aded to the acumulation It's done a few line below. Jean-Louis
Re: [Amanda-users] amanda error
Check the client amandad.*.debug and sendsize.*.debug files. Jean-Louis ay4you wrote: Hi i am getting an error with amanda backup i am using amanda 2.6.0 on the server and 2.5.1 on the client. the error is FAILURE DUMP SUMMARY: LON-TI-OFF-01 /home/company lev 0 FAILED [missing result for /home/company in LON-TI-OFF-01 response] in the log files there is no sign of an error except in dump.1 in the /etc/amanda/DailySet11/ SENDING FLUSHES... ENDFLUSH SETTING UP FOR ESTIMATES... planner: time 0.016: setting up estimates for LON-TI-OFF-01:/home/company LON-TI-OFF-01:/home/company overdue 14299 days for level 0 setup_estimate: LON-TI-OFF-01:/home/company: command 0, options: none last_level -1 next_level0 -14299 level_days 0getting estimates 0 (-2) -1 (- 2) -1 (-2) planner: time 0.016: setting up estimates took 0.000 secs GETTING ESTIMATES... driver: pid 2936 executable /usr/libexec/amanda/driver version 2.6.0p2 driver: adding holding disk 0 dir /media/Backup/dumps/DailySet11 size 533192704 chunksize 1048576 planner: time 0.197: got result for host LON-TI-OFF-01 disk /home/company: 0 - -2K, -1 - -2K, -1 - -2K error result for host LON-TI-OFF-01 disk /home/company: missing estimate planner: time 0.198: getting estimates took 0.181 secs FAILED QUEUE: 0: LON-TI-OFF-01 /home/company DONE QUEUE: empty Can anyone help i have also changes the etimeout to 3600 still no joy the server is a fedora and the client is an ubuntu any other info need i can provide +-- |This was sent by mahmoudh...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: 2.6.1 build process anomoly
./configure --help --with-amlibexecdir[[[=PATH]]] Where amanda own programs are installed, default: $libexecdir/amanda --without-amlibexecdir Amanda own programs are installed in $libexecdir Files are installed in an 'amanda' subdir to reduce possible conflict with files from others packages. Jean-Louis stan wrote: Why, given the following arguemnts to configure: ./configure \ --with-config=DailyDump \ --prefix=/opt/amanda \ --with-index-server=amanda.meadwestvaco.com \ --with-tape-server=amanda.meadwestvaco.com \ --with-tape-device=chg-multi \ --with-changer-device=chg-multi \ --with-user=amanda \ --with-group=operator \ --with-debugging \ --sbindir=/opt/amanda/sbin \ --libexecdir=/opt/amanda/libexec \ --libdir=/opt/amanda/lib \ --with-configdir=/opt/amanda/etc \ --with-gnutar-listdir=/opt/amanda/var/gnutar-lists \ --mandir=/opt/amanda/man \ --with-buffered-dump \ --without-rundump \ --with-maxtapeblocksize=256 Do the files, which I think should be installed in /opt/amanda/lib, actually get installed in /opt/amanda/lib/amanda ? ama...@amanda:/opt/amanda$ cd libexec ama...@amanda:/opt/amanda/libexec$ ls amanda ama...@amanda:/opt/amanda/libexec$ cd amanda ama...@amanda:/opt/amanda/libexec/amanda$ ls amandad amplot.gpchg-iomega chg-rth planner amanda-sh-lib.sh amtrmidx chg-jukechg-scsi rundump amcat.awk amtrmlog chg-lib.sh chg-zd-mtxruntar amcleanupdisk application chg-manual chunker selfcheck amidxtapedcalcsize chg-mcutil driversendbackup amindexd chg-chio chg-mtx dumpersendsize amlogroll chg-chs chg-multi killpgrp taper amplot.awkchg-disk chg-nullnoop teecount amplot.g chg-glue chg-raitpatch-system versionsuffix
Re: 2.6.1 build process anomoly
stan wrote: On Thu, Feb 19, 2009 at 10:23:59AM -0500, Jean-Louis Martineau wrote: ./configure --help --with-amlibexecdir[[[=PATH]]] Where amanda own programs are installed, default: $libexecdir/amanda --without-amlibexecdir Amanda own programs are installed in $libexecdir Files are installed in an 'amanda' subdir to reduce possible conflict with files from others packages. But, if one is already puting amanda in it's own tree, as we are (/opt/amanda) then this just adds another (confusing) directory to the path (EG /opt/amanda/libexec/amanda) `. Is it possible to overide this behavior? --without-amlibexecdir Jean-Louis
Re: 2.6.1 build process anomoly
Read previous post and './configure --help' output. Add --without-amlibexecdir Jean-Louis stan wrote: On Thu, Feb 19, 2009 at 11:18:37AM -0500, Dustin J. Mitchell wrote: On Thu, Feb 19, 2009 at 10:48 AM, stan st...@panix.com wrote: But, if one is already puting amanda in it's own tree, as we are (/opt/amanda) then this just adds another (confusing) directory to the path (EG /opt/amanda/libexec/amanda) `. Is it possible to overide this behavior? Yep -- see --without-amlibdir in the ./configure --help output that Jean-Louis pasted. Hmm, I'm having a bad dy. I put: --without-amlibdir In my script that runs configure. but i still get: Build documentation: no Directories: Application: /opt/amanda/libexec/amanda/application Configuration: /opt/amanda/etc GNU Tar lists: /opt/amanda/var/gnutar-lists Perl modules (amperldir): /opt/amanda/lib/perl Template and example data files (amdatadir): /opt/amanda/share/amanda Temporary: /tmp/amanda I alos put --with-amperldir=/opt/amanda/lib/perl in the same script, and, as you can see it was honored. Also can i change /opt/amanda/share/amanda to /opt/amanda/share somehow?
Re: Using amrecover with amgtar has trouble
Yoshihiro Ishikawa wrote:
[r...@centos32 recover-src]# diff -uNr extract_list.c.o extract_list.c
--- extract_list.c.o2008-12-13 02:59:47.0 +0900
+++ extract_list.c 2009-02-06 12:40:52.0 +0900
@@ -1755,6 +1755,10 @@
if (file.program != NULL) {
if (strcmp(file.program, BACKUP) == 0)
dumptype = IS_APPLICATION_API;
+
+if (strcmp(file.program, APPLICATION) == 0)
+dumptype = IS_APPLICATION_API;
+
#ifdef GNUTAR
if (strcmp(file.program, GNUTAR) == 0)
dumptype = IS_GNUTAR;
Is this the correct and simple solution?
Patch is good, but you can only change BACKUP for APPLICATION two
lines above
Thanks for reporting the bug and a fix
Jean-Louis
Re: amanda 2.6.1, Solaris 10/Sparc, amstatus error
This bug is already fixed. Fix will be in 2.6.1p1. Jean-Louis Brian Cuttler wrote: Successful run of the new version yesterday, performing a new run this morning with autoflush (production capacity tape drive is on the current production system). Ran amstatus and noted an error, thought I'd pass it on. Please let me know what additional detail I can provide. I do not consider this a serious problem, I don't need a fix, just an FYI. Note, this error did NOT occur while the flush of that first partition was still in progress. I did NOT see any amstatus errors during the original amdump yesterday. thanks, Brian amstatus griffy Using /usr/local/etc/amanda/griffy/DailySet1/amdump From Tue Feb 3 10:24:01 EST 2009 griffy:/ 0 3331m flushed (10:36:45) Use of uninitialized value in addition (+) at /usr/local/sbin/amstatus line 1042. griffy:/ 0 7208m estimate done griffy:/griffyp/climsgl0 227m estimate done griffy:/griffyp/csssoft0 0m estimate done griffy:/griffyp/dew0 1292m estimate done griffy:/griffyp/encphrev 0 1m estimate done griffy:/griffyp/export 0 674m estimate done griffy:/griffyp/grifadmin 0 957m estimate done griffy:/griffyp/hiu0 37812m flushing to tape (10:36:45) griffy:/griffyp/hiu getting estimate griffy:/griffyp/hiu2getting estimate griffy:/griffyp/ivcpgetting estimate griffy:/griffyp/virologypt 015m estimate done griffy:/var0 889m estimate done SUMMARY part real estimated size size partition : 14 estimated : 911266m flush : 2 41143m failed : 00m ( 0.00%) wait for dumping: 00m ( 0.00%) dumping to tape : 00m ( 0.00%) dumping : 0 0m 0m ( 0.00%) ( 0.00%) dumped : 1 3331m 3331m (100.00%) ( 29.57%) wait for writing: 0 0m 0m ( 0.00%) ( 0.00%) wait to flush : 0 0m 0m (100.00%) ( 0.00%) writing to tape : 1 37812m 37812m (100.00%) (335.61%) failed to tape : 0 0m 0m ( 0.00%) ( 0.00%) taped : 1 3331m 3331m (100.00%) ( 6.36%) tape 1: 1 3331m 3331m ( 4.76%) Griffy02 (2 chunks) 4 dumpers idle : runq taper writing, tapeq: 0 network free kps:80 holding space : 36833m (109.94%) taper busy : 0:12:35 ( 99.02%) 0 dumpers busy : 0:12:35 ( 99.06%)runq: 0:12:35 (100.00%) --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: Amanda 2.6.1 on Solaris 10/Sparc build
man amzfs-snapshot You must give to the 'amanda' user the right to execute some zfs command. Use 'zfs allow' or set the 'PFEXEC' and 'PFEXEC-PATH' properties. Brian Cuttler wrote: Yes! leaving the /opt/sfw/lib out of the path entirely seems to have done the trick, we linked against the correct library and I can now proceed with the next level of errors. Could have sworn I saw something about this on the list last week and I am checking the wiki now. ERROR: griffy: cannot create snapshot 'griffyp/clim...@amanda-_griffyp_climsgl-check': permission denied
Re: amanda 2.6.1 - configuration problem ?
Hi Stefan,
Try the attached patch.
Jean-Louis
Stefan G. Weichinger wrote:
Greets,
as I start to explore the wonders of opensolaris I have a testbox
running OpenSolaris 2008.11. I installed the amanda-packages from zmanda
and set up amanda 2.6.1 to give zfs-snapshots a try.
Things work fine when I use a DLE like this:
sun.oops.intern home /export/home zfs-snapshot
Let's call it the one-line syntax.
When I use the multi-line syntax:
sun.oops.intern r_storage /export/storage {
zfs-snapshot
} 5
the defined script is not included.
(( sidenote: I wanted to use that syntax to enable tape_splitsize for
the particular DLE, my example here does not contain that line as it
should work like this as well ))
---
## relevant parts in amanda.conf
define script-tool script_zfs_snapshot {
comment zfs-snapshot
plugin amzfs-snapshot
execute-where client
execute-on pre-dle-amcheck, post-dle-amcheck, pre-dle-estimate,
post-dle-estimate, pre-dle-backup, post-dle-backup
property DF-PATH /usr/sbin/df
property ZFS-PATH /usr/sbin/zfs
}
define application-tool app_amgtar {
comment amgtar
plugin amgtar
property ATIME-PRESERVE no
property GNUTAR-PATH /usr/bin/gtar
}
define dumptype zfs-snapshot {
program APPLICATION
application app_amgtar
script script_zfs_snapshot
auth bsdtcp
}
## output of amadmin daily ...
s...@sun:~$ amadmin daily disklist sun r_storage | grep script
s...@sun:~$ amadmin daily disklist sun /home | grep script
script script_zfs_snapshot
Only the one-liner triggers the usage of the script.
This is also traceable by zfs list -t snapshot while amdump is
running: there is no snapshot created etc.
The one-line syntax works as expected, creating the snapshot etc
--
I assume that this is not wanted behavior, at least it seems to hurt the
rule of least surprise ...
Stefan
Index: common-src/conffile.c
===
--- common-src/conffile.c (revision 15137)
+++ common-src/conffile.c (working copy)
@@ -5708,7 +5708,7 @@
valdst-v.pp_scriptlist = NULL;
if (valsrc-v.pp_scriptlist) {
g_slist_foreach(valsrc-v.pp_scriptlist, copy_pp_scriptlist,
-valdst-v.pp_scriptlist);
+valdst-v.pp_scriptlist);
}
break;
@@ -5747,9 +5747,9 @@
gpointer user_data_p)
{
pp_script_t *pp_script = data_p;
-pp_scriptlist_t pp_scriptlist = user_data_p;
+pp_scriptlist_t *pp_scriptlist = user_data_p;
-pp_scriptlist = g_slist_append(pp_scriptlist, pp_script);
+*pp_scriptlist = g_slist_append(*pp_scriptlist, pp_script);
}
static void
Re: Error on backup
The DETAIL section of the report list the output of tar, you should see why it failed (exit with code 2). Jean-Louis Prashant Ramhit wrote: Hi All. Does any one knows what this error code means FAILURE AND STRANGE DUMP SUMMARY: backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump (22576) /usr/bin/tar returned 2] backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump to tape failed] And how can I troubleshoot that, Thanks Prashant
Re: Error on backup
No, it's not a system call returning with setting errno to 2. It is tar exiting with an exit status of 2. Check 'man tar' or 'info tar'. Check the DETAIL section of the report, it give the tar error message. Jean-Louis donald.ritc...@comed.com wrote: And error code 2 can be found in either /usr/include/errno.h or /usr/include/sys/errno.h, depending on your particular version of UNIX and how it structures the include files. (On Tru64 UNIX, the code is 'file or directory not found'.) Don Ritchey -Original Message- From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On Behalf Of Jean-Louis Martineau Sent: Thursday, January 29, 2009 06:01 To: Prashant Ramhit Cc: amanda-users Subject: Re: Error on backup The DETAIL section of the report list the output of tar, you should see why it failed (exit with code 2). Jean-Louis Prashant Ramhit wrote: Hi All. Does any one knows what this error code means FAILURE AND STRANGE DUMP SUMMARY: backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump (22576) /usr/bin/tar returned 2] backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump to tape failed] And how can I troubleshoot that, Thanks Prashant - ** This e-mail and any of its attachments may contain Commonwealth Edison Company proprietary information, which is privileged, confidential, or subject to copyright belonging to Commonwealth Edison Company or its affiliates. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. **
Re: 2.6.2alpha question.
What do you get if you run: /usr/bin/smbclient '//not.a.host.name/notashare' -U nosuchuser -N -Tx /dev/null Maybe your DNS is slow to return that 'not.a.host.name' is not a valid hostname Check your DNS configuration. Jean-Louis Gene Heskett wrote: On Sunday 25 January 2009, Dustin J. Mitchell wrote: On Sat, Jan 24, 2009 at 11:29 PM, Gene Heskett gene.hesk...@verizon.net wrote: I've been following along and doing my usual canary imitation with the 2.6.2 tree as its released, and I've noted that the configure script has been hanging for about 30 seconds, looking for /usr/bin/smbclient before it goes on, since at least the 0121 version. 0123 reminded me when it did the same just now. Samba is working here, so I'm wondering what this hangup might be trying to tell me? I don't see any interesting changes to configure since January 1, at least. Can you run 'ps -auxwwf' a few times during the hang to see what configure is up to? Dustin Ok Dustin, here is a capture of that, stripped to the results of my running ./gh.cf, my build script: Word wrap off of course.. amanda 15320 0.0 0.0 5492 2228 pts/5S10:41 0:00 | | \_ bash amanda9633 0.0 0.0 4648 1028 pts/5S+ 10:51 0:00 | | \_ /bin/sh ./gh.cf amanda 10170 6.9 0.0 4960 1576 pts/5S+ 10:51 0:00 | | \_ /bin/sh ./configure --with-user=amanda --with-group=disk --with-owner=amanda --with-gnu-ld --prefix=/usr/local --with-tapedev=FILE:/amandatapes --with-debugging=/tmp/amanda-dbg/ --with-tape-server=coyote --with-bsdtcp-security --with-amandahosts --with-configdir=/usr/local/etc/amanda --with-config=Daily --with-gnutar=/bin/tar amanda 15605 0.0 0.0 4960 824 pts/5S+ 10:51 0:00 | | \_ /bin/sh ./configure --with-user=amanda --with-group=disk --with-owner=amanda --with-gnu-ld --prefix=/usr/local --with-tapedev=FILE:/amandatapes --with-debugging=/tmp/amanda-dbg/ --with-tape-server=coyote --with-bsdtcp-security --with-amandahosts --with-configdir=/usr/local/etc/amanda --with-config=Daily --with-gnutar=/bin/tar amanda 15606 1.0 0.0 8320 2528 pts/5S+ 10:51 0:00 | | \_ /usr/bin/smbclient \\not.a.host.name\notashare -U nosuchuser -N -Tx /dev/null root 19103 0.0 0.0 4712 880 pts/6Ss Jan27 0:00 | \_ su - root 19127 0.0 0.0 5492 2072 pts/6SJan27 0:00 | | \_ -bash root 15607 0.0 0.0 4496 924 pts/6R+ 10:51 0:00 | | \_ ps auxwwf That was taken about 1.5 seconds after it stalled. Does that give enough of a hint? FWIW, this version of ps fusses about the - sign, but gives the same output without it.
Re: Weird compression results for DLE using 'compress NONE' (nocomp-root)
Tom Robinson wrote: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- --- host /disk 1 20316904063380 200.0 36:34 1852.3 6:27 10487.2 Note the ORIG-KB blows out to twice the size! COMP% is 200.0... ORIG-KB is the size reported by the dump program, it report a number of blocks, but all dump doesn't have the same blocksize. Can you post the sendsize.*.debug and sendbackup.*.debug files from the client and answer the following questions? amanda version on the client? Os of the client? Filesystem? dump program? dump version?
Re: Weird compression results for DLE using 'compress NONE' (nocomp-root)
Tom Robinson wrote: Client: amanda: 2.4.4p3 It is an old release, sendbackup: time 2193.228: 93: normal(|): DUMP: Volume 1 4063380 blocks (3968.14MB) The block size is 1KB. It is improved in newer release. I can do nothing for the release you are using, if you have program with the latest stable release, I will be happy to provide a patch. Jean-Louis
Re: Amrecover issue...
Christiaan de Vries wrote:
Hello Jean-Louis,
File Permissions:
==
bac...@dub-amanda1:~$ ls -al /usr/lib/amanda/amidxtaped
-rwxr-xr-x 1 root root 16248 2007-11-09 01:08 /usr/lib/amanda/amidxtaped
Xinetd.d conf:
r...@dub-amanda1:/etc/xinetd.d# cat /etc/xinetd.d/amidxtape
#default: on
# description: The amanda tape service
service amidxtape
{
#only_from= Amanda client list
socket_type= stream
protocol= tcp
wait= no
user= backup
group= backup
groups= yes
server= /usr/lib/amanda/amidxtaped
server_args= -auth=bsd amdump amindexd amidxtaped
disable= no
}
xinetd amindexd and amidxtaped are not use, you should disable them if
you don't have older client.
Post /etc/xinetd.d/amanda
Post the amandad.*.debug file
Do /usr/lib/amanda/amidxtaped have the same permission as
/usr/lib/amanda/amindexd?
Socket:
r...@dub-amanda1:/etc/xinetd.d# netstat -an | grep 10083
tcp0 0 0.0.0.0:10083 0.0.0.0:*
LISTEN
FYI: I have tried changing the file ownership to the backup user, but
to no avail... I also tried to start the amixdtaped deamon with root,
also no change, still the same error:
amrecover - can't talk to tape server: NAK: execute access to
/usr/lib/amanda/amidxtaped denied
Kind regards again,
Christiaan de Vries
(Btw, where would I set the 'sethost' and 'settape' variables on the
client machine permanently?)
Either when you configure amanda or in the amanda-client.conf file.
Jean-Louis
Re: Amrecover issue...
Christiaan de Vries wrote:
Hello all,
(After quite some time spent on initial configuration issues...)
It seems the dump works successfully, but when I try an amrecover from
the client, I get the following error:
=
r...@chris-desktop:~# amrecover -s 10.100.100.150
AMRECOVER Version 2.5.2p1. Contacting server on 10.100.100.150 ...
NAK: user root from chris-desktop is not allowed to execute the
service amindexd: Please add amindexd amidxtaped to the line in
/var/backups/.amandahosts on the client
The message is not 100% correct, for amrecover, the line must be added
to the .amandahosts on the server.
Add the following to the .amandahosts on the server:
chris-desktop backup amindexd amidxtaped
The message is fixed in 2.6.1
Jean-Louis
My .amandahosts file contains:
=
r...@chris-desktop:~# cat /var/backups/.amandahosts
localhost root amindexd amidxtaped
localhost backup amdump
chris-desktop root amindexd amidxtaped
chris-desktop backup imindexd amidxtaped
The amrecover debug output:
=
amrecover: debug 1 pid 11618 ruid 0 euid 0: start at Mon Dec 29
13:37:01 2008
Could not open conf file /etc/amanda/amanda-client.conf: No such
file or directory
Could not open conf file /etc/amanda/DailySet1/amanda-client.conf:
No such file or directory
amrecover: debug 1 pid 11618 ruid 0 euid 0: rename at Mon Dec 29
13:37:01 2008
amrecover: time 0.000: security_getdriver(name=bsd) returns 0xb8033c00
amrecover: time 0.000: security_handleinit(handle=0x8c7ced0,
driver=0xb8033c00 (BSD))
amrecover: time 0.001: bind_portrange2: Try port 855: Available -
Success
amrecover: time 0.001: dgram_bind: socket 3 bound to ::.855
amrecover: time 0.001: dgram_send_addr(addr=0x8c7cef0, dgram=0xb8045a84)
amrecover: time 0.001: (sockaddr_in6 *)0x8c7cef0 = { 10, 10080,
:::10.100.100.150 }
amrecover: time 0.001: dgram_send_addr: 0xb8045a84-socket = 3
amrecover: time 0.006: dgram_recv(dgram=0xb8045a84, timeout=0,
fromaddr=0xb8055a70)
amrecover: time 0.007: (sockaddr_in6 *)0xb8055a70 = { 10, 10080,
:::10.100.100.150 }
amrecover: time 0.007: security_close(handle=0x8c7ced0,
driver=0xb8033c00 (BSD))
FYI: When I run a amcheck -c DailySet1 on the server, I receive the
following output:
=
Amanda Backup Client Hosts Check
ERROR: NAK 10.100.100.160: user backup from
dub-amanda1.dublinoffice.bfx is not allowed to execute the service
noop: Please add amdump to the line in /var/backups/.amandahosts on
the client
Client check: 1 host checked in 10.003 seconds, 1 problem found
(brought to you by Amanda 2.5.2p1)
Anybody have a clue/tips?
After the server gave me that pointer (add amdump to the .amandahosts
file), the contents now look as follows:
=
r...@chris-desktop:~# cat /var/backups/.amandahosts localhost root
amindexd amidxtaped amdump
localhost backup amdump
chris-desktop root amindexd amidxtaped amdump
chris-desktop backup imindexd amidxtaped
The message clearly state that it is the host
'dub-amanda1.dublinoffice.bfx' that try to connect, .amandahosts must be:
dub-amanda1.dublinoffice.bfx backup amdump
Re: [Amanda-users] Amanda backup problem - a tape error occured
Are you sure of the size of your tape? 4Gb is with compression or not,
Do your data are compressible or not, are you using software compression?
Jean-Louis
mandaillou wrote:
Thanks for your prompt replies.
Dustin J. Mitchell wrote:
On Fri, Dec 19, 2008 at 4:06 AM, mandaillou
amanda-forum at backupcentral.com wrote:
On the forum, I found people facing the same problem and the error was related
to the tapecycle. Mine is 12 and I have 12 reusable tapes.
Right -- if you're doing 14 backups (2 weeks, every day), you're not
going to fit that on 12 tapes. You need 15 tapes.
I wasn't clear enough. I run a backup every working day (monday to friday),
which means 10 backup per cycle so I guess 12 tapes is enough.
Dustin J. Mitchell wrote:
Furthermore, it looks like you don't have enough holding-disk space:
FAILED [no more holding disk space]
which is causing your dumps to go straight to tape, which isn't very efficient.
I confess I haven't configurated this part. I understood (maybe I'm wrong) that
it would work anyway.
Dustin J. Mitchell wrote:
Furthermore, your tape only wrote a bit over 1G:
DailySet-05 2:11 1140224K 28.8 1 0
which is 28% of the length you specified in your tapetype definition.
Is there a problem with the tape? Or is the tapetype definition
incorrect?
I'm using 4Go tapes. They are all new and I have the same problem for every
tape. I've used amtapetype for amanda.conf configuration.
Below is the extract from amanda.conf related to the tapetype definition.
define tapetype HP-C1537A{
length 3868 mbytes
filemark 225 kbytes
speed 491 kps
}
Jean-Louis Martineau wrote:
mandaillou wrote:
Quote:
NOTES:
taper: tape DailySet-05 kb 1783648 fm 2 writing file: No space left on
device
The tape got full after 1783648 was written, you need bigger tape.
The capacity of all my tapes is 4Go. I feel like Amanda doesn't overwrite the tape but
just fill the tape until it's full and then exit with the previous error message :
The tape got full after 1783648 was written, you need bigger tape.
PS:can anybody tell me why I can't see my original post but only the replies ?
+--
|This was sent by mandail...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--
Re: [Amanda-users] Amanda backup problem - a tape error occured
mandaillou wrote: NOTES: taper: tape DailySet-05 kb 1783648 fm 2 writing file: No space left on device The tape got full after 1783648 was written, you need bigger tape.
Re: chg-zd-mtx strange behaviour
What is the error you get in the report? What is the number of 'reuse' tape in the tapelist? Is it greater than your tapecycle? Jean-Louis Jean-Francois Malouin wrote: Hi, An amanda run last night ended up in the holddisk due to the fact that chg-zd-mtx didn't hunt for the requested tape even it's loaded and it is in 'reuse' mode. Note that previous to the run I had put a tape in `no-reuse' mode but that tape wasn't in the expected set of tapes for this run. Amanda-2.6.0p2 btw. I have attached the debug files but essentially the events went like this: the tape drive got unloaded (the drive was empty so nothing really happened there), then current slot was loaded, then an attemp to add its label to the amanda barcode file but the barcode was already in there, then proceeded to load the next slot containing the tape that amanda was expecting but it just kept going, trying the sync the label to the barcodes file, and that went on for the remaining slots and amanda finally gave up after scanning the whole slot list. Any ideas? I just did a 'amtape $conf label _some_label' without a glitch, amanda hunting and loading the right tape but I see the same pattern right now after trying the flush the hold disk to tape. thanks! jf
Re: Advice on flushing a large dump
Zembower, Kevin wrote: Is your 'holding delete' the same as this version's 'delete'? I'm nervous about something that just says, Delete from database. NO, it's not the same. You should move the holding files on another directory force a full dump of the disk: amadmin $conf force $host $disk run the dump If the full succeed, you can remove the copy of the holding files. Jean-Louis Thanks, again, for trying to help me. -Kevin -Original Message- From: djmit...@gmail.com [mailto:djmit...@gmail.com] On Behalf Of Dustin J. Mitchell Sent: Wednesday, December 17, 2008 10:48 AM To: Zembower, Kevin Cc: amanda-users@amanda.org Subject: Re: Advice on flushing a large dump On Wed, Dec 17, 2008 at 9:54 AM, Zembower, Kevin kzemb...@jhuccp.org wrote: 3). Is there any way to destroy what's on my holdingdisk now for the tobaccodev server, so that amanda will again try to backup at the level it tried before? I've now set the dumptype to use server compression for this host, so I may get a result that will fit on the tape. amadmin $conf holding delete $host [ $disk [ .. ] ] Dustin -- Storage Software Engineer http://www.zmanda.com
Re: autoflush not working in 2.6.0p2?
Steve, you are just crying that autoflush is not working, you post nothing that show it. As a bug reporter, you should show us that you have a bug. Always prove what you say? Prove autoflush is set: what is the output of: amgetconf conf autoflush Prove you have something in the holding disk (before and after a run): ls -alR /path/to/holdingdisk Do those files are amanda file? for each file: dd if=/path/to/holdingdisk/file bs=32k count=1 'amadmin conf find' can also show you have valid amanda image on holding disk. Post all debug and log file if you don't know which one can be useful. Jean-Louis Steven Backus wrote: Ever since upgrading from 2.5.2p1 to 2.6.0p2 my autoflush hasn't worked. After running amdump there's always stuff left in the holding disks. I've also tried amanda-2.6.0p2-20081114 without joy. Let me know what logs you'd like to see. Thanks, Steve
Re: amanda-2.6.2alpha-20081209
Check firewall
Check xinetd configuration
Check system log for error to start amandad
Check amandad.*.debug files.
Check selfcheck.*.debug files.
Jean-Louis
Gene Heskett wrote:
Greetings;
Its borken:
[EMAIL PROTECTED] amanda-2.6.2alpha-20081209]# su amanda -c amcheck Daily
Amanda Tape Server Host Check
-
Holding disk /dumps: 360378368 kB disk space available, using 359866368 kB
slot 5:read label `Dailys-5', date `20081109151648'.
NOTE: skipping tape-writable test
Tape Dailys-5 label ok
Server check took 0.774 seconds
Amanda Backup Client Hosts Check
WARNING: coyote: selfcheck request failed: timeout waiting for ACK
Client check: 1 host checked in 30.034 seconds. 1 problem found.
(brought to you by Amanda 2.6.2alpha-20081209)
But, I get the same response from 2.6.2alpha-20081208 too, wth? It worked
perfectly here last night.
Yumex had just installed updates for awstats, two cups packages, and kdelibs4.
I don't see a connection. I used the same ./gh.cf script:
=
#!/bin/sh
# since I'm always forgetting to su amanda...
if [ `whoami` != 'amanda' ]; then
echo
echo Warning
echo Amanda needs to be configured and built by the user amanda,
echo but must be installed by user root.
echo
exit 1
fi
make clean
rm -f config.status config.cache
./configure --with-user=amanda \
--with-group=disk \
--with-owner=amanda \
--with-gnu-ld \
--prefix=/usr/local \
--with-tapedev=FILE:/amandatapes \
--with-debugging=/tmp/amanda-dbg/ \
--with-tape-server=coyote \
--with-bsdtcp-security --with-amandahosts \
--with-configdir=/usr/local/etc/amanda \
--with-config=Daily \
--with-gnutar=/bin/tar
make
=
That I have been using for ages.
One item I noted, cups was, maybe is also being difficult, and its error
messages are showing the ipv6 stuff, but I don't have that setup here.
The amcheck-debug logs for just now all end like this:
1228884453.747217: amcheck-server: changer: 5 file:/amandatapes/Dailys/
1228884462.991055: amcheck-clients: dgram_send_addr(addr=0x958b258,
dgram=0xb7ea6aa4)
1228884462.991077: amcheck-clients: (sockaddr_in *)0x958b258 = { 2, 10080,
192.168.71.3 }
1228884462.991083: amcheck-clients: dgram_send_addr: 0xb7ea6aa4-socket = 4
1228884473.001013: amcheck-clients: dgram_send_addr(addr=0x958b258,
dgram=0xb7ea6aa4)
1228884473.001034: amcheck-clients: (sockaddr_in *)0x958b258 = { 2, 10080,
192.168.71.3 }
1228884473.001040: amcheck-clients: dgram_send_addr: 0xb7ea6aa4-socket = 4
1228884483.010961: amcheck-clients: security_seterror(handle=0x958b238,
driver=0xb7e9eae0 (BSD) error=timeout waiting for ACK)
1228884483.010994: amcheck-clients: security_close(handle=0x958b238,
driver=0xb7e9eae0 (BSD))
1228884483.011940: amcheck: pid 4664 finish time Tue Dec 9 23:48:03 2008
/home/amanda/.amandahosts hasn't changed in 2 years:
-rw--- 1 amanda amanda 417 2006-11-27 19:29 .amandahosts
Ideas folks?
Re: Fix the order of the dump in Amanda
Is it each samba dle that take take a long time or because they are done sequentially? If each dle take a long time, check for 'dumporder' setting. you might want to set it to TTT. If they are done sequentially, you should increase maxdumps, and be sure the DLEs are not on the same spindle. Jean-Louis Olivier Nicole wrote: Hi, I am using amanda 2.5.1 on the server, is there a way to tell Amanda that dump of certain DLE should be started as soon as possible? I am bacukuping some Unix machines and some Windows machines via Samba. The backup via Samba takes very long time, so I would like to have those started very soon (so they are finished before the user come back to work next morning). Best regards, Olivier
Re: permissions
Seth Rothenberg wrote: I'm looking for a clue for troubleshooting a new amandaclient install. My main problem is that this hasn't been worked on in about 5 years... I have a dozen clients, including two ubuntu GNU/Linux, and we are trying to add one more. This one happens to be Ubuntu/Linux on VMWARE. I can ssh into the new server without password. Is there a way to confirm that amanda is running as the correct user on the new client?Also, I was unable to locate the dumptypes file. I suspect that's where noop is referenced. The error is below - and I found the same text in the amandad log on the client. Thanks Seth Amanda Backup Client Hosts Check ERROR: NAK jirahost: user root from eair2.montefiore.org is not allowed to execute the service noop: Please add amdump to the line in /var/backups/.amandahosts on the client Have you tried what it suggest? Read the amanda man page to know the format of the .amandahosts file. It need: eair2.montefiore.org root amdump Why are you running amcheck as root? It is highly recommended to user a different user for security reason. Jean-Louis
Release of Amanda-2.6.1b1
Hello, The Amanda core team is pleased to announce the first beta release of Amanda 2.6.1, the 2.6.1b1 release. Source tarballs are available from * http://www.amanda.org * https://sourceforge.net/project/showfiles.php?group_id=120 Binaries for many systems are available from * http://www.zmanda.com/download-amanda.php Documentation can be found at * http://wiki.zmanda.com Here's a list of the changes for release 2.6.1b1(from the NEWS file): Look at the ReleaseNotes and ChangeLog file for more details. * Application API: Allow to easily write wrappers around any backup program, see the 'amanda-applications' man page. o amgtar: Use GNU tar, it is a lot more configurable than the GNUTAR program. See 'amgtar' man page. o amstar: Use star to do a backup, it work only on a partition. See'amstar' man page. * Script API: Allow to run script before and after amanda process, see the 'amanda-scripts' man page. o amzfs-snapshot: Do a snapshot of a ZFS filesystem, then 'amgtar'application will backup the snapshot. See 'amzfs-snapshot' man page. o script-email: Simple script to send email. see 'script-email' man page. * Changer API v2.0: perl-based changer interface supporting concurrent use of multiple devices and changers. o currently operating in compatibility mode, calling old changershell scripts. o under active development. * Xfer API: generic library to move and filter data with maximal efficiency o can read from and write to arbitrary devices, files, etc. o only used in some applications. * Amanda archive format: A simple archive format that an application canuse to create backup image. * 'amarchiver' program to manipulate file in amanda archive format. * Many improvements to report better error message to user. * amtape subcommands 'slot prev' and 'slot last' are removed. * Dozens more perl libraries, with more stable interfaces. * Many bugs fixed and improvement. * amgetconf '--client' option to retrieve config from amanda-client.conf on a client. * Amanda configuration file changes o new application-tool section o new script-tool section o new device section o new changer section Jean-Louis martineau
Re: 2.6.1alpha-20081121 oddity
What are you extracting? If the DLE have hard link you must extract the complete DLE. gtar save the DLE only for the first file, this file must be extracted. You tried to extract './sysconfig/networking/profiles/default/hosts' but you didn't extracted './hosts'. Which release of amrecover are you using? Jean-Louis Gene Heskett wrote: Greetings; I have not restarted the nightly amanda run yet, still fine tuning this new install. amrecover finally decided to work for about 95% of the time, but I find its an exellent hard link finder, cuz tar can't deal with those and does an error exit: ./sysconfig/networking/profiles/default/hosts tar: ./sysconfig/networking/profiles/default/hosts: Cannot hard link to `./hosts': No such file or directory ./sysconfig/networking/profiles/default/ifcfg-eth0 ./sysconfig/networking/profiles/default/network ./sysconfig/networking/profiles/default/resolv.conf tar: ./sysconfig/networking/profiles/default/resolv.conf: Cannot hard link to `./resolv.conf': No such file or directory tar: Error exit delayed from previous errors Extractor child exited with status 2 Extracting files using tape drive chg-disk on host coyote. = this doesn't surprise me as I was extracting to /tmp, not /etc. But this next thing bothers me. Can it not get that -o info the /$config/amanda.conf? = Load tape Dailys-13 now Continue [?/Y/n/s/d]? warning: restore program for APPLICATION not available. amrecover couldn't exec: No such file or directory problem executing restore Extractor child exited with status 1 Extracting files using tape drive chg-disk on host coyote. Load tape Dailys-16 now Continue [?/Y/n/s/d]? warning: restore program for APPLICATION not available. amrecover couldn't exec: No such file or directory problem executing restore Extractor child exited with status 1 amrecover exit 200 Good bye. I would assume I would set the '-o amgtar' option on the cli, in which case the first extraction above would probably have failed, while the last 2 tapes would have been read ok instead of the error. Comments Dustin? Have I uncovered a potential gotcha? These tapes straddle the time frame where I converted to using amgtar.
Re: only one slot recognized
Nicholas Brockner wrote: Hi Jean-Louis, Please see inline. Jean-Louis Martineau wrote: What's in your changer config file? -sh-3.2$ more changer.conf changerdev=/dev/sg3 havereader=1 offline_before_unload=1 OFFLINE_BEFORE_UNLOAD=1 poll_drive_ready=10 Max_drive_wait=99 unloadpause=20 driveslot=0 Try to set firstslot and lastslot in the changer.conf file: firstslot=1 lastslot=16 What's the output of : mtx -f /dev/sg? status MTX looks fine: -sh-3.2$ mtx -f /dev/sg3 status Storage Changer /dev/sg3:1 Drives, 16 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Empty Storage Element 3:Empty Storage Element 4:Empty Storage Element 5:Empty Storage Element 6:Empty Storage Element 7:Empty Storage Element 8:Empty Storage Element 9:Empty Storage Element 10:Empty Storage Element 11:Empty Storage Element 12:Empty Storage Element 13:Empty Storage Element 14:Empty Storage Element 15:Empty Storage Element 16:Empty What's in the debug file? -sh-3.2$ more changer.debug Args - -slot advance - loaded -1 Exit - 0 /dev/null Args - -slot advance - loaded -1 Exit - 0 /dev/null Args - -slot advance - loaded -1 Exit - 0 /dev/null Args - -info - info -1 Exit - 0 5 1 Args - -slot current - loaded -1 Exit - 1 /dev/nst0 Args - -slot next - loaded -1 - load 0 - status 1 - result Exit - 0 arguments - -info Exit - none chg-multi: firstslot not specified in /etc/amanda/dailyfull/changer.conf What's that? chg-multi Which changer are you using? You should use chg-zd-mtx What is your tpchanger: amgetconf dailyfull tpchanger It must be set to chg-zd-mtx Jean-Louis
Re: only one slot recognized
Try to put tape in the library, chg-zd-mtx automatically skip empty slot. Jean-Louis Nicholas Brockner wrote: Jean-Louis Martineau wrote: Nicholas Brockner wrote: Hi Jean-Louis, Please see inline. Jean-Louis Martineau wrote: What's in your changer config file? -sh-3.2$ more changer.conf changerdev=/dev/sg3 havereader=1 offline_before_unload=1 OFFLINE_BEFORE_UNLOAD=1 poll_drive_ready=10 Max_drive_wait=99 unloadpause=20 driveslot=0 Try to set firstslot and lastslot in the changer.conf file: firstslot=1 lastslot=16 I did this, and it comes back with: -sh-3.2$ amtape dailyfull show amtape: scanning all 16 slots in tape-changer rack: slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 slot 1: time X label week1tape1 What's the output of : mtx -f /dev/sg? status MTX looks fine: -sh-3.2$ mtx -f /dev/sg3 status Storage Changer /dev/sg3:1 Drives, 16 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Empty Storage Element 3:Empty Storage Element 4:Empty Storage Element 5:Empty Storage Element 6:Empty Storage Element 7:Empty Storage Element 8:Empty Storage Element 9:Empty Storage Element 10:Empty Storage Element 11:Empty Storage Element 12:Empty Storage Element 13:Empty Storage Element 14:Empty Storage Element 15:Empty Storage Element 16:Empty What's in the debug file? -sh-3.2$ more changer.debug Args - -slot advance - loaded -1 Exit - 0 /dev/null Args - -slot advance - loaded -1 Exit - 0 /dev/null Args - -slot advance - loaded -1 Exit - 0 /dev/null Args - -info - info -1 Exit - 0 5 1 Args - -slot current - loaded -1 Exit - 1 /dev/nst0 Args - -slot next - loaded -1 - load 0 - status 1 - result Exit - 0 arguments - -info Exit - none chg-multi: firstslot not specified in /etc/amanda/dailyfull/changer.conf What's that? chg-multi Which changer are you using? You should use chg-zd-mtx That is a remnant- I was trying everything yesterday to get it working. I am using chg-zd-mtx. What is your tpchanger: amgetconf dailyfull tpchanger -sh-3.2$ amgetconf dailyfull tpchanger chg-zd-mtx It must be set to chg-zd-mtx Jean-Louis
Re: only one slot recognized
What's in your changer config file? What's the output of : mtx -f /dev/sg? status What's in the debug file? Jean-Louis Nicholas Brockner wrote: Hi All, I have been banging my head against this all day: I have a superloader3 16 slot LTO3 unit I am trying to set up. For some reason, the glue script only sees one slot (slot 1): -sh-3.2$ /usr/libexec/amanda/chg-zd-mtx -info 1 1 1 1 -sh-3.2$ amtape dailyfull show amtape: scanning all 1 slots in tape-changer rack: slot 1: time X label week1tape1 I am using 2.6.0p2 on Centos 5.2. any ideas? -Nick
Re: amanda-2.6.0p2: a few remarks and questions
Try this newest patch.
Some fix will works only if the dump is done with the patched version.
Jean-Louis
Jean-Francois Malouin wrote:
* Jean-Louis Martineau [EMAIL PROTECTED] [2008 20:12]:
Hi Jean-François,
Can you try the attached patch?
Tried it but something is still missing. Mind you, I just applied
the patch and recompiled: this is from a previous run.
-amreport: patch works: it reports tape rate above 100MBs
Avg Tp Write Rate (k/s) 109575 109575--
-amstatus: I still don't get the lines 'tape X', like:
taped : 25422328m423178m ( 99.80%) ( 99.80%)
tape 1: 25422328m423178m (109.40%) av24_U00061L3 (79 chunks)
-amtoc: I was doing my own edit of the amtoc perl script when you sent
me the patch. If I run the patched amtoc on a previous log file I get
something like:
# Server:/partition date lev size[Kb]
0 av48-1_top_R00012L4:200811101 - -
1 gustav:/raid/prefrontal 200811101 0 *16777216
2 gustav:/raid/prefrontal 200811101 0 *16777216
...
21 gustav:/raid/prefrontal 200811101 0 *16777216
22 gustav:/raid/prefrontal 200811101 0 367489930
Notice the '*'. There is something wrong around line 228 of amtoc:
if(!/^CHUNK/){
# this case should never happend:
$strange=1;
$note = *;
}
It inserts the '*' on the chunk size. Also the total:on_tape is missing.
This is simple perl stuff, I should be able to do something about it!
Thanks a lot.
jf
Jean-Louis
Jean-Francois Malouin wrote:
Hello,
I've finally got to install amanda-2.6.0p2 on a system going soon into
production and while getting used to the new features and I noticed a
few things that have changed since 2.5.x :
- I use amtoc after a dump ends to get stats on what was written on
tape and noticed that it doesn't parse correctly the log files and the
toc files end up not showing what was written on tape. Looking at the
source I believe that this is due to the fact that amtoc doesn't parse
lines that start with 'PART' as the new log format seems to use
compared to 'CHUNK' in pre-2.6.x.
- amstatus doesn't show which tape(s) is being used and how much data
been written to it so far, a useful feature when I want to check that
a flush is being done correctly when using a changer with 'runtapes1'
- As I posted a few days ago, amreport doesn't report correctly the
aggragated transfer rate to tape beyond 99.99MiBs...
- The new version features 'device_output_buffer_size' that replaces
'tapebufs'. Any hint on a ballpark figure for this? Right now I have
set it to 8192k (I use a blocksize=2048k) but I really don't know if I
overshooting with this...the server has 32GB of memory btw.
Thank you for the amazing work you guys are doing!
jf
Index: server-src/amstatus.pl
===
--- server-src/amstatus.pl (revision 14198)
+++ server-src/amstatus.pl (working copy)
@@ -722,6 +722,16 @@
$ntsize{$nb_tape} = 0;
$ntesize{$nb_tape} = 0;
}
+ elsif($line[1] eq using) {
+ #1:using #2:label #3:`label' #4:date #5 `timestamp'
+ $nb_tape++;
+ $lineX =~ /using label `(\S*)'/;
+ $label = $1;
+ $ntlabel{$nb_tape} = $label;
+ $ntpartition{$nb_tape} = 0;
+ $ntsize{$nb_tape} = 0;
+ $ntesize{$nb_tape} = 0;
+ }
}
elsif($line[0] eq splitting
$line[1] eq chunk
Index: server-src/driver.c
===
--- server-src/driver.c (revision 14198)
+++ server-src/driver.c (working copy)
@@ -303,6 +303,7 @@
conf_runtapes = getconf_int(CNF_RUNTAPES);
tape = lookup_tapetype(conf_tapetype);
tape_length = tapetype_get_length(tape);
+g_printf(driver: tape size %lld\n, (long long)tape_length);
conf_flush_threshold_dumped = getconf_int(CNF_FLUSH_THRESHOLD_DUMPED);
conf_flush_threshold_scheduled = getconf_int(CNF_FLUSH_THRESHOLD_SCHEDULED);
conf_taperflush = getconf_int(CNF_TAPERFLUSH);
Index: server-src/amtoc.pl
===
--- server-src/amtoc.pl (revision 14198)
+++ server-src/amtoc.pl (working copy)
@@ -162,11 +162,26 @@
}
if ( ! /^([A-Z]+) taper (\S+) (\S+) (\S+) (\S+) (\S+)/) { next;}
# $_ = $1;
- $host = $2;
- $disk = $3;
- $date = $4;
- $chunk = $5;
- $level = $6;
+ if (/PART taper/) {
+/^([A-Z]+) taper (\S+) (\S+) (\S+) (\S+) (\S+) (\S+) (\S+)/;
+$filenum = $3;
+$host = $4;
+$disk = $5;
+$date = $6;
+$chunk = $7;
+$level = $8;
+if ($filenum != $filenumber) {
+ # This should not be possible */
+ $filenumber = $filenum;
+}
+ } else {
+/^([A-Z]+) taper (\S+) (\S+) (\S+) (\S+) (\S+)/;
+$host = $2;
+$disk = $3;
+$date = $4;
+$chunk = $5;
+$level = $6
Re: amanda-2.6.0p2: a few remarks and questions
Hi Jean-François,
Can you try the attached patch?
Jean-Louis
Jean-Francois Malouin wrote:
Hello,
I've finally got to install amanda-2.6.0p2 on a system going soon into
production and while getting used to the new features and I noticed a
few things that have changed since 2.5.x :
- I use amtoc after a dump ends to get stats on what was written on
tape and noticed that it doesn't parse correctly the log files and the
toc files end up not showing what was written on tape. Looking at the
source I believe that this is due to the fact that amtoc doesn't parse
lines that start with 'PART' as the new log format seems to use
compared to 'CHUNK' in pre-2.6.x.
- amstatus doesn't show which tape(s) is being used and how much data
been written to it so far, a useful feature when I want to check that
a flush is being done correctly when using a changer with 'runtapes1'
- As I posted a few days ago, amreport doesn't report correctly the
aggragated transfer rate to tape beyond 99.99MiBs...
- The new version features 'device_output_buffer_size' that replaces
'tapebufs'. Any hint on a ballpark figure for this? Right now I have
set it to 8192k (I use a blocksize=2048k) but I really don't know if I
overshooting with this...the server has 32GB of memory btw.
Thank you for the amazing work you guys are doing!
jf
Index: server-src/amstatus.pl
===
--- server-src/amstatus.pl (revision 14148)
+++ server-src/amstatus.pl (working copy)
@@ -722,6 +722,16 @@
$ntsize{$nb_tape} = 0;
$ntesize{$nb_tape} = 0;
}
+ elsif($line[1] eq using) {
+ #1:using #2:label #3:`label' #4:date #5 `timestamp'
+ $nb_tape++;
+ $lineX =~ /using label `(\S*)'/;
+ $label = $1;
+ $ntlabel{$nb_tape} = $label;
+ $ntpartition{$nb_tape} = 0;
+ $ntsize{$nb_tape} = 0;
+ $ntesize{$nb_tape} = 0;
+ }
}
elsif($line[0] eq splitting
$line[1] eq chunk
Index: server-src/driver.c
===
--- server-src/driver.c (revision 14148)
+++ server-src/driver.c (working copy)
@@ -303,6 +303,7 @@
conf_runtapes = getconf_int(CNF_RUNTAPES);
tape = lookup_tapetype(conf_tapetype);
tape_length = tapetype_get_length(tape);
+g_printf(driver: tape size %lld\n, (long long)tape_length);
conf_flush_threshold_dumped = getconf_int(CNF_FLUSH_THRESHOLD_DUMPED);
conf_flush_threshold_scheduled = getconf_int(CNF_FLUSH_THRESHOLD_SCHEDULED);
conf_taperflush = getconf_int(CNF_TAPERFLUSH);
Index: server-src/amtoc.pl
===
--- server-src/amtoc.pl (revision 14148)
+++ server-src/amtoc.pl (working copy)
@@ -162,11 +162,26 @@
}
if ( ! /^([A-Z]+) taper (\S+) (\S+) (\S+) (\S+) (\S+)/) { next;}
# $_ = $1;
- $host = $2;
- $disk = $3;
- $date = $4;
- $chunk = $5;
- $level = $6;
+ if (/PART taper/) {
+/^([A-Z]+) taper (\S+) (\S+) (\S+) (\S+) (\S+) (\S+) (\S+)/;
+$filenum = $3;
+$host = $4;
+$disk = $5;
+$date = $6;
+$chunk = $7;
+$level = $8;
+if ($filenum != $filenumber) {
+ # This should not be possible */
+ $filenumber = $filenum;
+}
+ } else {
+/^([A-Z]+) taper (\S+) (\S+) (\S+) (\S+) (\S+)/;
+$host = $2;
+$disk = $3;
+$date = $4;
+$chunk = $5;
+$level = $6;
+ }
switch: {
/START taper/ do {
$tocfilename=tfn($chunk) if ($#subs = 0);
@@ -191,7 +206,7 @@
pr(#,Server,/partition,date, level,size[Kb],part);
pr($filenumber,$chunk,,$disk,-,-,-);
last switch; };
-/^(?:SUCCESS|CHUNK) taper/ do {
+/^(?:SUCCESS|CHUNK|PART) taper/ do {
if(/SUCCESS/){
$level = $chunk;
$chunk = -;
@@ -239,6 +254,9 @@
}
last switch; };
/FAIL taper/ do { next; };
+/DONE taper/ do {
+ $filenumber -= 1;
+ last switch; };
}
$filenumber += 1;
}
Index: server-src/reporter.c
===
--- server-src/reporter.c (revision 14148)
+++ server-src/reporter.c (working copy)
@@ -826,20 +826,24 @@
double q = (b); \
if (!isnormal(q)) \
g_fprintf((fp), -- ); \
- else if ((q = (a)/q) = 999.95) \
- g_fprintf((fp), ###.#); \
+ else if ((q = (a)/q) = 9.95) \
+ g_fprintf((fp), #); \
+ else if (q = 999.95) \
+ g_fprintf((fp), %5.0lf,q);\
else\
- g_fprintf((fp), %5.1lf,q); \
+ g_fprintf((fp), %5.1lf,q);\
} while(0)
#define divzero_wide(fp,a,b) \
do { \
double q = (b); \
if (!isnormal(q)) \
g_fprintf((fp),-- ); \
- else if ((q = (a)/q) = 9.95) \
- g_fprintf((fp), #.#); \
+ else if ((q = (a)/q) = 999.95) \
+ g_fprintf((fp), ###); \
+ else if (q = 9.95) \
+ g_fprintf((fp), %7.0lf,q);\
else\
- g_fprintf((fp), %7.1lf,q);
Re: amrecover ignores --prefix
What are the other configure option? Is it amrecover that use /usr/local or is it amindexd and amidxtaped? check you xinetd config to be sure you run the amandad in /local/... Jean-Louis Steven Backus wrote: I'm doing a trial installation of amanda and don't want to mess up my regular install, so I compiled with --prefix=/local. Regardless of this, amrecover is still looking for my config files in /usr/local/etc/amanda/config instead of /local/etc/amanda/config. Is this expected behavior, a bug or ? I'm using amanda-2.6.0p2. Steve
Re: amfetchdump: running as user root instead of amanda ??
Jean-Francois Malouin wrote: * Jean-Louis Martineau [EMAIL PROTECTED] [20081104 13:46]: Jean-Francois Malouin wrote: Is this a new feature? I've done restore as root in the past I'm sure and never seen this before. Have been living blind all this time? :) So I guess I was lucky enough to do the amfetchdump in a dir owned by amanda and then it could recreate the dir structure and file ownerships... Maybe you were using amrestore? It doesn't need amanda privilege. I've used both for testing purposes before. I've just finished a new restore test on a new piece of hardware: # su amanda -c /opt/amanda/sbin/amfetchdump -b 2048k -p -d tape:/dev/nst0 top gustav /raid/ipl 20081104 | tar -xpGf - amfetchdump must be run by amanda, tar must be run by root. Logged as root, you do: # su amanda -c /opt/amanda/sbin/amfetchdump -b 2048k -p -d tape:/dev/nst0 top gustav /raid/ipl 20081104 | tar -xpGf - Look where I put the . completes ok, looks good, the dle was successfully restored but tar didn't restore the original ownerships of the dirs and files, they all belong to user 'amanda' and group 'disk', its primary group, as I was suspicious it would do in the first place, but I wanted to be 100% sure before posting. # tar --version tar (GNU tar) 1.16 I don't see this on a another system, running the same amanda version, 2.5.2p1, but from a much earlier configured and compiled tarball Proof is in the pudding. From a debug amandad: amandad: time 0.016: build: VERSION=Amanda-2.5.2p1 amandad: time 0.016:BUILT_DATE=Fri Jul 6 12:27:48 EDT 2007 amandad: time 0.016:BUILT_MACH=IRIX64 wart 6.5 01062343 IP27 yorick 117# /opt/amanda/amanda1/sbin/amfetchdump -p -d /hw/tape/tps21d1nrnsv stk_80-conf1 yorick /data/speechprod/speechprod2 20081030 | /usr/freeware/bin/tar -xpGf - 1 tape(s) needed for restoration The following tapes are needed: 38 Press enter when ready Scanning 38 (slot 1) and the restore completes ok. That's with tar (GNU tar) 1.13.25. So that leads me to believe that it's either something that has been backported in the tarball for 2.5.2p1 since then or is it a problem with tar 1.16 on a Debian Etch machine? thanks, jf Jean-Louis
Re: Stranded on waitq failure (planner: Message too long)
Ian Turner wrote: I don't know if 2.5.1 is old enough to qualify for this issue, but it used to be the case that the entire set of disklists for a client had to fit in a single packet. What that meant is that if you had more than a few dozen disks on one client (depending on disklist options), you would run into this issue. The solution is to upgrade, but a workaround is to create a second IP address and DNS name on the same physical client, and move some of the disklist entries to the latter. Or change to the 'bsdtcp' auth. Jean-Louis --Ian On Wednesday 05 November 2008 13:57:22 Dustin J. Mitchell wrote: On Fri, Oct 31, 2008 at 9:01 AM, Leon Meßner [EMAIL PROTECTED] wrote: i get the following message with Amanda-2.5.1p3 on FreeBSD7.0: FAILED [hmm, disk was stranded on waitq] planner: ERROR Request to myhostandserver failed: error sending REQ: send REQ to myhostandserver failed: Message too long As you've no doubt discovered, this means that the REQ packet was too large to fit into a single UDP datagram. I know that we've added some additional information to the packets in recent versions, but I don't know why that would be the case in 2.5.1. Have others seen a similar error? Dustin
Re: amfetchdump: running as user root instead of amanda ??
Jean-Francois Malouin wrote: Running amanda-2.6.0p2 an attempting to restore a run: # id uid=0(root) gid=0(root) groups=0(root) # amfetchdump -p -d tape:/dev/nst0 conf1 gustav | tar -xpGf - amfetchdump: running as user root instead of amanda ugh? jf amfetchdump must be able to access the amanda log and index. Only the 'amanda' user can do it. su amanda -c amfetchdump -p -d tape:/dev/nst0 conf1 gustav | tar -xpGf - Jean-Louis
Re: amfetchdump: running as user root instead of amanda ??
Jean-Francois Malouin wrote: Is this a new feature? I've done restore as root in the past I'm sure and never seen this before. Have been living blind all this time? :) So I guess I was lucky enough to do the amfetchdump in a dir owned by amanda and then it could recreate the dir structure and file ownerships... Maybe you were using amrestore? It doesn't need amanda privilege. Jean-Louis
Re: [Amanda-users] Amrecover is not starting
rakesh wrote: Hi I have tried to apply the recommended changes and after doing so i started to get the error, i have copied syslog along with .amandahosts contents and xinetd config details for amanda [EMAIL PROTECTED]:/backup/amanda_hold/DailySet1# amrecover AMRECOVER Version 2.5.1p1. Contacting server on localhost ... NAK: user root from localhost is not allowed to execute the service amindexd: Please add amindexd amidxtaped to the line in /var/lib/amanda/.amandahosts /var/lib/amanda/.amandahosts needs the following line localhost root amindexd amidxtaped Jean-Louis ### [EMAIL PROTECTED]:/var/lib/amanda# cat .amandahosts localhost amanda localhost root localhost.localdomain root amindexd amidxtaped BackUp-Host-Server root amindexd amidxtaped BackUp-Client amanda BackUp-Client amanda BackUp-Client amanda BackUp-Client amanda BackUp-Client amanda ##
Re: [Amanda-users] Amrecover is not starting
rakesh wrote: Hi Thanks a lot your recomendations worked, atlast amrecover has started but i haven't recovered any files till now.I would like to share some entries of the same , what am i missing in here ? [EMAIL PROTECTED]:/backup/amanda_hold/DailySet1# amrecover AMRECOVER Version 2.5.1p1. Contacting server on localhost ... 220 BackUp-Host-Server AMANDA index server (2.5.1p1) ready. Setting restore date to today (2008-10-31) 200 Working date set to 2008-10-31. 200 Config set to DailySet1. 501 No index records for host: BackUp-Host-Server. Have you enabled indexing? Trying host BackUp-Host-Server.translogicsys.com ... 501 Host BackUp-Host-Server.translogicsys.com is not in your disklist. Trying host BackUp-Host-Server ... 501 No index records for host: BackUp-Host-Server. Have you enabled indexing? Use the sethost command to choose a host to recover Use the sethost command to choose a host to recover. What help do you want, amrecover told you what to do! Use the 'listhost' command if you don't know the hostname in the disklist file You can also try the 'help' command or 'man amrecover'. Jean-Louis
Re: [Amanda-users] Amrecover is not starting
rakesh wrote: Hi amandad.*.debug is not generating any new logs Then check your xinetd config and system log. Jean-Louis
Re: amrecover, enter directory with a space
Thomas Vogt wrote: Hello I use amanda-server-2.5.1p3 and amanda-client-2.5.1p3 with FreeBSD 6.3. Today I tried to restore a file from a directory with spaces in the name. I started amrecover, set host and disk and tried to access my directory called Data Check. When i type ls in amrecover i see: 2008-10-28 Data Check/ 2008-10-20 Data/ 2008-10-20 Security I can not access Data Check/. cd Data Check puts my into Data/ instead of Data Check. Also cd Data\ Check (Data\ is not a valid shell wildcard pattern: trailing backslash (\)) or cd Data Check (Invalid directory -) didnt help. Any idea how i can enter my directory with a space in its name? Next time, do a cut-and-paste of your amrecover session, it is easier to read. try: cd Data*Check Jean-Louis
Re: Indexing a client
Prashant Ramhit wrote: Hi Paddy, Thanks for you email. I am using GNUTAR. Index is set to yes in amanda.conf and all other clients are being indexed. What's the output of: amadmin config disklist Did it list 'index YES' for the DLE? Do you get index under your indexdir (amgetconf config indexdir)? Do the DLE was successfully backup? amadmin config find Why do you think indexing is not done? Jean-Louis
Re: [Fwd: Re: Tape Autoloader]
Prashant Ramhit wrote: Changer problem: mtx command (mtx) doesn't exist changer problem: mtx command (mtx) doesn't exist (expecting a new tape) mtx was not in your when you configured amanda, add it to your PATh and reconfigure amanda. Check the configure output to know if it find it. Server check took 0.052 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.111 seconds, 0 problems found (brought to you by Amanda 2.5.2) [EMAIL PROTECTED]:~$ 2. No access to mtx [EMAIL PROTECTED]:~$ mtx -f /dev/sg2 status cannot open SCSI device '/dev/sg2' - Permission denied You must to the amanda user or group the privilege to read/write that device. Jean-Louis
Re: problems with amtape and amanda 2.6.0p2
Are you sure /dev/rmt/1cn is the device for the tape drive? What's the output of: mt -f /dev/rmt/1cn status mt -f /dev/rmt/1cn rewind Jean-Louis Krahn, Anderson wrote: Trying to label my tapes and I get the following errors: ]#/opt/amanda/amanda-2.6.0p2/server-src/amtape Full update amtape: scanning all 7 slots in tape-changer rack: /dev/rmt/1cn uses deprecated device naming convention; using tape:/dev/rmt/1cn instead. Error rewinding device /dev/rmt/1cn amtape: slot 2: Device error, or Volume error /dev/rmt/1cn uses deprecated device naming convention; using tape:/dev/rmt/1cn instead. Error rewinding device /dev/rmt/1cn amtape: slot 3: Device error, or Volume error /dev/rmt/1cn uses deprecated device naming convention; using tape:/dev/rmt/1cn instead. Error rewinding device /dev/rmt/1cn amtape: slot 4: Device error, or Volume error /dev/rmt/1cn uses deprecated device naming convention; using tape:/dev/rmt/1cn instead. Error rewinding device /dev/rmt/1cn amtape: slot 5: Device error, or Volume error /dev/rmt/1cn uses deprecated device naming convention; using tape:/dev/rmt/1cn instead. Error rewinding device /dev/rmt/1cn amtape: slot 6: Device error, or Volume error /dev/rmt/1cn uses deprecated device naming convention; using tape:/dev/rmt/1cn instead. Error rewinding device /dev/rmt/1cn amtape: slot 7: Device error, or Volume error /dev/rmt/1cn uses deprecated device naming convention; using tape:/dev/rmt/1cn instead. Error rewinding device /dev/rmt/1cn amtape: slot 8: Device error, or Volume error server debug logs: 14:41:49 Return (0) - 7 /dev/rmt/1cn 14:41:49 LOADSLOT - loading tape from slot 8 to drive 0 (/dev/rmt/1cn) 14:41:50 Running: /usr/local/sbin/mtxRunning: loadRunning: 8Running: 0 14:42:31 Exit code: 0 Stdout: Loading media from Storage Element 8 into drive 0...done 14:42:31 - status 0, result Loading - status media, result from - status Storage, result Element - status 8, result into - status drive, result 0...done 14:42:47 Exit (0) - 8 /dev/rmt/1cn 1224531767.850148: chg-zd-mtx: pid 1479 finish time Mon Oct 20 14:42:47 2008 Config debug logs: /dev/rmt/1cn uses deprecated device naming convention; using tape:/dev/rmt/1cn instead. Error rewinding device /dev/rmt/1cn 1224531422.139664: amtape: device_read_label; mode = 0 /dev/rmt/1cn uses deprecated device naming convention; using tape:/dev/rmt/1cn instead. Error rewinding device /dev/rmt/1cn 1224531530.131799: amtape: device_read_label; mode = 0 /dev/rmt/1cn uses deprecated device naming convention; using tape:/dev/rmt/1cn instead. Error rewinding device /dev/rmt/1cn 1224531646.317800: amtape: device_read_label; mode = 0 /dev/rmt/1cn uses deprecated device naming convention; using tape:/dev/rmt/1cn instead. Error rewinding device /dev/rmt/1cn 1224531767.865606: amtape: device_read_label; mode = 0 1224531782.916559: amtape: pid 29419 finish time Mon Oct 20 14:43:02 2008 For some reason it is not able to rewind the tape. Any ideas? Anderson
Re: Disklist question
man amanda.conf: diskfile string Default: disklist. The file name for the disklist file holding client hosts, disks and other client dumping information. You can use: amdump -odiskfile=disklista Why do you want to do use different disklist file? You could have one disklist and specify the DLE on the command line. Jean-Louis McGraw, Robert P wrote: I want to be able to use a different disklist for different runs. Other than use shell scripting to mv disklista to disklist is there a way to tell amanda what disklist to use during a run. Robert -- Robert P. McGraw, Jr. Manager, Computer System EMAIL: [EMAIL PROTECTED] Purdue University ROOM: MATH-807 Department of Mathematics PHONE: (765) 494-6055 150 N. University Street West Lafayette, IN 47907-2067
Re: DUMP: You can't update the dumpdates file when dumping a subdirectory
Aaron, You are right some dump works on directory but amanda doesn't use the -T parameter. It is a dangerous option, all backup program working with a timestamps (all dump flavour and star) have the same problem. If a directory is moved across the directories you backup, it is not include in the dump until the next full. GNUTAR doesn't have this problem because it keep a complete list of files, not just a timestamps. A small example of the problem: /home is the root of the partition, you have two files: /home/foo/a/b/c /home/bar/c/b/a You backup the two directory separately. You have the following backup sequence and one user operation: /home/foo /home/bar TAPE day 1 0 1 tape-01 day 2 1 1 tape-02 day 3 1 1 tape-03 day 4 1 1 tape-04 day 5 1 0 tape-05 a user do: mv /home/foo/a /home/bar day 6 1 1 tape-06 day 7 1 1 tape-07 day 8 0 1 tape-08 day 9 1 1 tape-01 day 10 1 1 tape-02 day 11 1 1 tape-03 day 12 1 0 tape-04 /home/bar/a/b/c will not be in the backup of /home/bar until day 12 on tape-04 If you restore the backup for day 6 or 7 /home/foo level 0 on tape tape-01, level 1 on tape tape-06 or tape-07 /home/bar level 0 on tape tape-05, level 1 on tape tape-06 or tape-07 then you end up with no /home/bar/a/b/c file, and no /home/foo/a/b/c file, you can recover /home/foo/a/b/c from level 0 of /home/foo on tape-01, but how do you know the user moved the files. That's worse, after day 9 and overwrite of tape-01, the a/b/c file is not on tape, there is no way to recover it On day 12, it will be on the level 0 backup of /home/bar. Jean-Louis Aaron J. Grier wrote: On Thu, Oct 02, 2008 at 10:15:52AM -0400, Jean-Louis Martineau wrote: sendbackup: info end | DUMP: You can't update the dumpdates file when dumping a subdirectory | DUMP: The ENTIRE dump is aborted. sendbackup: error [dump (20830) /sbin/dump returned 1] Like the message says: You can't use DUMP to backup a subdirectory, DUMP work only on partition. You must use GNUTAR to backup a directory. I beg your pardon, but /sbin/dump is perfectly capable of dumping subdirectories on most unixes. it just won't record (or read) the date of the dump in /etc/dumpdates. a lot of /sbin/dump will accept a -T parameter to specify a date for incrementals. I assume tar requires a similar parameter, perhaps it could be used with /sbin/dump as well?
Re: DUMP: You can't update the dumpdates file when dumping a subdirectory
Like the message says: You can't use DUMP to backup a subdirectory, DUMP work only on partition. You must use GNUTAR to backup a directory. Jean-Louis Neil Marjoram wrote: Hello all, I'm a little confused, I've been running the same config for years, last change a couple of years ago, and now I am starting to get some errors on two systems. Both the systems are RHEL 5.x (latest), running a compiled 2.5.2p1 to get over a redhat omission, interestingly one system is a clone of the other (nearly!), both the system fail backing up /usr/local. Other directories backup with no issues. I've got no clues, the debug spits out exactly the same error as the log, so no extra info there, /-- host1 /usr/local lev 0 FAILED [dump (20830) /sbin/dump returned 1] sendbackup: start [host1:/usr/local level 0] sendbackup: info BACKUP=/sbin/dump sendbackup: info RECOVER_CMD=/bin/gzip -dc |/sbin/restore -xpGf - ... sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | DUMP: You can't update the dumpdates file when dumping a subdirectory | DUMP: The ENTIRE dump is aborted. sendbackup: error [dump (20830) /sbin/dump returned 1] \ Does anyone know what this is? Many thanks, Neil.
Re: amanda and live directory
Increase the estimate timeout setting (etimeout) in amanda.conf.
Jean-Louis
aminukapon wrote:
Hello all,
I have 2 directories that I'm trying to backup ...both directories are live and
constantly running (P.s:- running a website off them).. I have tried to backup
them up but amanda keeps giving me a time out error...
Here is a the report I get from one of the directories (webdir)
To: [EMAIL PROTECTED]
Subject: DailySet5 AMANDA MAIL REPORT FOR October 1, 2008
Message-Id: [EMAIL PROTECTED]
From: backup [EMAIL PROTECTED]
Date: Wed, 01 Oct 2008 17:18:22 -0400
Hostname: sys1
Org : DailySet5
Config : DailySet5
Date: October 1, 2008
These dumps were to tape DailySet50-07.
The next tape Amanda expects to use is: a new tape.
The next new tape already labelled is: DailySet50-08.
FAILURE AND STRANGE DUMP SUMMARY:
localhost /home1/webdir lev 0 FAILED [disk /home1/webdir, all estimate
timed out]
planner: ERROR Request to localhost failed: timeout waiting for REP
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min)0:15
Run Time (hrs:min) 0:15
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Chunks Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
USAGE BY TAPE:
Label Time Size %NbNc
DailySet50-07 0:000K0.0 0 0
NOTES:
planner: disk localhost:/home1/webdir, estimate of level 0 timed out.
driver: WARNING: got empty schedule from planner
taper: tape DailySet50-07 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- - -
localhost-/webdir 0 FAILED
(brought to you by Amanda version 2.5.2p1)
Re: Space in directory name
Hans Sandsdalen wrote: Hi I use amanda 2.4.4p3 and have a problem with a space ( ) in a directory name in a disklist. How do I specify a directory name with a space in it? You can't, newer version can do it easily. Easiest solution is to create a simlink: cd /disk1/vmuser ln -s Virtual\ Machines/puck Virtual_Machines/puck and backup /disk1/vmuser/Virtual_Machines/puck New newer release, you can do: host /disk1/vmuser/Virtual Machines/puck comp-user-tar Jean-Louis I have a directory called /disk1/vmuser/Virtual Machines/puck on a host, and I try with host /disk1/vmuser/Virtual_Machines/puck comp-user-tar in the diskelist. A result from amcheck -c CONFIG: Amanda Backup Client Hosts Check ERROR: host: [Can't open exclude file 'Machines/puck/.exclude': No such file or directory] ERROR: host: [could not access Machines/puck (/disk1/vmuser/Virtual): No such file or directory] ERROR: host: [Can't open exclude file '/home/Virtual-Machines/kastra/.exclude': No such file or directory] Client check: 1 host checked in 0.018 seconds, 3 problems found (brought to you by Amanda 2.4.4p3)
Re: Logs and reporting
Prashant Ramhit wrote: Hi All, Thanks for your help. Attached is the amdump.1 Do you think its because it is not using the tape FULLBACK-01. How can I make it to reuse fullback-01 again. Do the following two command: amrmtape fullbackfullback-01 amlabel -f fullback fullback-01 Your 'mailto' is set to 'root', did it receive the email report? Jean-Louis
Re: Dumps cannot be retrieved from tape...
Do 'amadmin config find' list the dump you want to restore? What error do you get from amrecover? no longer accessible is not helpful to find the problem. Which amanda release are you using? You can try to use amrestore on the server. Jean-Louis Dan Brown wrote: Hi, I've got a backup set for a bunch of Mac OS X users who are backed up on a daily basis via Samba shares. Backups are first backed up to holding disk, then dumped to tape once I've got enough to fill an LTO3 tape. The other day I was asked to restore a file which had ended up going on to tape (just a day or two ago). I came to realize that all backups which have been flushed to tape, are no longer accessible via amrecover. Backups which are still on the holding disk can be accessed. This appears to be a samba share backup specific problem as a near identical setup with a number of Linux servers (although using the server client) does not have this problem. There was one samba share backup in that profile up until a month or so ago but I've never had to restore anything for it. I know it's there because the index exists for it but the index-tape association doesn't appear to have occured. So I've got two questions: 1. How do I fix my config (I assume it's a config problem) so that files can be retrieved from tape for this profile (otherwise I might as well set my tape device to be /dev/null)? 2. How do I retrieve my file off of tape not using amrecover? - Dan Brown [EMAIL PROTECTED]
Re: Dumps cannot be retrieved from tape...
amrecover require a level 0 to still exist to works. You have no level 0 dump of the disk (according to amadmin), it is very dangerous, it is impossible for amanda to restore the complete disk. I'm surprised amrecover show you the level 2 dump that are on holding disk, it should not. Jean-Louis Dan Brown wrote: Chris Hoogendyk wrote: First, it should work. amrecover should get things off the holding disk or off tape as appropriate. When you say came to realize, I think we need some more detail on what you mean by that. What errors did you get? How did you try? Did you use setdate to get the file you wanted from a particular backup? Here's what I see when I use amrecover. [EMAIL PROTECTED] __designmac_design_resources_]# amrecover Macs could not open conf file /etc//amanda/amanda-client.conf: No such file or directory AMRECOVER Version 2.6.0p1. Contacting server on ministryofinformation ... 220 ministryofinformation AMANDA index server (2.5.2p1) ready. Setting restore date to today (2008-09-23) 200 Working date set to 2008-09-23. 200 Config set to Macs. 200 Dump host set to ministryofinformation. Use the setdisk command to choose dump disk to recover amrecover setdisk //designmac/design_resources/ 200 Disk set to //designmac/design_resources/. amrecover setdate ---16 200 Working date set to 2008-09-16. No index records for cwd on new date Setting cwd to mount point amrecover It does this for anything before 2008-09-19, which is for when I still have backups still waiting in the holding disk. The file I want is from the 16th however. Did you try history in amrecover to see what it thought you had after you had sethost and setdisk? Did you sethost to where the samba share was mounted and backed up from? As opposed to the machine it originated on? The backup server is the ministryofinformation (Brazil reference), hence all samba shares on Mac OS X clients are backed up from being mounted by the server. ministryofinformation //designmac/design_resource_archive/user-tar ministryofinformation //designmac/design_resources/ user-tar A history command shows the following: amrecover setdisk //designmac/design_resources/ 200 Disk set to //designmac/design_resources/. amrecover history 200- Dump history for config Macs host ministryofinformation disk //designmac/design_resources/ 201- 2008-09-22-10-45-01 2 /dumps/holding-mac/20080922104501/ministryofinformation.__designmac_design_r esources_.2:0 201- 2008-09-21-10-45-01 2 /dumps/holding-mac/20080921104501/ministryofinformation.__designmac_design_r esources_.2:0 201- 2008-09-20-10-45-01 2 /dumps/holding-mac/20080920104501/ministryofinformation.__designmac_design_r esources_.2:0 201- 2008-09-19-10-45-01 2 /dumps/holding-mac/20080919104501/ministryofinformation.__designmac_design_r esources_.2:0 200 Dump history for config Macs host ministryofinformation disk //designmac/design_resources/ amrecover
Re: gtar 1.13.25 follows symlinks?
man tar -C, --directory DIR change to directory DIR It change the directory to '/data/nihpd/nihpd3/users' and then backup '.' It is the expected behaviour. The DLE should not be a symlink if you don't want to follow it. Jean-Louis Jean-Francois Malouin wrote: A funny thing happened when I forced a full of a DLE on a client. I had noticed a few days before that a user had moved the content of the entire DLE (/data/nihpd/nihpd3/users) to another disk and replaced it with a symlink pointing to its new location: # ls -ld /data/nihpd/nihpd3/users lrwxr-xr-x1 root sys 24 Sep 10 09:49 /data/nihpd/nihpd3/users - /data/nihpd/nihpd1/users/ Now, I see in the amanda report that the dump size this DLE is 126GB. Scary: looks like this version of gnutar (1.13.25) follows symlinks. I always thought that this version was 'safe'... I manually reran the gnutar sending the output to the bit bucket: /usr/freeware/bin/tar --create --file /dev/null \ --directory /data/nihpd/nihpd3/users --one-file-system \ --sparse --ignore-failed-read --totals . Total bytes written: 135834787840 (126GB, 1.7GB/s) /usr/freeware/bin/tar --version tar (GNU tar) 1.13.25 ?!? The sendbackup and runtar debug files on the client are attached. Both server and client are at 2.5.2p1. Any thoughts/comments? jf
Re: tar ignoring --one-file-system
--one-file-system doesn't works for NFS mountpoint. You must exclude the ./rabbit.honeypot.net directory. Jean-Louis Kirk Strauser wrote: I'm using Amanda 2.5.1p3 and GNU tar 1.20 on a FreeBSD 7 system. I noticed something was askew when Amanda made an 11GB backup of a 6GB filesystem: # amstatus Daily | grep '/jail ' kanga.honeypot.net:/jail 1 11419996k writing to tape (11:47:21) # du -shx /jail 5.8G/jail After digging around, I found that tar is ignoring the --one-file-system option. From the associated sendbackup file, I see that Amanda is calling tar with that option: sendbackup: argument list: runtar Daily GNUTAR --create --file - --directory /jail --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/kanga.honeypot.net_jail_1.new --sparse --ignore-failed-read --totals . But later I see (in that same file) errors like: sendbackup: time 33.813: 118: strange(?): GNUTAR: ./rabbit.honeypot.net/proc: file changed as we read it In this case, /jail/rabbit.honeypot.net is a mountpoint, and /jail/rabbit.honeypot.net/proc is definitely its own filesystem. Basically, tar is recursing on down anyway. Any suggestions?
Re: amanda-2.5.1p3 ignores no-reuse
As Jon said, it's a problem with new tape marked as no-reuse, only the
report is bad, amanda will works as expected.
The attached patch fix 'amadmin CONF tape' and amreport.
I don't know if the patch apply to 2.5.1p3.
Jean-Louis
Olivier Nicole wrote:
Hello,
I am setting up a new Amanda server.
Using virtual tapes on USB disk, it seems to be fast enough (20 to 40
MBps) depending on the hardware, the speed of the holding disks,
etc. Faster than the dump, so no problem.
I am currently hit by the IPv6 only problem on the client side, but
that one I identified and hope to solve it by reinstalling amanda for
IPv4 only.
The problem is the following:
I have 3 USB disks for virtual tapes, and only one is connected at a
given time, so in tapelist I marked the tapes that are not accessible
with no-reuse. They cannot be used because the disk is not online.
Despite, the report at the end of a dump mention that amanda will try
to use these;
These dumps were to tape CSIM-set-1-06.
The next 5 tapes Amanda expects to use are: 5 new tapes.
The next 5 new tapes already labelled are: CSIM-set-1-07, CSIM-set-1-08,
CSIM-set-1-09, CSIM-set-2-01, CSIM-set-2-02.
The tapes CSIM-set-2-01, CSIM-set-2-02 are on a disk that is not
online and they are marked no-reuse:
0 CSIM-set-2-02 no-reuse
0 CSIM-set-2-01 no-reuse
0 CSIM-set-1-09 reuse
0 CSIM-set-1-08 reuse
0 CSIM-set-1-07 reuse
Is that a feature?
Best regards,
Olivier
Index: amadmin.c
===
--- amadmin.c (revision 12873)
+++ amadmin.c (working copy)
@@ -805,16 +805,29 @@
tp = lookup_last_reusable_tape(i + 1);
}
}
+
+/* Find latest reusable new tape */
lasttp = lookup_tapepos(lookup_nb_tape());
+while (lasttp lasttp-reuse == 0)
+ lasttp = lasttp-prev;
+
i = runtapes;
if(lasttp i 0 strcmp(lasttp-datestamp,0) == 0) {
int c = 0;
+ /* find how many new tape are reusable */
while(lasttp i 0 strcmp(lasttp-datestamp,0) == 0) {
- c++;
+ if (lasttp-reuse) {
+ c++;
+ i--;
+ }
lasttp = lasttp-prev;
- i--;
}
+
+ /* Find latest reusable new tape */
lasttp = lookup_tapepos(lookup_nb_tape());
+ while (lasttp lasttp-reuse == 0)
+ lasttp = lasttp-prev;
+
i = runtapes;
if(c == 1) {
g_printf(_(The next new tape already labelled is: %s.\n),
@@ -826,9 +839,11 @@
lasttp = lasttp-prev;
c--;
while(lasttp c 0 strcmp(lasttp-datestamp,0) == 0) {
- g_printf(, %s, lasttp-label);
+ if (lasttp-reuse) {
+ g_printf(, %s, lasttp-label);
+ c--;
+ }
lasttp = lasttp-prev;
- c--;
}
g_printf(.\n);
}
Index: reporter.c
===
--- reporter.c (revision 12873)
+++ reporter.c (working copy)
@@ -1103,16 +1103,22 @@
}
fputs(.\n, mailf);
+/* Find latest reusable new tape */
lasttp = lookup_tapepos(lookup_nb_tape());
+while (lasttp lasttp-reuse == 0)
+ lasttp = lasttp-prev;
+
run_tapes = getconf_int(CNF_RUNTAPES);
if(lasttp run_tapes 0 strcmp(lasttp-datestamp,0) == 0) {
int c = 0;
iter = lasttp;
/* count the number of tapes we *actually* used */
while(iter run_tapes 0 strcmp(iter-datestamp,0) == 0) {
- c++;
+ if (iter-reuse) {
+ c++;
+ run_tapes--;
+ }
iter = iter-prev;
- run_tapes--;
}
if(c == 1) {
g_fprintf(mailf, _(The next new tape already labelled is: %s.\n),
@@ -1124,9 +1130,11 @@
iter = lasttp-prev;
c--;
while(iter c 0 strcmp(iter-datestamp,0) == 0) {
- g_fprintf(mailf, , %s, iter-label);
+ if (iter-reuse) {
+ g_fprintf(mailf, , %s, iter-label);
+ c--;
+ }
iter = iter-prev;
- c--;
}
g_fprintf(mailf, .\n);
}
Re: amanda ssh security
Which release of amanda?
Are you sure you are running the newly compiled amcheck? Use the full
patch when running it and show me the file is recent with 'ls -l'.
Post the configure output, did it find the ssh binary?
Post the output of make, did it compiled the ssh-security.c file?
Jean-Louis
Mister Olli wrote:
hi...
I compiled amanda on freebsd 7.0 with SSH security activated...
since the port had some bug, after fixing, the configure output starts
like this:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.61. Invocation command line was
$ ./configure --libexecdir=/usr/local/libexec/amanda
--with-amandahosts --with-fqdn --with-dump-honor-nodump
--with-buffered-dump --dis
able-libtool --prefix=/usr/local --with-user=amanda --with-group=backup
--with-index-server=hdb-bak-001.DOMAIN --with-tape-server=hdb-ba
k-001.DOMAIN --with-gnutar-listdir=/usr/local/var/amanda/gnutar-lists
--with-gnutar=/usr/local/bin/gtar --without-client --with-ssh-secu
rity --prefix=/usr/local --mandir=/usr/local/man
--infodir=/usr/local/info/ --build=i386-portbld-freebsd6.2
## - ##
## Platform. ##
## - ##
[...SNIP...]
so to me it looks like SSH security is activated, and there are no
problems during compilation.
however, with this configuration
[...SNIP...]
define dumptype tar {
comment Default backup method, using GNU-tar and no holding
disk
compressnone
exclude list/etc/amanda/daily-exclude
holdingdisk auto
index yes
program GNUTAR
record yes
index yes
tape_splitsize 20 GB # split dumps, to reduce disc usage;
size=tapesize/10
}
define dumptype ssh-tar {
tar
auth ssh
ssh_keys /home/amanda/.ssh/id_rsa
client_username amanda
}
[...SNIP...]
amcheck on this job always fails with this messages:
# sudo -u amanda amcheck daily
Amanda Tape Server Host Check
-
Holding disk /holding/daily: 424871 MB disk space available, using
424871 MB
slot 3: read label `Tape03', date `20080704'
NOTE: skipping tape-writable test
Tape Tape03 label ok
NOTE: host info dir /home/amanda/daily/curinfo/172.31.1.11 does not
exist
NOTE: it will be created on the next run.
NOTE: index dir /home/amanda/daily/index/172.31.1.11 does not exist
NOTE: it will be created on the next run.
Server check took 0.037 seconds
amcheck-clients: could not find security driver 'ssh' for host
'172.31.1.11'
Amanda Backup Client Hosts Check
(brought to you by Amanda 2.5.1p3)
I followed the instructions from the wiki
(http://wiki.zmanda.com/index.php/How_To:Set_up_transport_encryption_with_SSH),
but no success to get SSH authentication to work.
any hints, on what is going wrong?
are there any package requirements when using SSH authentication?
greetz
olli
Re: another selfcheck problem
Mister Olli wrote: Hi... when I try to do an 'amcheck' on my daily backup jobs I have one system, that does not pass the selftest. it's configured identically to some other machines that work like a charm. the debug output of 'amandad' on the client side looks like this: -auth=bsd: debug 1 pid 76969 ruid 1002 euid 1002: start at Wed Jul 16 10:33:47 2008 '-auth=bsd' at the beginning of the line is bogus, check your inetd/xinetd configuration. Jean-Louis
Re: another selfcheck problem
Mister Olli wrote: hi... my /etc/inetd.conf looks like this on all of my freebsd 7 systems. amanda dgram udp waitamanda /usr/local/libexec/amandad -auth=bsd amdump amindexd amidxtaped A 'amandad' is missing, it should be: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad -auth=bsd amdump amindexd amidxtaped Jean-Louis and it works like a charm, except for that one system... gladly I'm only the backup-administrator of that system. I wasn't the one who did the setup, so I'm not quite sure if there's something wrong with the system setup... are there any hints on what to check, or how to trace/ debug this failure in more detail? greetz olli Am Mittwoch, den 16.07.2008, 07:20 -0400 schrieb Jean-Louis Martineau: Mister Olli wrote: Hi... when I try to do an 'amcheck' on my daily backup jobs I have one system, that does not pass the selftest. it's configured identically to some other machines that work like a charm. the debug output of 'amandad' on the client side looks like this: -auth=bsd: debug 1 pid 76969 ruid 1002 euid 1002: start at Wed Jul 16 10:33:47 2008 '-auth=bsd' at the beginning of the line is bogus, check your inetd/xinetd configuration. Jean-Louis
Re: tar vs. dump for / backup?
[EMAIL PROTECTED] wrote: sendsize[7952]: time 0.003: /dev/sda2: Bad magic number in super-block while opening filesystem^M sendsize[7952]: time 0.003: DUMP: The ENTIRE dump is aborted. sendsize[7952]: time 0.004: . sendsize[7952]: time 0.004: estimate time for / level 0: 0.002 sendsize[7952]: time 0.004: no size line match in /usr/sbin/dump output for / This error offers more information as to why it really died. What do I do about it? What does it mean? Is this a manifestation of the reiserfs-dump incompatibility? Yes, dump is for ext2/3, it can't backup a reiserfs filesystem, you must use GNUTAR for reiserfs. Jean-Louis
Re: speeding up estimates
John Heim wrote: # Do faster estimates estimate calcsize It must be in a dumptype. Jean-Louis
Re: Newbie's question: server is not allowed to execute ther service noop
It search the .amandahosts file in the home directory of the user. Jean-Louis Weiwei Luo wrote: Hi all, When I use amcheck, the following error message is returned. *** Amanda Backup Client Hosts Check ERROR: NAK web2.blueprint.org: user amandabackup from WENDY is not allowed to execute the service noop: cannot open /home/amandabackup/.amandahosts: No such file or directory Client check: 3 hosts checked in 1.168 seconds. 1 problem found. First of all, amcheck is right: I don't have any folder as /home/amandabackup. The .amadahosts file in server or client is always at /var/lib/amanda/.amandahost. May I know which setting make amcheck to check the directory at /home/amanda? My setting: Amanda server: wendy Amanda client: web1(linux), archie(linux), web2(Windows) On web2 the Windows cilent (2.5.1p) is installed. This problem only happens when I try to add web2 as the client. If I don't have web2 in the disklist everything is fine. My .amandahosts is putting at /var/lib/amanda on the server, as following: wendy.blueprint.org amandabackup amdump wendy.blueprint.org amandabackup amindexd amidxtaped web1.blueprint.org amandabackup amindexd amidxtaped web2.blueprint.org amandabackup amindexd amidxtaped archie.blueprint.org amandabackup amindexd amidxtaped My .amandahosts at the windows clinet web2: wendy.blueprint.org amandabackup amdump My amanda-client.conf at the windows client web2: confDailySet1 authbsdtcp index_serverlocalhost.localdomain tape_server localhost.localdomain ssh_keys/var/lib/amanda/.ssh/id_rsa_amrecover With regards, Weiwei
Re: amreport: ERROR unexpected log line: ...
Amanda lock the file while writing to it. What is the output of: amadmin vv version | grep LOCKING Which filesystem is used, is it NFS mounted? Jean-Louis Jukka Salmi wrote: Jukka Salmi -- amanda-users (2008-06-25 12:37:15 +0200): Hello, since I upgraded an Amanda installation from 2.4.4p4 to 2.5.2p1, backup reports always contain lines like these: FAILURE AND STRANGE DUMP SUMMARY: amreport: ERROR unexpected log line: 20080625 2 [sec 45.227 kb 41655 kps 921.7] amreport: ERROR unexpected log line: 20080625 0 [sec 35.747 kb 67281 kps 1883.0] The log file which causes these warnings contains amongst others the following two lines: grouper.salmi.ch /var/spool/imap 20080625 2 [sec 45.227 kb 41655 kps 921.7] grouper.salmi.ch /home 20080625 0 [sec 35.747 kb 67281 kps 1883.0] (grouper is the hostname of the host running amdump.) Any hints about what could be wrong here? I just had a closer look at this problem and it seems to be caused by a race condition between programs started by Amanda's driver program: all of these programs (dumper, chunker, taper) and the driver program itself write to the same log file. Since these programs run simultaneously, their calls to log_add() may result in interleaved writes. And this is exactly what happens here almost daily: e.g. yesterday's logfile contains SUCCESS dumper grouper.salmi.ch /home 20080625 0 [...] SUCCESS chunker STATS driver estimate grouper.salmi.ch /home 20080625 0 [...] grouper.salmi.ch /home 20080625 0 [...] SUCCESS taper grouper.salmi.ch /home 20080625 0 [...] The chunker and the driver wrote to the log file at the same time... To fix this problem correctly, the writing of the log file should be synchronised. As a hack, the two calls to fullwrite() in log_add() could be replaced by a single call; this would probably cause the problem to occur less often. I'd certainly prefer the correct solution... Any comments? Regards, Jukka
Re: amreport: ERROR unexpected log line: ...
Jukka Salmi wrote: What about using record locking on a file in the logdir (maybe on the logfile itself)? I.e. making sure that all involved processes always acquire an exclusive lock, then write the log and afterwards release the lock? Amanda already lock the 'log' file. But why it is not working on your machine? First step, find which locking amanda use. What is the output of: amadmin vv version | grep LOCKING Which filesystem is used, is it NFS mounted? Which OS? Jean-Louis
Re: krb5 auth problem
Chad,
I don't have a krb5 setup and the developers sometimes break it.
amandad relinquish root permissions too soon.
Can you try the attached patch?
Jean-Louis
Chad Kotil wrote:
When i run spawn amandad via xinetd as root, i get this error.
1214490832.259079: amandad: critical (fatal): running as user root
instead of amandabackup
In the kerberos wiki it says amandad will relinquish root permissions
after reading the keytab. It doesnt seem to be doing that.
Also, What keytab on the client needs to be read as root?
--Chad
On Jun 25, 2008, at 5:29 PM, Jean-Louis Martineau wrote:
xinetd must be configured to run amandad as root.
Jean-Louis
Chad Kotil wrote:
I am trying to setup krb5 auth on amanda 2.6.0p1. I built the server
and client --with-krb5-security, added a new principal to my KDC
([EMAIL PROTECTED] REALM), and wrote a keytab file and placed it
on the server. It is locked down so only amandabackup (the user that
runs amanda) can read it. The clients have a .k5amandahosts file
containing the following:
[EMAIL PROTECTED] REALM
backupmaster.f.q.d.n [EMAIL PROTECTED] REALM
my amanda.conf file contains
krb5keytab /etc/amanda/krb5.keytab-amanda
krb5principal [EMAIL PROTECTED] REALM
On both of my krb5 auth clients I am seeing this error:
1214425629.641678: amandad: critical (fatal): gss_server failed:
real uid is 10036, needs to be 0 to read krb5 host key
10036 is the UID for amandabackup, 0 is the UID for root.
Both clients work fine if I just use bsdtcp auth. I am using ssh
auth everywhere else but for these two particular hosts I cannot use
ssh keys.
Any ideas?
Thanks,
--Chad
Chad E. Kotil
Global Research NOC
[EMAIL PROTECTED]
Phone: 812 855-5288
--- amandad-src/amandad.c.orig 2008-06-26 13:35:38.0 -0400
+++ amandad-src/amandad.c 2008-06-26 13:35:47.0 -0400
@@ -218,7 +218,15 @@ main(
config_init(CONFIG_INIT_CLIENT, NULL);
-check_running_as(RUNNING_AS_CLIENT_LOGIN);
+if (geteuid() == 0) {
+ check_running_as(RUNNING_AS_ROOT);
+ initgroups(CLIENT_LOGIN, get_client_gid());
+ setgid(get_client_gid());
+ setegid(get_client_gid());
+ seteuid(get_client_uid());
+} else {
+ check_running_as(RUNNING_AS_CLIENT_LOGIN);
+}
erroutput_type = (ERR_INTERACTIVE|ERR_SYSLOG);
@@ -409,6 +417,18 @@ main(
exit_on_qlength = 1;
}
+if (getuid() == 0) {
+ if (strcasecmp(auth, krb5) != 0) {
+ error(_('%s' auth require amandad to be run as '%s'), auth,
+ CLIENT_LOGIN);
+ }
+} else {
+ if (strcasecmp(auth, krb5) == 0) {
+ error(_('krb5' auth require amandad to be run as root));
+ }
+}
+
+
/* initialize */
startclock();
@@ -422,6 +442,11 @@ main(
dbprintf(_(WARNING: argv[0] not defined: check inetd.conf\n));
}
+/* krb5 require the euid to be 0 */
+if (strcasecmp(auth, krb5) == 0) {
+ seteuid((uid_t)0);
+}
+
/*
* Schedule to call protocol_accept() when new security handles
* are created on stdin.
Re: krb5 auth problem
xinetd must be configured to run amandad as root. Jean-Louis Chad Kotil wrote: I am trying to setup krb5 auth on amanda 2.6.0p1. I built the server and client --with-krb5-security, added a new principal to my KDC ([EMAIL PROTECTED] REALM), and wrote a keytab file and placed it on the server. It is locked down so only amandabackup (the user that runs amanda) can read it. The clients have a .k5amandahosts file containing the following: [EMAIL PROTECTED] REALM backupmaster.f.q.d.n [EMAIL PROTECTED] REALM my amanda.conf file contains krb5keytab /etc/amanda/krb5.keytab-amanda krb5principal [EMAIL PROTECTED] REALM On both of my krb5 auth clients I am seeing this error: 1214425629.641678: amandad: critical (fatal): gss_server failed: real uid is 10036, needs to be 0 to read krb5 host key 10036 is the UID for amandabackup, 0 is the UID for root. Both clients work fine if I just use bsdtcp auth. I am using ssh auth everywhere else but for these two particular hosts I cannot use ssh keys. Any ideas? Thanks, --Chad
Re: Should usetimestamps setting effect holding disk directory names?
Amanda use 14 digits for holding disk directory name since many releases, it is not related to usetimestamps. Jean-Louis Paul Yeatman wrote: Hi, Are 14 digit directory names on the holding disk only when using time stamps or in any case with amanda 2.6.0p1? I tried using time stamps for awhile and then decided I'd prefer not to and, as I'm not planning to downgrade or anything, don't expect it to be a problem. 14 digit directory names are still being used on the holding disk, however, even though the index directories for this config changed back from 14d_1d.gz to 8d_1d.gz filenames. I expected the directory names on the holding disk to drop back down to 8 digits. Thanks, Paul
Re: Intermittent FAILED [cannot read header: got 0 instead of 32768] errors
Do you have a firewall on the server? That would explain why amanda doesn't receive the packet even if the server receive it. Can you post the amandad.*.debug from the client and the dumper.*.debug from the server. Jean-Louis Wallace, Michael wrote: Hello, I have Amanda 2.5.1 running on a Mandriva 2008 server and 8 clients which are running either Amanda 2.4 or Amanda 2.5.1. Generally everything is working okay but I am getting the following intermittent error which occurs on one or more DLEs: FAILURE AND STRANGE DUMP SUMMARY: HOSTNAME/opt lev 1 FAILED [cannot read header: got 0 instead of 32768] HOSTNAME/opt lev 1 FAILED [too many dumper retry: [request failed: timeout waiting for ACK]] The corresponding information in /tmp/amanda/sendbackup... on the client is: sendbackup: debug 1 pid 14475 ruid 203 euid 203: start at Sat May 31 00:13:12 2008 /usr/local/libexec/sendbackup: version 2.4.3 parsed request as: program `DUMP' disk `/opt' device `/opt' level 1 since 2008:5:29:23:29:11 options `|;auth=BSD;compress-fast;index;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.004: stream_server: waiting for connection: 0.0.0.0.40506 sendbackup: time 0.004: stream_server: waiting for connection: 0.0.0.0.40507 sendbackup: time 0.005: stream_server: waiting for connection: 0.0.0.0.40508 sendbackup: time 0.005: waiting for connect on 40506, then 40507, then 40508 sendbackup: time 30.015: stream_accept: timeout after 30 seconds sendbackup: time 30.015: timeout on data port 40506 sendbackup: time 60.025: stream_accept: timeout after 30 seconds sendbackup: time 60.025: timeout on mesg port 40507 sendbackup: time 90.035: stream_accept: timeout after 30 seconds sendbackup: time 90.035: timeout on index port 40508 sendbackup: time 90.035: pid 14475 finish time Sat May 31 00:14:42 2008 Sometimes this happens for all disks on a single host and sometimes it only happens on one or two. There doesn't seem to be any correlation between dump levels, disk, disk size or host, and I can't see any other patterns in the failures. These failures seem to occur on average 1 day out of 3, but only one or two hosts will fail each time. The problems only started when we upgraded from Amanda version 2.5.0 to 2.5.1 on the server as part of an upgrade to Mandriva 2008. I've had a search through the mailing list archive and similar errors seem to point to network issues. Capturing the packets between the server and one of the hosts gave the following packet trace: Amanda 2.5 REQ HANDLE 000-000b SEQ 1213076860 SECURITY USER amanda SERVICE sendbackup OPTIONS features=feff9ffeff7f;hostname=HOSTNAME; DUMP /opt 1 2008:5:29:23:29:11 OPTIONS |;auth=BSD;compress-fast;index; Amanda 2.4 ACK HANDLE 000-000b SEQ 1213076860 Amanda 2.4 REP HANDLE 000-000b SEQ 1213076860 CONNECT DATA 40506 MESG 40507 INDEX 40508 OPTIONS features=feff9f00; Amanda 2.5 REQ HANDLE 000-000b SEQ 1213076860 SECURITY USER amanda SERVICE sendbackup OPTIONS features=feff9ffeff7f;hostname=HOSTNAME; DUMP /opt 1 2008:5:29:23:29:11 OPTIONS |;auth=BSD;compress-fast;index; Amanda 2.4 REP HANDLE 000-000b SEQ 1213076860 CONNECT DATA 40506 MESG 40507 INDEX 40508 OPTIONS features=feff9f00; Amanda 2.5 REQ HANDLE 000-000b SEQ 1213076860 SECURITY USER amanda SERVICE sendbackup OPTIONS features=feff9ffeff7f;hostname=HOSTNAME; DUMP /opt 1 2008:5:29:23:29:11 OPTIONS |;auth=BSD;compress-fast;index; ... For comparison, a packet trace for a successful connection between the same client and server looked like this: Amanda 2.5 REQ HANDLE 000- SEQ 1212388333 SECURITY USER amanda SERVICE sendbackup OPTIONS features=feff9ffeff7f;hostname=HOSTNAME; DUMP /export/home1 0 1970:1:1:0:0:0 OPTIONS |;auth=BSD;srvcomp-fast;index; Amanda 2.4 ACK HANDLE 000- SEQ 1212388333 Amanda 2.4 REP HANDLE 000- SEQ 1212388333 CONNECT DATA 40403 MESG 40404 INDEX 40405 OPTIONS features=feff9f00; Amanda 2.5 ACK HANDLE 000- SEQ 1212388333 So it looks like the client is responding but the server is not receiving the packet. The packet capture software (Wireshark) is running on the same machine as the Amanda server so the packet is definitely being received by the server, but for some reason the Amanda process doesn't receive it and it sends out another request - this repeats until it eventually gives up. Does anyone have any suggestions as to what might be going on here? We've been trying to work out what the problem could be for some time now so any ideas would be very welcome. Regards, Michael
Re: 2.5.2p1 under StrongBolt/CentOS on Cobalt Raq-4i - dump errors etc.
Craig Dewick wrote: ERROR: ziri: [could not access /dev/hda6 (/dev/hda6): Permission denied] ERROR: ziri: [could not access /dev/hda2 (/dev/hda2): Permission denied] ERROR: ziri: [could not access /dev/hda1 (/dev/hda1): Permission denied] which is rather strange as I've already made sure, as far as I'm aware, that the disk devices are in the same group (sys) as the 'amanda' user (and 'amanda' is included in group 'sys' in the /etc/group file on the Cobalt machine). Do the amandad process is executed with the 'sys' group? What's the xinetd config? do you have 'groups = yes' Jean-Louis
Re: amdump fails: port open: Resource temporarily unavailable
Can you post the dumper.*.debug file? Jean-Louis Luc Romain wrote: I recently installed FedoraCore 9 and I am having trouble getting amdump to run. I am using amanda (amanda-2.5.2p1-10.fc9.i386). Amcheck runs clean but amdump fails. Here is the error I get when I run 'amstatus DailySet1' shortly after amdump has started: === skippy.localdomain:/home/ftpsecure 0 driver: port open: Resource temporarily unavailable (21:31:25) ... holding space : 69062468k (100.00%) dumper0 busy : 0:00:00 ( 0.00%) 0 dumpers busy : 0:00:00 ( 0.01%) 1 dumper busy : 0:10:00 ( 96.79%) no-dumpers: 0:10:00 (100.00%) === The dump directory gets created in /var/dumps/amanda but it does not contain the dump files. Here is a portion of the amdump log file: === driver: started chunker0 pid 8160 driver: send-cmd time 19.993 to chunker0: START 20080611212605 driver: send-cmd time 19.993 to chunker0: PORT-WRITE 00-1 /var/dumps/amanda/20080611212605/skippy.localdomain._home_ftpsecure.0 skippy.localdomain 9ffe00 /home/ftpsecure 0 1970:1:1:0:0:0 1048576 GNUTAR 739008 |;auth=BSD;compress-fast;index; chunker: pid 8160 executable chunker0 version 2.5.2p1 driver: result time 20.006 from chunker0: PORT 55277 driver: send-cmd time 20.006 to dumper0: PORT-DUMP 00-1 55277 skippy.localdomain 9ffe00 /home/ftpsecure NODEVICE 0 1970:1:1:0:0:0 GNUTAR X X X |;auth=BSD;compress-fast;index; driver: state time 20.009 free kps: 976 space: 68323460 taper: idle idle-dumpers: 3 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle: no-dumpers driver: interface-state time 20.009 if default: free 0 if local: free 1000 if le0: free 400 driver: hdisk-state time 20.009 hdisk 0: free 68323460 dumpers 1 driver: result time 20.010 from dumper0: FAILED 00-1 port open: Resource temporarily unavailable driver: send-cmd time 20.010 to chunker0: FAILED 00-1 === I carefully read the Quick Start instructions and spent several hours trying to identify the problem without success. Before I installed FC9, amanda was runing on Fedora Core 8 for the last year and I've never had issues configuring it on FC8. Any help would be greatly appreciated. Luc
Re: amdump fails: port open: Resource temporarily unavailable
Luc Romain wrote: dumper: time 319.981: stream_client: Could not bind to port in range 0-0. 0-0 ? that's strange, do you have set reserved-udp-port in amanda.conf? amadmin config config | grep -i reserved What was the value of --with-udpportrange setting when amanda was configured? Jean-Louis
Re: amdump fails: port open: Resource temporarily unavailable
Sorry, it's not an error with an udp port, what's the setting of unreserved-tcp-port amgetconf config unreserved-tcp-port Jean-Louis Jean-Louis Martineau wrote: Luc Romain wrote: dumper: time 319.981: stream_client: Could not bind to port in range 0-0. 0-0 ? that's strange, do you have set reserved-udp-port in amanda.conf? amadmin config config | grep -i reserved What was the value of --with-udpportrange setting when amanda was configured? Jean-Louis
Re: amdump fails: port open: Resource temporarily unavailable
Luc Romain wrote: bash-3.2$ amadmin DailySet1 config | grep -i reserved RESERVED-UDP-PORT 512,1023 RESERVED-TCP-PORT 512,1023 UNRESERVED-TCP-PORT 0,0 These properties are not specified in my amanda.conf file. Then add: UNRESERVED-TCP-PORT 1025,65535 Jean-Louis Luc Jean-Louis Martineau wrote: Sorry, it's not an error with an udp port, what's the setting of unreserved-tcp-port amgetconf config unreserved-tcp-port Jean-Louis Jean-Louis Martineau wrote: Luc Romain wrote: dumper: time 319.981: stream_client: Could not bind to port in range 0-0. 0-0 ? that's strange, do you have set reserved-udp-port in amanda.conf? amadmin config config | grep -i reserved What was the value of --with-udpportrange setting when amanda was configured? Jean-Louis
Re: dumper abort()ing occasionally
Douglas, Many bugs are already fixed in the 2.5.1 tree, but we didn't made a release. You can try the latest 2.5.1 snapshot from http://www.zmanda.com/community-builds.php It is only bug fixes since the 2.5.1p3 release. I don't remember if this bug was fixed. Jean-Louis Douglas K. Rand wrote: Once or twice a week my amanda backups are failing when a dumper exits on signal 6, SIGABRT: Jun 5 23:27:38 scotch kernel: pid 82566 (dumper), uid 0: exited on signal 6 Jun 8 19:53:43 scotch kernel: pid 96672 (dumper), uid 0: exited on signal 6 In looking at the source there clearly are calls to abort() in several places. I'm assuming that there is an overflow problem with file descriptors, that 4294967295 isn't a valid FD? driver: event_register: Invalid file descriptor 4294967295 I'm running FreeBSD 6.3 with Amanda 2.5.1p3 from ports. There isn't much information in the log:
Re: Amanda 2.5.0 spanning
Johan Booysen wrote: Ok, on Thurday night at 21:00 I kicked off a backup job that should span over 2 tapes. I wasn't in the office on Friday, but this morning the first tape was ejected, and amstatus tells me the following: server:/whatever/clients 0127494663k writing to tape (9:43:32) I believe then that amanda wrote stuff to tape until 09:43 on Friday morning, and then filled up the first tape, ejected it, and has been patiently waiting for the second tape. Or will it have timed out by now? So I inserted the second tape this morning, and nothing seems to be happening at all. It certainly does not appear to be writing anything to the second tape... What's the best way of seeing what amanda's doing now? I've tried the following: Amcheck skips the tape check, and tells me that amdump or amflush is running. Changer.debug contains lots of these (lots and lots): - rewind /dev/nst0 /dev/nst0 rewind failed: Input/output error - status /dev/nst0 /dev/nst0 status failed: Input/output error - loaded chg-manual check regularly if you put a tape in the drive, if you put a valid tape in the driver then it should succeed, are they the latest lines of the files? Maybe try another tape. Jean-Louis
Re: Amanda 2.5.0 spanning
Is it adding new lines to changer.debug? If yes, then something is buggy, try to kill the script: kill 11652 Jean-Louis Johan Booysen wrote: Yes, they are the last lines in changer.debug. Unfortunately no times or dates are recorded. I can't really see if the tape drive is writing anything. Usually it has a little light on it that flickers when there's activity, but now it's just shining all the time and that's no good. Is there anywhere else I can check to see if the job is actively and running? Or whether the tape drive is actually writing something? What is strange is that mt -f /dev/nst0 status reports: SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 0 bytes. Density code 0x49 (Quantum SDLT320). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN But I'm sure that while writing it usually comes back with: /dev/nst0: Device or resource busy So, alas, I don't think it's doing anything. Any other suggestions at all? Thanks. -Original Message- From: Jean-Louis Martineau [mailto:[EMAIL PROTECTED] Sent: 09 June 2008 13:25 To: Johan Booysen Cc: Amanda user's group Subject: Re: Amanda 2.5.0 spanning Johan Booysen wrote: Ok, on Thurday night at 21:00 I kicked off a backup job that should span over 2 tapes. I wasn't in the office on Friday, but this morning the first tape was ejected, and amstatus tells me the following: server:/whatever/clients 0127494663k writing to tape (9:43:32) I believe then that amanda wrote stuff to tape until 09:43 on Friday morning, and then filled up the first tape, ejected it, and has been patiently waiting for the second tape. Or will it have timed out by now? So I inserted the second tape this morning, and nothing seems to be happening at all. It certainly does not appear to be writing anything to the second tape... What's the best way of seeing what amanda's doing now? I've tried the following: Amcheck skips the tape check, and tells me that amdump or amflush is running. Changer.debug contains lots of these (lots and lots): - rewind /dev/nst0 /dev/nst0 rewind failed: Input/output error - status /dev/nst0 /dev/nst0 status failed: Input/output error - loaded chg-manual check regularly if you put a tape in the drive, if you put a valid tape in the driver then it should succeed, are they the latest lines of the files? Maybe try another tape. Jean-Louis
Re: [Amanda-users] confusing problem with NO-NEW-TAPE
What's is the runtapes setting? It's hard to read files when many characters are converted to HTML, it's a lot better if you attach a file, they will not be converted. Jean-Louis nbarss wrote: Can you send your whole amflush log, as well as the taper debug log? Sure. Here is amflush.1, taper.20080609100127.debug follows: amdump#58; start at Mon Jun 9 10#58;01#58;26 MDT 2008 amdump#58; datestamp 20080609 amdump#58; starttime 20080609100126 amdump#58; starttime-locale-independent 2008-06-09 10#58;01#58;26 MDT planner#58; pid 31982 executable /usr/libexec/amanda/planner version 2.6.0p1 planner#58; build#58; VERSION=Amanda-2.6.0p1 planner#58;nbsp; nbsp; nbsp; nbsp; BUILT_DATE=Tue May 13 19#58;36#58;27 PDT 2008 planner#58;nbsp; nbsp; nbsp; nbsp; BUILT_MACH=i686-pc-linux-gnu BUILT_REV=1019 planner#58;nbsp; nbsp; nbsp; nbsp; BUILT_BRANCH=amanda-260 CC=gcc planner#58; paths#58; bindir=/usr/bin sbindir=/usr/sbin planner#58;nbsp; nbsp; nbsp; nbsp; libexecdir=/usr/libexec planner#58;nbsp; nbsp; nbsp; nbsp; amlibexecdir=/usr/libexec/amanda mandir=/usr/share/man planner#58;nbsp; nbsp; nbsp; nbsp; AMANDA_TMPDIR=/tmp/amanda planner#58;nbsp; nbsp; nbsp; nbsp; AMANDA_DBGDIR=/var/log/amanda CONFIG_DIR=/etc/amanda planner#58;nbsp; nbsp; nbsp; nbsp; DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/r planner#58;nbsp; nbsp; nbsp; nbsp; DUMP=/sbin/dump RESTORE=/sbin/restore VDUMP=UNDEF planner#58;nbsp; nbsp; nbsp; nbsp; VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF planner#58;nbsp; nbsp; nbsp; nbsp; VXRESTORE=UNDEF SAMBA_CLIENT=UNDEF GNUTAR=/bin/tar planner#58;nbsp; nbsp; nbsp; nbsp; COMPRESS_PATH=/usr/bin/gzip planner#58;nbsp; nbsp; nbsp; nbsp; UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=/usr/bin/lpr planner#58;nbsp; nbsp; nbsp; nbsp; MAILER=/usr/bin/Mail planner#58;nbsp; nbsp; nbsp; nbsp; listed_incr_dir=/var/lib/amanda/gnutar-lists planner#58; defs#58;nbsp; DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 planner#58;nbsp; nbsp; nbsp; nbsp; DEFAULT_TAPE_SERVER=localhost DEFAULT_TAPE_DEVICE= planner#58;nbsp; nbsp; nbsp; nbsp; HAVE_MMAP NEED_STRSTR HAVE_SYSVSHM LOCKING=**NONE** planner#58;nbsp; nbsp; nbsp; nbsp; SETPGRP_VOID ASSERTIONS AMANDA_DEBUG_DAYS=4 BSD_SECURITY planner#58;nbsp; nbsp; nbsp; nbsp; USE_AMANDAHOSTS CLIENT_LOGIN=amandabackup CHECK_USERID planner#58;nbsp; nbsp; nbsp; nbsp; HAVE_GZIP COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast planner#58;nbsp; nbsp; nbsp; nbsp; COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc READING CONF INFO... driver#58; pid 31983 executable /usr/libexec/amanda/driver version 2.6.0p1 planner#58; timestamp 20080609100126 planner#58; time 0.000#58; startup took 0.000 secs SENDING FLUSHES... ENDFLUSH SETTING UP FOR ESTIMATES... planner#58; time 0.000#58; setting up estimates for 172.16.1.126#58;/test 172.16.1.126#58;/test overdue 14040 days for level 0 setup_estimate#58; 172.16.1.126#58;/test#58; command 0, options#58; nonenbsp; nbsp; last_level -1 next_level0 -14040 level_days 0nbsp; nbsp; getting estimates 0 #40;-2#41; -1 #40;-2#41; -1 #40;-2#41; planner#58; time 0.001#58; setting up estimates took 0.000 secs GETTING ESTIMATES... driver#58; adding holding disk 0 dir /var/dumps/Main size 190496768 chunksize 1048576 reserving 190496768 out of 190496768 for degraded-mode dumps driver#58; send-cmd time 0.003 to taper#58; START-TAPER 20080609100126 driver#58; started dumper0 pid 31985 driver#58; send-cmd time 0.004 to dumper0#58; START 20080609100126 driver#58; started dumper1 pid 31986 driver#58; send-cmd time 0.006 to dumper1#58; START 20080609100126 driver#58; started dumper2 pid 31987 driver#58; send-cmd time 0.008 to dumper2#58; START 20080609100126 driver#58; started dumper3 pid 31988 driver#58; send-cmd time 0.010 to dumper3#58; START 20080609100126 driver#58; start time 0.010 inparallel 4 bandwidth 8000 diskspace 190496768nbsp; dir OBSOLETE datestamp 20080609100126 driver#58; drain-ends tapeq FIRST big-dumpers sssS dumper#58; pid 31985 executable dumper0 version 2.6.0p1 taper#58; pid 31984 executable taper version 2.6.0p1 dumper#58; pid 31987 executable dumper2 version 2.6.0p1 dumper#58; pid 31988 executable dumper3 version 2.6.0p1 dumper#58; pid 31986 executable dumper1 version 2.6.0p1 planner#58; time 0.179#58; got partial result for host 172.16.1.126 disk /test#58; 0 - -2K, -1 - -2K, -1 - -2K planner#58; time 1.059#58; got partial result for host 172.16.1.126 disk /test#58; 0 - 2065870K, -1 - -2K, -1 - -2K planner#58; time 1.061#58; got result for host 172.16.1.126 disk /test#58; 0 - 2065870K, -1 - -2K, -1 - -2K planner#58; time 1.061#58; getting estimates took 1.060 secs FAILED QUEUE#58; empty DONE QUEUE#58; nbsp; 0#58; 172.16.1.126 /test ANALYZING ESTIMATES... pondering 172.16.1.126#58;/test... next_level0 -14040 last_level -1 #40;due for level 0#41; #40;new disk, can't switch to degraded mode#41; nbsp; curr level 0 nsize 2065870 csize 1032935 total size 1033031 total_lev0 1032935 balanced-lev0size 258233 INITIAL SCHEDULE #40;size 1033031#41;#58;
Re: Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148
A bug in amstatus should not prevent your backup to run correctly. Changing amdump.1 can't help to start a backup run (amdump). Your backup should run correctly even if amstatus crash. Can you send me a copy of the bogus amdump.1 file? I would like to look at it. Which locale are you using? Jean-Louis Dominik Schips wrote: Hello, since Saturday (2008-05-31) my ananda backup didn't run. A closer look when I run the command /usr/sbin/amstatus DailyFull get me this output: Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148 using /var/lib/amanda/DailyFull/log/amdump.1 from Sa Mai 21 15:30:08 CEST I coudn't find any errors or someting else in the logs. Because I didn't know what went wrong I had to fake (change) the date in /var/lib/amanda/DailyFull/log/amdump.1 from 31 to 30... Know the backup starts and I hope that it finish correct without problem. The question is what can cause this error Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148? I use Amanda 2.4.4p3 from Debian sarge. I know it's old, but there wasn't time to make a update to Etch. This is on my todo within the nex 4 weeks. Best regards, Dominik
Re: Amanda 2.5.0 spanning
In 2.5.0, it write a message to /dev/tty, if you start the command from an interactive shell, you should see a message, if you run it from cron, then the message is lost. Newer version allow to send an email message. Jean-Louis Johan Booysen wrote: Hi, I've now gotten as far as getting Amanda to think the tape drive has 2 slots (I believe)...well at least I can do an amcheck successfully... One question: When amdump runs and fills up the first tape, what should I expect to see? Does Amanda simply eject the first tape and just waits until the second tape is inserted? Does it give any sort of indication that it's time to insert the second tape? Just a little confused over that issue. Thanks very much. -Original Message- From: Jean-Louis Martineau [mailto:[EMAIL PROTECTED] Sent: 30 May 2008 12:56 To: Johan Booysen Cc: Amanda user's group Subject: Re: Amanda 2.5.0 spanning Johan Booysen wrote: Well, there wasn't any email report because it was waiting for the job to finish... I eventually manually killed the job, but the email report only says: *** THE DUMPS DID NOT FINISH PROPERLY! These dumps were to tape daily-3. The next 2 tapes Amanda expects to use are: a new tape, a new tape. The next 2 new tapes already labelled are: daily-4, daily-5 It tell me the tapes should have been accepted. I'm not surprise there is nothing in the log, the taper log the error when it find a tape, but you killed it before. You can change the lastslot=99 to lastslot=3 in the chg-manual scripts. That way, the taper will exit after you feed 3 tapes and it will log error messages. Jean-Louis
Re: Amanda 2.5.0 spanning
Everything look good. But it doesn't explain why amanda rejected those tape, the email report will tell you why. I'm not sure if the error is already written to the log file, but you can check them: (amdump or amdump.1) or (log or log.TIMESTAMP.*). btw, why are you installing an old amanda version? Jean-Louis Johan Booysen wrote: Yesterday I did a test run using Amanda 2.5.0 - just backing up a single DLE, and all seemed well. So last night I ran my first test to see how Amanda 2.5.0 handles spanning across multiple tapes. This morning, tape daily-3 was ejected, amstatus looked OK, and I inserted the next tape (daily-4). However, the tape drive thinks about it for a while and then spits out the tape. I thought it may be the tape itself, so tried daily-5 eventually, but with the same result (I'm pretty sure the tapes are good). I'm using a single-slot HP StorageWorks SDLT320 tape drive, so I have a feeling that somewhere there's a problem with using it as if it has multiple slots. In amanda.conf, I've got the following entries - the rest are pretty much standard: runtapes 2 tpchanger chg-manual tapedev /dev/nst0 changerfile /etc/amanda/daily/changer.conf changerdev /dev/null chunksize 1Gb tape_splitsize 1Gb In /etc/amanda/daily: changer.conf is an empty file, created manually (by me) changer.conf-access contains a value of 9 changer.conf-clean contains a value of 9 changer.conf-slot contains a value of 8 I've had a look a the logs, but don't know what the make of them: amindexd.20080529170749.debug shows no errors. amcheck.20080529172331.debug contains the following, and succeeds: changer: got exit: 0 str: 2 99 1 changer_query: changer return was 99 1 changer_query: searchable = 0 changer_find: looking for NULL changer is searchable = 0 changer: got exit: 0 str: 2 /dev/nst0 changer.debug contains: First attempt to insert next tape (daily-4) /dev/nst0 status: ONLINE BOT - loaded /dev/nst0 status: ONLINE BOT AMANDA: TAPESTART DATE X TAPE daily-4 014 1+0 in 1+0 out Exit - 3 /dev/nst0 MT - /usr/sbin/ammt -f DD - /usr/sbin/amdd Args - -slot next - rewind /dev/nst0 - status /dev/nst0 /dev/nst0 status: ONLINE BOT - loaded /dev/nst0 status: ONLINE BOT - offline /dev/nst0 - load 4 - rewind /dev/nst0 /dev/nst0 rewind failed: Input/output error - status /dev/nst0 /dev/nst0 status failed: Input/output error - loaded - rewind /dev/nst0 /dev/nst0 rewind failed: Input/output error - status /dev/nst0 Second attempt to insert next tape (daily-4) /dev/nst0 status: ONLINE BOT - loaded /dev/nst0 status: ONLINE BOT AMANDA: TAPESTART DATE X TAPE daily-4 014 1+0 in 1+0 out Exit - 4 /dev/nst0 MT - /usr/sbin/ammt -f DD - /usr/sbin/amdd Args - -slot next - rewind /dev/nst0 - status /dev/nst0 /dev/nst0 status: ONLINE BOT - loaded /dev/nst0 status: ONLINE BOT - offline /dev/nst0 - load 5 - rewind /dev/nst0 Would appreciate any advice. I've read through http://wiki.zmanda.com/index.php/Amanda.conf and http://wiki.zmanda.com/index.php/Splitting_dumps_across_tapes, but may be missing something somewhere. Thanks, as always.
Re: Amanda 2.5.0 spanning
Johan Booysen wrote: Well, there wasn't any email report because it was waiting for the job to finish... I eventually manually killed the job, but the email report only says: *** THE DUMPS DID NOT FINISH PROPERLY! These dumps were to tape daily-3. The next 2 tapes Amanda expects to use are: a new tape, a new tape. The next 2 new tapes already labelled are: daily-4, daily-5 It tell me the tapes should have been accepted. I'm not surprise there is nothing in the log, the taper log the error when it find a tape, but you killed it before. You can change the lastslot=99 to lastslot=3 in the chg-manual scripts. That way, the taper will exit after you feed 3 tapes and it will log error messages. Jean-Louis
Re: .amandahosts owned by id ## should be ##
Paul Yeatman wrote: -In response to your message- --received from Jean-Louis Martineau-- Paul, I haven't followed the thread and I don't have old mail. You should not need bsdudp. Your disklist should specify : auth bsdtcp Are you sure you have a correct plist for bsdtcp? Are you sure in run the good amandad? Can you post it? I'm pretty sure about all of these. Dustin has helped me go over these intricacies. What, more sepcifically, would be helpul to post amandad debug file show it is started with bsdudp, either your disklist doesn't set auth to bsdtcp or your plist is not correct. Add 'debug_auth 1' in amanda.conf and the client amanda-client.conf Post the output of 'amanda conf disklist' and your plist files. Retry a dump. Post the amcheck.*.debug from the server and amandad.*.debug from the client. Jean-Louis
Re: amdump freezes
You are doing a dump to tape and the taper failed. The dumper close the socket to the client, and the client detect the socket is close. The first error is the taper. sendbackup error is the result of the taper error. Jean-Louis Stefan G. Weichinger wrote: Some infos from the client-side: --- sendbackup: start: server:data_db lev 0 sendbackup: time 0.092: spawning /bin/gzip in pipeline sendbackup: time 0.092: argument list: /bin/gzip --fast sendbackup-gnutar: time 0.092: pid 29494: /bin/gzip --fast sendbackup-gnutar: time 0.092: doing level 0 dump as listed-incremental to '/usr/local/var/amanda/gnutar-lists/serverdata_db_0.new' sendbackup-gnutar: time 0.099: doing level 0 dump from date: 1970-01-01 0:00:00 GMT sendbackup: time 0.108: spawning /usr/local/libexec/runtar in pipeline sendbackup: time 0.108: argument list: runtar daily gtar --create --file - --directory /data/db --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/serverdata_db_0.new --sparse --ignore-failed-read --totals . sendbackup-gnutar: time 0.109: /usr/local/libexec/runtar: pid 29497 sendbackup: time 0.109: started backup sendbackup: time 0.109: started index creator: /bin/gtar -tf - 2/dev/null | sed -e 's/^\.//' sendbackup: time 11140.170: index tee cannot write [Broken pipe] sendbackup: time 11140.214: pid 29495 finish time Thu May 29 05:53:19 2008 Seems as if the index-creation fails, correct? But why would it then say taper: retrying server:data_db.0 on new tape due to: [writing file: No space left on device] ?? hmm Stefan
Re: Amanda 2.5.0 amrecover to server
It's not a .amandahosts problem. Check the xinetd configuration for the amindexd service. Check system log for xinetd error. Jean-Louis Johan Booysen wrote: Hope someone can help me out here. I'm testing Amanda 2.5.0 on RHEL5, to upgrade from our older version. Everything went well and I can successfully back up older clients. However, when trying to do an amrecover (as root and to the backup server itself), using the config I've set up (called daily), I consistently get: # amrecover daily AMRECOVER Version 2.5.0p2. Contacting server on amandahost ... amrecover: cannot connect to amandahost: Success This happens even when I remove the amandahost entry from .amandahosts... My understanding has always been that /var/lib/amanda/.amandahosts dictates access to the server when using amrecover, and my .amandahosts file is suitably modified with FQDNs and so on. Am I missing something? Thanks.
Re: amdump freezes
It must abort the dump, and restart it. Jean-Louis Stefan G. Weichinger wrote: Jean-Louis Martineau schrieb: You are doing a dump to tape and the taper failed. The dumper close the socket to the client, and the client detect the socket is close. The first error is the taper. sendbackup error is the result of the taper error. But shouldn't the taper simply retry that with the next tape? Stefan
Re: amdump freezes
Stefan G. Weichinger wrote: Jean-Louis Martineau schrieb: It must abort the dump, and restart it. And what's the solution for my problem? Did it retried the dump on the next tape? Can you explain the problem, because i don't understand it, except you hit the end of a tape. Post the amdump.1 log file. You can increase runtapes, split your dle in smaller dles, add more holding disk, ... amanda only try a dump 2 times, maybe it hit end of tape on both tries? You can try to dump only that disk: amdump conf hodt disk Jean-Louis
Re: .amandahosts owned by id ## should be ##
Paul, I haven't followed the thread and I don't have old mail. You should not need bsdudp. Your disklist should specify : auth bsdtcp Are you sure you have a correct plist for bsdtcp? Are you sure in run the good amandad? Can you post it? Jean-Louis Paul Yeatman wrote: -In response to your message- --received from Dustin J. Mitchell-- Sorry, there are a lot of moving parts here, and they all need to move in the same direction. Both server and client should be compiled to include bsdtcp (and whatever else -- doesn't matter). Both server and client should be configured to use bsdtcp - the server in the dumptype, and the client in /etc/amanda/amanda-client.conf. The client should be listening for TCP connections using the bsdtcp plist. It's messy, I know -- it's all there for historical reasons. Okay, I see how this should work . . . but I'm not getting the desired result on my end. If I do everything you specify above, the server won't connect with the client. I can only get the server to connect to the client if I also compile the client with bsdudp and load the according plist file. Then I get the client configured for auth=bsdudp while server requested 'bsdtcp' even when the amanda-client.conf specifies auth bsdtcp. So, I'm to the point (unless you have any other suggestions to resolve the problem with bsdtcp alone not connecting) of just going with bsdudp. I know you suggested bsdtcp and I would like to get this to work but it just won't. I assume you suggest bsdtcp over bsdudp for security reasons. Is bsdudp that bad? If I'm forced to go with bsdudp and configure both server and client to use bsdudp instead of bsdtcp, I still get this error message with an amcheck [client configured for auth=bsdudp while server requested 'BSD'] If you notice in my previous emails, this line has always been at the top before subsequent lines which then switch to server requested 'bsdtcp'. Any idea on this? Thanks again for all the help!!! Paul
Re: what is /etc/.gnupg ?
Paul,
The error is only in the output message, see the attached patch.
Jean-Louis
Paul Bijnens wrote:
Instead of compiling from sources, as I did up to now, I tried the
rpm from zmanda on a new host I'm preparing.
Downloaded: amanda-backup_client-2.6.0p1-1.rhel5.i386.rpm
When installing, I got these lines:
...
May 26 2008 16:55:46: The directory '/var/lib/amanda/.gnupg' created
successfully.
May 26 2008 16:55:46: Ensuring correct permissions for '/etc/.gnupg'.
May 26 2008 16:55:46: '/var/lib/amanda/.gnupg' Installation successful.
...
The middle line, mentioning /etc/.gnupg, is, I suppose, not correct.
Minor error, as it's only the message. The permissions of the directory
'/var/lib/amanda/.gnupg' are correct after installing, AFAIK.
Index: packaging/rpm/amanda.spec
===
--- packaging/rpm/amanda.spec (revision 1046)
+++ packaging/rpm/amanda.spec (working copy)
@@ -649,7 +649,7 @@
fi
fi
if [ ${ret_val} -eq 0 ]; then
-echo `date +'%b %e %Y %T'`: Ensuring correct permissions for '%{SYSCONFDIR}/.gnupg'. ${TMPFILE}
+echo `date +'%b %e %Y %T'`: Ensuring correct permissions for '%{AMANDAHOMEDIR}/.gnupg'. ${TMPFILE}
chown %{amanda_user}:%{amanda_group} %{AMANDAHOMEDIR}/.gnupg ${TMPFILE} 21
ret_val=$?
if [ ${ret_val} -eq 0 ]; then
@@ -1052,7 +1052,7 @@
fi
fi
if [ ${ret_val} -eq 0 ]; then
-echo `date +'%b %e %Y %T'`: Ensuring correct permissions for '%{SYSCONFDIR}/.gnupg'. ${TMPFILE}
+echo `date +'%b %e %Y %T'`: Ensuring correct permissions for '%{AMANDAHOMEDIR}/.gnupg'. ${TMPFILE}
chown %{amanda_user}:%{amanda_group} %{AMANDAHOMEDIR}/.gnupg ${TMPFILE} 21
ret_val=$?
if [ ${ret_val} -eq 0 ]; then
@@ -1419,7 +1419,7 @@
fi
fi
if [ ${ret_val} -eq 0 ]; then
-echo `date +'%b %e %Y %T'`: Ensuring correct permissions for '%{SYSCONFDIR}/.gnupg'. ${TMPFILE}
+echo `date +'%b %e %Y %T'`: Ensuring correct permissions for '%{AMANDAHOMEDIR}/.gnupg'. ${TMPFILE}
chown %{amanda_user}:%{amanda_group} %{AMANDAHOMEDIR}/.gnupg ${TMPFILE} 21
ret_val=$?
if [ ${ret_val} -eq 0 ]; then
Re: Problem Restoring Files
Steven Backus wrote: amrecover: time 392.438: security_close(handle=0x8c40330, driver=0xd4b120 (BSD)) amrecover: time 408.626: security_stream_close(0x8c48fa8) amrecover: time 408.627: Can't read file header amrecover: time 408.627: pid 6276 finish time Fri May 16 08:55:28 2008 amrecover: time 408.627: security_stream_close(0x8c40f70 It failed to restore the full, it only restored the incremental level 1 and 2. Did you see a failed message in the amrecover session? Can you post the corresponding amandad.*.debug and amidxtaped.*.debug files from the server. Jean-Louis
Re: Problem Restoring Files
Steven Backus wrote: I'm having a problem restoring on my 2.5.2p1 system. The indexes show all the data is there: amrecover sethost ambiance 501 Host ambiance is not in your disklist. Trying host ambiance.med.utah.edu ... 200 Dump host set to ambiance.med.utah.edu. amrecover listdisk 200- List of disk for host ambiance.med.utah.edu 201- / 201- sdc1 201- sdb5 200 List of disk for host ambiance.med.utah.edu amrecover setdisk sdc1 200 Disk set to sdc1. amrecover cd /9gb/jv/mcsim/prost/ICPCG_CIDR /9gb/jv/mcsim/prost/ICPCG_CIDR amrecover ls 2008-05-09 noLDanal/ 2008-05-09 Summary/ 2008-05-09 . 2008-05-05 tmp.pl~ 2008-05-05 tmp.pl 2008-05-05 summclinx 2008-05-05 runProstSet2 2008-05-05 runProstSet1 2008-05-05 runMela_SNP_summary 2008-05-05 runICPCG_CIDR.summary 2008-05-05 runICPCG_CIDR.best~ 2008-05-05 runICPCG_CIDR.best 2008-05-05 runGWMelaSNP 2008-05-05 run.merlin2labout~ 2008-05-05 run.merlin2labout 2008-05-05 run.mcsimPrep2~ 2008-05-05 run.mcsimPrep2 2008-05-05 out.log 2008-05-05 icpcg_cidr.noLD.hets But only the directory structure is restored when I extract: % cd /9gb/jv/mcsim/prost/ICPCG_CIDR % ls Files/ LDanal/ Rcode/ Summary/ noLDanal/ None of the files are restored. I'm using tar 1.15.1, just let me know if you need more information. As always, the complete debug files and the complete amrecover session. The 'amadmin ... find ambiance sdc1' output. Looks like it restored only the level 1, not the full. It is a known bug, it is fixed in latest 2.5.2p1 snapshot from http://www.zmanda.com/community-builds.php/amanda-2.5.2p1-20071101.tar.gz Jean-Louis
Re: Problem with a multi-homed client: amcheck: timeout waiting, for ACK: Receive packet from unknown source
Christopher,
Try to use the bsdtcp authentification.
It require change to your dumptype and your xinetd/inetd configuration.
See
http://wiki.zmanda.com/index.php/Configuring_bsd/bsdudp/bsdtcp_authentication
Jean-Louis
Christopher Brooks wrote:
I have a Solaris 10 client that has multiple virtual ethernet
interfaces. In other words, it has one physical wire, but there
are multiple virtual interfaces assigned to that wire.
The problem is that amcheck to this multi-homed client fails with:
WARNING: AA.BB.CC.edu: selfcheck request failed: timeout waiting for ACK
Interestingly, this worked in Amanda-2.4.5, but now fails in
Amanda-2.6.0.
BTW - The primary reason I'm upgrading is because under Amanda-2.4.5,
killpgrp is periodically killing extra processes and hosing one of my
machines. Unfortunately, when the machine goes down, it erases
/tmp/amanda, so I can't get at the amanda logs. With 2.6.0, I'm
putting the amanda files in a separate directory. I have pretty good
evidence of this bug because with account processing, I can see when
killpgrp runs, it kills a heartbeat script I hacked in which runs
every 10 seconds.
Anyway, back to the multi-homed problem.
I have a tapeserver machine and then a separate machine with
four IP addresses.
The XX.YY.ZZ.30 address is the primary address
XX.YY.ZZ.31 is a virtual address.
ipconfig -a looks like
--start--
lo0: flags=2001000849UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL mtu 8232
index 1
inet 127.0.0.1 netmask ff00
bge0: flags=1004843UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4 mtu 1500 index 2
inet XX.YY.ZZ.30 netmask ff00 broadcast XX.YY.ZZ.255
ether 0:3:ba:c6:e7:a9
bge0:1: flags=1000843UP,BROADCAST,RUNNING,MULTICAST,IPv4 mtu 1500 index 2
inet XX.YY.ZZ.31 netmask ff00 broadcast XX.YY.ZZ.255
bge0:2: flags=1000843UP,BROADCAST,RUNNING,MULTICAST,IPv4 mtu 1500 index 2
inet XX.YY.ZZ.32 netmask ff00 broadcast XX.YY.ZZ.255
bge0:3: flags=1000843UP,BROADCAST,RUNNING,MULTICAST,IPv4 mtu 1500 index 2
inet XX.YY.ZZ.34 netmask ff00 broadcast XX.YY.ZZ.255
--end--
What happens is that amcheck traffic from the tapeserver goes to
the .30 address, but the traffic returns from the .31 address.
This causes amcheck to fail.
I can see this in the debug log file on the tape server:
--start--
1210631008.444594: amcheck: pid 13583 ruid 201 euid 201: start at Mon May 12 1
5:23:28 2008
1210631008.451774: amcheck: pid 13583 ruid 201 euid 201: rename at Mon May 12 1
5:23:28 2008
1210631008.462034: amcheck-clients: security_getdriver(name=BSD) returns ff2db3
cc
1210631008.462315: amcheck-clients: security_handleinit(handle=37d48, driver=ff
2db3cc (BSD))
1210631008.471146: amcheck-clients: bind_portrange2: Try port 813: Available -
Success
1210631008.471258: amcheck-clients: dgram_bind: socket 3 bound to 0.0.0.0.813
1210631008.471808: amcheck-clients: dgram_send_addr(addr=37d68, dgram=ff2e0cd4)
1210631008.471833: amcheck-clients: (sockaddr_in *)37d68 = { 2, 10080,
XX.YY.ZZ.30 }
The last lines above send out to XX.YY.ZZ.30
1210631008.471849: amcheck-clients: dgram_send_addr: ff2e0cd4-socket = 3
1210631008.534349: amcheck-clients: dgram_recv(dgram=ff2e0cd4, timeout=0, froma
ddr=ff2f0cc0)
1210631008.534414: amcheck-clients: (sockaddr_in *)ff2f0cc0 = { 2, 10080, 128.3
2.244.31 }
1210631008.534520: amcheck-clients: Receive packet from unknown source121063100
9.560074: amcheck-clients: dgram_recv(dgram=ff2e0cd4, timeout=0, fromaddr=ff2f0
cc0)
--end--
However, the tapehost is receiving from XX.YY.ZZ.31:
Running snoop on the tapehost, I can see it sends packets to
the .30
tapehost - XX.YY.ZZ.30 UDP D=10080 S=813 LEN=133
tapehost - XX.YY.ZZ.30 UDP D=10080 S=813 LEN=133
tapehost - XX.YY.ZZ.30 UDP D=10080 S=813 LEN=133
However, running snoop on the multi-homed, machine, I can see that
it receives on .30 and sends on .31
tapehost - XX.YY.ZZ.30 UDP D=10080 S=813 LEN=133
XX.YY.ZZ.31 - tapehost UDP D=813 S=10080 LEN=99
XX.YY.ZZ.31 - tapehost UDP D=813 S=10080 LEN=99
tapehost - XX.YY.ZZ.30 UDP D=10080 S=813 LEN=133
XX.YY.ZZ.31 - tapehost UDP D=813 S=10080 LEN=99
XX.YY.ZZ.31 - tapehost UDP D=813 S=10080 LEN=99
XX.YY.ZZ.31 - tapehost UDP D=813 S=10080 LEN=99
XX.YY.ZZ.31 - tapehost UDP D=813 S=10080 LEN=99
The Receive packet from unknown source message comes from
common-src/security-util.c udp_netfd_read_callback():
/*
* If we didn't find a handle, then check for a new incoming packet.
* If no accept handler was setup, then just return.
*/
if (udp-accept_fn == NULL) {
dbprintf(_(Receive packet from unknown source));
return;
}
I think the problem is that the kernel is sending the ack on whatever
interface it wants to, which is probably permitted. An explanation
can be found at
Socket Binding on a Multihomed Host
http://blogs.msdn.com/zhengpei/archive/2007/04/25/socket-binding-on-a-multihomed-host.aspx
See also:
* Re: Binding amanda to specific interface (2003)
Re: problem deleting DLE from backup
I tested with latest version and it works, Which version are you using? You can remove the 192.168.95.225 directory from the 'curinfo' directory, that's what the delete command do. Why do you want to do that? Jean-Louis Mister Olli wrote: hi list... I have the following problem when trying to delete all DLE for host 192.168.95.225 [EMAIL PROTECTED] /tmp/amanda/server/weekly]$ amadmin weekly find 192* Argument '192*' match neither a host nor a disk. date host disk lv tape or file file part status 2008-04-20 192.168.95.225 / 0 weekly 261 OK 2008-04-27 192.168.95.225 / 0 weekly 201 OK 2008-05-04 192.168.95.225 / 0 weekly 251 OK 2008-04-20 192.168.95.225 /usr 0 weekly 241 OK 2008-04-27 192.168.95.225 /usr 0 weekly 181 OK 2008-05-04 192.168.95.225 /usr 0 weekly 241 OK 2008-04-20 192.168.95.225 /var 0 weekly 251 OK 2008-04-27 192.168.95.225 /var 0 weekly 251 OK 2008-05-04 192.168.95.225 /var 0 weekly 261 OK [EMAIL PROTECTED] /tmp/amanda/server/weekly]$ amadmin weekly delete 192.168.95.225 Argument '192.168.95.225' match neither a host nor a disk. amadmin: no disk matched [EMAIL PROTECTED] /tmp/amanda/server/weekly]$ amadmin weekly delete 192.168.95.225 / Argument '192.168.95.225' match neither a host nor a disk. Argument '/' match neither a host nor a disk. amadmin: no disk matched [EMAIL PROTECTED] /tmp/amanda/server/weekly]$ exit [EMAIL PROTECTED] /tmp/amanda/server/weekly]# amadmin weekly delete 192.168.95.225 amadmin: ERROR: running as user root instead of amanda [EMAIL PROTECTED] /tmp/amanda/server/weekly]# Can anyone help me out on this? I don't understand why I can find the DLE but can not delete them. regards, olli
