- 1. tar got signal 11 (score: 1)
- Author: Rodrigo Ventura <yoda AT isr.ist.utl DOT pt>
- Date: Mon, 28 Nov 2005 10:45:32 +0000
- This just happened this night amdump: (/tmp/amanda/sendbackup.20051128003448.debug) [...] sendbackup: time 3.133: index created successfully sendbackup: time 3.134: error [/bin/tar got signal 11] sen
- /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2005-11/msg00327.html (10,968 bytes)
- 2. Re: tar got signal 11 (score: 1)
- Author: Sven Rudolph <rudsve AT drewag DOT de>
- Date: Mon, 28 Nov 2005 12:26:56 +0100
- We run a job that syncs /etc/passwd from a remote source. Sometimes this jobs is triggered continuously; and then /etc/passwd is written many times per second. This causes tar to receive SIGSEGV. In
- /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2005-11/msg00328.html (11,123 bytes)
- 3. Re: tar got signal 11 (score: 1)
- Author: Gene Heskett <gene.heskett AT verizon DOT net>
- Date: Mon, 28 Nov 2005 06:28:10 -0500
- Signal 11 is usually a memory error. Have you run memtest86 on that box for a day or so recently? The results might be illuminating. -- Cheers, Gene "There are four boxes to be used in defense of lib
- /usr/local/webapp/mharc-adsm.org/html/Amanda-Users/2005-11/msg00329.html (11,408 bytes)
This search system is powered by
Namazu