RE: Errors still occuring on one drive...
John R. Jackson [mailto:[EMAIL PROTECTED]] wrote: > Look at your amandad*debug file for lines like this: > > SERVICE sendbackup > OPTIONS hostname=fortress.cc.purdue.edu; > DUMP /data 2 2002:4:6:7:59:19 OPTIONS |;bsd-auth;index; > > Put the OPTIONS (if you have one) and GNUTAR lines in a file > (do not put > the "SERVICE" line in it). Then run sendbackup **as your > Amanda user** > with "-t" as an argument and this file as standard input: > > .../libexec/sendbackup -t < service-file > index-output > > My guess is this will also not show you anything. And you were correct. This worked just fine > We can also test this from the server side. Find the line > for this disk > in the "GENERATING SCHEDULE" section of your amdump. file: > > fortress.cc.purdue.edu /data 2 5 2002:4:6:7:59:19 2722448 1995 > > Put that in a file someplace. Then make (and remember :-) > these changes > to your amanda.conf: > > * set "record no" > * comment out any tape changer settings > * change tapedev to "/dev/null" (or "null:" if you're using 2.4.3) > > Then run libexec/driver as your Amanda user with the config > name as the > only arg and the file as stdin: > > .../libexec/driver CONFIG < schedule-file 2>&1 | tee test-log OK. This worked. It seemed to dump just fine. There seemed to be nothing in the output that would indicate why the dump has been failing in the past. I'm now wondering if the problem has to do with having more than one dumper dumping at the same time -- I think that it might be that some of the partitions are on the same disk, and perhaps there is a conflict with dump? I will try using the "spindle" values in the disklist to see if that helps solve the problem... Any other suggestions? Thanks, Ricky
Re: 2.4.2p2 compiling problems on Solaris 2.6 and RedHat 7.2
>Is "gdbm" support just broken in this release? ... I'm sure that's the case. >Has anyone found a solution to this problem? As I said, if you can get by without out, that's probably the way to go. If you can't, then I'll take a look when I get back from a conference next week (or someone else can take a shot at it in between). I'm sure it's just some header file magic that has to be dealt with. >Marc Davignon John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: 2.4.2p2 compiling problems on Solaris 2.6 and RedHat 7.2
Thanks for the suggestions. I will make sure I change the --with-user and --with-group options before this goes into production. On the --with-db=gdbm issue, your also right. Setting --with-db=text gets around this issue completely and this is probably the way I will go. Just for kicks though I also tried a compile on a RedHat 7.2 box with the following options: ./configure --prefix=/usr/local/amanda --libexecdir=/usr/local/amanda/lib --with-configdir=/proj/amanda --with-suffixes --with-fqdn --with-bsd-security --with-config=NONE --with-tape-device=/dev/rmt/0mn --with-smbclient=/usr/bin/smbclient --with-user=root --with-group=root --with-db=gdbm --with-debugging --with-includes=/usr/local/include /usr/include/gdbm --with-libraries=/usr/local/lib and got the same result: -- gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../tape-src -D_FILE_OFFSET_BITS=64 -I/usr/local/include -I/usr/include/gdbm -D_FILE_OFFSET_BITS=64 -g -O2 -c infofile.c -o infofile.o infofile.c:46: parse error before `*' infofile.c:46: warning: data definition has no type or storage class infofile.c: In function `open_infofile': infofile.c:391: warning: assignment makes pointer from integer without a cast infofile.c: In function `get_info': infofile.c:525: incompatible types in assignment infofile.c: In function `get_firstkey': infofile.c:554: incompatible types in assignment infofile.c: In function `get_nextkey': infofile.c:597: incompatible types in assignment infofile.c: In function `put_info': infofile.c:658: `DBM_REPLACE' undeclared (first use in this function) infofile.c:658: (Each undeclared identifier is reported only once infofile.c:658: for each function it appears in.) make[1]: *** [infofile.lo] Error 1 make[1]: Leaving directory `/home/mpdavig/stuff/downloads/amanda-2.4.2p2/server-src' make: *** [all-recursive] Error 1 -- Is "gdbm" support just broken in this release? Or is there something wrong with gdbm-1.8.0 itself? Has anyone found a solution to this problem? -- Thanks, Marc Davignon Systems Administrator, Merrill Lynch ITG On Fri, 12 Apr 2002, John R. Jackson wrote: > >I'm compiling with the following params: > >... > >--with-user=root --with-group=root > > Side issue. Do you really need to run as user root? Amanda is not > normally set up that way (why ask for permissions you don't need). > > >--with-db=gdbm > > Sigh. At 2.4 a new database format, "text", was introduced. It's **so** > much easier to work with, it was made the default and I doubt anyone has > used "real" DBM files for years. There never was enough load on those > files to justify a database engine (IMO). > > So, rather than digging into making DBM work again (and as I recall, it's > going to be completely removed before too long), how about switching to > --with-db=text (or just leaving it off)? All you have to do (as I recall) > is run "amadmin export" on your old config before upgrading, > then "amadmin import" afterward. > > U, maybe you shouldn't have nuked the old 2.3.0.4 version yet? :-) > > If you really, really, have to have DBM support, it can probably be > fixed up. Although I'll be away at a conference next week (at the UofMD, > birthplace of Amanda, I just realized :-) and won't be able to help > until after that. > > >Marc Davignon > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
./configure error, Amanda 2.4.2p2 CVS of 20011020
Hi,
when trying to build Amanda 2.4.2p2 CVS of 20011020 on a Linux box (SuSE
Linux 8.0), configure fails:
checking for xfsdump... /sbin/xfsdump
checking for xfsrestore... /sbin/xfsrestore
./configure: line 5093: syntax error near unexpected token
`&m4_default(['
./configure: line 5093: `{ echo "$as_me:5093: WARNING: *** to
disable it, just #undef XFSDUMP in config/config.h"
>&m4_default([AS_MESSAGE_LOG_FD], [AS_MESSAGE_FD])'
Building starts with
+ cd /usr/src/packages/BUILD
+ cd amanda-2.4.2p2-20011020
+ ./autogen
configure.in: 8: required file `config/config.h.in' not found
configure.in:25: warning: AC_ARG_PROGRAM invoked multiple times
configure.in:1544: warning: AC_PROG_LEX invoked multiple times
+ ./configure --prefix=/usr --sysconfdir=/var/lib
--libdir=/usr/lib/amanda --localstatedir=/var/lib
--libexecdir=/usr/libexec/amanda --with-index-server=amandahost
--with-portrange=15000,15029 --with-tape-device=/dev/nst0
--with-user=amanda --with-group=disk --with-dump-honor-nodump
--with-gnu-ld --enable-shared
autoconf (GNU Autoconf) 2.52
automake (GNU automake) 1.4-p5
