[Work Around] 50k+ messages in Corrupt Message Queue

Discuss the Scalix Server software

Moderators: ScalixSupport, admin

thardison
Posts: 10
Joined: Wed Mar 28, 2007 11:12 am

[Work Around] 50k+ messages in Corrupt Message Queue

Postby thardison » Fri May 11, 2007 9:34 am

I had inadvertently created a mail loop with Archiver, and came in to find that I had 50,000+ messages in the Corrupt Message Queue. I've fixed the loop so it wont happen again, but I have some left-over garbage.

There are some legitimate messages in there, and I would like to just "blow away" the unwanted messages. I've already been using omtidyallu to clear out the messages from mailboxes:

Code: Select all

omtidyallu -d -k -T i -S -t "failure notice"

Is there a similar method for removing the messages from the "Corrupt Message Queue"?

-- Tyler
Last edited by thardison on Fri May 11, 2007 12:39 pm, edited 2 times in total.

thardison
Posts: 10
Joined: Wed Mar 28, 2007 11:12 am

Postby thardison » Fri May 11, 2007 9:36 am

And if anyone is curious, omshowlog shows this:

Code: Select all

WARNING                        Local Delivery(Local Delivery) 05.11.07 04:19:13
[OM 2213] Unable to allocate memory. malloc errno 12 size 208
Current errno value: 12
  Last Msg Id: 25543.21221178804950.avalon.bayfed.com


ERROR                          Local Delivery(Local Delivery) 05.11.07 04:19:13
[OM 2207] Unable to allocate memory.
Current errno value: 12
  Last Msg Id: 25543.21221178804950.avalon.bayfed.com
        <- ld_ExtractOrigRecip
        -> ld_DeliverMsgToRecip
        -> nm_ParseORN
        <- nm_ParseORN
        -> ul_FindRecipient
        -> ul_utGetUserEntry
        -> nm_ParseORN
        <- nm_ParseORN
        -> dr_ACIModContextFlags
        <- dr_ACIModContextFlags
        <- /build/11.0.4/src/lib/ombase/os/os_mem.c:97[100,2207]
        <- /build/11.0.4/src/lib/ombase/vi/vi_locks.c:323[100,2207]
        <- /build/11.0.4/src/lib/ombase/vi/vi_locks.c:201[100,2207]
        <- /build/11.0.4/src/lib/ombase/dr/dr_search.c:470[100,2207]
        <- /build/11.0.4/src/lib/ombase/ul/ul_FindPU.c:290[100,2207]
        <- /build/11.0.4/src/bin/ld/ld_main.c:1405[100,2207]

For each message.

ScalixSupport
Scalix
Scalix
Posts: 5503
Joined: Thu Mar 25, 2004 8:15 pm

Postby ScalixSupport » Fri May 11, 2007 10:03 am

Hi!

Use omqdump to delete messages from the queue. Password for omqdump is same as that
for omcontain.

Thanks,
Subir

thardison
Posts: 10
Joined: Wed Mar 28, 2007 11:12 am

Postby thardison » Fri May 11, 2007 10:08 am

Subir, what about the legitimate messages that are also jammed in there?

thardison
Posts: 10
Joined: Wed Mar 28, 2007 11:12 am

Postby thardison » Fri May 11, 2007 12:38 pm

What I am doing as a temporary work around, is to dump 1000 messages at a time into the router queue, then using omtidyallu to remove the offending messages. However this is going to take me some time.

ScalixSupport
Scalix
Scalix
Posts: 5503
Joined: Thu Mar 25, 2004 8:15 pm

Postby ScalixSupport » Mon May 14, 2007 2:02 am

Hi!

For the error you get:
ERROR Local Delivery(Local Delivery) 05.11.07 04:19:13
[OM 2207] Unable to allocate memory.

to know more about the error code, run the command omsolve -n OM 2207 , it describes
that you are getting this error, because of the shortage of Virtual Memory.

The above error might also be caused because, JVM, might require a higher file descriptor
limit. If an application can't open files because the file descriptor limit has been exceeded,
you might get a NoClassDefFoundError error message. Increase the limit by issuing the
command:

Code: Select all

ulimit -n 10000

Once this is done try resubmitting the legitimate messages using command omresub, see
the man pages for details.

Thanks,
Subir

thardison
Posts: 10
Joined: Wed Mar 28, 2007 11:12 am

Postby thardison » Tue May 15, 2007 7:15 pm

Thanks Subir, this was also helpful.


Return to “Scalix Server”



Who is online

Users browsing this forum: No registered users and 2 guests

cron