Re: [AMaViS-user] Amavis Crashes on Solaris x86

2010-09-14 Thread Ihsan Dogan
Hello Mark, On 09/13/10 15:42, Ihsan Dogan wrote: A detailed log may narrow down the problem area. If the crash occurs within SpamAssassin, that would be: $sa_debug=1; along with $log_level 3 or more (preferably 5). Ok, I'll try that. I've changed sa_debug to 1 and log_level to 5. This are

Re: [AMaViS-user] Amavis Crashes on Solaris x86

2010-09-14 Thread Mark Martinec
Ihsan, I've changed sa_debug to 1 and log_level to 5. This are the last log entries before the crash: [...] If needed, I could also provide the complete log file. Thanks. The 03003-02 is the only one whose log starts early enough to be informative. A grep on '03003-02' yields the most

Re: [AMaViS-user] Amavis Crashes on Solaris x86

2010-09-13 Thread Ihsan Dogan
Hello Mark, On 09/07/10 15:49, Mark Martinec wrote: Is this reproducible by submitting the same problematic message? Better still, reproducible using a command line spamassassin? No, unfortunately not. A detailed log may narrow down the problem area. If the crash occurs within

Re: [AMaViS-user] Amavis Crashes on Solaris x86

2010-09-07 Thread Mark Martinec
Ihsan, I've got a problem on a Solaris x86 host (running within VmWare). Recently, Amavis crashes very (core dumps) very offen and I can't find a reason why. A backtrace of the core dump: #0 0xfeb25302 in t_splay () from /lib/libc.so.1 #1 0x09a21d30 in ?? () #2 0xfebfe000 in

Re: [AMaViS-user] Amavis Crashes on Solaris x86

2010-09-07 Thread Phil Pearl (Lobbes)
this helps! Phil - Original Message - From: Ihsan Dogan ih...@dogan.ch To: amavis-user@lists.sourceforge.net Sent: Sunday, September 5, 2010 4:37:05 PM Subject: [AMaViS-user] Amavis Crashes on Solaris x86 Hello, I've got a problem on a Solaris x86 host (running within VmWare). Recently

[AMaViS-user] Amavis Crashes on Solaris x86

2010-09-05 Thread Ihsan Dogan
Hello, I've got a problem on a Solaris x86 host (running within VmWare). Recently, Amavis crashes very (core dumps) very offen and I can't find a reason why. A backtrace of the core dump: #0 0xfeb25302 in t_splay () from /lib/libc.so.1 #1 0x09a21d30 in ?? () #2 0xfebfe000 in _sys_cldlist ()