Hi,

I've been using this module for a few weeks with no problems (actually very impressed at how easy it is to set up and use).

I have a mailchimp block in my page footer and also use ubercart mailchimp to place a sign up on checkout.

This week I started receiving errors on various pages (not just checkout)

warning: fsockopen() [function.fsockopen]: unable to connect to us2.api.mailchimp.com:80 (Connection timed out) in /sites/all/modules/mailchimp/MCAPI.class.php on line 1971.

It occurs even when the sign up form isn't been activated. Any help or advice much appreciated.

Comments

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented

It appears mailchimp is having issues at their servers, we are seeing this as well.

tharpa.osang’s picture

tharpa.osang commented

same thing here. In addition, the block does not even show up.

The module was working fine last week on a dev server. we went to go live and now this???

levelos’s picture

levelos commented
Status: Active » Closed (works as designed)

If the MC API is down, than obviously this module won't work, including displaying any blocks. This was actually addressed in a previous issue where we lowered the server timeout. Until a complete overhaul is undertaken where perhaps more of the MC data is cached locally, not much can be done.

canishk’s picture

canishk commented
Version: 6.x-2.3 » 6.x-2.4

While using the new stable version available is having the same issue. Is there is anything we might do to make this working ?

Please reply, is this a bug that stops its functioning ?

Regards,

Anish

canishk’s picture

canishk commented
Status: Closed (works as designed) » Active

Changed to active, I am getting this error still

Anish

levelos’s picture

levelos commented
Status: Active » Closed (works as designed)

Please don't reopen a closed issue unless you have a suggested solution. I can't think of anyway to resolve the instances of the MC API being down in this module. This has already been addressed in previous issues, and the timeout has also been decreased to reduce lag time.

davepoon’s picture

davepoon commented

I am also getting the error here...

hplunkett’s picture

hplunkett commented
Status: Closed (works as designed) » Active

I'm receiving this error periodically, and it is slowing my website to a crawl. Why should the module have to "phone-home" on each page load? Here's a suggested solution: don't try to connect to the MC API on every page load. Only connect to the MC API when a request is made through the sign up form.

Max_Headroom’s picture

Max_Headroom commented

Check with your host if they block the phpfunction fsockopen. Some are paranoid it can be used by hackers.
They recommend curl should be used. Which this module does not use.

levelos’s picture

levelos commented
Status: Active » Closed (works as designed)

> Here's a suggested solution: don't try to connect to the MC API on every page load.
It doesn't, only when it needs to determine a users subscription status to a list, namely when an authenticated user is presented with a sign up form. When initially designed, this was the only way to accurately determine a user's status in regards to a list as communication was one way, from drupal to MC. MC has since enabled a web hook system, which the 7.x-2.x version is aiming to take advantage and thus improve performance and reduce the number of requests to the API.