Hi,

I keep seeing the following in my logs, right after this issue cron jobs also display as failed or stuck, I keep seeing the same error even after Cron runs successfully. Does the cron job failing have anything to do with mollom and what's error 110?


	Error -110 from http://82.103.131.136: Connection timed out - mollom.getImageCaptcha -

Array
(
    [author_ip] => 208.36.144.10
)

Comments

dries’s picture

dries commented
Status: Active » Fixed

Fixed!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

dakku’s picture

dakku commented

HI,
I am getting the exact same error

Error -110 from http://174.37.205.152: Connection timed out - mollom.getImageCaptcha -

Array
(
[author_ip] => 89.151.84.35
)

I am running D6 + latest Mollom CVS

Any ideas?

hansrossel’s picture

hansrossel commented

Same thing here but for Mollom 5 - 1.7.

Error -110 from http://88.151.243.81: 110 Connection timed out - mollom.getImageCaptcha -
Array
(
[author_ip] => 81.246.127.226
)

hansrossel’s picture

hansrossel commented
Category: support » bug
Priority: Normal » Critical

Marking as critical bug because several users complain it is not possible anymore to register because Mollom captcha is never accepted.

hansrossel’s picture

hansrossel commented
Status: Closed (fixed) » Active
dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Postponed (maintainer needs more info)

This probably means that your server cannot make outbound requests. The error handling has been improved in Mollom 6.x-1.8 and above, so upgrading is highly recommended.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Postponed (maintainer needs more info) » Fixed

No response in over two months. Marking as fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

HS’s picture

HS commented
Status: Closed (fixed) » Active

I'm on 6.x 1.10 and still seeing this error in my logs.

HS’s picture

HS commented
Version: 6.x-1.6 » 6.x-1.10

Still seeing this error. Here's more from my log:

	Error -110 from http://174.37.205.152: Connection timed out - mollom.getImageCaptcha -

Array
(
    [author_ip] => 67.195.115.248
)

Changed version to 6.x-1.10 because I am experiencing these errors on the new version of this module.

dries’s picture

dries commented
Priority: Critical » Normal
Status: Active » Fixed

We made some changes to our webservers so this should now be a lot better. Reopen if this is still a problem.

HS’s picture

HS commented
Priority: Normal » Critical
Status: Fixed » Active

My log today is filled with pages and pages of the following:

Error -110 from http://174.37.205.152: Connection timed out - mollom.getImageCaptcha -

Array
(
[author_ip] => 64.94.67.203
)

HS’s picture

HS commented

@Dries

Mate could you be kind enough to tell me what this error really means? Am I loosing any comments?

dries’s picture

dries commented

It means we couldn't serve a CAPTCHA because of a network error either on our side, or on your side.

You're not loosing comments depending on how you configured the Mollom fallback strategy. Check your Mollom settings.

We'll investigate the time-outs because those shouldn't happen. It might not something on our side though.

pixelpreview@gmail.com’s picture

pixelpreview@gmail.com commented

today same error on my site with last version of drupal and mollom
I use ajax comment too

Error -110 from http://174.37.205.152: Connection timed out - mollom.getImageCaptcha -
Array
(
[author_ip] => 82.243.49.92
)

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Active » Postponed (maintainer needs more info)

Setting as needs more info. Most likely an infrastructure issue and Dries is best to investigate 'em.

HS’s picture

HS commented
Issue tags: +Mollom

Hi Dries,

Thanks for the response. Happy new year.

If the fallback strategy is to allow all comments including SPAM, then it's not much of a strategy, nor a solution. Can't risk allowing spammers to have a free hand when Mollom servers are down.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Postponed (maintainer needs more info) » Fixed

Marking as fixed for now, as the server-side issues seem to be resolved.

Further, technical investigation for the client-side happens in #507896: XML-RPC communication errors are not properly caught (What does Error -60 mean?)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

HS’s picture

HS commented
Status: Closed (fixed) » Active

Pages and pages of my logs are filled with the following today:

Error -110 from 'http://174.37.205.152' for 'mollom.getImageCaptcha': 'Connection timed out'
Data:

  author_ip = '1.......0'
  ssl = false
HS’s picture

HS commented

Now seeing the following errors on my logs, possibly related to the same issues the Mollom servers are experiencing these days.

All servers unreachable or returning errors. The server list was emptied.
sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)
Issue tags: -Mollom

@HS: Do you still experience this issue? We had a temporary server hiccup in the past days, but that should be resolved by now.

ebeyrent’s picture

ebeyrent commented

I just got this error this morning, running on 6.x-1.15.

Type	mollom
Date	Wednesday, December 8, 2010 - 1:42am
User	Anonymous
Location	http://mysite.com/user/register
Referrer	http://mysite.com/user/register
Message	Error -110 from 'http://174.37.205.152' for 'mollom.checkContent': 'Connection timed out' 
Data:
  post_body = 'tokrenttt'
  author_name = 'tokrenttt'
  author_mail = 'tokrenta@kiralikaraclar.org'
  author_ip = '78.160.30.198'
  session_id = ''
  checks = 'spam'
Severity	debug
HS’s picture

HS commented

Not seeing the errors these days.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Postponed (maintainer needs more info) » Fixed

OK, I'm going to mark this issue as resolved now.

It is possible that this message is getting logged from time to time (for example, one of the Mollom servers is being restarted), but the client-side server fallback handling that is implemented in the module should automatically resolve the issue by skipping to the next server in the known server list.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

ebeyrent’s picture

ebeyrent commented

This looks good - I haven't seen the errors in a few days. Thanks!