Re: DLE RESULTS MISSING after failed backup due to drive not being turned on
amdump now seems to think it should include the old test DLE in new backups. The test DLE is not actually included in the backup as it has no information on where to get it from but it still shows up in the status screen from amdump. When i removed it i ran amadmin delete for the test DLE and then removed it from the disklist. Log has "INFO planner Adding new disk localhost:test" and amdump log has "localhost:test overdue 19105 days for level 0". I removed the tape which the test DLE was on (and some actual backups with it) with 'amrmtape backup --keep-label --cleanup ROT09' and now amadmin find does not see the test DLE anymore and seems to also have resolved amdump. Do i really need to do it this way or should i have done something else to remove the old DLE? Anton "exuvo" Olsson ex...@exuvo.se On 2022-04-20 15:58, Exuvo wrote: Resolved, had an old test DLE on the tape it was trying to use. I don't understand why it still loaded the tape and did not give any useful error message about it. My testing: If i make a new logs directory the estimate actually runs. Tried moving out all the logs from that day but it still fails which i found weird. Tried moving out one log at a time to find the culprit but it seems that as long as any one of the old logs is there my storage DLE fails. I was only running the storage DLE as that was the only one that failed during the normal backup schedule. I also tried clearing the curinfo file for the DLE. Next i tried running a full backup with all DLEs and now they all showed as MISSING immediately. Which was very interesting. The only common thing for when the DLEs started being missing is that they want to use tape ROT09. Which is the first tape i did a test backup on. I think the actual issue is that it is not finding a usable tape even tho it loads the tape first as if it thinks it is an valid tape to use. Removing the test DLE with amadmin delete made it start working again. Anton "exuvo" Olsson ex...@exuvo.se On 2022-04-19 03:54, Exuvo wrote: The disk was full of old partial dumps from testing of another backup set so i did not want to flush them to any tapes. The logs "driver: adding holding disk 0 dir /dumps/ size 1949288448 chunksize 9007199254740896" indicate that it is finding the dump disk with correct size of 2TB free. Even if the dump drive was full i should be getting "FAILED [can't dump required holdingdisk when no holdingdisk space available ]" not MISSING on the DLE. I even tested with the holding disk disabled and it still says it is missing. The path is most certainly not missing from the filesystem. I also tried changing to another file path but still MISSING. It must be something in the database that got stuck, i will have to parse it myself and see if i can figure out what. Anton "exuvo" Olsson ex...@exuvo.se On 2022-04-18 02:34, John Lauro wrote: I normally use amflush to clear the holding disk. Not saying rm doesn't work, but that will not update the Amanda info database. It might think that space is still being used. On Sun, Apr 17, 2022 at 2:09 PM Exuvo wrote: I take it you did not read what i wrote. The holding disk is already empty after i 'rm -r':ed it. But even if i tell amanda to never use the holding disk for the failing DLE it just stops immediately when trying to run the planner (it normally takes a few minutes for that DLE). All other DLEs run fine.
Re: DLE RESULTS MISSING after failed backup due to drive not being turned on
Resolved, had an old test DLE on the tape it was trying to use. I don't understand why it still loaded the tape and did not give any useful error message about it. My testing: If i make a new logs directory the estimate actually runs. Tried moving out all the logs from that day but it still fails which i found weird. Tried moving out one log at a time to find the culprit but it seems that as long as any one of the old logs is there my storage DLE fails. I was only running the storage DLE as that was the only one that failed during the normal backup schedule. I also tried clearing the curinfo file for the DLE. Next i tried running a full backup with all DLEs and now they all showed as MISSING immediately. Which was very interesting. The only common thing for when the DLEs started being missing is that they want to use tape ROT09. Which is the first tape i did a test backup on. I think the actual issue is that it is not finding a usable tape even tho it loads the tape first as if it thinks it is an valid tape to use. Removing the test DLE with amadmin delete made it start working again. Anton "exuvo" Olsson ex...@exuvo.se On 2022-04-19 03:54, Exuvo wrote: The disk was full of old partial dumps from testing of another backup set so i did not want to flush them to any tapes. The logs "driver: adding holding disk 0 dir /dumps/ size 1949288448 chunksize 9007199254740896" indicate that it is finding the dump disk with correct size of 2TB free. Even if the dump drive was full i should be getting "FAILED [can't dump required holdingdisk when no holdingdisk space available ]" not MISSING on the DLE. I even tested with the holding disk disabled and it still says it is missing. The path is most certainly not missing from the filesystem. I also tried changing to another file path but still MISSING. It must be something in the database that got stuck, i will have to parse it myself and see if i can figure out what. Anton "exuvo" Olsson ex...@exuvo.se On 2022-04-18 02:34, John Lauro wrote: I normally use amflush to clear the holding disk. Not saying rm doesn't work, but that will not update the Amanda info database. It might think that space is still being used. On Sun, Apr 17, 2022 at 2:09 PM Exuvo wrote: I take it you did not read what i wrote. The holding disk is already empty after i 'rm -r':ed it. But even if i tell amanda to never use the holding disk for the failing DLE it just stops immediately when trying to run the planner (it normally takes a few minutes for that DLE). All other DLEs run fine.
Re: DLE RESULTS MISSING after failed backup due to drive not being turned on
The disk was full of old partial dumps from testing of another backup set so i did not want to flush them to any tapes. The logs "driver: adding holding disk 0 dir /dumps/ size 1949288448 chunksize 9007199254740896" indicate that it is finding the dump disk with correct size of 2TB free. Even if the dump drive was full i should be getting "FAILED [can't dump required holdingdisk when no holdingdisk space available ]" not MISSING on the DLE. I even tested with the holding disk disabled and it still says it is missing. The path is most certainly not missing from the filesystem. I also tried changing to another file path but still MISSING. It must be something in the database that got stuck, i will have to parse it myself and see if i can figure out what. Anton "exuvo" Olsson ex...@exuvo.se On 2022-04-18 02:34, John Lauro wrote: I normally use amflush to clear the holding disk. Not saying rm doesn't work, but that will not update the Amanda info database. It might think that space is still being used. On Sun, Apr 17, 2022 at 2:09 PM Exuvo wrote: I take it you did not read what i wrote. The holding disk is already empty after i 'rm -r':ed it. But even if i tell amanda to never use the holding disk for the failing DLE it just stops immediately when trying to run the planner (it normally takes a few minutes for that DLE). All other DLEs run fine.
Re: DLE RESULTS MISSING after failed backup due to drive not being turned on
I take it you did not read what i wrote. The holding disk is already empty after i 'rm -r':ed it. But even if i tell amanda to never use the holding disk for the failing DLE it just stops immediately when trying to run the planner (it normally takes a few minutes for that DLE). All other DLEs run fine. Anton "exuvo" Olsson ex...@exuvo.se On 2022-04-17 01:54, badd...@ingodsfamily.com wrote: I have frequently done an "ls" on my holding disk, and manually deleted files and directories older than 7 days ago, which clearly amanda is not planning to flush to tape. 7 days because I ran amanda nightly. Your time window is up to you. I'm not sure 'amcleanup -rv backup' gets everything. I had an "onboot" job to send me email and remind me of that command, but perhaps I didn't reboot often, or perhaps amanda didn't register those files any more. If amanda hasn't flushed them during normal backups (assuming autoflush = ALL, i think it is), then it isn't planning to. Manual deletions never hurt my setup. If your holding disk isn't empty, but amanda sees nothing she wants to backup, then I suggest a manual cleanup. Deb Baddorf retired from Fermilab On Saturday, April 16, 2022, 01:27:15 PM EDT, Exuvo wrote: My backup failed tonight as i forgot to turn on my tape drive before i went to bed. Nothing was written to my dump drive as it was too full from a previous aborted backup i had done. When i woke up i turned on the tape drive and ran the backup again as i have done before when this has happend, most DLEs ran fine but the one DLE i have with 'holdingdisk required' failed as there was too little space left on the holding disk. I cleared out the holding disk and ran just that one failed DLE but it fails instantly and i get: FAILURE DUMP SUMMARY: planner: FATAL find_est_for_dp return NULL localhost storage RESULTS MISSING I tried running 'amcleanup -rv backup' but it did not do anything: # sudo -u amanda amcleanup -rv backup amcleanup: pid 2972312 is done amcleanup: pid 2972313 is done amcleanup: pid 2972311 is done amcleanup: pid 2972309 is done amcleanup: pid 2972305 is done amcleanup: no unprocessed logfile to clean up I also tested removing 'holdingdisk required' from the affected DLE but same result. Any ideas about what i should try? The logs don't seem to hold any more information (partial log from a RESULTS MISSING run): SENDING FLUSHES... Cleaning up holding disk '/dumps/' driver: adding holding disk 0 dir /dumps/ size 1949288448 chunksize 9007199254740896 ENDFLUSH SETTING UP FOR ESTIMATES... reserving 1949288448 out of 1949288448 for degraded-mode dumps driver: taper taper0 storage backup-storage tape_size 1499463680 driver: started dumper0 pid 2972312 driver: send-cmd time 0.001 to dumper0: START 20220416185052 planner: time 0.000: setting up estimates for localhost:storage driver: started dumper1 pid 2972313 driver: send-cmd time 0.001 to dumper1: START 20220416185052 setup_estimate: localhost:storage: command 0, options: none last_level 3 next_level0 14 level_days 1 getting estimates 0 (-3) 3 (-3) -1 (-3) planner: time 0.001: setting up estimates took 0.000 secs GETTING ESTIMATES... planner: find_est_for_dp return NULL driver: send-cmd time 0.001 to taper0: START-TAPER taper0 worker0-0 backup-storage 20220416185052 more about starting dumpers which never get used here until quitting. -Mail report 03:14 with drive off- Hostname: minerva Org : exuvo Config : backup Date : april 16, 2022 *** A TAPE ERROR OCCURRED: ['/dev/tape/by-id/scsi-DEC8320699' not found]. Some dumps may have been left in the holding disk. The next 2 tapes Amanda expects to use are: ROT09, ROT07. FAILURE DUMP SUMMARY: localhost efi lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost boot lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost root lev 1 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost storage lev 3 FAILED [can't dump required holdingdisk when no holdingdisk space available ] localhost backup-minerva lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost exuvo-desktop-root lev 1 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost backup lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] STATISTICS: Total Full Incr. Level:# 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.0 0.0 0.0 Original Size (meg) 0.0 0.0 0.
Re: DLE RESULTS MISSING after failed backup due to drive not being turned on
I have frequently done an "ls" on my holding disk, and manually deleted files and directories older than 7 days ago, which clearly amanda is not planning to flush to tape. 7 days because I ran amanda nightly. Your time window is up to you. I'm not sure 'amcleanup -rv backup' gets everything. I had an "onboot" job to send me email and remind me of that command, but perhaps I didn't reboot often, or perhaps amanda didn't register those files any more. If amanda hasn't flushed them during normal backups (assuming autoflush = ALL, i think it is), then it isn't planning to. Manual deletions never hurt my setup. If your holding disk isn't empty, but amanda sees nothing she wants to backup, then I suggest a manual cleanup. Deb Baddorf retired from Fermilab On Saturday, April 16, 2022, 01:27:15 PM EDT, Exuvo wrote: My backup failed tonight as i forgot to turn on my tape drive before i went to bed. Nothing was written to my dump drive as it was too full from a previous aborted backup i had done. When i woke up i turned on the tape drive and ran the backup again as i have done before when this has happend, most DLEs ran fine but the one DLE i have with 'holdingdisk required' failed as there was too little space left on the holding disk. I cleared out the holding disk and ran just that one failed DLE but it fails instantly and i get: FAILURE DUMP SUMMARY: planner: FATAL find_est_for_dp return NULL localhost storage RESULTS MISSING I tried running 'amcleanup -rv backup' but it did not do anything: # sudo -u amanda amcleanup -rv backup amcleanup: pid 2972312 is done amcleanup: pid 2972313 is done amcleanup: pid 2972311 is done amcleanup: pid 2972309 is done amcleanup: pid 2972305 is done amcleanup: no unprocessed logfile to clean up I also tested removing 'holdingdisk required' from the affected DLE but same result. Any ideas about what i should try? The logs don't seem to hold any more information (partial log from a RESULTS MISSING run): SENDING FLUSHES... Cleaning up holding disk '/dumps/' driver: adding holding disk 0 dir /dumps/ size 1949288448 chunksize 9007199254740896 ENDFLUSH SETTING UP FOR ESTIMATES... reserving 1949288448 out of 1949288448 for degraded-mode dumps driver: taper taper0 storage backup-storage tape_size 1499463680 driver: started dumper0 pid 2972312 driver: send-cmd time 0.001 to dumper0: START 20220416185052 planner: time 0.000: setting up estimates for localhost:storage driver: started dumper1 pid 2972313 driver: send-cmd time 0.001 to dumper1: START 20220416185052 setup_estimate: localhost:storage: command 0, options: none last_level 3 next_level0 14 level_days 1 getting estimates 0 (-3) 3 (-3) -1 (-3) planner: time 0.001: setting up estimates took 0.000 secs GETTING ESTIMATES... planner: find_est_for_dp return NULL driver: send-cmd time 0.001 to taper0: START-TAPER taper0 worker0-0 backup-storage 20220416185052 more about starting dumpers which never get used here until quitting. -Mail report 03:14 with drive off- Hostname: minerva Org : exuvo Config : backup Date : april 16, 2022 *** A TAPE ERROR OCCURRED: ['/dev/tape/by-id/scsi-DEC8320699' not found]. Some dumps may have been left in the holding disk. The next 2 tapes Amanda expects to use are: ROT09, ROT07. FAILURE DUMP SUMMARY: localhost efi lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost boot lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost root lev 1 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost storage lev 3 FAILED [can't dump required holdingdisk when no holdingdisk space available ] localhost backup-minerva lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost exuvo-desktop-root lev 1 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost backup lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] STATISTICS: Total Full Incr. Level:# 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.0 0.0 0.0 Original Size (meg) 0.0 0.0 0.0 Avg Compressed Size (%) -- -- -- DLEs Dumped 0 0 0 Avg Dump Rate (k/s) -- -- -- Tape Time (hrs:min) 0:00 0:00 0:00 Tape Size (meg) 0.0 0.0 0.0 Tape Used (%) 0.0 0.0 0.0 DLEs Taped 0 0 0 Parts Taped 0 0
DLE RESULTS MISSING after failed backup due to drive not being turned on
My backup failed tonight as i forgot to turn on my tape drive before i went to bed. Nothing was written to my dump drive as it was too full from a previous aborted backup i had done. When i woke up i turned on the tape drive and ran the backup again as i have done before when this has happend, most DLEs ran fine but the one DLE i have with 'holdingdisk required' failed as there was too little space left on the holding disk. I cleared out the holding disk and ran just that one failed DLE but it fails instantly and i get: FAILURE DUMP SUMMARY: planner: FATAL find_est_for_dp return NULL localhost storage RESULTS MISSING I tried running 'amcleanup -rv backup' but it did not do anything: # sudo -u amanda amcleanup -rv backup amcleanup: pid 2972312 is done amcleanup: pid 2972313 is done amcleanup: pid 2972311 is done amcleanup: pid 2972309 is done amcleanup: pid 2972305 is done amcleanup: no unprocessed logfile to clean up I also tested removing 'holdingdisk required' from the affected DLE but same result. Any ideas about what i should try? The logs don't seem to hold any more information (partial log from a RESULTS MISSING run): SENDING FLUSHES... Cleaning up holding disk '/dumps/' driver: adding holding disk 0 dir /dumps/ size 1949288448 chunksize 9007199254740896 ENDFLUSH SETTING UP FOR ESTIMATES... reserving 1949288448 out of 1949288448 for degraded-mode dumps driver: taper taper0 storage backup-storage tape_size 1499463680 driver: started dumper0 pid 2972312 driver: send-cmd time 0.001 to dumper0: START 20220416185052 planner: time 0.000: setting up estimates for localhost:storage driver: started dumper1 pid 2972313 driver: send-cmd time 0.001 to dumper1: START 20220416185052 setup_estimate: localhost:storage: command 0, options: none last_level 3 next_level0 14 level_days 1 getting estimates 0 (-3) 3 (-3) -1 (-3) planner: time 0.001: setting up estimates took 0.000 secs GETTING ESTIMATES... planner: find_est_for_dp return NULL driver: send-cmd time 0.001 to taper0: START-TAPER taper0 worker0-0 backup-storage 20220416185052 more about starting dumpers which never get used here until quitting. -Mail report 03:14 with drive off- Hostname: minerva Org : exuvo Config : backup Date : april 16, 2022 *** A TAPE ERROR OCCURRED: ['/dev/tape/by-id/scsi-DEC8320699' not found]. Some dumps may have been left in the holding disk. The next 2 tapes Amanda expects to use are: ROT09, ROT07. FAILURE DUMP SUMMARY: localhost efi lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost boot lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost root lev 1 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost storage lev 3 FAILED [can't dump required holdingdisk when no holdingdisk space available ] localhost backup-minerva lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost exuvo-desktop-root lev 1 FAILED [can't dump 'holdingdisk never' dle in degraded mode] localhost backup lev 0 FAILED [can't dump 'holdingdisk never' dle in degraded mode] STATISTICS: Total Full Incr. Level:# 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.0 0.0 0.0 Original Size (meg) 0.0 0.0 0.0 Avg Compressed Size (%) -- -- -- DLEs Dumped 0 0 0 Avg Dump Rate (k/s) -- -- -- Tape Time (hrs:min) 0:00 0:00 0:00 Tape Size (meg) 0.0 0.0 0.0 Tape Used (%) 0.0 0.0 0.0 DLEs Taped 0 0 0 Parts Taped 0 0 0 Avg Tp Write Rate (k/s) -- -- -- NOTES: planner: Last full dump of localhost:efi on tape ROT05 overwritten in 4 runs. planner: Last full dump of localhost:boot on tape ROT05 overwritten in 4 runs. planner: Last full dump of localhost:root on tape ROT05 overwritten in 4 runs. planner: Last full dump of localhost:storage on tape ROT04 overwritten in 3 runs. planner: Last full dump of localhost:backup-minerva on tape ROT03 overwritten in 3 runs. planner: Last full dump of localhost:exuvo-desktop-root on tape ROT08 overwritten in 2 runs. planner: Last full dump of localhost:backup on tape ROT03 overwritten in 3 runs. planner: Full dump of localhost:backup-minerva promoted from 14 days ahead. planner: Full dump of localhost:boot promoted from 22 days ahead. planner: Full dump of localhost:efi promoted from 22 days ahead. planner: Full dump of localh
RESULTS MISSING on all DLE when only one estimate fails?
Hallo! I've installed Amanda 3.3.3 on a Centos server. Sometimes backups are failing with "RESULTS MISSING" and "driver: WARNING: got empty schedule from planner". I think this is mostly because of estimate timeouts. I see "planner: ERROR Some estimate timeout on a.example.com, using server estimate if possible". Thats something I can handle. But why do I get "RESULTS MISSING" for all hosts/DLE and "... empty schedule ..." when only one estimate fails? There are planner/estimate results from all my DLE, except one, in the logs. Shouldn't the amanda planner return a schedule without the failing DLE? Thanks! Matthias
results missing
I finally got past the gnutar problem I was having. I ran amcheck and
everything looked good, but amdump gives me a bunch of results missing
errors (even for hosts that worked fine before). Attached is the output
from amdump.
Thanks,
Steve
*** THE DUMPS DID NOT FINISH PROPERLY!
These dumps were to tape VOL24.
The next tape Amanda expects to use is: VOL01.
FAILURE AND STRANGE DUMP SUMMARY:
helios.medsci.domain /var lev 2 STRANGE
snapserver.medsci.domain /hd/vol_mnt0/shares/biochem lev 1 FAILED
[data write: Broken pipe]
wagstaff.asel.domain /usr/local lev 1 FAILED
[data write: Connection reset by peer]
helios.medsci.domain /usr/local RESULTS MISSING
lollipop.asel.domain /files1 RESULTS MISSING
wagstaff.asel.domain /RESULTS MISSING
wagstaff.asel.domain /files1 RESULTS MISSING
wagstaff.asel.domain /files3 RESULTS MISSING
wagstaff.asel.domain /files4 RESULTS MISSING
wagstaff.asel.domain /files5 RESULTS MISSING
wagstaff.asel.domain /files6/vol/SynthRESULTS MISSING
wagstaff.asel.domain /files6/vol/VoicewareRESULTS MISSING
wagstaff.asel.domain /files6/vol/bvd RESULTS MISSING
wagstaff.asel.domain /files6/vol/spdata1 RESULTS MISSING
wagstaff.asel.domain /files6/vol/spdata2 RESULTS MISSING
wagstaff.asel.domain /files6/vol/speech7 RESULTS MISSING
wagstaff.asel.domain /usr RESULTS MISSING
wizard.asel.domain/var/mailRESULTS MISSING
wizard.asel.domain/files2 RESULTS MISSING
snapserver.medsci.domain /hd/vol_mnt0/shares/bcl RESULTS MISSING
driver: FATAL Don't know how to send ABORT command to chunker
chunker: FATAL error [bad command after RQ-MORE-DISK: "QUIT"]
chunker: FATAL error [bad command after RQ-MORE-DISK: "QUIT"]
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min)0:10
Run Time (hrs:min) 0:14
Dump Time (hrs:min)0:14 0:00 0:14
Output Size (meg) 765.70.0 765.7
Original Size (meg) 1948.10.0 1948.1
Avg Compressed Size (%)39.3--39.3 (level:#disks ...)
Filesystems Dumped 36 0 36 (1:35 2:1)
Avg Dump Rate (k/s) 966.6-- 966.6
Tape Time (hrs:min)0:04 0:00 0:04
Tape Size (meg) 767.70.0 767.7
Tape Used (%) 2.10.02.1 (level:#disks ...)
Filesystems Taped36 0 36 (1:35 2:1)
(level:#chunks ...)
Chunks Taped 36 0 36 (1:35 2:1)
Avg Tp Write Rate (k/s) 3038.4-- 3038.4
USAGE BY TAPE:
Label Time Size %NbNc
VOL24 0:04 786080k2.13636
FAILED AND STRANGE DUMP DETAILS:
/-- helios.medsci.domain /var lev 2 STRANGE
sendbackup: start [helios.medsci.domain:/var level 2]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar:
./lib/amanda/asel/index/professor.asel.domain/_usr_local/20061026_1.gz.tmp:
Warning: Cannot stat: No such file or directory
? gtar:
./lib/amanda/asel/index/snapserver.medsci.domain/_hd_vol__mnt0_shares_NeuroGen/20061026_1.gz.tmp:
Warning: Cannot stat: No such file or directory
| gtar: ./run/postgresql/.s.PGSQL.5432: socket ignored
| Total bytes written: 1115033600 (1.1GiB, 6.5MiB/s)
sendbackup: size 1088900
sendbackup: end
\
/-- snapserver.medsci.domain /hd/vol_mnt0/shares/biochem lev 1 FAILED
[data write: Broken pipe]
sendbackup: start [snapserver.medsci.domain:/hd/vol_mnt0/shares/biochem
level 1]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
\
/-- wagstaff.asel.domain /usr/local lev 1 FAILED [data write:
Connection reset by peer]
sendbackup: start [wagstaff.asel.domain:/usr/local level 1]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc
|/usr/sbin/ufsrestore -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| DUMP: Writing 32 Kilobyte records
| DUMP: Date of this level 1 dump: Thu Oct 26 23:55:10 2006
| DUMP: Date of last level 0 dump: Mon Oct 23 23:55:43 2006
| DUMP: Dumping /dev/rdsk/c0t0d0s7 (wagstaff:/usr/local) to standard
output.
| DUMP: Mapping (Pass I) [regular files]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Mapping (Pass II) [directories]
| DUMP: Mapping (Pass II) [directories]
|
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 * ***
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?
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
Dump results missing from report?
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. George
amandad still running/ RESULTS MISSING
I am having a problem with amanda whereby some of the dumps (DLE's on the amanda server itself) are showing as RESULTS MISSING in the logs. There is an amandad process which is still running after quite a long time (24 hours) and which has a defunct child process: backup3318 0.0 0.1 3044 1076 ?SMay26 0:00 amandad backup3320 0.0 0.0 00 ?ZMay26 0:00 [amandad ] I googled the RESULTS MISSING error and checked that the appropriate files have SUID set and that the entries in inetd are right (they have not been changed). The only change that I have made in the last couple days is to add a DLE on a remote system (which already had other DLE's being backed up). Anyone have a clue for me? TIA, Vicki
Re: [RESULTS MISSING]
Daniel García wrote: Amanda has send this report today, and i don't know if the backup of the disk is done ok. svrbackup //svrficheros/usr RESULTS MISSING svrbackup //svrcitrixs/YagoMir RESULTS MISSING svrbackup //svrcitrixs/carto RESULTS MISSING It means there were no results, not even a backup, for these entries. I bet in the same report there are also other messages about these same entries that can shed some light why there were no results. (amanda configured for samba? username/password in /etc/amandapass? etc.) -- 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 * ***
Re: `RESULTS MISSING' error
On Thu, 29 Jul 2004, Geert Uytterhoeven wrote:
> But amdump itself still fails:
>
> | *** THE DUMPS DID NOT FINISH PROPERLY!
> |
> | The next tape Amanda expects to use is: a new tape.
> | The next new tape already labelled is: DAILY01.
> |
> | FAILURE AND STRANGE DUMP SUMMARY:
> | driver: FATAL reading result from taper: Connection reset by peer
> | anakin sda5 RESULTS MISSING
I found the cause of the problem: apparently Debian's cdrw-taper package
contains a syntax error in the supplied config file, causing Amanda to fail.
Bug submitted and my complete bug report is available at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=263760
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Re: `RESULTS MISSING' error
On Tue, 13 Jul 2004, Geert Uytterhoeven wrote:
> I'm trying to make Amanda backup my home network (several Linux machines) to
> disk. My first plan is to specify a non-existent tape drive (I don't have a
> tape drive anymore), and just copy the archives from the holding disk to a
> remote disk.
>
> However, I always (for both local and remote disks) get the following error
> (after the missing tape error, of course):
>
> anakin sda5 RESULTS MISSING
>
> I started from the amanda.conf I used to backup to DDS tape some years ago, so
> I'm quite sure it's not a problem with the config file. Basically I just added
> `reserve 20'. Am I missing something?
>
> If needed, I can tar-up /tmp/amanda/.
>
> Or should I use the `file' output driver? It seems to be less flexible to me.
So I tried the `file' output driver and `chg-disk', using 8 virtual tapes...
| tpchanger "chg-disk"
| changerfile "/etc/amanda/DailySet1/changer"
| tapedev "file:/scratch/amanda/DailySet1"
| tapetype HARD-DISK
| labelstr "DAILY[0-9][0-9]*$"# label constraint regex: all tapes must match
Labeling the tapes (8 tapes) worked fine.
Amcheck runs fine:
| # su - backup amcheck DailySet1
| Amanda Tape Server Host Check
| -
| amcheck-server: slot 8: date Xlabel DAILY08 (new tape)
| NOTE: skipping tape-writable test
| Tape DAILY08 label ok
| NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist
| NOTE: it will be created on the next run
| NOTE: index dir /var/lib/amanda/DailySet1/index/anakin: does not exist
| Server check took 0.217 seconds
|
| Amanda Backup Client Hosts Check
|
| Client check: 1 host checked in 0.178 seconds, 0 problems found
|
| (brought to you by Amanda 2.4.4p2)
| #
But amdump itself still fails:
| *** THE DUMPS DID NOT FINISH PROPERLY!
|
| The next tape Amanda expects to use is: a new tape.
| The next new tape already labelled is: DAILY01.
|
| FAILURE AND STRANGE DUMP SUMMARY:
| driver: FATAL reading result from taper: Connection reset by peer
| anakin sda5 RESULTS MISSING
|
|
| STATISTICS:
| Total Full Daily
|
| Estimate Time (hrs:min)0:00
| Run Time (hrs:min) 0:00
| 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
| Avg Tp Write Rate (k/s) -- -- --
|
| ?
| NOTES:
| planner: Adding new disk anakin:sda5.
|
| ?
| DUMP SUMMARY:
| DUMPER STATSTAPER STATS
| HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
| -- -
| anakin sda5 MISSING --
|
| (brought to you by Amanda version 2.4.4p2)
I can send the contents of /tmp/amanda/* if you need them, but I didn't see
anything fishy there.
Anyone with a clue? Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
`RESULTS MISSING' error
Hi,
I'm trying to make Amanda backup my home network (several Linux machines) to
disk. My first plan is to specify a non-existent tape drive (I don't have a
tape drive anymore), and just copy the archives from the holding disk to a
remote disk.
However, I always (for both local and remote disks) get the following error
(after the missing tape error, of course):
anakin sda5 RESULTS MISSING
I started from the amanda.conf I used to backup to DDS tape some years ago, so
I'm quite sure it's not a problem with the config file. Basically I just added
`reserve 20'. Am I missing something?
If needed, I can tar-up /tmp/amanda/.
Or should I use the `file' output driver? It seems to be less flexible to me.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
[RESULTS MISSING]
Hi, Amanda has send this report today, and i don't know if the backup of the disk is done ok. svrbackup //svrficheros/usr RESULTS MISSING svrbackup //svrcitrixs/YagoMir RESULTS MISSING svrbackup //svrcitrixs/carto RESULTS MISSING What mean those errors. Thank you! -- Daniel García Franco e-mail: [EMAIL PROTECTED] SADIEL, S.A. C\ Isaac Newton s/n, Edificio Sadiel, Isla de la Cartuja C.P. 41002 SEVILLA Tlf: +34 955043600 (83736) Fax: 955043601 http://www.sadiel.es e-mail: [EMAIL PROTECTED]
RE: New client to Amanda dump returns "RESULTS MISSING"???
Thanks! I actually just fixed it. There were many weird things about this setup. I found it installed in different locations and different versions of the source files. Yesterday I thought I completely uninstalled everything and found that the reports said same thing this morning. So what I did then was searched for every damn (excuse my French) Amanda Makefile (locate amanda | grep Makefile | more) and CD'd to there and did a make uninstall. I found that a few actually took the uninstall. Once I did that I edited the "inted" file to disable any amanda stuff, rebooted and found no more messages or anything. Then I was able to install the latest version (amanda-2.4.4.tar) with user=amanda group=backup, --- ./configure --without-server --with-user=amanda --with-group=backup make make install --- edited & restarted inetd. Still came up with an issue and what appears to have fixed it was checking/setting the permissions for amanda as owner for all relevant amanda directories. Mainly "/tmp/amanda" was owned by someone other than amanda. `amcheck` returns no errors now from the backup server!!! Here's the selfcheck debug file on the client: - /usr/local/libexec/selfcheck: version 2.4.4 selfcheck: time 0.001: checking disk /dev/da0s1e selfcheck: time 0.001: device /dev/da0s1e selfcheck: time 0.001: disk "/dev/da0s1e" OK selfcheck: time 0.001: amdevice "/dev/da0s1e" OK selfcheck: time 0.001: device "/dev/da0s1e" OK selfcheck: time 0.001: checking disk /dev/da0s1a selfcheck: time 0.001: device /dev/da0s1a selfcheck: time 0.001: disk "/dev/da0s1a" OK selfcheck: time 0.001: amdevice "/dev/da0s1a" OK selfcheck: time 0.001: device "/dev/da0s1a" OK selfcheck: time 0.001: pid 247 finish time Wed May 28 10:15:27 2003 - Wooo-hooo!!! We should see no errors tomorrow morning!!! I appreciate your help guys, and will definitely look into FreeBSD ports installs Toomas for any future needs. -Regards, Gibran Marquez * I hear if you play the Windows XP CD backward you'll hear satanic messages. But even scarier, if you play it forward it installs Windows XP!! -Original Message- From: Toomas Aas [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 28, 2003 11:15 AM To: Gibran Marquez; [EMAIL PROTECTED] Subject: RE: New client to Amanda dump returns "RESULTS MISSING"??? Hi! > Is there an easy way to "UNINSTALL" Amanda? I need to do this because well > first of all this isn't a server anymore and it was set up as user > "operator", and all my other clients are using "amanda" user. > > I'd like to completely uninstall everything server/client and then install a > new version (amanda-client-2.4.3-4) with user as "amanda". If the existing version was installed from FreeBSD ports, you can do something like this to uninstall it: pkg_delete amanda-client-2.4.3b2 pkg_delete amanda-server-2.4.3b2 Then update your ports tree (see the FreeBSD handbook for details) And then... cd /usr/ports/misc/amanda-client make AMANDA_USER=amanda AMANDA_GROUP=backup install I know everyone here recommends that you get the latest source tarball and build Amanda yourself from that, but the FreeBSD ports have worked really well for me, FWIW.
RE: New client to Amanda dump returns "RESULTS MISSING"???
Hi! > Is there an easy way to "UNINSTALL" Amanda? I need to do this because well > first of all this isn't a server anymore and it was set up as user > "operator", and all my other clients are using "amanda" user. > > I'd like to completely uninstall everything server/client and then install a > new version (amanda-client-2.4.3-4) with user as "amanda". If the existing version was installed from FreeBSD ports, you can do something like this to uninstall it: pkg_delete amanda-client-2.4.3b2 pkg_delete amanda-server-2.4.3b2 Then update your ports tree (see the FreeBSD handbook for details) And then... cd /usr/ports/misc/amanda-client make AMANDA_USER=amanda AMANDA_GROUP=backup install I know everyone here recommends that you get the latest source tarball and build Amanda yourself from that, but the FreeBSD ports have worked really well for me, FWIW.
RE: New client to Amanda dump returns "RESULTS MISSING"???
Yeah I kind of figured it was going to turn out to be something like this. Seems to actually be on the client side. What I found is that this FreeBSD system had a previous version of Amanda, both server and client packages. (amanda-2.4.3b2 beta???) Is there an easy way to "UNINSTALL" Amanda? I need to do this because well first of all this isn't a server anymore and it was set up as user "operator", and all my other clients are using "amanda" user. I'd like to completely uninstall everything server/client and then install a new version (amanda-client-2.4.3-4) with user as "amanda". Any suggestions, recommendations??? -Regards, Gibran Marquez -Original Message- From: Martin, Jeremy [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2003 10:58 AM To: Gibran Marquez Subject: RE: New client to Amanda dump returns "RESULTS MISSING"??? > From: Gibran Marquez [mailto:[EMAIL PROTECTED] > > Any reason why Amanda is stating that the results are missing > for newly > added client. This client is probably my only FreeBSD so far > to disklist. I > did a df on tgs-1 (client) and added file systems I wanted, > next I added them to config disklist. > > However, I'm receiving errors for dump on this client. > > FAILURE AND STRANGE DUMP SUMMARY: > tgs-1 /dev/da0s1a RESULTS MISSING > tgs-1 /dev/da0s1e RESULTS MISSING I'm no amanda expert, but are you sure you're not getting any amandahostsauth failed messages? I was getting a bunch of RESULTS MISSING messages when my client wasn't allowing the server to connect: FAILURE AND STRANGE DUMP SUMMARY: planner: ERROR jayhawker: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed jayhawker /var RESULTS MISSING
New client to Amanda dump returns "RESULTS MISSING"???
Any reason why Amanda is stating that the results are missing for newly added client. This client is probably my only FreeBSD so far to disklist. I did a df on tgs-1 (client) and added file systems I wanted, next I added them to config disklist. Tgs: df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/da0s1a 1016303 253749 68125027%/ /dev/da0s1e 33172783 24711907 580705481%/usr Amanda backup server config disklist: tgs-1 /dev/da0s1a comp-user tgs-1 /dev/da0s1e comp-user However, I'm receiving errors for dump on this client. FAILURE AND STRANGE DUMP SUMMARY: tgs-1 /dev/da0s1a RESULTS MISSING tgs-1 /dev/da0s1e RESULTS MISSING DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - qadb /dev/hda2 0 1322320 344512 26.1 3:251678.5 1:204293.3 qadist /dev/hda2 0 880660 287104 32.6 2:561626.5 1:044480.4 qaweb/dev/hdc2 0 1145490 318432 27.8 3:131645.4 1:154264.0 stagingall /dev/hda2 0 947830 315520 33.3 3:061699.3 1:104503.9 tgs-1/dev/da0s1a MISSING -- tgs-1/dev/da0s1e MISSING -- -Regards, Gibran Marquez * "Documentation? The code is the documentation!"
re: results missing
Hello again. i accidently deleted the previous answer to my question and therefore did a little research myself, as i forgot what conf files you asked for. The conclusion is that i found out my inetd.conf was not configured correctly to run amanda client on the server itself. once i restored old inetd.conf also, all problems disappeared. So, another reason for RESULTS MISSING has popped up. Laas Toom
Re: results missing
Laas Toom wrote: Now amanda backs up only the freebsd workstations, but for all samba shares amanda says: RESULTS MISSING. We need more information (like the /tmp/amanda/* debug files), but one thing that comes to mind is, have you restored the /etc/amandapass file on your samba client host (the one that backs up the windows share). Another strange thing happened when i moved one of my freebsd servers filesystems from a ccd too small to a bigger ccd device (everything is the same, exept the /etc/fstab row that mounts the filesystem). Now amanda says the disk is offline. Again we need more information. What do you specify in your disklist? A device or a mount point? The exact cause is probably found in an error message in the /tmp/amanda/* debug files. BTW what is a "ccd"? I'm not a freebsd user. -- 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 * ***
results missing
Hello, I use amanda to back up my whole site: freebsd workstations as well as windows samba shares. recently my backup server chrashed and i had to reinstall the operatingsystem (in the way upgrading it from freebsd 4.6 to 4.7). After what i copied amanda config files to the locations they were before crash (the index files survived). Now amanda backs up only the freebsd workstations, but for all samba shares amanda says: RESULTS MISSING. What is the problem? How can i eliminate it? The Amanda Faq-o-matic did not help, because i know the system worked before, so i do not need to make any alters to my filesystems or catalog tree. Another strange thing happened when i moved one of my freebsd servers filesystems from a ccd too small to a bigger ccd device (everything is the same, exept the /etc/fstab row that mounts the filesystem). Now amanda says the disk is offline. Thanks in advance, Laas Toom
Re: results missing
Hi! I guess, the problem kinda solved itself, amanda just didn't like the dumptype always-full Konni
Re: results missing
Hello Josh. Here is the output of the debug file /tmp/amanda/amandad.20030226103633.debug: amandad: debug 1 pid 30977 ruid euid : start at Wed Feb 26 10:36:33 200 3 amandad: version 2.4.3 amandad: build: VERSION="Amanda-2.4.3" amandad:BUILT_DATE="Sat Jan 25 19:50:43 GMT 2003" amandad:BUILT_MACH="FreeBSD gohan15.freebsd.org 4.7-STABLE FreeBSD 4.7-S TABLE #0: Sun Apr 1 02:34:56 PST 2002 [EMAIL PROTECTED]:/usr/src/sys/compi le/BENTO i386" amandad:CC="cc" amandad:CONFIGURE_COMMAND="'./configure' '--libexecdir=/usr/local/libexe c/amanda' '--with-amandahosts' '--with-fqdn' '--with-dump-honor-nodump' '--with- buffered-dump' '--without-server' '--disable-libtool' '--prefix=/usr/local' '--w ith-gnutar=/usr/local/bin/gtar' '--with-user=operator' '--with-group=operator'" amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" amandad:libexecdir="/usr/local/libexec/amanda" amandad:mandir="/usr/local/man" AMANDA_TMPDIR="/tmp/amanda" amandad:AMANDA_DBGDIR="/tmp/amanda" amandad:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/" amandad:RDEV_PREFIX="/dev/r" DUMP="/sbin/dump" amandad:RESTORE="/sbin/restore" GNUTAR="/usr/local/bin/gtar" amandad:COMPRESS_PATH="/usr/bin/gzip" amandad:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail" amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="gohan15.freebsd.org" amandad:DEFAULT_CONFIG="DailySet1" amandad:DEFAULT_TAPE_SERVER="gohan15.freebsd.org" amandad:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL DEBUG_CODE AMANDA_DEBUG_DAYS=4 amandad:BSD_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN="operator" amandad:FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=".gz" amandad:COMPRESS_FAST_OPT="--fast" COMPRESS_BEST_OPT="--best" amandad:UNCOMPRESS_OPT="-dc" amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 000-00850708 SEQ 1046252193 SECURITY USER amanda SERVICE noop OPTIONS features=feff9f00; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 000-00850708 SEQ 1046252193 amandad: time 0.000: bsd security: remote host altair.wirecard.com user amanda l ocal user amanda amandad: time 0.000: amandahosts security check passed amandad: time 0.000: running service "noop" amandad: time 0.034: sending REP packet: Amanda 2.4 REP HANDLE 000-00850708 SEQ 1046252193 OPTIONS features=feff9f00; amandad: time 0.034: got packet: Amanda 2.4 ACK HANDLE 000-00850708 SEQ 1046252193 The other files do not exist The system is a freebsd 4.7 server trying to backup itself.
Re: results missing
On Tue, 25 Feb 2003 at 6:47pm, Konrad Dienst wrote > FAILURE AND STRANGE DUMP SUMMARY: > altair.wir aacd0s1f RESULTS MISSING *snip* > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > -- - > altair.wirec aacd0s1f MISSING -- > > (brought to you by Amanda version 2.4.3) To really be able to look this, we'll need to know the client OS and see the contents of /tmp/amanda/amandad*debug (and /tmp/amanda/sendsize*debug and /tmp/amanda/sendbackup*debug if they exist) on the client. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
results missing
Hi!
does anybody know, what this is supposed to mean? (amcheck doesn't come
up with any errors)
Subject: test AMANDA MAIL REPORT FOR BogusMonth 0, 0
*** THE DUMPS DID NOT FINISH PROPERLY!
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
altair.wir aacd0s1f RESULTS MISSING
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
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
Avg Tp Write Rate (k/s) -- -- --
^L
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
altair.wirec aacd0s1f MISSING --
(brought to you by Amanda version 2.4.3)
Re: amanda 2.4.3 RESULTS MISSING
Oh yes, the "refuses to mail report" thing. I've had it too.
Have no idea *why* but the only fix I've heard about
works for me, too.
Fix: remove thelbl-temp line from your configuration.
The report should get emailed OK now. Tomorrow you
can probably put the line back in, and it will be okay
for a while.
Maybe this "fix" can prompt an actual developer to recognize
what it causing this?
Deb Baddorf
And what is funnier: I forgot changing the tape yesterday, so I have had to
run amflush, and the report DID get the results:
---
Subject: AMFLUSH MAIL REPORT FOR January 15, 2003
Date: Wed, 15 Jan 2003 12:04:55 +0100
The dumps were flushed to tape PRMD-002.
The next tape Amanda expects to use is: a new tape.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:01
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.20.00.2
Tape Used (%) 0.00.00.0 (level:#disks ...)
Filesystems Taped 2 0 2 (1:2)
Avg Tp Write Rate (k/s)22.0--22.0
NOTES:
taper: tape PRMD-002 kb 160 fm 2 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
prmb /etc1 260 96 36.9 N/A N/A0:05 18.3
prmb -ias/enfrio 1 10 64 640.0 N/A N/A0:02 31.2
(brought to you by Amanda version 2.4.3)
---
Why amreport invoked by amdump fails to collect the stats and
invoked by amflush does not?
Sergio
---
Deb Baddorf [EMAIL PROTECTED] 840-2289
"You can't help getting older, but you don't have to get old."
- George Burns <
Re: amanda 2.4.3 RESULTS MISSING
On Wednesday 15 January 2003 07:24, Sergio G. Reus wrote: >Tue, 14 Jan 2003 13:09:38 -0500 Gene Heskett <[EMAIL PROTECTED]>: >> Mmm, one question: >> >> Have you more than one installed version of amanda? >> >> The reason I ask is that the normal amanda ./configuration will >> put stuff in /usr/local, but the rpm install like from redhat, >> puts it in /usr. > >No, I configure it with --prefix=/opt/amanda, so there is no > posibility of file shuffling. Well, if locate says your system is clean of older stuff, then that was my best shot at it. You did unpack, configure and make amanda as the user amanda, and install as root I assume, so there shouldn't be any permissions problems. I'll have to leave this one to the real experts, I just play one occasionally. :-) >> Get the latest version of amanda from Jean-Louis's site at >> umontreal, link near the bottom of the amanda.org web page, and >> check the ChangeLog, you might find something related there. >> Since thats the Jan 4th issue when I last looked last night, and >> I've been running that one since the 5th with no problems, you >> might even build and install it. > >I've tried with 2.4.2p2, 2.4.3 stable, 2.4.3-20030104 and > 2.5.0-20030104. All produce the same amreport results. >Searching through the code of reporter.c I don't see any function >more complex than strcmp(), so what is different in my system? (I > don't think strcmp can be somehow corrupt). > >And what is funnier: I forgot changing the tape yesterday, so I > have had to run amflush, and the report DID get the results: > >-- >- Subject: AMFLUSH MAIL REPORT FOR January 15, 2003 >Date: Wed, 15 Jan 2003 12:04:55 +0100 > >The dumps were flushed to tape PRMD-002. >The next tape Amanda expects to use is: a new tape. > > >STATISTICS: > Total Full Daily > >Estimate Time (hrs:min)0:00 >Run Time (hrs:min) 0:01 >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.20.00.2 >Tape Used (%) 0.00.00.0 > (level:#disks ...) Filesystems Taped 2 0 > 2 (1:2) Avg Tp Write Rate (k/s)22.0-- > 22.0 > > >NOTES: > taper: tape PRMD-002 kb 160 fm 2 [OK] > > >DUMP SUMMARY: > DUMPER STATSTAPER > STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS > KB/s MMM:SS KB/s -- > - prmb /etc > 1 260 96 36.9 N/A N/A0:05 18.3 prmb > -ias/enfrio 1 10 64 640.0 N/A N/A0:02 31.2 > >(brought to you by Amanda version 2.4.3) >-- >- > >Why amreport invoked by amdump fails to collect the stats and >invoked by amflush does not? > >Sergio > > >[This E-mail scanned for viruses by Declude Virus] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.22% setiathome rank, not too shabby for a WV hillbilly
Re: amanda 2.4.3 RESULTS MISSING
Tue, 14 Jan 2003 13:09:38 -0500 Gene Heskett <[EMAIL PROTECTED]>:
> Mmm, one question:
>
> Have you more than one installed version of amanda?
>
> The reason I ask is that the normal amanda ./configuration will put
> stuff in /usr/local, but the rpm install like from redhat, puts it
> in /usr.
No, I configure it with --prefix=/opt/amanda, so there is no posibility of
file shuffling.
>
> Get the latest version of amanda from Jean-Louis's site at
> umontreal, link near the bottom of the amanda.org web page, and
> check the ChangeLog, you might find something related there.
> Since thats the Jan 4th issue when I last looked last night, and
> I've been running that one since the 5th with no problems, you
> might even build and install it.
I've tried with 2.4.2p2, 2.4.3 stable, 2.4.3-20030104 and 2.5.0-20030104.
All produce the same amreport results.
Searching through the code of reporter.c I don't see any function
more complex than strcmp(), so what is different in my system? (I don't
think strcmp can be somehow corrupt).
And what is funnier: I forgot changing the tape yesterday, so I have had to
run amflush, and the report DID get the results:
---
Subject: AMFLUSH MAIL REPORT FOR January 15, 2003
Date: Wed, 15 Jan 2003 12:04:55 +0100
The dumps were flushed to tape PRMD-002.
The next tape Amanda expects to use is: a new tape.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:01
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.20.00.2
Tape Used (%) 0.00.00.0 (level:#disks ...)
Filesystems Taped 2 0 2 (1:2)
Avg Tp Write Rate (k/s)22.0--22.0
NOTES:
taper: tape PRMD-002 kb 160 fm 2 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
prmb /etc1 260 96 36.9 N/A N/A0:05 18.3
prmb -ias/enfrio 1 10 64 640.0 N/A N/A0:02 31.2
(brought to you by Amanda version 2.4.3)
---
Why amreport invoked by amdump fails to collect the stats and
invoked by amflush does not?
Sergio
Re: amanda 2.4.3 RESULTS MISSING
On Tue, Jan 14, 2003 at 05:10:35PM +0100, Sergio G. Reus wrote:
> >
> > If the log file looks ok, does
> >
> > amreport -l -f
> >
> > generate a more reasonable report in , or is it the
> > same report that was mailed to you after the amdump. If the
>
> You are right, amreport is not reading the logs properly. When I
> execute:
>
> amreport PRMCompleta -l log -f /tmp/rep.txt
>
> I get the same report than in the mail, and the following errors in the
> standard output:
>
> line 8 of log is bogus
> line 9 of log is bogus
> line 10 of log is bogus
> line 11 of log is bogus
>
> Just the "SUCCESS" lines. But the log file is correct. Judge yourself:
Both my 2.4.2 and 2.4.3 amreports worked fine on the data you supplied.
Guess you have to look into YOUR build of amreport.
Here is a copy of the report just FYI.
To: [EMAIL PROTECTED]
Subject: Portal Regional de Murcia AMANDA MAIL REPORT FOR January 14, 2003
These dumps were to tape PRMD-000.
The next tape Amanda expects to use is: a new tape.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:03
Dump Time (hrs:min)0:02 0:02 0:00
Output Size (meg) 150.2 150.20.0
Original Size (meg) 1407.3 1407.30.0
Avg Compressed Size (%)10.7 10.7--
Filesystems Dumped2 2 0
Avg Dump Rate (k/s) 1591.9 1591.9--
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 150.2 150.20.0
Tape Used (%) 0.10.10.0
Filesystems Taped 2 2 0
Avg Tp Write Rate (k/s) 9852.9 9852.9--
NOTES:
planner: Adding new disk prmb:/etc.
planner: Adding new disk prmb:/u04/copias/enfrio.
taper: tape PRMD-000 kb 153824 fm 2 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
prmb /etc02590480 18.5 0:01 644.1 0:01 405.7
prmb -ias/enfrio 0 1438450 153344 10.7 1:361598.7 0:1410627.2
(brought to you by Amanda version 2.4.3b4)
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amanda 2.4.3 RESULTS MISSING
On Tuesday 14 January 2003 11:10, Sergio G. Reus wrote:
>> If the log file looks ok, does
>>
>> amreport -l -f
>>
>> generate a more reasonable report in , or is it the
>> same report that was mailed to you after the amdump. If the
>> latter, then probably something is wrong with your amreport.
>> Send me a note with your log file attached and I'll see if
>> the amreport's I have here (both 2.42 and 2.4.3) produce the
>> same or different results as your amreport. Also attach your
>> config file.
>>
>> jon
>
>You are right, amreport is not reading the logs properly. When I
>execute:
>
> amreport PRMCompleta -l log -f /tmp/rep.txt
>
>I get the same report than in the mail, and the following errors
> in the standard output:
>
>line 8 of log is bogus
>line 9 of log is bogus
>line 10 of log is bogus
>line 11 of log is bogus
>
>Just the "SUCCESS" lines. But the log file is correct. Judge
> yourself:
>
>START driver date 20030114
>START planner date 20030114
>INFO planner Adding new disk prmb:/etc.
>INFO planner Adding new disk prmb:/u04/copias/enfrio.
>FINISH planner date 20030114
>STATS driver startup time 0.557
>START taper datestamp 20030114 label PRMD-000 tape 0
>SUCCESS dumper prmb /etc 20030114 0 [sec 0.695 kb 448 kps 644.1
> orig-kb 2590] SUCCESS taper prmb /etc 20030114 0 [sec 1.183 kb
> 480 kps 405.7 {wr: writers 15 rdwait 0.000 wrwait 0.023 filemark
> 1.159}] SUCCESS dumper prmb /u04/copias/enfrio 20030114 0 [sec
> 95.896 kb 153312 kps 1598.7 orig-kb 1438450] SUCCESS taper prmb
> /u04/copias/enfrio 20030114 0 [sec 14.429 kb 153344 kps 10627.2
> {wr: writers 4792 rdwait 1.103 wrwait 12.515 filemark 0.760}]
> INFO taper tape PRMD-000 kb 153824 fm 2 [OK]
>FINISH driver date 20030114 time 150.796
>
>I also attatch the config file. Now I'm browsing the reporter.c
> source code, although I hope someone can give an easier solution.
>
>Thanks in advance,
>
>Sergio
Mmm, one question:
Have you more than one installed version of amanda?
The reason I ask is that the normal amanda ./configuration will put
stuff in /usr/local, but the rpm install like from redhat, puts it
in /usr.
Since /usr/local is usually the later thing in the $PATH, the old
stuff might be being found first. Just a thought. Locate will
tell that tale easily enough.
Get the latest version of amanda from Jean-Louis's site at
umontreal, link near the bottom of the amanda.org web page, and
check the ChangeLog, you might find something related there.
Since thats the Jan 4th issue when I last looked last night, and
I've been running that one since the 5th with no problems, you
might even build and install it.
I long ago commited all the ./configuration options to a script so I
can install the new one exactly like the older one I'm overwriting.
I recommend this practice because it protects you from forgetting
what options you gave it the last time you built it. Old coots
like me need all the help in that dept. we can get. :-)
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Re: amanda 2.4.3 RESULTS MISSING
>
> If the log file looks ok, does
>
> amreport -l -f
>
> generate a more reasonable report in , or is it the
> same report that was mailed to you after the amdump. If the
> latter, then probably something is wrong with your amreport.
> Send me a note with your log file attached and I'll see if
> the amreport's I have here (both 2.42 and 2.4.3) produce the
> same or different results as your amreport. Also attach your
> config file.
>
> jon
You are right, amreport is not reading the logs properly. When I
execute:
amreport PRMCompleta -l log -f /tmp/rep.txt
I get the same report than in the mail, and the following errors in the
standard output:
line 8 of log is bogus
line 9 of log is bogus
line 10 of log is bogus
line 11 of log is bogus
Just the "SUCCESS" lines. But the log file is correct. Judge yourself:
START driver date 20030114
START planner date 20030114
INFO planner Adding new disk prmb:/etc.
INFO planner Adding new disk prmb:/u04/copias/enfrio.
FINISH planner date 20030114
STATS driver startup time 0.557
START taper datestamp 20030114 label PRMD-000 tape 0
SUCCESS dumper prmb /etc 20030114 0 [sec 0.695 kb 448 kps 644.1 orig-kb 2590]
SUCCESS taper prmb /etc 20030114 0 [sec 1.183 kb 480 kps 405.7 {wr: writers 15 rdwait
0.000 wrwait 0.023 filemark 1.159}]
SUCCESS dumper prmb /u04/copias/enfrio 20030114 0 [sec 95.896 kb 153312 kps 1598.7
orig-kb 1438450]
SUCCESS taper prmb /u04/copias/enfrio 20030114 0 [sec 14.429 kb 153344 kps 10627.2
{wr: writers 4792 rdwait 1.103 wrwait 12.515 filemark 0.760}]
INFO taper tape PRMD-000 kb 153824 fm 2 [OK]
FINISH driver date 20030114 time 150.796
I also attatch the config file. Now I'm browsing the reporter.c source code,
although I hope someone can give an easier solution.
Thanks in advance,
Sergio
amanda.conf
Description: Binary data
Re: amanda 2.4.3 RESULTS MISSING
This should have gone to amanda-users. I've redirected it there. On Tue, Jan 14, 2003 at 12:57:40PM +0100, Sergio G. Reus wrote: > > Hi, > > I've installed amanda 2.4.3 on an AIX server. After following > every installation step, and creating a simple configuration, I have run > amdump. It runs perfectly, the logs do not say anything abnormal, the dumps > are in the tape and can be recovered, but the report mail complains with > "MISSING RESULTS": My first reaction was "what is he talking about, 'ran perfectly'? But then I noticed these lines of the report : > NOTES: > taper: tape PRMC-0 kb 153824 fm 2 [OK] Which suggests 153MB were written to tape. So, it seems like a reporting or a logging problem. I use 2.4.2, but I don't think the log files format has changed. You say the logs are normal. Just to check, each line starts with a keyword in caps (START, INFO, SUCCESS, STATS, FINISH, ???) By far the most frequent in mine is "SUCCESS", but with only 2 disklist entries, you may have fewer (I'm guessing 4 total). Is that a decent description of your log file? If yes, I'd guess the problem is reporting, if no, I'd suspect logging. If the log file looks ok, does amreport -l -f generate a more reasonable report in , or is it the same report that was mailed to you after the amdump. If the latter, then probably something is wrong with your amreport. Send me a note with your log file attached and I'll see if the amreport's I have here (both 2.42 and 2.4.3) produce the same or different results as your amreport. Also attach your config file. jon > > -- > These dumps were to tape PRMC-0. > The next tape Amanda expects to use is: a new tape. > > FAILURE AND STRANGE DUMP SUMMARY: > prmb /etc RESULTS MISSING > prmb /u04/copias/enfrio RESULTS MISSING > > > STATISTICS: > Total Full Daily > > Estimate Time (hrs:min)0:00 > Run Time (hrs:min) 0:02 > 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 > Avg Tp Write Rate (k/s) -- -- -- > > > NOTES: > taper: tape PRMC-0 kb 153824 fm 2 [OK] > > > DUMP SUMMARY: > DUMPER STATSTAPER STATS > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > -- - > prmb /etc MISSING -- > prmb -ias/enfrio MISSING -- > > (brought to you by Amanda version 2.4.3) > --- > > So the only thing failing is the mail generation. I have checked file permissions > with my other AMANDA server and they are OK. So why the mail can't get the >statistics? > > Thanks in advance, > > Sergio > >>> End of included message <<< -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Results Missing
I had that problem ("Results missing") on one of my samba-based hosts when
I had forgotten to add an entry in /etc/amandapass. Perhaps you are running
into the same sort of problem? (user authentication, or ability to 'find'
it)
Shooting in the dark: check .amandahosts?
Jesse
On Wed, 26 Jun 2002 08:52:11 -0700 (PDT)
"Tanniel Simonian" <[EMAIL PROTECTED]> wrote:
> Okay,
>
> I am strictly annoyed.
>
> I just added a new host to my backups. Its a debian system running amanda
> version 2.4.2p2 client.
>
> I tried using TAR, and I tried using DUMP. I am not getting TAPE out of
> space messages or any other error reports on amcheck.
>
> Amcheck comes out clean, no hosts problems, no tape problems. I have 17
> file systems that I back up and it just keep messing up on this host. I
> can't put my finger on it, and its driving me nuts.
>
>
> Here is the message I get from Amanda when it emails me.
>
> /dev/hda1 RESULTS MISSING
>
> I can't tell what I need to look for in the logs to help me understand my
> problem.
>
> Any help would be greatly appreciated.
>
> Thanks.
>
>
>
Results Missing
Okay, I am strictly annoyed. I just added a new host to my backups. Its a debian system running amanda version 2.4.2p2 client. I tried using TAR, and I tried using DUMP. I am not getting TAPE out of space messages or any other error reports on amcheck. Amcheck comes out clean, no hosts problems, no tape problems. I have 17 file systems that I back up and it just keep messing up on this host. I can't put my finger on it, and its driving me nuts. Here is the message I get from Amanda when it emails me. /dev/hda1 RESULTS MISSING I can't tell what I need to look for in the logs to help me understand my problem. Any help would be greatly appreciated. Thanks.
Results missing
Hi I'm having problems with my amanda installation. It has run without any problems for quite a while, but suddenly it gives the "RESULTS MISSING" error on alle servers in the backup-report. The log.* from the lates run is as follows: --- SNIP --- START planner date 20020530 START driver date 20020530 INFO planner Adding new disk firewall.eos:/etc. INFO planner Adding new disk firewall.eos:/afs/eos.dk/admin/hostdb. INFO planner Adding new disk afs1.eos:/etc. INFO planner Adding new disk afs1.eos:/var. INFO planner Adding new disk afs1.eos:/service. START taper datestamp 20020530 label EOS-005 tape 0 INFO planner Incremental of lemon.eos.dk:/home bumped to level 2. INFO planner Incremental of lemon.eos.dk:/ bumped to level 2. INFO planner Incremental of tinus.eos.dk:/home bumped to level 2. INFO planner Incremental of afs1.eos:/data02/cvsroot bumped to level 2. FINISH planner date 20020530 FATAL driver schedule line 4: syntax error INFO taper tape EOS-005 kb 0 fm 0 [OK] --- SNIP --- And the corresponding amdump file (only the part with errors is included): --- SNIP --- GENERATING SCHEDULE: afs1.eos /var 11839 0 1970:1:1:0:0:0 11525 384 afs1.eos /etc 11839 0 1970:1:1:0:0:0 2440 81 afs1.eos /service 11839 0 1970:1:1:0:0:0 5 0 firewall.eos /afs/eos.dk/admin/hostdb 11839 0 1970:1:1:0:0:0 0 0 6778732 firewall.eos /etc 11839 0 1970:1:1:0:0:0 0 0 6778732 svabonius.eos.dk / 206 0 1970:1:1:0:0:0 432210 382 1 2001:10:28:0:3:56 43620 263 firewall.eos /d106 7 4 2002:5:22:23:31:45 1 0 firewall.eos / 6 0 1970:1:1:0:0:0 537151 1823 2 2002:5:20:23:36:32 13831 70 afs1.eos /data01 3 0 1970:1:1:0:0:0 4339878 7708 2 2002:5:25:23:39:13 1043 6 firewall.eos /c0t1d0s7 3 0 1970:1:1:0:0:0 354601 1632 2 2002:5:22:0:31:46 19602 161 maconomyserver.eos.dk / 3 0 1970:1:1:0:0:0 288089 896 1 2002:5:18:23:11:52 14811 100 lemon.eos.dk / 3 0 1970:1:1:0:0:0 116063 186 2 2002:5:27:23:40:20 3539 9 afs1.eos //adm/backup 3 0 1970:1:1:0:0:0 45806 469 1 2002:5:18:23:37:49 82011 2562 maconomyserver.eos.dk /var 3 0 1970:1:1:0:0:0 1555 18 1 2002:5:18:23:11:31 1318 36 svabonius.eos.dk /etc 3 0 1970:1:1:0:0:0 1473 6 1 2002:5:18:23:11:46 462 2 firewall.eos /ext 2 1 2002:5:21:23:11:30 2826747 11977 firewall.eos /var 2 1 2002:5:22:0:34:52 132735 804 tinus.eos.dk /home 2 2 2002:5:27:23:32:26 124405 389 afs1.eos /data02/eos 2 1 2002:5:28:0:24:5 69644 829 afs1.eos /data02/cvsroot 2 2 2002:5:27:23:37:16 63666 535 svabonius.eos.dk /home 2 1 2002:5:28:6:54:56 48871 125 lemon.eos.dk /home 2 2 2002:5:27:23:32:24 2209 7 tinus.eos.dk / 2 1 2002:5:27:23:45:17 2023 21 svabonius.eos.dk /usr/bb18d1 2 1 2002:5:27:23:32:24 31 0 firewall.eos /pack/eoswww 2 1 2002:5:22:23:11:30 1 0 proxy.eos / 1 0 1970:1:1:0:0:0 259941 1355 1 2002:5:18:23:11:39 962 99 driver: schedule line 4: syntax error driver: adding holding disk 0 dir /amanda-cache/eos size 33306364 reserving 33306364 out of 33306364 for degraded-mode dumps taper: DONE [idle wait: 1110.422 secs] taper: writing end marker. [EOS-005 OK kb 0 fm 0] amdump: end at Thu May 30 01:18:39 CEST 2002 --- SNIP --- It's quite obvious that the driver is upset about the results the planner generated, but what could have coursed the error? Kind regards -- Jens Rohde, System Administrator --- Eastfork Object Space (EOS), Margrethepladsen 3, 8000 Aarhus C, Denmark Tel: +45 8732 8787 / Fax: +45 8732 8788
Re: RESULTS MISSING
>What does "RESULTS MISSING" mean? Strictly speaking it means when amreport ran to generate the E-mail after planner and driver had done all the work, it could not find those clients/disks in the log file. Look at the corresponding log.MMDD.NN file. First, make sure it ends properly with a "FINISH driver ..." line. Then find all the lines related to one of the clients/disks that worked so you see what a normal run should look like. Then look for one of the "RESULTS MISSING" ones and see what's different. Next, look at the corresponding amdump.NN file for the "RESULTS MISSING" clients/disks. If planner says it got estimates from them, look for driver FILE-DUMP or PORT-DUMP commands to a dumper. Then track that particular dumper and see what it had to say after that. >Dick John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RESULTS MISSING
What does "RESULTS MISSING" mean? I am running Intel RH Linux with Amanda version 2.4.2p2... *** THE DUMPS DID NOT FINISH PROPERLY! These dumps were to tape Daily6. The next tape Amanda expects to use is: Daily1. FAILURE AND STRANGE DUMP SUMMARY: gorn.ameri /ideroot2 lev 1 FAILED [/sbin/dump returned 3] solo.ameri /idebigger RESULTS MISSING vulcan.int /usr RESULTS MISSING maul.ameri / RESULTS MISSING andorian.a / RESULTS MISSING Thanks, Dick
RESULTS MISSING
Hi, As of yesterday my AMANDA backups stopped running, and simply send me a mail report listings all my hosts with "RESULTS MISSING". I've reviewed sendsize.debug on each of the hosts and it looks like everything was working normal. I'm using the fully qualified hostname for the machine local to AMANDA. What other reasons are there for AMANDA to give up and report "RESULTS MISSING" for _EVERY_ host? I'm running Amanda version 2.4.1p1 on each host. Thank You, Rob
Re: RESULTS MISSING
>FAILURE AND STRANGE DUMP SUMMARY: > localhost /etc RESULTS MISSING What version of Amanda? First, don't use "localhost" in your disklist. It will bite you eventually. Use the fully qualified host name. Next, look at /tmp/amanda/sendsize*debug. That's likely where the problem will show up. >Elisa Dalla John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RESULTS MISSING
Hi, we're trying to start our first amanda bkup session without any success Facts: amcheck and amverify succeded: -- Tape DailySet1-01 label ok NOTE: info dir /var/lib/amanda/DailySet1/curinfo: does not exist NOTE: it will be created on the next run Server check took 0.117 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.063 seconds, 0 problems found but amdump fails: *** THE DUMPS DID NOT FINISH PROPERLY! The next tape Amanda expects to use is: DailySet1-01. FAILURE AND STRANGE DUMP SUMMARY: localhost /etc RESULTS MISSING -- Everything seems OK. Any idea about that? Thanks in advance! -- - Elisa Dalla - Dip. Scienze dell'Ambiente e del Territorio Universita' di Milano-Bicocca P.za della Scienza 1 - Milano 20126 - Italy tel: 02-64482824
Re: results missing
>Having this problem where two of my directories say >RESULTS MISSING in the log files. It probably said more than this in the E-mail. Please post more detail, if it's available. What happens if you run amcheck? >... Is it because I didn't have enough tape to do a level 0? No, that wouldn't do it. It's more likely a communications problem between the Amanda server and client. >e John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
results missing
Having this problem where two of my directories say RESULTS MISSING in the log files. Anyone know what that means? Is it because I didn't have enough tape to do a level 0? thanks e = --Eff Edwards __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Re: RESULTS MISSING
On Thu, Nov 09, 2000 at 06:45:02AM -0600, Tom Hudak wrote: Ok, one last update, I noticed that the "planner" wasn't being initiated or there was an error occuring, when running planner from the command line, it spits out some config info, and then get's to "Getting Estimates" and starts getting these errors: "protocol packet receive: Connection refused" From what I can tell, the amanda user has all the access needed to access the disks, maybe there's something not quite right with the inetd.conf or /etc/services but that should have come up while running amcheck(?). >On Thu, Nov 09, 2000 at 06:26:54AM -0600, Tom Hudak wrote: >I have a modification, it turns out the dumpers program was not u+x, so it >choked, now I'm getting "request to HOST timed out." I do not see a resolution >before leaving work tonight being reasonable, but If I should get any more >info in the next day or so, I'll repost. > PGP signature
Re: RESULTS MISSING
On Thu, Nov 09, 2000 at 06:26:54AM -0600, Tom Hudak wrote: I have a modification, it turns out the dumpers program was not u+x, so it choked, now I'm getting "request to HOST timed out." I do not see a resolution before leaving work tonight being reasonable, but If I should get any more info in the next day or so, I'll repost. >I have just ironed out my config, setup my clients and gotten amcheck to run >without problems, after setting the "record no" global option, running amdump >spits out this: >FAILURE AND STRANGE DUMP SUMMARY: > smb/home RESULTS MISSING > smb/var/data/kalisa RESULTS MISSING > homer /dev/hda1 RESULTS MISSING > homer /dev/md0 RESULTS MISSING > > >STATISTICS: > Total Full Daily > >Dump Time (hrs:min)0:00 0:00 0:00 (0:00 start, 0:00 >idle) >Output Size (meg) 0.00.00.0 >Original Size (meg) 0.00.00.0 >Avg Compressed Size (%) -- -- -- >Tape Used (%) 0.00.00.0 >Filesystems Dumped0 0 0 >Avg Dump Rate (k/s) -- -- -- >Avg Tp Write Rate (k/s) -- -- -- > >^L >NOTES: > driver: WARNING: got empty schedule from planner > taper: tape Daily-05 kb 0 fm 0 [OK] > >^L >DUMP SUMMARY: > DUMPER STATS TAPER >STATS >HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s >homer /dev/hda1 MISSING > >homer /dev/md0 MISSING > >smb /home MISSING > >smb -r/data/kalisaMISSING > > >(brought to you by Amanda version 2.4.1p1) >My question relates to the line's containing RESULTS MISSING (although I'm not >sure how the -r got in there, the disklist contains the full path: "smb --> >-r/data/kalisa <--". I >have checked the amdump.debug, selfcheck.debug and looked for other .debug files but >found >none on both the server and the client. Neither the client or host .debug >files contain anything about error's or problems, yet the error continues. >What causes this? am I not looking at the right debug files? I have found MANY >submissions like this to the hackers list, none of them seem to fit my current >setup. This is a brand spankin' new config and I *believe* it's correct. Any >info would be MUCH appreciated. > PGP signature
RESULTS MISSING
I have just ironed out my config, setup my clients and gotten amcheck to run
without problems, after setting the "record no" global option, running amdump
spits out this:
FAILURE AND STRANGE DUMP SUMMARY:
smb/home RESULTS MISSING
smb/var/data/kalisa RESULTS MISSING
homer /dev/hda1 RESULTS MISSING
homer /dev/md0 RESULTS MISSING
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:00 0:00 0:00 (0:00 start, 0:00
idle)
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Tape Used (%) 0.00.00.0
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) -- -- --
^L
NOTES:
driver: WARNING: got empty schedule from planner
taper: tape Daily-05 kb 0 fm 0 [OK]
^L
DUMP SUMMARY:
DUMPER STATS TAPER
STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
homer /dev/hda1 MISSING
homer /dev/md0 MISSING
smb /home MISSING
smb -r/data/kalisaMISSING
(brought to you by Amanda version 2.4.1p1)
My question relates to the line's containing RESULTS MISSING (although I'm not
sure how the -r got in there, the disklist contains the full path: "smb -->
-r/data/kalisa <--". I
have checked the amdump.debug, selfcheck.debug and looked for other .debug files but
found
none on both the server and the client. Neither the client or host .debug
files contain anything about error's or problems, yet the error continues.
What causes this? am I not looking at the right debug files? I have found MANY
submissions like this to the hackers list, none of them seem to fit my current
setup. This is a brand spankin' new config and I *believe* it's correct. Any
info would be MUCH appreciated.
PGP signature
Re: AMDump Reporting Results Missing
>(null): version 2.4.1p1 >... In addition to the /etc/amandates issue, the "(null)" above indicates another problem. I suspect you forgot to add an extra "amandad" on the end of your /etc/inetd.conf line. It should look something like this (your path will be different): amanda dgram udp wait backup /opt/amanda/libexec/amandad amandad Note that both the path to amandad and an extra "amandad" must be on the line. >Nathan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: AMDump Reporting Results Missing
On Nov 8, 2000, Nathan Bird <[EMAIL PROTECTED]> wrote:
> Isn't amandates meant to be created automagically?
As in user `amanda' creating files in /etc? :-)
> If it is, then why would it be creating it as a directory?
Amanda certainly doesn't create it as a directory.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
RE: AMDump Reporting Results Missing
Isn't amandates meant to be created automagically?
If it is, then why would it be creating it as a directory?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Alexandre Oliva
Sent: Wednesday, 8 November 2000 2:33 PM
To: Nathan Bird
Cc: '[EMAIL PROTECTED]'; 'Peter Schaffrath'; 'Amanda user's group'
Subject: Re: AMDump Reporting Results Missing
On Nov 8, 2000, Nathan Bird <[EMAIL PROTECTED]> wrote:
> sendsize: reading /etc/amandates: Is a directory
Here's the answer. It should be a file, not a directory.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: AMDump Reporting Results Missing
On Nov 8, 2000, Nathan Bird <[EMAIL PROTECTED]> wrote:
> sendsize: reading /etc/amandates: Is a directory
Here's the answer. It should be a file, not a directory.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
RE: AMDump Reporting Results Missing
John and others who are helping me with this problem heres the latest increment. >>That's it?? That would certainly explain the message. The file is >>very incomplete. I thought that it looked a little small, but this is the first time I have ever tried to get Amanda working, so I was unsure as to what else should be in there. >>What's in /tmp/amanda/amandad*debug? Make sure you don't run anything >>of Amanda between the failure and grabbing the file as it's usually >>overwritten (unless you used --with-pid-debug-files). ---START-* amandad: debug 1 pid 31903 ruid 0 euid 0 start time Wed Nov 8 08:30:17 2000 (null): version 2.4.1p1 (null): build: VERSION="Amanda-2.4.1p1" (null):BUILT_DATE="Thu Nov 2 14:54:26 EST 2000" (null):BUILT_MACH="Linux paperbark.hunterlink.net.au 2.2.5-15 #1 Mon Apr 19 23:00:46 EDT 1999 i686 unknown" (null):CC="gcc" (null): paths: bindir="/usr/local/bin" sbindir="/usr/local/amanda/sbin" (null):libexecdir="/usr/local/amanda/libexec" (null):mandir="/usr/local/amanda/man" (null):CONFIG_DIR="/usr/local/amanda/etc/amanda" (null):DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/" (null):GNUTAR="/usr/bin/gtar" COMPRESS_PATH="/bin/gzip" (null):UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/bin/Mail" (null):listed_incr_dir="/usr/local/amanda/gnutar-lists" (null): defs: DEFAULT_SERVER="paperbark.hunterlink.net.au" (null):DEFAULT_CONFIG="DailySet1" (null):DEFAULT_TAPE_SERVER="paperbark.hunterlink.net.au" (null):DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM (null):LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY (null):CLIENT_LOGIN="root" FORCE_USERID HAVE_GZIP (null):COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" (null):COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" got packet: Amanda 2.4 REQ HANDLE 000-D86F0508 SEQ 973632617 SECURITY USER root SERVICE sendsize OPTIONS maxdumps=1;hostname=paperbark; GNUTAR /home 0 1970:1:1:0:0:0 -1 sending ack: Amanda 2.4 ACK HANDLE 000-D86F0508 SEQ 973632617 bsd security: remote host paperbark.hunterlink.net.au user root local user root bsd security check passed (null): running service "/usr/local/amanda/libexec/sendsize" sendsize: reading /etc/amandates: Is a directory (null): sending REP packet: Amanda 2.4 REP HANDLE 000-D86F0508 SEQ 973632617 (null): got ack: Amanda 2.4 ACK HANDLE 000-D86F0508 SEQ 973632617 amandad: pid 31903 finish time Wed Nov 8 08:30:17 2000 ---END-* >>Can you tell if there are any stray processes running for your Amanda >>user? The user that is running is ROOT, so it is possible that there may be a stray process, do you suggest I reboot the machine and try to run from a fresh reboot, to ensure ( or at least try to ensure ) that there is no stray processes? If a stray process were present how would this affect Amanda? >> Are there any messages in the system logs about amandad or sendsize? There is no mention of either in the /var/log/messages file, should there be somewhere else I should be looking? However I have just noticed that in the "amdump.1" file the following exists ---START-* GETTING ESTIMATES... driver: started dumper0 pid 2432 driver: started dumper1 pid 2433 driver: started dumper2 pid 2434 driver: started dumper3 pid 2435 dumper: pid 2432 executable dumper version 2.4.1p1, using port 896 taper: pid 2431 executable taper version 2.4.1p1 dumper: pid 2434 executable dumper version 2.4.1p1, using port 898 dumper: pid 2433 executable dumper version 2.4.1p1, using port 897 dumper: pid 2435 executable dumper version 2.4.1p1, using port 899 error result for host paperbark disk /home: missing estimate getting estimates took 0.377 secs FAILED QUEUE: 0: paperbark /home DONE QUEUE: empty ---END-* "error result for host paperbark disk /home: missing estimate" this line, where it refers to a missing estimate, would this be causing the problem? If so, why? and how can I/we fix it? >>What happens if you do this on paperbark (or whatever machine you used >>to build those binaries): >> cd client-src >> gmake getfsent >> ./getfsent /home### run this on paperbark >>(none of this has to be done as root). This tests out some of the file >>system name conversion routines. According to some of my log files, >>that's the next line that should have show up in the debug file. gmake getfsent return the following.. ---START-* [root@paperbark client-src]# gmake getfsent echo '#define TEST' >getfsent.test.c echo '#include "getfsent.c"' >>getfsent.test.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -D_FILE_OFFSET_BITS=64-g -c getfsent.test.c /bin/sh ../libtool --mode=link gcc -g -o getf
Re: AMDump Reporting Results Missing
>>> What is in /tmp/amanda/sendsize*debug on paperbark after a failed amdump? > >sendsize: debug 1 pid 31909 ruid 0 euid 0 start time Wed Nov 8 08:30:17 >2000 >/usr/local/amanda/libexec/sendsize: version 2.4.1p1 That's it?? That would certainly explain the message. The file is very incomplete. What's in /tmp/amanda/amandad*debug? Make sure you don't run anything of Amanda between the failure and grabbing the file as it's usually overwritten (unless you used --with-pid-debug-files). Can you tell if there are any stray processes running for your Amanda user? Are there any messages in the system logs about amandad or sendsize? What happens if you do this on paperbark (or whatever machine you used to build those binaries): cd client-src gmake getfsent ./getfsent /home### run this on paperbark (none of this has to be done as root). This tests out some of the file system name conversion routines. According to some of my log files, that's the next line that should have show up in the debug file. >back to the line "paperbark /home lev 0 FAILED [missing result for /home in >paperbark response]" > >does the lev 0 mean anything? ... It means Amanda was asking about a level 0 (full) backup. Probably not of interest, but we'll keep it in mind. >Nathan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: AMDump Reporting Results Missing
Thanks again for your respones... here are the answers to your questions. >> What happens when you run amcheck now that you've fixed disklist? Amanda Tape Server Host Check - /usr/local/amanda/dumps: 2410172 KB disk space available, that's plenty. NOTE: skipping tape-writable test. Tape DailySet101 label ok. Server check took 26.914 seconds. Amanda Backup Client Hosts Check Client check: 1 host checked in 0.106 seconds, 0 problems found. (brought to you by Amanda 2.4.1p1) >> What is in /tmp/amanda/sendsize*debug on paperbark after a failed amdump? sendsize: debug 1 pid 31909 ruid 0 euid 0 start time Wed Nov 8 08:30:17 2000 /usr/local/amanda/libexec/sendsize: version 2.4.1p1 --- back to the line "paperbark /home lev 0 FAILED [missing result for /home in paperbark response]" does the lev 0 mean anything? It probably doesn't but I am fishing for ideas as to why this is not working. :) Nathan
Re: AMDump Reporting Results Missing
>I did have another look at the Amanda FAQamatic and found an article on >there saying that the UDP packets may not be large enough, but it also says >that this should no longer occurr since they increased the packet size from >1 kB to 64 kb. Actually, it was 8 KBytes -> 64 KBytes, but that only changed (I think) in 2.4.2. In 2.4.1p1 you still need to tweak the source. But I don't think that's what's happening to you. This would only be a problem if you had lots and lots of disklist entries. What happens when you run amcheck now that you've fixed disklist? What is in /tmp/amanda/sendsize*debug on paperbark after a failed amdump? >I am using Redhat 7.0 on a PII 400 with 192 MB ram, surely I needed worry >about the UDP packet size... ?? UDP size has nothing to do with system size, so yes, you could potentially have the problem. >Peter John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: AMDump Reporting Results Missing
I have tried all sorts of wierd and wonderfull combinations of things as the
diskdev.
I have tried
paperbark /dev/hda8 dumptype
paperbark /home dumptype
paperbark /mnt/c-drive dumptype
paperbark / dumptype
You name it and I have probably tried it :) ( i think? )
And I still recieve the same error message
The following message is same for them all except the diskdev section
changes. ( below )
I did have another look at the Amanda FAQamatic and found an article on
there saying that the UDP packets may not be large enough, but it also says
that this should no longer occurr since they increased the packet size from
1 kB to 64 kb.
I am using Redhat 7.0 on a PII 400 with 192 MB ram, surely I needed worry
about the UDP packet size... ??
Thanks everyone for their help so far... I just hope that we can nut this
one out.
--- ERROR MESSAGE STARTS HERE. --
*** THE DUMPS DID NOT FINISH PROPERLY!
*** A TAPE ERROR OCCURRED: [cannot overwrite active tape DailySet100].
*** PERFORMED ALL DUMPS TO HOLDING DISK.
THESE DUMPS WERE TO DISK. Flush them onto a new tape.
Tonight's dumps should go onto 1 tape: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
paperbark /home lev 0 FAILED [missing result for /home in paperbark
response]
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:00 0:00 0:00 (0:00 start)
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Tape Used (%) 0.00.00.0
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk paperbark:/home.
driver: WARNING: got empty schedule from planner
DUMP SUMMARY:
DUMPER STATS TAPER
STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- --
--
paperbark /home 0 FAILED
(brought to you by Amanda version 2.4.1p1)
- END ERROR MESSAGE ---
Thanks again
Nathan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Peter Schaffrath
Sent: Tuesday, 7 November 2000 9:55 AM
To: Nathan Bird
Cc: '[EMAIL PROTECTED]'; 'Amanda user's group'
Subject: RE: AMDump Reporting Results Missing
On Tue, 7 Nov 2000, Nathan Bird wrote:
> In disklist I was under the impression that you had to write the
following.
>
> hostname diskdev dumptype [spindle [interface]]
>
> The diskdev that it is referring to is the tape device isn't it?
Nice idea :-)
No, "diskdev" is the harddisk (sig!) on the client that you want to
backup. Ex. if you have 2 disks on client1 there are 2 entries:
client1 /mountpoint1/of/disk1 dumptype
client1 /mountpoint2/of/disk2 dumptype
And possibly lots more for other clients.
The tape device is set in your amanda.conf file and that's the only place
where it is needed.
Peter
RE: AMDump Reporting Results Missing
On Tue, 7 Nov 2000, Nathan Bird wrote: > In disklist I was under the impression that you had to write the following. > > hostname diskdev dumptype [spindle [interface]] > > The diskdev that it is referring to is the tape device isn't it? Nice idea :-) No, "diskdev" is the harddisk (sig!) on the client that you want to backup. Ex. if you have 2 disks on client1 there are 2 entries: client1 /mountpoint1/of/disk1 dumptype client1 /mountpoint2/of/disk2 dumptype And possibly lots more for other clients. The tape device is set in your amanda.conf file and that's the only place where it is needed. Peter
RE: AMDump Reporting Results Missing
John, In disklist I was under the impression that you had to write the following. hostname diskdev dumptype [spindle [interface]] The diskdev that it is referring to is the tape device isn't it? Thanks Nathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John R. Jackson Sent: Friday, 3 November 2000 11:00 AM To: Nathan Bird Cc: 'Amanda user's group' Subject: Re: AMDump Reporting Results Missing >paperbark /dev/nst0 lev 0 FAILED [ missing result for >/dev/nst0 in paperbark response ] Ummm, that's a bizarre message. Why are you trying to back up /dev/nst0? Isn't that your tape device? It looks like your disklist has that in the first field instead of a disk or file system name. >Nathan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: AMDump Reporting Results Missing
>paperbark /dev/nst0 lev 0 FAILED [ missing result for >/dev/nst0 in paperbark response ] Ummm, that's a bizarre message. Why are you trying to back up /dev/nst0? Isn't that your tape device? It looks like your disklist has that in the first field instead of a disk or file system name. >Nathan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
AMDump Reporting Results Missing
Hi, I am running Redhat Linux 7.0, and have just installed Amanda. I run amcheck with no reports of errors, however when I attempt to run amdump, i get the following messages. paperbark /dev/nst0 lev 0 FAILED [ missing result for /dev/nst0 in paperbark response ] Has anyone seen this message before and if they have, does anyone know a way around it? Awaiting many helpfull responses :) Nathan
