"Please Wait" after Query, "Please Wait" never quits after Query

[gmaxwell]

I am unable to list any E-mails from the Xmail server. After hitting the Query button, the "Please wait" dialog never goes away. Does anyone have any Ideas?

[hschneider]

Wich version of XQM?
Wich OS ?
Remote or local access to the queue ?

Does it output any errors when you start it from the command prompt ?

[gmaxwell]

We are now able to view the xmail queue. It just took forever I think because of the quantity.

Thanks for the help!

[hschneider]

'think next release will get an abort button ... ;-)

[ripper951]

I am having this same problem query window never goes away.

My Xmail is on remote server on my lan.

I am running Xmail Queue Manager on a windows machine on the same lan.

Have the mailroot mapped to a drive letter on my windows machine via samab on the linux box I can access all the folders and files via that mapped drive.

When I configure and run XQM and hit query, it runs non-stop. It has been a couple hours now and its still queying ...

Any Ideas?

[hschneider]

There are huge amounts of frozen messages in your spool, more thatn the SMB protocol can handle. Use XQM or XQM/CMD on the remote machine to examine delete the frozen messages.

This slowdown isalos the reason for your XMail Server going to delay or hang.

[ripper951]

Thanks for the info I am going to test that theory tomorow by running XQM again since i have deleted all the frozen messages that were there, but I am sure there are more by now, but not as many as before.


There were about 500 frozen messages. Is that alot would that cuase XQM to behave that way?

[hschneider]

500 is not that much. Maybe there is another prob, that slows down your machine and/or network connection.

[hschneider]

I can verify this performance loss here on a Win2K machine. Seems to be the SMB protocol that is bogged down by the huge number of subdirectories and files in XMail spool. The scanned messages are coming in nearly in sequence, not in paralell. So you need approx. 3000 seconds for 3000 messages .. :-/

I'll move that filesytem intensive part to the agent, so this all happens on the remote host then. After the query, the list data is beamed to XQM. Think this will overcome any performance loss, since SMB access won't be needed anymore.

Hang on guys - I'm working on it.

[bennyp]

not to add to the problem but i was reading this post and I am having a similar problem so i downloaded the CMD version and got these stats:

./xqm -q all
--- Sending: 0, resending: 0, frozen: 0

Now if I try to access the queue from remote, I get the "Please Wait". But I have 0's across the board? Any ideas?

btw, I am running SuseLinux 8.1, new version of xmail, newest version of xqm. Trying to access with Windows XP over SMB.

Q:\=/var/MailRoot

benny

[hschneider]

If XQM reports 0 files then your Q is empty.

The ultra long wait is a problem on some Windows machines, because the SMB protocol is overloaded with the multithtreaded file search. The next release won't need SMB any longer.

[bennyp]

thanks, i will be eagerly waiting till the next release!

benny