Mollom has been a great SPAM solution for us, but starting just today, all our attempts to connect with Mollom fail, generating log messages that say "Error 900: Network error" and "Response: -1 request timed out". We're on Drupal 7.15 with Mollom 7.x-2.2 and I'm able to establish a connection to the Mollom servers using "wget http://rest.mollom.com/v1/content".

Interestingly, when on /admin/config/content/mollom/settings the screen shows the message "Mollom servers verified your keys. The services are operating correctly". However, when the configuration is saved, the log contains a message "API keys could not be verified".

The full (redacted) message is ...

Error 900: Network error.

Error 900: Network error.
Request: POST http://rest.mollom.com/v1/content

postBody = 'sopyiasovc
sopyiasovc3@gmail.com
123456
unconscious behaviors once these tasks are mastered. ,http://www.vanlug.bc.ca/node/19070
'
authorIp = '127.0.0.1'
checks =
0 = 'spam'
1 = 'profanity'
strictness = 'normal'

Request headers:

Accept = 'application/xml, application/json;q=0.8, */*;q=0.5'
Content-Type = 'application/x-www-form-urlencoded'
Authorization = 'OAuth oauth_consumer_key="[redacted]", oauth_version="1.0", oauth_nonce="[redacted]", oauth_timestamp="1348800388", oauth_signature_method="HMAC-SHA1", oauth_signature="[redacted]"'

Response: -1 request timed out

Error 900: Network error.
Request: POST http://rest.mollom.com/v1/content

postBody = 'sopyiasovc
sopyiasovc3@gmail.com
123456
unconscious behaviors once these tasks are mastered. ,http://www.vanlug.bc.ca/node/19070
'
authorIp = '127.0.0.1'
checks =
0 = 'spam'
1 = 'profanity'
strictness = 'normal'

Request headers:

Accept = 'application/xml, application/json;q=0.8, */*;q=0.5'
Content-Type = 'application/x-www-form-urlencoded'
Authorization = 'OAuth oauth_consumer_key="[redacted]", oauth_version="1.0", oauth_nonce="[redacted]", oauth_timestamp="1348800391", oauth_signature_method="HMAC-SHA1", oauth_signature="[redacted]"'

Response: -1 request timed out

Comments

MercuryPDX’s picture

MercuryPDX CreditAttribution: MercuryPDX commented

Same issue, different version:

API keys could not be verified.
Error 900: Network error.
Request: POST http://rest.mollom.com/v1/site/[KEY WAS HERE BUT I DELETED IT FOR POST]
  platformName = 'Drupal'
  platformVersion = '6.26'
  clientName = 'Mollom'
  clientVersion = '6.x-2.1'

...

Response: -1 request timed out

API keys could not be verified.

Same message in the config module:

    The configuration options have been saved.
    Mollom servers verified your keys. The services are operating correctly.

EDIT: Checking through the logs, this started happening: 09/27/2012 - 10:49am Pacific Time. It was operating just fine before that.

kenwest’s picture

kenwest CreditAttribution: kenwest commented

I note that the request timeout is set to 3 seconds on line 106 of includes/mollom.class.inc

When I increase this value, the REST call sometimes succeeds. Here are the results of a single trial for different timeout values.

3s = fail
4s = fail
10s = fail
11s = success
12s = fail
13s = success

When I set the timeout to 20s it works 4 times out 5, and it works 3 times out of 5 when the timeout is 30s!

When I try to connect to the Mollom REST server I get mixed results.

Here's a connection that works (except I get a failure for using a GET rather than a POST). It returns a response in 5 seconds.

wget http://rest.mollom.com/v1/content
--2012-09-28 15:14:31-- http://rest.mollom.com/v1/content
Resolving rest.mollom.com (rest.mollom.com)... 67.228.84.11
Connecting to rest.mollom.com (rest.mollom.com)|67.228.84.11|:80... connected.
HTTP request sent, awaiting response... 405 Method Not Allowed
2012-09-28 15:14:36 ERROR 405: Method Not Allowed.

Here's a response that fails. Each attempt times out after roughly 30s.

wget http://rest.mollom.com/v1/content
--2012-09-28 15:09:55-- http://rest.mollom.com/v1/content
Resolving rest.mollom.com (rest.mollom.com)... 174.37.205.152
Connecting to rest.mollom.com (rest.mollom.com)|174.37.205.152|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2012-09-28 15:10:32-- (try: 2) http://rest.mollom.com/v1/content
Connecting to rest.mollom.com (rest.mollom.com)|174.37.205.152|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2012-09-28 15:11:07-- (try: 3) http://rest.mollom.com/v1/content
Connecting to rest.mollom.com (rest.mollom.com)|174.37.205.152|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2012-09-28 15:12:03-- (try: 4) http://rest.mollom.com/v1/content
Connecting to rest.mollom.com (rest.mollom.com)|174.37.205.152|:80... connected.
HTTP request sent, awaiting response... No data received.
Retrying.

--2012-09-28 15:12:39-- (try: 5) http://rest.mollom.com/v1/content
Connecting to rest.mollom.com (rest.mollom.com)|174.37.205.152|:80... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
2012-09-28 15:13:05 ERROR 503: Service Unavailable.

I'm setting my timeout to 30s until this is sorted.

kenwest’s picture

kenwest CreditAttribution: kenwest commented

Our first "900" message came through at 2012-09-28 03:54 AEST (Sydney time) which is 5 minutes later than the first one @MercuryPDX observed

TimG1’s picture

TimG1 CreditAttribution: TimG1 commented
Status: Active » Closed (duplicate)

Hi All,

Mollom has been having some issues recently. They noted this on their twitter feed and there's another issue going on about this. (#1797182: The spam filter installed on this site is currently unavailable) Going to mark this one as duplicate. They have a patch over on that one that increases the timeout, which is seems like some of you have already tried.

Thanks for reading,
-Tim

kenwest’s picture

kenwest CreditAttribution: kenwest commented

Thanks, Tim!