2.5.0 compile problems on HP-UX 10.10
I;m upgrading one of my Amanda servers. I noticed that on one of my Oracle machines (HP-UX 10.20) that the report was returning file changed errors on some of the .dbf files. ell, yes, but they are in the gtar exclude file. Odd I thought. I have not upgraded the clients yet, so I thought I would do that on this machine first, before trying to figure out why the exclude file is not working. Problem 2.5.0 does not compile on this machine. I recjecked, and re-ran configure on 2.4.5, and it compiled fine. Here ar my configure settings: #/bin/ksh export CPPFLAGS=-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 export CFLAGS=-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 export PERL=/opt/perl5/bin/perl ./configure --with-config=DailyDump \ --prefix=/opt/amanda --with-index-server=debian --with-user=amanda \ --with-group=operator --with-tape-server=debian --with-debugging \ --with-tape-device=/dev/nst0 --sbindir=/opt/amanda/sbin \ --libexecdir=/opt/amanda/libexec --libdir=/opt/amanda/lib \ --with-configdir=/opt/amanda/etc/amanda \ --with-gnutar-listdir=/opt/amanda/var/amanda/gnutar-lists \ --mandir=/opt/amanda/man --without-rundump \ --with-includes=/opt/gnu/include --with-libraries=/opt/amanda/lib \ --with-gnuplot=/opt/gnuplot/bin \ --with-tcpportrange=1702,1712 \ --with-udpportrange=702,712 Here are (what I hope are) some details on teh failure: Script started on Sun Apr 16 10:42:14 2006 WARNING: YOU ARE SUPERUSER !! [EMAIL PROTECTED]:/local/src/pd/amanda/amanda-2.5.0 $ make No suffix list. Making all in config No suffix list. make all-am No suffix list. Making all in common-src source='alloc.c' object='alloc.lo' libtool=yes \ DEPDIR=.deps depmode=gcc /bin/sh ../config/depcomp \ /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D__STDC_EXT__ -I/opt/gnu/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -c -o alloc.lo alloc.c mkdir .libs gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D__STDC_EXT__ -I/opt/gnu/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -c alloc.c -Wp,-MD,.deps/alloc.TPlo -fPIC -DPIC -o .libs/alloc.o In file included from amanda.h:245, from alloc.c:33: amanda-int.h:328: warning: `INT8_MIN' redefined /usr/include/inttypes.h:102: warning: this is the location of the previous definition amanda-int.h:329: warning: `INT16_MIN' redefined /usr/include/inttypes.h:103: warning: this is the location of the previous definition amanda-int.h:330: warning: `INT32_MIN' redefined /usr/include/inttypes.h:104: warning: this is the location of the previous definition amanda-int.h:331: warning: `INT64_MIN' redefined /usr/include/inttypes.h:105: warning: this is the location of the previous definition amanda-int.h:333: warning: `INT8_MAX' redefined /usr/include/inttypes.h:97: warning: this is the location of the previous definition amanda-int.h:334: warning: `INT16_MAX' redefined /usr/include/inttypes.h:98: warning: this is the location of the previous definition amanda-int.h:335: warning: `INT32_MAX' redefined /usr/include/inttypes.h:99: warning: this is the location of the previous definition amanda-int.h:336: warning: `INT64_MAX' redefined /usr/include/inttypes.h:100: warning: this is the location of the previous definition amanda-int.h:339: warning: `UINT8_MAX' redefined /usr/include/inttypes.h:117: warning: this is the location of the previous definition amanda-int.h:340: warning: `UINT16_MAX' redefined /usr/include/inttypes.h:118: warning: this is the location of the previous definition amanda-int.h:341: warning: `UINT32_MAX' redefined /usr/include/inttypes.h:119: warning: this is the location of the previous definition amanda-int.h:342: warning: `UINT64_MAX' redefined /usr/include/inttypes.h:120: warning: this is the location of the previous definition --- skip --- /usr/include/inttypes.h:120: warning: this is the location of the previous definition /bin/sh ../libtool --tag=CC --mode=link gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -L/opt/amanda/lib -o noop noop.o ../common-src/libamanda.la libamclient.la ../tape-src/libamtape.la ../common-src/libamanda.la -lm -ltermcap -lcur_colr libtool: link: warning: this platform does not like uninstalled shared libraries libtool: link: `noop' will be relinked during installation gcc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -o .libs/noop noop.o -L/opt/amanda/lib ./.libs/libamclient.sl ../tape-src/.libs/libamtape.sl ../common-src/.libs/libamanda.sl -lm -ltermcap -lcur_colr -Wl,+b -Wl,/local/src/pd/amanda/amanda-2.5.0/client-src/.libs:/local/src/pd/amanda/amanda-2.5.0/tape-src/.libs:/local/src/pd/amanda/amanda-2.5.0/common-src/.libs:/opt/amanda/lib creating noop source='calcsize.c' object='calcsize.o' libtool=no \ DEPDIR=.deps depmode=gcc /bin/sh ../config/depcomp \ gcc
Re: 2.5.0 compile problems on HP-UX 10.10
stan wrote: Here's the line that causes the error: char *aparent = vstralloc(parent_dir, /, include, NULL); Any sugestiosn as to wheer to begin on resoloving this? see if this patch help: --- calcsize.c 9 Mar 2006 16:51:41 - 1.36 +++ calcsize.c 29 Mar 2006 15:45:08 - 1.37 @@ -24,7 +24,7 @@ * file named AUTHORS, in the root directory of this distribution. */ /* - * $Id: calcsize.c,v 1.36 2006/03/09 16:51:41 martinea Exp $ + * $Id: calcsize.c,v 1.37 2006/03/29 15:45:08 martinea Exp $ * * traverse directory tree to get backup size estimates */ @@ -329,10 +329,11 @@ int l; int parent_len; int has_exclude = !is_empty_sl(exclude_sl) use_gtar_excl; +char *aparent; if(parent_dir == NULL || include == NULL) return; -char *aparent = vstralloc(parent_dir, /, include, NULL); +aparent = vstralloc(parent_dir, /, include, NULL); if(stat(parent_dir, finfo) != -1) parent_dev = finfo.st_dev; -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: 2.5.0 compile problems on HP-UX 10.10
On Sun, Apr 16, 2006 at 08:14:55AM -0700, Kevin Till wrote: stan wrote: Here's the line that causes the error: char *aparent = vstralloc(parent_dir, /, include, NULL); Any sugestiosn as to wheer to begin on resoloving this? see if this patch help: --- calcsize.c 9 Mar 2006 16:51:41 - 1.36 +++ calcsize.c 29 Mar 2006 15:45:08 - 1.37 @@ -24,7 +24,7 @@ * file named AUTHORS, in the root directory of this distribution. */ /* - * $Id: calcsize.c,v 1.36 2006/03/09 16:51:41 martinea Exp $ + * $Id: calcsize.c,v 1.37 2006/03/29 15:45:08 martinea Exp $ * * traverse directory tree to get backup size estimates */ @@ -329,10 +329,11 @@ int l; int parent_len; int has_exclude = !is_empty_sl(exclude_sl) use_gtar_excl; +char *aparent; if(parent_dir == NULL || include == NULL) return; -char *aparent = vstralloc(parent_dir, /, include, NULL); +aparent = vstralloc(parent_dir, /, include, NULL); if(stat(parent_dir, finfo) != -1) parent_dev = finfo.st_dev; Thanks, that fixed it. Guess this old version of GCC gcc version 2.95.2 19991024 can't handle the decleration, and definition at the same time. I don't know if this fix should be comited, as I suppose, I should be using a newer version of GCC. Even on a system as old as this. I'm trying to do as little updating on these baoxes as ai can. They are production critacl, but dead ended as the will eventually be replaced by Soalris boxes. Thanks, again. -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Dump results missing from report?
I recently set up an amanda (2.4.3-4)server servicing two amanda clients, allrunning RHES 3.0 Linux. For both clients, I chose to use GNU Tar (1.13.25) to backup partitions vice dump. Everything works quite well, but I'm used to seeing a dump summary in the emailed report from other amanda environments I've set up. The reports I'm getting from the amanda server lack the detailed dump summary showing all the hosts:partitions, compression stats, etc. Is this symptomatic of this particular build of amanda (I've been using 2.4.2 exclusively in the past). If not, is there a setting I've missed somewhere? Any and all help appreciated. Thanks. George
Re: Dump results missing from report?
On Sun, Apr 16, 2006 at 03:44:32PM -0400, George wrote: I recently set up an amanda (2.4.3-4) server servicing two amanda clients, all running RHES 3.0 Linux. For both clients, I chose to use GNU Tar ( 1.13.25) to backup partitions vice dump. Everything works quite well, but I'm used to seeing a dump summary in the emailed report from other amanda environments I've set up. The reports I'm getting from the amanda server lack the detailed dump summary showing all the hosts:partitions, compression stats, etc. Is this symptomatic of this particular build of amanda (I've been using 2.4.2 exclusively in the past). If not, is there a setting I've missed somewhere? Any and all help appreciated. Thanks. Are you refering to the section of the report that starts with: DUMP SUMMARY: ? If so I've always gotten lines in that for clients backed up with Gnu tar. -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967
Re: Dump results missing from report?
On 4/16/06, stan [EMAIL PROTECTED] wrote: On Sun, Apr 16, 2006 at 03:44:32PM -0400, George wrote: I recently set up an amanda (2.4.3-4) server servicing two amanda clients, all running RHES 3.0 Linux. For both clients, I chose to use GNU Tar ( 1.13.25) to backup partitions vice dump. Everything works quite well, but I'm used to seeing a dump summary in the emailed report from other amanda environments I've set up. The reports I'm getting from the amanda server lack the detailed dump summary showing all the hosts:partitions, compression stats, etc. Is this symptomatic of this particular build of amanda (I've been using 2.4.2 exclusively in the past). If not, is there a setting I've missed somewhere? Any and all help appreciated. Thanks.Are you refering to the section of the report that starts with: DUMP SUMMARY: ?If so I've always gotten lines in that for clients backed up with Gnu tar.--U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror- New York Times 9/3/1967 Hi Stan; Yes, thats the section of the report to which I'm referring. Here's an example of what I'm getting automatically after the backups finish: These dumps were to tape Backup-12.The next tape Amanda expects to use is: a new tape.STATISTICS: Total Full Daily Estimate Time (hrs:min) 0:00Run Time (hrs:min) 0:01Dump Time (hrs:min) 0:01 0:01 0:00Output Size (meg) 9.8 8.4 1.4Original Size (meg) 33.5 29.1 4.4Avg Compressed Size (%) 29.2 28.8 31.9 (level:#disks ...)Filesystems Dumped 7 2 5 (1:5)Avg Dump Rate (k/s) 156.5 140.4 501.1
Re: Dump results missing from report?
George schreef: I recently set up an amanda (2.4.3-4) server servicing two amanda clients, all running RHES 3.0 Linux. For both clients, I chose to use GNU Tar (1.13.25) to backup partitions vice dump. Everything works quite well, but I'm used to seeing a dump summary in the emailed report from other amanda environments I've set up. The reports I'm getting from the amanda server lack the detailed dump summary showing all the hosts:partitions, compression stats, etc. Is this symptomatic of this particular build of amanda (I've been using 2.4.2 exclusively in the past). If not, is there a setting I've missed somewhere? Any and all help appreciated. Thanks. I believe that somewhere in version 2.4.2p2 (or as it p1?) there was formfeed added between the sections. Is the mail broken off, or is it just showing a lot of white space followed by the next section? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Size of holding disk when backing up to HDD
Hello! I am backing up to disk. I thought I put away enough holding space, but apparently not. I get the following warning. WARNING: holding disk /data: only 91831964 KB free (104857600 KB requested) How important is this? Am I taking a big performance hit because of this? Or can I ignore this warning? Thanks! David
Re: Size of holding disk when backing up to HDD
David Leangen wrote: Hello! I am backing up to disk. I thought I put away enough holding space, but apparently not. I get the following warning. WARNING: holding disk /data: only 91831964 KB free (104857600 KB requested) How important is this? Am I taking a big performance hit because of this? Or can I ignore this warning? It just means you told Amanda you had nearly 105GB of holding disk but it only found about 92GB of available space. Unless your backups are very large and your tape drive is slow, 92GB should be plenty. If you're not getting errors about running out of holdingdisk and dumps going directly to tape, I wouldn't worry about it. Frank Thanks! David -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Size of holding disk when backing up to HDD
Thank you! I'm still having trouble with my backup on a particular client, but it may be due to another issue... So, I'll start another thread. On Sun, 2006-04-16 at 22:16 -0500, Frank Smith wrote: David Leangen wrote: Hello! I am backing up to disk. I thought I put away enough holding space, but apparently not. I get the following warning. WARNING: holding disk /data: only 91831964 KB free (104857600 KB requested) How important is this? Am I taking a big performance hit because of this? Or can I ignore this warning? It just means you told Amanda you had nearly 105GB of holding disk but it only found about 92GB of available space. Unless your backups are very large and your tape drive is slow, 92GB should be plenty. If you're not getting errors about running out of holdingdisk and dumps going directly to tape, I wouldn't worry about it. Frank Thanks! David
Could not open index directory bla
I'm still not able to backup one of my local networked hosts. The only problem I can find in the logs is this: could not open index directory /usr/adm/amanda/daily/index/host/_home/ Could this be a cause of my problems? I am running the process from my backup server like so: $root: sudo -u amanda amdump daily And the directory (as well as its parent directories) on my backup server have permissions: In dir: /usr/adm/amanda/daily/index drwxr-sr-x 3 amanda amanda 4096 Apr 4 16:48 host Why would this error occur? The process owner is amanda and the permissions are ok for user amanda... Thanks!! Dave
Re: Could not open index directory bla
On Mon, Apr 17, 2006 at 12:46:15PM +0900, David Leangen wrote: I'm still not able to backup one of my local networked hosts. The only problem I can find in the logs is this: could not open index directory /usr/adm/amanda/daily/index/host/_home/ Could this be a cause of my problems? The index would not be created unless a backup had succeeded. Have you ever succeeded in backing up this DLE? If not, the problem is likely elsewhere. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Could not open index directory bla
The index would not be created unless a backup had succeeded. Have you ever succeeded in backing up this DLE? If not, the problem is likely elsewhere. No, since I have updated to 2.5.0, I have not. But this is the only error or warning message that I could find. Any ideas where I could look, other than the log files in /tmp/amanda on both the backup server and networked host? Cheers, Dave
Each file on Samba backup target produces NT_STATUS_OBJECT_PATH_NOT_FOUND error
I just had to move to a new install of Amanda due to a crash of my backup server. The new server is using the Amanda 2.4.5p1 packages under Fedora Core 5, the old server was redhat 9 and Amanda 2.4.4p2. I copied the config from the old server to the new exact, and all worked fine (minus the need to migrate from chg-scsi to chg-zd-mtx as documented in my earlier thread). This new setup ran for the first time last night, with disastrous results. More than half of my backup targets had estimate timeouts, and the root problem seems to be that the one and only Samba mount that I backup threw 10 megabytes worth of errors like those below into the log file... ? NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\grads\xu xi\Hw3\Ch\ifa\draw\images\Diamond1.gif (\home\grads\xuxi\Hw3\Ch\ifa\dr aw\images\) ... one of those for each and every file on that share. From the command line, I can browse the mount fine with 'smbclient' and these files are all there. I've triple-checked the user, password, and workgroup settings in /etc/amandapass. Sorta stumped as to where to go from here. For tonight, I am disabling the samba share backup in the hopes that this will allow the rest of my targets to successfully backup. After that, I have to figure out what's up here. Any thoughts? Thanks, Fran
dump larger than available tape space
I finally noticed some log files that I never before noticed existed. Apparently, my backup is larger than my tape space. But, shouldn't it span multiple tapes? If I'm not mistaken, this is what happened in earlier versions. I suppose that this explains why my backup suddenly fails now for 2.5.0. Has the chg-disk behaviour changed somehow? Thanks so much! DISK planner host /home START planner date 20060417 INFO planner Adding new disk host:/home. START driver date 20060417 STATS driver startup time 0.046 START taper datestamp 20060417 label daily19 tape 0 FAIL planner host /home 20060417 0 [dump larger than available tape space, 5953830 KB, but cannot incremental dump new disk] FATAL planner cannot fit anything on tape, bailing out WARNING driver WARNING: got empty schedule from planner INFO taper tape daily19 kb 0 fm 0 [OK] FINISH driver date 20060417 time 217.380
