Looks like a crash after a failed character set conversion. This
would happen in the content adaptation module. Will investigate.
Just saw your posts to mantis and will apply!
On Jan 10, 2006, at 16:41, Loïc Minier wrote:
Hi,
I've seen a new mmsproxy crash, very different to the one I reported
earlier, and this time on a system witout any memory constraint.
From
mmsgw.log:
2006-01-10 13:06:57 [26907] [0] INFO: Called "/bin/echo 'y'",
returned msisdn = y
2006-01-10 13:06:58 [26907] [60] ERROR: Failed to convert string
from <iso-8859-1> to <US-ASCII>, errno was <84>
2006-01-10 13:07:43 [26907] [0] INFO: Calling "/bin/echo 'y'"
2006-01-10 13:07:43 [26907] [0] INFO: Called "/bin/echo 'y'",
returned msisdn = y
2006-01-10 13:07:43 [26907] [61] ERROR: Failed to convert string
from <iso-8859-1> to <US-ASCII>, errno was <84>
2006-01-10 13:07:43 [26907] [61] PANIC: gwlib/octstr.c:2326:
seems_valid_real: Assertion `ostr != NULL' failed. (Called from
gwlib/octstr.c:852:octstr_compare.)
2006-01-10 13:07:43 [26907] [61] PANIC: /usr/bin/mmsproxy(gw_panic
+0x19a) [0x808b9d7]
2006-01-10 13:07:43 [26907] [61] PANIC: /usr/bin/mmsproxy [0x8093860]
2006-01-10 13:07:43 [26907] [61] PANIC: /usr/bin/mmsproxy
(octstr_compare+0x4c) [0x808f7eb]
2006-01-10 13:07:43 [26907] [61] PANIC: /usr/bin/mmsproxy [0x8066698]
2006-01-10 13:07:43 [26907] [61] PANIC: /usr/bin/mmsproxy
(mms_transform_msg+0x55) [0x80672a8]
2006-01-10 13:07:43 [26907] [61] PANIC: /usr/bin/mmsproxy [0x8053218]
2006-01-10 13:07:43 [26907] [61] PANIC: /usr/bin/mmsproxy [0x8081a7e]
2006-01-10 13:07:43 [26907] [61] PANIC: /lib/tls/libpthread.so.0
[0xb7eb0b63]
2006-01-10 13:07:43 [26907] [61] PANIC: /lib/tls/libc.so.6(__clone
+0x5a) [0xb7c7018a]
What's particularly strange is that no traffic seems visible
around the
crash, in my access log, all I see is:
2006-01-10 13:06:58 Fetched MMS [INT:MM1] [ACT:] [MMSC:]
[from:foobar] [to:y/TYPE=PLMN] [msgid:3-35-
[EMAIL PROTECTED] [size=26030] [UA:SAGEM-myV-65/2.1
Profile/MIDP-2.0 Configuration/CLDC-1.0 UP.Browser/6.2.2.5.d.2
(GUI) MMP/1.0] [MMBox:]
(The 'y' here is a bit strange too, I suspect the detokenizer
might not
work properly, I have:
detokenizer-library = /usr/lib/mbuni/libmms_detokenize_shell.so
detokenizer-module-parameters = /bin/echo)
However, from the proxy server that protects mmsproxy itself, I can
see:
192.168.98.22 - - [10/Jan/2006:13:06:57 +0100] [dummy/sid#81439a8]
[rid#819cfc0/initial] (2) init rewrite engine with requested uri /
[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:06:57 +0100] [dummy/sid#81439a8]
[rid#819cfc0/initial] (2) rewrite /[EMAIL PROTECTED]/y
-> http://127.0.0.1:8191/[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:06:57 +0100] [dummy/sid#81439a8]
[rid#819cfc0/initial] (2) forcing proxy-throughput with http://
127.0.0.1:8191/[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:06:57 +0100] [dummy/sid#81439a8]
[rid#819cfc0/initial] (1) go-ahead with proxy request proxy:http://
127.0.0.1:8191/[EMAIL PROTECTED]/y [OK]
192.168.98.22 - - [10/Jan/2006:13:07:43 +0100] [dummy/sid#81439a8]
[rid#81b5020/initial] (2) init rewrite engine with requested uri /
[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:07:43 +0100] [dummy/sid#81439a8]
[rid#81b5020/initial] (2) rewrite /[EMAIL PROTECTED]/y ->
http://127.0.0.1:8191/[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:07:43 +0100] [dummy/sid#81439a8]
[rid#81b5020/initial] (2) forcing proxy-throughput with http://
127.0.0.1:8191/[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:07:43 +0100] [dummy/sid#81439a8]
[rid#81b5020/initial] (1) go-ahead with proxy request proxy:http://
127.0.0.1:8191/[EMAIL PROTECTED]/y [OK]
192.168.98.22 - - [10/Jan/2006:13:07:45 +0100] [dummy/sid#81439a8]
[rid#81b3018/initial] (2) init rewrite engine with requested uri /q-
[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:07:45 +0100] [dummy/sid#81439a8]
[rid#81b3018/initial] (2) rewrite /[EMAIL PROTECTED]/y -
> http://127.0.0.1:8191/[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:07:45 +0100] [dummy/sid#81439a8]
[rid#81b3018/initial] (2) forcing proxy-throughput with http://
127.0.0.1:8191/[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:07:45 +0100] [dummy/sid#81439a8]
[rid#81b3018/initial] (1) go-ahead with proxy request proxy:http://
127.0.0.1:8191/[EMAIL PROTECTED]/y [OK]
192.168.98.22 - - [10/Jan/2006:13:07:46 +0100] [dummy/sid#81439a8]
[rid#81b7028/initial] (2) init rewrite engine with requested uri /
[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:07:46 +0100] [dummy/sid#81439a8]
[rid#81b7028/initial] (2) rewrite /[EMAIL PROTECTED]/y ->
http://127.0.0.1:8191/[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:07:46 +0100] [dummy/sid#81439a8]
[rid#81b7028/initial] (2) forcing proxy-throughput with http://
127.0.0.1:8191/[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:13:07:46 +0100] [dummy/sid#81439a8]
[rid#81b7028/initial] (1) go-ahead with proxy request proxy:http://
127.0.0.1:8191/[EMAIL PROTECTED]/y [OK]
The logs probably indicate timeouts occured after the crash, a normal
fetch looks like this:
192.168.98.22 - - [10/Jan/2006:08:25:12 +0100] [dummy/sid#81439a8]
[rid#8194fa0/initial] (2) init rewrite engine with requested uri /w-
[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:08:25:12 +0100] [dummy/sid#81439a8]
[rid#8194fa0/initial] (2) rewrite /[EMAIL PROTECTED]/
y -> http://127.0.0.1:8191/[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:08:25:12 +0100] [dummy/sid#81439a8]
[rid#8194fa0/initial] (2) forcing proxy-throughput with http://
127.0.0.1:8191/[EMAIL PROTECTED]/y
192.168.98.22 - - [10/Jan/2006:08:25:12 +0100] [dummy/sid#81439a8]
[rid#8194fa0/initial] (1) go-ahead with proxy request proxy:http://
127.0.0.1:8191/[EMAIL PROTECTED]/y [OK]
and a post:
192.168.98.22 - - [10/Jan/2006:08:25:23 +0100] [dummy/sid#81439a8]
[rid#8198fb0/initial] (2) init rewrite engine with requested uri /
123456
192.168.98.22 - - [10/Jan/2006:08:25:23 +0100] [dummy/sid#81439a8]
[rid#8198fb0/initial] (2) rewrite /123456 -> http://
127.0.0.1:8191/123456
192.168.98.22 - - [10/Jan/2006:08:25:23 +0100] [dummy/sid#81439a8]
[rid#8198fb0/initial] (2) forcing proxy-throughput with http://
127.0.0.1:8191/123456
192.168.98.22 - - [10/Jan/2006:08:25:23 +0100] [dummy/sid#81439a8]
[rid#8198fb0/initial] (1) go-ahead with proxy request proxy:http://
127.0.0.1:8191/123456 [OK]
After a glance at the source code, it seems to me the stack trace is
incomplete, and I have no idea what kind of trafic caused the crash.
Cheers,
--
Loïc Minier <[EMAIL PROTECTED]>
Current Earth status: NOT DESTROYED
_______________________________________________
Devel mailing list
Devel@mbuni.org
http://mbuni.org/mailman/listinfo/devel_mbuni.org
_______________________________________________
Devel mailing list
Devel@mbuni.org
http://mbuni.org/mailman/listinfo/devel_mbuni.org