Re: Issue with MantisConnect And email_queue_api.php
Damien Regad <[email protected]> Thu, 19 Jun 2014 12:22:38 +0200
| Newsgroups | gmane.comp.bug-tracking.mantis.general |
|---|---|
| Message-ID | <[email protected]> |
Hi Stanislas,
On 2014-06-19 08:25, Stanislas Kita wrote:
> [Mon Jun 16 11:30:16 2014] [error] [client 10.0.0.128]
> [mantisconnect.php] Error Type: SYSTEM NOTICE,\n Error *Description:
> unserialize(): Error at offset 185 of 249 bytes* \ nStack
> Trace:\nemail_queue_api.php L118
Are you using a customized version of MantisBT ? On 1.2.17, there is no
unserialize() call at line 118 [1] (it's actually on line 121). If
that's the case, please check if the problem is reproducible on standard
code.
[1]
https://github.com/mantisbt/mantisbt/blob/release-1.2.17/core/email_queue_api.php#L118
> unserialize(<string>'a:4:{s:8:"priority";s:1:"3";s:7:"charset";
> s:11:"iso-8859-15";s:8:"hostname";s:22:"********";s:7:"headers";a:2:{
> s:8:"keywords";s:39:"[Fonds documentaires] scripts d\\'export";
> s:11:"In-Reply-To";s:34:"<2f034b8cb3d79e3d4563b0e0ad013749>";}}')
At first glance, (excluding the "********" string which is probably you
manually masking sensitive data) I'd guess the error is due to escaping
in "d\\'export". How does the raw data in email queue table look ?
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems