Stipe,

Can you provide us some more lines before the first PANIC?!

Unfortunately the logs have since rotated away into oblivion. Here is a more recent panic from a couple of days ago as well. Note that this log file will also rotate into oblivion in another 12 hours or so.


2005-02-15 19:29:49 [31332] [0] WARNING: WTP: got a truncated datagram, ignoring
2005-02-15 19:29:49 [31332] [0] PANIC: wap/wap_events.c:218: wap_event_assert: Assertion `event != NULL' failed.
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(gw_panic+0x19a) [0x80d03f7]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(wap_event_assert+0x40) [0x808c19c]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(wtp_unpack_wdp_datagram+0x1f0) [0x80a4674]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(wap_dispatch_datagram+0xa4) [0x8081fb8]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox(main+0x481) [0x8056480]
2005-02-15 19:29:49 [31332] [0] PANIC: /lib/libc.so.6(__libc_start_main+0xc0) [0x402de460]
2005-02-15 19:29:49 [31332] [0] PANIC: /usr/local/sbin/wapbox [0x8054611]


The above is all I really have for this one. The log-level is turned down quite a bit due to all of the traffic we get. I can't run it at debug or anything like that.

And also please use 'addr2line' to resolve the source code lines of the backtrace addresses, see 'man addr2line' for details on how to use.

What am I doing wrong here?

# addr2line -e /usr/local/sbin/wapbox 80d03f7
??:0

# addr2line -e /usr/local/sbin/wapbox 0x80d03f7
??:0

Jon



Reply via email to