Dennis,
Post the amvault.datastamp.debug file.
Can you run amvault inside gdb?
$gdb perl
(gdb) run /path/to/amvault [amvault arg]
And get a backtrace of all threads?
(gdb) info threads
Then for each threads:
(gdb) thread thread id
(gdb) where
Jean-Louis
On 05/15/2012 03:21 AM, Dennis
Hello Jean-Louis,
the debug file is really short:
amanda@dl380-54:~$ cat /tmp/amanda/server/daily/amvault.20120515134859.debug
Tue May 15 13:48:59 2012: thd-0x2230400: amvault: pid 10772 ruid 1001
euid 1001 version 3.3.1.svn.4721: start at Tue May 15 13:48:59 2012
Tue May 15 13:48:59 2012:
On 05/15/2012 07:54 AM, Dennis Benndorf wrote:
Log file /usr/local/etc/amanda/daily/catalog/log.20120506180002.0
stamped 20120506180002, expecting 20120505180458!
I never saw amanda print this message.
Program received signal SIGSEGV, Segmentation fault.
0x75dcd7b0 in g_str_hash ()
Dennis,
The attached patch fix the crash.
You have log corruption because of amdump and amvault running
simultaneously.
Jean-Louis
On 05/15/2012 08:20 AM, Dennis Benndorf wrote:
Am 15.05.2012 14:14, schrieb Jean-Louis Martineau:
On 05/15/2012 07:54 AM, Dennis Benndorf wrote:
Log file
Really big thanks to you,
I tested amrecover and it works now. The test of amvault will be
available tommorow. I will send another email then.
Kind Regards,
Dennis
Dennis,
The attached patch make amvault to check if a log file already exists
and abort in this case.
It will abort if amdump is already running.
Jean-Louis
On 05/15/2012 09:16 AM, Jean-Louis Martineau wrote:
Dennis,
The attached patch fix the crash.
You have log corruption because of
