Page 1 of 1

recover mail from poison queue

Posted: Mon Feb 25, 2008 3:22 pm
by bbryan
Hi, I need to recover some mail from the poison queue... Does anyone know how to go about doing this?

Thanks! Ben

Posted: Tue Feb 26, 2008 4:04 am
by Valerion
You can use omqdump to move it. However, mails are only moved to POISON if they caused issues in Scalix. They may not be deliverable, so you need to understand why they are in the queue.

Posted: Tue Feb 26, 2008 2:43 pm
by bbryan
Valerion wrote:You can use omqdump to move it. However, mails are only moved to POISON if they caused issues in Scalix. They may not be deliverable, so you need to understand why they are in the queue.


Thanks Valerion, I'm not trying to resubmit them, I mostly just want to recover the content of the messages before deleting them in case we need it later.

I haven't been able to figure out the criteria for messages getting in the POISON queue, I have been able to omresub the poison queue (after deleting messages I know are bad) without problems so it appears to take some messages that aren't problem messages.

I am starting to think it more has to do with what message is currently being processed when I manually kill the local delivery service (after it freezes) than with what messages actually caused it to freeze.

Thanks.
Ben

Posted: Wed Feb 27, 2008 4:00 am
by Valerion
The criteria for the POISON queue is very simple. Any message that causes a service to crash for 3 consecutive attempts is automatically moved to the POISON queue. Anything that creates some kind of error in a service, or that a service cannot handle is moved to the ERROR queue.

Posted: Thu Feb 28, 2008 10:32 am
by mikethebike
ben,

why/how are you killing the local delivery service?

If you are killing the PID(s), that is a bad thing to do :-)

If you cannot stop the service using omoff, have you tried "omsetsvc"?

Mick

Posted: Thu Feb 28, 2008 1:25 pm
by bbryan
mikethebike wrote:ben,

why/how are you killing the local delivery service?

If you are killing the PID(s), that is a bad thing to do :-)

If you cannot stop the service using omoff, have you tried "omsetsvc"?

Mick


Thanks Mick,

After local delivery freezes I run this to stop it...
# omoff -d 0 -w local
but it never works, it just hangs so I have to
# killall local.delivery
then I start it back up with
# omon -s local
then after delivering half the messages in the queue the local delivery service freezes again and I end up going through the above commands 30 or 40 times to get the queue flushed. Usually 10 or so messages will end up in the Poison queue, if I resubmit them immediately with omresub the local delivery service will freeze again, if I wait 30 minutes or so then resubmit them they go through fine. I'll try omsetsvc next time to see if it does any better.

Ben

Posted: Fri Feb 29, 2008 3:19 am
by Valerion
This is definitely something wrong with LD and/or the messages. This is something that needs to be investigated by Scalix Support, it may point to a bug in the system.

Posted: Fri Feb 29, 2008 1:21 pm
by bbryan
Valerion wrote:This is definitely something wrong with LD and/or the messages. This is something that needs to be investigated by Scalix Support, it may point to a bug in the system.


Support has been looking into it for awhile. Thanks.