http://www.magentocommerce.com/bug-tracking/ en MagentoCommerce Copyright {gmt_date format="%Y"} {gmt_date format="%Y-%m-%dT%H:%i:%s%Q"} http://www.magentocommerce.com/bug-tracking/issue?issue=6531 Posted: 2009-06-08 10:33:49
Category: Configuration
Version: 1.3.1.1
Priority: urgent
Status: closed
Reported By: thE_iNviNciblE

Hello again,

Magentocommerce.com was down... and all of my shops also going down... the logins had taken a long time...

is it possible that on every Page Request in the Adminhtml a magento server will be connected ???

i think so, because in the down time the backend of magento doesn't react...
i'm wating for minutes for a reaction of the page request.... but if i'm loged in ... the secet url doesn't work, i will be redirected to the dashboard.... i think it's an timeout issue...

and i think @login every time the magentocommerce messages will be received and not only like in the config says 12 hours...

maybe on every page request magento will be connected ??
as magentocommerce.com was down, the whole installations are slowing down...

Thanks..

Jan Bludau

---

]]> #1 / Comment by Morningtime

I can ackknowledge this!

mag.com goes down and the admin becomes inaccessible. This is a critical bug.

The cause are two CURL functions in AdminNotification. Apparently, every single page hit in Magento backend requires a check with magentocommerce.com... When its down, the CURL takes 5 minutes to time-out. Making work impossible.

Please remove that!]]> #2 / Comment by Morningtime

By the way, I bypassed the problem by simple removing the two CURL checks from AdminNotification module.

There's two functions that do CURL, one in Data.php and one in Feed.php. I removed their contents, returning null. Then I could use the admin again.]]> #3 / Comment by thE_iNviNciblE

@Morningtime:
thanks ...

this is really a critital bug...

why on every page hit in the magento admin ??
that really slows down the backend and your own webseite... it's like an Denial of Service from all Magento installations....

this should be fixed ASAP .... 1.3.1.1.1]]> #4 / Comment by malpayne

The most disturbing thing to me is that Varien makes no acknowledgement of the issue. Nothing on the home page to let us know there even was an Issue. No apology or ?Sorry for any inconvenience? notice anywhere on the site. They will not even answer the bug posts here in a timely manner.

If they are going to program in a dependency on their site, they need to make dead sure that they have enough redundancy built in to their systems that this never happens. Some of us take orders over the phone and cannot conduct business without access to the backend. I simple acknowledgement would go a long way?]]> #5 / Comment by readmanr

They need to forkout on better hosting, end of.

http://www.magentocommerce.com/bug-tracking/issue?issue=6484]]> #6 / Comment by thE_iNviNciblE

Also related...

http://www.magentocommerce.com/bug-tracking/issue?issue=6530

and also this one:

http://www.magentocommerce.com/bug-tracking/issue?issue=6484]]> #7 / Comment by Morningtime

Maybe Varien uses these checks as hidden usage statistics? ;)]]> #8 / Comment by thE_iNviNciblE

for example moving a category ...
"Please Wait" says the DHTML backend Window" but if i press STRG + F5 on frontend its already saved... and i can see it...

i think fixing the bug would rise up the performance... :)]]> #9 / Comment by J.T.

Also note that disabling the AdminNotification module doesn't seem to actually stop these feed checks. I also had to hardcode the checks out.]]> #10 / Comment by thE_iNviNciblE

@J.T.
yes the settings doesn't work... it seems to ask on every pageload ... and on some ajax functions... like categories...

thats the problem... i think magento could react much faster if these requests will stop...]]> #11 / Comment by Pixxa

You gotta be joking me?! So our stores are depending on mage*.com.. Ive noticed mage*.com have been having problems lately, they also made some notice on twitter about it but this gotta be a joke!]]> #12 / Comment by Paul Gregory

Comparing 1.3.2.1 to 1.3.1.1 I see that a timeout (value 2) has been added, which alleviates matters and would appear to be Varien's fix for related issues.

Respondents above are saying that Magento tries to get admin notifications on every page load. Clearly that's not supposed to happen. It seems the trouble is that Magento will only skip this if it's been successful recently.

I've filed a separate bug at
http://www.magentocommerce.com/bug-tracking/issue?issue=6701]]> #13 / Comment by thE_iNviNciblE

on 1.3.2.1 these issue seems to be fixed... but now a new server

on 1.3.1.1 version i see all the time the "magento information bar" also if i had marked every item as read...]]> #14 / Comment by Magento Team

Hello thE_iNviNciblE,

This issue was fixed in latest stable release. Please check it out at http://www.magentocommerce.com/download/

Thank you.]]>