slow authentication popup in 2.5.0: dtml-sendmail in standard_error_message on winnt 4
AFAIK Hans is doing all this testing on a Windows 98 machine, not his production system, so it's reasonable that he'd experience differences between his production setup and his test setup.
It is a windows nt machine not a w98. More testing: Clean installations, only with a mailhost it is de <dtml-sendmail> in the standard_error_message that does it. Removing it from the standard_error_message makes the authentication popup show immediately. In 2.4.3 the <dtml-sendmail> is not causing a pauze in the authentication popup to show. I took a different machine, also a windows nt 4.0 machine. The same. Then i tested it on our production server (don't tell my boss). That is a windows 2000 machine. There the problem does not show up. Ah, could it be OS dependent? Another windows 2000 machine No problem A windows 95 machine. It took 8 seconds for the authentication popup to show, without the sendmail it popped up immediately. Why would a sendmail in an error_message cause the authentication popup to wait for 25 seconds to show up,? even in the case that there is a misconfiguration of ..things.. I don't see the connection Is it OS related? It seems to be. Suggestions for more tests? Hans de Wit Stichting Farmaceutische Kengetallen Postbus 30460 2500 GL DEN HAAG Tel. 070-3737448 Fax 070-3737445
what happens is that standard error message gets called whenever someone authenticates for the first time, meaning whenever they get the username/password popup. even though you never see the rendered standard_error_message its code gets executed. your standard_error_message tries to send mail and that's where the DNS lookup stuff comes in. i have to second chris in his opinion that this is due to DNS lookup problems on that particular machine. jens On Friday, February 15, 2002, at 07:27 , H.de.Wit@SFK.NL wrote:
AFAIK Hans is doing all this testing on a Windows 98 machine, not his production system, so it's reasonable that he'd experience differences between his production setup and his test setup.
It is a windows nt machine not a w98.
More testing: Clean installations, only with a mailhost it is de <dtml-sendmail> in the standard_error_message that does it. Removing it from the standard_error_message makes the authentication popup show immediately. In 2.4.3 the <dtml-sendmail> is not causing a pauze in the authentication popup to show.
I took a different machine, also a windows nt 4.0 machine. The same.
Then i tested it on our production server (don't tell my boss). That is a windows 2000 machine. There the problem does not show up.
Ah, could it be OS dependent?
Another windows 2000 machine No problem
A windows 95 machine. It took 8 seconds for the authentication popup to show, without the sendmail it popped up immediately.
Why would a sendmail in an error_message cause the authentication popup to wait for 25 seconds to show up,? even in the case that there is a misconfiguration of ..things.. I don't see the connection Is it OS related? It seems to be.
Suggestions for more tests?
Hans de Wit
On Fri, 15 Feb 2002 H.de.Wit@SFK.NL wrote:
More testing: Clean installations, only with a mailhost it is de <dtml-sendmail> in the standard_error_message that does it. Removing it from the standard_error_message makes the authentication popup show immediately.
Are your MailHost instances using the same SMTP host whatever Zope server you test on ? Could you try to send a message from each host using the MailHost code outside of Zope and see the result ? (I don't know if this is feasable or not, however) Jerome Alet
Another thing to try is to temporarily insert the line: import pdb; pdb.set_trace() ... on your test system at mabe line 130 in lib/python/Products/MailHost.py (inside the send method). Then, run Zope in debug mode (e.g. "start.bat -D") and try to authenticate with your hacked standard_error_message. You will likely be thrown into the Python debugger. Continue to hit "n"<return> (next statement, skips over subroutines) or "s"<return> (next statement, skips into subroutines) until you find the line or funciton causing the slowdown. (To get out of the debugger, press "c" several times and then press ctrl-C). When you find out where it's slowing things down (or maybe it doesn't even get called!) report back. HTH, - C Jerome Alet wrote:
On Fri, 15 Feb 2002 H.de.Wit@SFK.NL wrote:
More testing: Clean installations, only with a mailhost it is de <dtml-sendmail> in the standard_error_message that does it. Removing it from the standard_error_message makes the authentication popup show immediately.
Are your MailHost instances using the same SMTP host whatever Zope server you test on ?
Could you try to send a message from each host using the MailHost code outside of Zope and see the result ? (I don't know if this is feasable or not, however)
Jerome Alet
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"
At 09:27 a.m. 15/02/02, you wrote:
AFAIK Hans is doing all this testing on a Windows 98 machine, not his production system, so it's reasonable that he'd experience differences between his production setup and his test setup.
It is a windows nt machine not a w98.
More testing: Clean installations, only with a mailhost it is de <dtml-sendmail> in the standard_error_message that does it. Removing it from the standard_error_message makes the authentication popup show immediately. In 2.4.3 the <dtml-sendmail> is not causing a pauze in the authentication popup to show.
I took a different machine, also a windows nt 4.0 machine. The same.
Then i tested it on our production server (don't tell my boss). That is a windows 2000 machine. There the problem does not show up.
Ah, could it be OS dependent?
I don't think so. I have the same problem on a Windows 2000. I have installed Zope 2.4.4 and Zope 2.5. Both worked allright 'till I changed a couple of services' configuration option and now they have the same problem.
Another windows 2000 machine No problem
A windows 95 machine. It took 8 seconds for the authentication popup to show, without the sendmail it popped up immediately.
Lucky you! my authentication popup takes about 25 seconds to show up!
Why would a sendmail in an error_message cause the authentication popup to wait for 25 seconds to show up,?
I have the standard_error_message that comes with Zope. Didn't change it at all.
even in the case that there is a misconfiguration of ..things.. I don't see the connection Is it OS related? It seems to be.
Suggestions for more tests?
Do you start/stop any service before the problem? Maybe it's the same cause. Nico.-
I don't think so. I have the same problem on a Windows 2000. I have installed Zope 2.4.4 and Zope 2.5. Both worked allright 'till I changed a couple of services' configuration option and now they have the same problem.
What configuration options did you change?
Lucky you! my authentication popup takes about 25 seconds to show up!
This also sounds like DNS. Can your machine resovle its own hostname? (e.g. "nslookup frobnitz" where frobnitz is the windows machine name?)
I have the standard_error_message that comes with Zope. Didn't change it at all.
Your problem seems related to Hans but it's probably a different cause. I'd suggest making sure: - your machine can resolve its own hostname. (frobnitz -> 127.0.0.1) - your machine can reverse-resolve its IP address. (63.102.41.55 -> frobnitz.mydomain.com) - your machine "points to itself' when it reverse-resolves its IP address. (frobnitz.mydomain.com -> 63.102.41.55) -- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"
participants (5)
-
Chris McDonough -
H.de.Wit＠SFK.NL -
Jens Vagelpohl -
Jerome Alet -
Nicolas Rodriguez