Local Delivery Serious Errors [OM 10272]

[gren]

The OM 10272 message is a wrapper message for the results of a call to the system backtracing facility. This was initially introduced to provide extra information when we
hit more serious problems and can be very useful in tracking them down.

Since then, we've used it in a few diagnostic locations where we do things that might or might not cause real issues. The problem is that we still logged these as SERIOUS ERRORs.

Regards,
Gren.

[kjakkanen]

The amount of these messages has increased in the fatal log file, is this a sign of something possibly more serious or just "normal behavior"?

-Kimmo

[gren]

Typically, there will be another message preceding this one. Depends rather on how serious that error is.

[kjakkanen]

The errors preceding are always similar to the one below:
---
ERROR Browser (Service 14 ) Fri Aug 3 13:29:39 2007
[OM 0]
Pid of logging process: 4740
Last Msg Id: 20070803142937.24394.qmail(a)wherehouse
Last Msg DirectRef: 0039c0385e9277e4
---

What do the Browser (Service 14) error mean, omsolve -n OM 0 obviously doesn't shed too much light?

-Kimmo

[gren]

> ERROR Browser (Service 14 ) Fri Aug 3 13:29:39 2007
> [OM 0]

This is almost certainly a variant of the bug http://bugzilla.scalix.com/show_bug.cgi?id=15553

Regards,
Gren.

[kjakkanen]

OK thanks Gren, is it realistic to expect this to be fixed in the next release already?

KR;
Kimmo

[gren]

Yes it is realistic The code change is present in the version currently undergoing QA.

Actually, thanks for raising this as the target milestone hadn't been set for the bug as it should have been.

Regards,
Gren.