By InsideBevel on

Hi, I have a weird performance issue with my new Drupla 6.12 installation.
When I am logged in as administrator and click on the Administer menu, I get a very
slow responce (it takes at least 10 seconds).

Looking at the apache log I see this:
"GET .../?q=admin/reports/request-test HTTP/1.0" 200 12 "-" "Drupal (+http://drupal.org/)"

And using tcpdump on my server I find this:
...51646 > master.drupal.org.www: S 1987426451:1987426451(0) win 5840

For some reason there is made a connection to drupal.org, this doesn't look normal at all to me.
Anyone seen this before, and how to get rid of this behaviour?

Thanks
IB

⋅ Categories: Drupal 6.x

Comments

heine’s picture

heine commented

This is caused by the update status module which informs you of updates to modules and themes. You can disable the module on admin/build/modules.

InsideBevel’s picture

InsideBevel commented

That worked very well, thanks a lot guys :-)

But I could add.... It don't seem like a wise solution to check for
updates _everytime_ you click on a menu item.....

lionheart8’s picture

lionheart8 commented

Can you explain a bit more what you mean by

It don't seem like a wise solution to check for
updates _everytime_ you click on a menu item.....

If you mean you get a message telling you to check for updates everytime you click on a menu item ...
Well I dont have anything like that. The site functioned normally when I disabled that module - of course except that there was no automatic check for updates.

In the meantime as said, I re-enabled it & the site is functioning normally.

lionheart8’s picture

lionheart8 commented

Hi
As reported here http://drupal.org/node/472376, I had a problem with going to admin pages which seemed to come out of the blue. Whereas going to non-admin pages went smoothly, going to any admin page took many minutes at times & at other times ended up with page errors.
I was advised to try disabling the Update status module which I did & things returned to normal.
Since however I had had no problem with this module for years, I decided to try turning it on again the other day, since it makes it very convenient to find system & module updates and there was no problem at all, up to now. I'm still wondering what caused this.
Anyway, just give it a try.