I'm having the same problem. I'll provide what additional information I have:
Operating system: Solaris 5.9 on amanda server and client amanda version: 2.4.4p3 problem happens in both sendbackup and sendsize There seems to be a problem with permissions being created on some temporary directories ( in /tmp in this case ): $ ls -la /tmp total 178 drwxrwxrwt 12 root sys 867 Feb 23 08:30 . drwxr-xr-x 24 root root 1024 Feb 21 22:48 .. d--------- 2 amanda backup 117 Feb 23 04:00 .rlg.iDa4R3 d--------- 2 amanda backup 117 Feb 23 04:00 .rlg.o3aiS3 d--------- 2 amanda backup 117 Feb 23 04:23 .rlg.uUaWT3 drwx------ 2 amanda backup 718 Feb 23 04:23 amanda As you can see, amanda has no write permission in ".rlg*", though I am getting the debug files in /tmp/amanda. This could be the source of the problem, though I've no idea how to fix this. Could it be a umask issue when amandad is called from inetd? Speaking of the debug files, here are a couple that provide a little more information on the issue: :::::::::::::: sendbackup.20050223042349.debug :::::::::::::: sendbackup: debug 1 pid 28523 ruid 479 euid 479: start at Wed Feb 23 04:23:49 20 05 /usr/site/amanda-2.4.4p3/libexec/sendbackup: version 2.4.4p3 parsed request as: program `DUMP' disk `/dev/md/rdsk/d92' device `/dev/md/rdsk/d92' level 0 since 1970:1:1:0:0:0 options `|;bsd-auth;no-record;index;' sendbackup: try_socksize: send buffer size is 65536 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.50045 sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.50046 sendbackup: time 0.001: stream_server: waiting for connection: 0.0.0.0.50047 sendbackup: time 0.001: waiting for connect on 50045, then 50046, then 50047 sendbackup: time 0.004: stream_accept: connection from 172.23.247.34.50070 sendbackup: time 0.005: stream_accept: connection from 172.23.247.34.50071 sendbackup: time 0.007: stream_accept: connection from 172.23.247.34.50072 sendbackup: time 0.007: got all connections sendbackup: time 0.010: dumping device '/dev/md/rdsk/d92' with '' sendbackup: time 0.011: spawning /usr/sbin/ufsdump in pipeline sendbackup: argument list: dump 0sf 1048576 - /dev/md/rdsk/d92 sendbackup: time 0.016: started index creator: "/usr/sbin/ufsrestore -tvf - 2>&1 | sed -e ' s/^leaf[ ]*[0-9]*[ ]*\.// t /^dir[ ]/ { s/^dir[ ]*[0-9]*[ ]*\.// s%$%/% t } d '" sendbackup: time 0.024: 117: strange(?): Unable to create temporary directory in any of the directories listed below: sendbackup: time 0.026: 117: strange(?): /tmp/ sendbackup: time 0.029: 117: strange(?): /var/tmp/ sendbackup: time 0.031: 117: strange(?): / sendbackup: time 0.033: 117: strange(?): Please correct this problem and rerun t he program. sendbackup: time 0.188: 93: normal(|): DUMP: Date of this level 0 dump: Wed Feb 23 04:23:49 2005 sendbackup: time 0.190: 93: normal(|): DUMP: Date of last level 0 dump: the epoch sendbackup: time 0.192: 93: normal(|): DUMP: Dumping /dev/md/rdsk/d92 to sta ndard output. sendbackup: time 5.444: 93: normal(|): DUMP: Mapping (Pass I) [regular files ] sendbackup: time 7.467: 93: normal(|): DUMP: Mapping (Pass II) [directories] sendbackup: time 8.159: 93: normal(|): DUMP: Writing 32 Kilobyte records AND :::::::::::::: sendsize.20050223040002.debug :::::::::::::: sendsize: debug 1 pid 28507 ruid 479 euid 479: start at Wed Feb 23 04:00:02 2005 sendsize: version 2.4.4p3 sendsize[28507]: time 0.003: waiting for any estimate child: 1 running sendsize[28509]: time 0.004: calculating for amname '/dev/md/rdsk/d92', dirname '/dev/md/rdsk/d92', spindle 2 sendsize[28509]: time 0.004: getting size via dump for /dev/md/rdsk/d92 level 0 sendsize[28509]: time 0.007: calculating for device '/dev/md/rdsk/d92' with '' sendsize[28509]: time 0.007: running "/usr/sbin/ufsdump 0Ssf 1048576 - /dev/md/r dsk/d92" sendsize[28509]: time 0.008: running /usr/site/amanda-2.4.4p3/libexec/killpgrp sendsize[28509]: time 0.033: Unable to create temporary directory in any of the directories listed below: sendsize[28509]: time 0.035: /tmp/ sendsize[28509]: time 0.036: /var/tmp/ sendsize[28509]: time 0.038: / sendsize[28509]: time 0.039: Please correct this problem and rerun the program. sendsize[28509]: time 8.865: 43413370880 sendsize[28509]: time 8.867: ..... sendsize[28509]: estimate time for /dev/md/rdsk/d92 level 0: 8.860 sendsize[28509]: estimate size for /dev/md/rdsk/d92 level 0: 42395870 KB sendsize[28509]: time 8.867: asking killpgrp to terminate sendsize[28509]: time 9.865: getting size via dump for /dev/md/rdsk/d92 level 1 sendsize[28509]: time 9.867: calculating for device '/dev/md/rdsk/d92' with '' sendsize[28509]: time 9.868: running "/usr/sbin/ufsdump 1Ssf 1048576 - /dev/md/r dsk/d92" sendsize[28509]: time 9.869: running /usr/site/amanda-2.4.4p3/libexec/killpgrp sendsize[28509]: time 9.879: Unable to create temporary directory in any of the directories listed below: sendsize[28509]: time 9.881: /tmp/ sendsize[28509]: time 9.882: /var/tmp/ sendsize[28509]: time 9.884: / sendsize[28509]: time 9.885: Please correct this problem and rerun the program. sendsize[28509]: time 17.903: 43413370880 sendsize[28509]: time 17.905: ..... sendsize[28509]: estimate time for /dev/md/rdsk/d92 level 1: 8.037 sendsize[28509]: estimate size for /dev/md/rdsk/d92 level 1: 42395870 KB sendsize[28509]: time 17.905: asking killpgrp to terminate sendsize[28509]: time 18.905: done with amname '/dev/md/rdsk/d92', dirname '/dev /md/rdsk/d92', spindle 2 sendsize[28507]: time 18.906: child 28509 terminated normally sendsize: time 18.906: pid 28507 finish time Wed Feb 23 04:00:21 2005 These would seem to explain the three instances of "/tmp/.rlg*". Looking for all the help I can get on this issue. My other solaris systems are not showing this problem, though they are 5.8, not 5.9 systems. Is there some tightening of security associated with 5.9? Any thanks for any help that can be offered. --- In [EMAIL PROTECTED], "Gil Naveh" <[EMAIL PROTECTED]> wrote: > > Gene, thanks for the help. > Per your request below is the section that describes why I got the Strange > message: > > FAILED AND STRANGE DUMP DETAILS: > > /-- servername /bck/folder lev 0 STRANGE > sendbackup: start [servername:/bck/folder level 0] > sendbackup: info BACKUP=/usr/sbin/ufsdump > sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc > |/usr/sbin/ufsrestore -f... - > sendbackup: info COMPRESS_SUFFIX=.gz > sendbackup: info end > ? Unable to create temporary directory in any of the directories listed > below: > ? /tmp/ > ? /var/tmp/ > ? / > ? Please correct this problem and rerun the program. > | DUMP: Date of this level 0 dump: Wed Feb 16 00:46:26 2005 > | DUMP: Date of last level 0 dump: the epoch > | DUMP: Dumping /dev/rdsk/c1t1d0s6 (servername:/bck) to standard output. > | DUMP: Mapping (Pass I) [regular files] > | DUMP: Mapping (Pass II) [directories] > | DUMP: Writing 32 Kilobyte records > | DUMP: Estimated 230640 blocks (112.62MB) on 0.00 tapes. > | DUMP: Dumping (Pass III) [directories] > | DUMP: Dumping (Pass IV) [regular files] > | DUMP: 230590 blocks (112.59MB) on 1 volume at 10095 KB/sec > | DUMP: DUMP IS DONE > sendbackup: size 115295 > sendbackup: end > \-------- > > The above section shows that Amanda was not able to create temporary folders > in /tmp/ - but I checked it and it is not a disk issue as well as > permission? (I was able to manually create (as Amanda user) a new folder in > /tmp ) > Any ideas why Amanda is having problem creating temporary folders? > > Thx, > gil > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Gene Heskett > Sent: Wednesday, February 16, 2005 10:17 AM > To: [EMAIL PROTECTED] > Subject: Re: Amanda's report > > > On Wednesday 16 February 2005 09:45, Gil Naveh wrote: > >After running Amanda's backup, I receive an email with a report > > about the last backup. > >The first section of that report is: "FAILURE AND STRANGE DUMP > > SUMMARY:" and under this section I get the following message: > > > > FAILURE AND STRANGE DUMP SUMMARY: > > servername /folder/to/backup lev 0 STRANGE > > > You didn't post all the summary, so we can't guess really well. > > >What does STRANGE means? > > What it usually means here is that some file changed while it was > being read, like here, I get squawks about mail files from time to > time because kmail is running 24/7, and may do a mail fetch run,or > decide to purge old messages while amanda is running. > > >I checked the data that was backed up on the tape and was able to > > restore it - should I ignore that message or what does Amanda tries > > to tell me? > > Dunno, post the rest of summary and we'll take a look. > > >Many thanks, > >gil > > -- > Cheers, Gene > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > 99.33% setiathome rank, not too shabby for a WV hillbilly > Yahoo.com attorneys please note, additions to this message > by Gene Heskett are: > Copyright 2005 by Maurice Eugene Heskett, all rights reserved. ----------------------------------------------- Karl Burkett [EMAIL PROTECTED] Rice University 713.348.6256 -----------------------------------------------