[Kolab-devel] opensuse native kolabmailboxfilter php segfault

[Gunnar Wrobel]

Quoting Richard Bos <ml at radoeka.nl>:

> Hi Alar,
>
> Op dinsdag 05 mei 2009 16:10:34 schreef Alar Sing:
>> Hello,
>>
>> I have problem with kolabmailboxfilter in opensuse native kolab
>> installation. Attached logs are from postfix and kolab filter
>> This segfault occures when user tries to sent an invite to a resource
> account
>> that is configured to auto accept invites. After getting a bounce message
>> saying that php has died with signal 11 user gets accept from resource.
>>
>> And segfault messega from syslog
>> May  5 14:10:59 linux kernel: php5[4305]: segfault at 4c503d48 ip
>> 081b0473 sp bfed4d7c error 4 in php5[8048000+23d000]
>>
>> php version is 5.2.9 in opensuse
>>
>> What could be causing this?
>
> No Idea ;)  The line to look at in your original posting is this one:
> May  5 14:10:59 linux postfix/pipe[4304]: 3951113235C: to=<resource at domain>,
> relay=kolabmailboxfilter, delay=1.6, delays=0.09/0.01/0/1.5, dsn=5.3.0,
> status=bounced (Command died with signal 11: "/usr/bin/php5")
> (just for others, so they don't need to look carefully to the log files).

This line

May 05 14:10:58 Kolab Filter [error] [horde] PHP Error:  
file_get_contents(/tmp/Kolab_Filter_locks/resource at domain.lock):  
failed to open stream: No such file or directory; Code: 0 [on line 146  
of "/usr/share/php5/PEAR/Horde/Kolab/Filter/Response.php"]

looks problematic, too.

It seems the lock directory has been left unconfigured or does not exist.

Has

$conf['kolab']['filter']['simple_locks_dir']

been set for the Kolab_Filter configuration? And does it contain a  
valid directory?

Nevertheless even this should not lead to a segfault. I did not test  
php-5.2.9 yet.

Cheers,

Gunnar

>
> The To address looks strange to me: "resource at domain".  Did you edit it?
> Would it be possible to add printf statements, to obtain more information in
> the log file(s)?  It's a pity that the timestamp does not include
> milliseconds, that would make it easier to interleave the filter.log and
> mail.log.  Perhaps it is possible with the printf statements to find  
> the line,
> that is the reason for the segmentation fault....
>
> Oh, and at openSUSE we use kolab-filter-0.1.5
>
> --
> Richard
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
--------------------------------------------------------------------
    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.kolab.org/pipermail/devel/attachments/20090507/40a92949/attachment.sig>