Amanda failed.
OS: Solaris 10 SPARC AMANDA Version: 2.5.2P1 Last night my Soalris 10 sparc host Amanda failed with the following errors zorn /export/users-z lev 0 FAILED [/local/Amanda/amanda-2.5.2p1/libexec/runtar exited with status 1: see /tmp/amanda/client/daily/sendsize.20080221182142.debug] A section of the /tmp/amanda/client/daily/sendsize.20080221182142.debug] sendsize[13188]: time 23.002: estimate size for /export/users-a level 0: -1 KB sendsize[13188]: time 23.002: waiting for runtar /export/users-a child sendsize[13188]: time 23.002: after runtar /export/users-a wait errmsg is /local/Amanda/amanda-2.5.2p1/libexec/runtar exited with status 1: see /tmp/amanda/client/daily/sendsize.20080221182142.debug sendsize[13188]: time 23.003: getting size via gnutar for /export/users-a level 4 sendsize[13110]: time 23.038: getting size via dump for /export/varmail level 2 sendsize[13110]: time 23.042: calculating for device /dev/rdsk/c3t102d3s6 with ufs sendsize[13110]: time 23.042: running /usr/sbin/ufsdump 2Ssf 1048576 - /dev/rdsk/c3t102d3s6 sendsize[13110]: time 23.171: running /local/Amanda/amanda-2.5.2p1/libexec/killpgrp sendsize[13110]: time 23.172: cannot execute /local/Amanda/amanda-2.5.2p1/libexec/killpgrp: Permission denied sendsize[13188]: time 23.908: spawning /local/Amanda/amanda-2.5.2p1/libexec/runtar in pipeline sendsize[13188]: time 23.908: argument list: runtar daily /opt/csw/bin/gtar --create --file /dev/null --directory /export/fssnap/users --one-file-system --listed-incremental /var/am anda/gnutar-lists/zorn_export_users-a_4.new --sparse --ignore-failed-read --totals --files-from /tmp/amanda/sendsize._export_users-a.20080221182205.include sendsize[13188]: time 23.915: error [exec /local/Amanda/amanda-2.5.2p1/libexec/runtar: Permission denied] sendsize: time 23.915: pid 13196 finish time Thu Feb 21 18:22:06 2008 sendsize[13188]: time 23.999: sendsize: error [exec /local/Amanda/amanda-2.5.2p1/libexec/runtar: Permission denied] It seemed that everything with SUID that tried to run last night has permission denied. Here is an ls of the SUID files. -rwsr-x--- 1 root operator 23744 Jun 7 2007 calcsize* -rwsr-x--- 1 root operator 65820 Jun 7 2007 dumper* -rwsr-x--- 1 root operator 13524 Jun 7 2007 killpgrp* -rwsr-x--- 1 root operator 93424 Jun 7 2007 planner* -rwsr-x--- 1 root operator 11352 Jun 7 2007 rundump* -rwsr-x--- 1 root operator 14472 Jun 7 2007 runtar* The seem to be correct and have not been changed since Jun 7. All the other clients ran without problems. Any ideas on the cause or was this just a cosmic ray hitting my computer before the backup? I will just wait for tonight's backup to see if it happens again but just wanted to see if some saw a problem from the logs. Thanks Robert _ Robert P. McGraw, Jr. Manager, Computer SystemEMAIL: [EMAIL PROTECTED] Purdue UniversityROOM: MATH-807 Department of Mathematics PHONE: (765) 494-6055 150 N. University Street West Lafayette, IN 47907-2067 smime.p7s Description: S/MIME cryptographic signature
Re: Amanda failed.
On Fri, Feb 22, 2008 at 09:24:33AM -0500, McGraw, Robert P wrote: OS: Solaris 10 SPARC AMANDA Version: 2.5.2P1 Last night my Soalris 10 sparc host Amanda failed with the following errors zorn /export/users-z lev 0 FAILED [/local/Amanda/amanda-2.5.2p1/libexec/runtar exited with status 1: see /tmp/amanda/client/daily/sendsize.20080221182142.debug] A section of the /tmp/amanda/client/daily/sendsize.20080221182142.debug] sendsize[13188]: time 23.002: estimate size for /export/users-a level 0: -1 KB sendsize[13188]: time 23.002: waiting for runtar /export/users-a child sendsize[13188]: time 23.002: after runtar /export/users-a wait errmsg is /local/Amanda/amanda-2.5.2p1/libexec/runtar exited with status 1: see /tmp/amanda/client/daily/sendsize.20080221182142.debug sendsize[13188]: time 23.003: getting size via gnutar for /export/users-a level 4 sendsize[13110]: time 23.038: getting size via dump for /export/varmail level 2 sendsize[13110]: time 23.042: calculating for device /dev/rdsk/c3t102d3s6 with ufs sendsize[13110]: time 23.042: running /usr/sbin/ufsdump 2Ssf 1048576 - /dev/rdsk/c3t102d3s6 sendsize[13110]: time 23.171: running /local/Amanda/amanda-2.5.2p1/libexec/killpgrp sendsize[13110]: time 23.172: cannot execute /local/Amanda/amanda-2.5.2p1/libexec/killpgrp: Permission denied sendsize[13188]: time 23.908: spawning /local/Amanda/amanda-2.5.2p1/libexec/runtar in pipeline sendsize[13188]: time 23.908: argument list: runtar daily /opt/csw/bin/gtar --create --file /dev/null --directory /export/fssnap/users --one-file-system --listed-incremental /var/am anda/gnutar-lists/zorn_export_users-a_4.new --sparse --ignore-failed-read --totals --files-from /tmp/amanda/sendsize._export_users-a.20080221182205.include sendsize[13188]: time 23.915: error [exec /local/Amanda/amanda-2.5.2p1/libexec/runtar: Permission denied] sendsize: time 23.915: pid 13196 finish time Thu Feb 21 18:22:06 2008 sendsize[13188]: time 23.999: sendsize: error [exec /local/Amanda/amanda-2.5.2p1/libexec/runtar: Permission denied] It seemed that everything with SUID that tried to run last night has permission denied. Here is an ls of the SUID files. -rwsr-x--- 1 root operator 23744 Jun 7 2007 calcsize* -rwsr-x--- 1 root operator 65820 Jun 7 2007 dumper* -rwsr-x--- 1 root operator 13524 Jun 7 2007 killpgrp* -rwsr-x--- 1 root operator 93424 Jun 7 2007 planner* -rwsr-x--- 1 root operator 11352 Jun 7 2007 rundump* -rwsr-x--- 1 root operator 14472 Jun 7 2007 runtar* The seem to be correct and have not been changed since Jun 7. All the other clients ran without problems. Any ideas on the cause or was this just a cosmic ray hitting my computer before the backup? They are not world executable. So the process executing them must either be root or in the operator group. Might something have caused a change in the identity of your executing backup processes? Or your group memberships? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: Amanda failed.
* Jon LaBadie [EMAIL PROTECTED] [20080222 11:56]: On Fri, Feb 22, 2008 at 09:24:33AM -0500, McGraw, Robert P wrote: OS: Solaris 10 SPARC AMANDA Version: 2.5.2P1 Last night my Soalris 10 sparc host Amanda failed with the following errors zorn /export/users-z lev 0 FAILED [/local/Amanda/amanda-2.5.2p1/libexec/runtar exited with status 1: see /tmp/amanda/client/daily/sendsize.20080221182142.debug] A section of the /tmp/amanda/client/daily/sendsize.20080221182142.debug] sendsize[13188]: time 23.002: estimate size for /export/users-a level 0: -1 KB [...] sendsize: time 23.915: pid 13196 finish time Thu Feb 21 18:22:06 2008 sendsize[13188]: time 23.999: sendsize: error [exec /local/Amanda/amanda-2.5.2p1/libexec/runtar: Permission denied] It seemed that everything with SUID that tried to run last night has permission denied. Here is an ls of the SUID files. -rwsr-x--- 1 root operator 23744 Jun 7 2007 calcsize* -rwsr-x--- 1 root operator 65820 Jun 7 2007 dumper* -rwsr-x--- 1 root operator 13524 Jun 7 2007 killpgrp* -rwsr-x--- 1 root operator 93424 Jun 7 2007 planner* -rwsr-x--- 1 root operator 11352 Jun 7 2007 rundump* -rwsr-x--- 1 root operator 14472 Jun 7 2007 runtar* The seem to be correct and have not been changed since Jun 7. All the other clients ran without problems. Any ideas on the cause or was this just a cosmic ray hitting my computer before the backup? They are not world executable. So the process executing them must either be root or in the operator group. Might something have caused a change in the identity of your executing backup processes? Or your group memberships? Another thing to check: *if* the client is accessing those amanda suid execs through NFS, then the NFS server must not squash root on the client. Check how the server exports /local and how it is mounted on the client... jf -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive(703) 787-0884 Reston, VA 20194(703) 787-0922 (fax) -- °
RE: amanda failed to report via email
Title: amanda failed to report via email You need to have amcheck -am configname in your crontab -Original Message- From: [EMAIL PROTECTED]on behalf ofNina Pham Sent: Fri 16/07/2004 22:38 To: [EMAIL PROTECTED] Cc: Subject: amanda failed to report via email I have amanda running in a cron job, it suppose to backup 3 things.However, for some permission problem, 1 thing is failed to back up. Ithought it would send the report via email to the email addressspecified in mailto no matter what. But that day, I didn't recieve thereport via email. When I fix the permission problem, it successfullybackup and I received email report everyday since then. What might causethe problem of sending email? is it a amanda bug? I doesn't make senseto me that amanda doesn't send report when there's a problem .
amanda failed to report via email
I have amanda running in a cron job, it suppose to backup 3 things. However, for some permission problem, 1 thing is failed to back up. I thought it would send the report via email to the email address specified in mailto no matter what. But that day, I didn't recieve the report via email. When I fix the permission problem, it successfully backup and I received email report everyday since then. What might cause the problem of sending email? is it a amanda bug? I doesn't make sense to me that amanda doesn't send report when there's a problem .
RE: amanda failed
hello, and thanks for your answers. If my tar is broken or my amanda version is wrong, why it is the first time it happens since i started using amanda 4 months ago??? I will follow your advices. I recieved this mail, what is the meaning of no backup size line? Why the dump failded??? That message means Amanda could not parse the last line of output from tar that says how big the backups were. It reports the line: ? Total bytes written: nan (0B, ?B/s) That's clearly wrong. My guess is your version of GNU tar is broken. What version are you using? If it's 1.13 based, you need at least 1.13.17, or better yet, 1.13.19. If it's 1.12, you need the patch from www.amanda.org (although I don't think it affects this particular problem). FYI, these errors: | gtar: ./desar/desar11/LineaBase/lotoserver/var/socks/sock.bbox_server: socket ignored are fixed in the latest Amanda (2.4.2p2).
amanda failed
I recieved this mail, what is the meaning of no backup size line?
Why the dump failded???
Thanks
Montse
These dumps were to tape Miercoles.
The next tape Amanda expects to use is: Jueves.
FAILURE AND STRANGE DUMP SUMMARY:
marte /home lev 0 FAILED [no backup size line]
marte /home lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 0:23
Dump Time (hrs:min)0:11 0:11 0:00
Output Size (meg)1610.8 1610.80.0
Original Size (meg) 1610.8 1610.80.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped1 1 0
Avg Dump Rate (k/s) 2417.6 2417.6--
Tape Time (hrs:min)0:22 0:22 0:00
Tape Size (meg) 3311.5 3311.50.0
Tape Used (%) 20.0 20.00.0
Filesystems Taped 2 2 0
Avg Tp Write Rate (k/s) 2623.1 2623.1--
FAILED AND STRANGE DUMP DETAILS:
/-- marte /home lev 0 FAILED [no backup size line]
sendbackup: start [marte:/home level 0]
sendbackup: info BACKUP=/bin/gtar
sendbackup: info RECOVER_CMD=/bin/gtar -f... -
sendbackup: info end
| gtar:
./desar/desar11/LineaBase/lotoserver/var/socks/sock.bbox_server:
socket ignored
| gtar:
./desar/desar11/LineaBase/lotoserver/var/socks/sock.comext_server:
socket ignored
| gtar:
./desar/desar11/LineaBase/lotoserver/var/socks/sock.game_server:
socket ignored
| gtar:
./desar/desar11/LineaBase/lotoserver/var/socks/sock.scred_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/dev/log:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/tmp/.X11-unix/X0:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/var/opt/lotoserver/socks/sock.peana_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/var/opt/lotoserver/socks/sock.scard_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/var/opt/lotoserver/socks/sock.sound_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/var/opt/lotoserver/socks/sock.sound_udp_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/opt/lotoclient/exported/roots/
root1/var/opt/lotoserver/socks/sock.supv_gameclient:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/var/opt/lotoserver/socks/sock.
bbox_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/var/opt/lotoserver/socks/sock.
comext_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/var/opt/lotoserver/socks/sock.
game_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/var/opt/lotoserver/socks/sock.
scard_server:
socket ignored
| gtar:
./ingsis/jalvarez/tn2_prototipo/var/opt/lotoserver/socks/sock.
scred_server:
socket ignored
| gtar:
./ingsis/jrubio/desarrollo1/LineaBase/lotoserver/lotoserver_sc
/socks/sock.bbox_server:
socket ignored
| gtar:
./ingsis/jrubio/desarrollo1/LineaBase/lotoserver/lotoserver_sc
/socks/sock.comext_server:
socket ignored
| gtar:
./ingsis/jrubio/desarrollo1/LineaBase/lotoserver/lotoserver_sc
/socks/sock.ob_server:
socket ignored
| gtar:
./ingsis/jrubio/desarrollo1/LineaBase/lotoserver/lotoserver_sc
/socks/sock.sc_server:
socket ignored
| gtar: ./test/test2/lotoserver_sc/socks/sock.bbox_server:
socket ignored
| gtar: ./test/test2/lotoserver_sc/socks/sock.comext_server:
socket ignored
| gtar: ./test/test2/lotoserver_sc/socks/sock.sc_server:
socket ignored
? Total bytes written: nan (0B, ?B/s)
sendbackup: error [no backup size line]
\
NOTES:
taper: tape Miercoles kb 3390944 fm 2 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
--- -- --
marte/home0 N/A1741440 --N/A N/A 10:102853.2
srvlinux /home0 16494721649472 -- 11:222417.611:222417.3
(brought to you by Amanda version 2.4.2)
Re: amanda failed
I recieved this mail, what is the meaning of no backup size line? Why the dump failded??? That message means Amanda could not parse the last line of output from tar that says how big the backups were. It reports the line: ? Total bytes written: nan (0B, ?B/s) That's clearly wrong. My guess is your version of GNU tar is broken. What version are you using? If it's 1.13 based, you need at least 1.13.17, or better yet, 1.13.19. If it's 1.12, you need the patch from www.amanda.org (although I don't think it affects this particular problem). FYI, these errors: | gtar: ./desar/desar11/LineaBase/lotoserver/var/socks/sock.bbox_server: socket ignored are fixed in the latest Amanda (2.4.2p2). Montse John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
