Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Hi all,
Since updating to 6.x-2.2 all my Mollom events in /admin/reports/dblog say Error 900: Network error. (174.37.205.152) (see attached)
Any ideas please?
Thanks...
Comment | File | Size | Author |
---|---|---|---|
#16 | debug-request-timeout.patch | 396 bytes | sun |
#4 | dblog.jpg | 79.14 KB | Juc1 |
#4 | event.jpg | 84.54 KB | Juc1 |
mollom error 900-4.jpg | 57.6 KB | Juc1 | |
mollom error 900-3.jpg | 107.84 KB | Juc1 |
Comments
Comment #1
Juc1 CreditAttribution: Juc1 commentedJust to add it worked fine before updating to 6.x-2.2 but anyone trying to add a comment now gets this:
Comment #2
Juc1 CreditAttribution: Juc1 commented/admin/settings/mollom/settings =
Mollom servers verified your keys. The services are operating correctly.
/admin/reports/status =
Mollom API keys: Service error
The Mollom API keys could not be verified. Please try again later.
Comment #3
sunHm. That is odd.
The module stores the last known status in a variable, so as to not have to re-check and re-verify the API keys all over again.
Normally, when you visit the Mollom settings page, the API keys are validated and the status is updated accordingly.
I don't understand why your Status report still shows an error, after positively confirming your API keys on the settings page.
Can you try that again and check your logs for messages in the mollom category directly afterwards? (You can copy+paste the detailed log messages into a text file and attach that here.)
Comment #4
Juc1 CreditAttribution: Juc1 commented@ sun thanks for your reply...
Sorry - try what again?
I resaved 'save configuration' at /admin/settings/mollom/settings but no difference. I have attached the event log and one example and copied the text below.
By the way if necessary can I revert to the 6.x-1. version for now or will that cause a problem with my database?
Thanks...
Comment #5
sunThe actual error that you get is: Response: -1 request timed out
This means that your client/site is not able to connect to Mollom servers for some reason. To be safe, I double-checked and all Mollom servers are up and running right now.
Do you have command line access to that server? If you do, can you try whether you can
ping 174.37.205.152
and alsotelnet 174.37.205.152 80
?In any case, is it possible that there is a firewall that blocks outgoing requests from your site/server to other servers?
Comment #6
Juc1 CreditAttribution: Juc1 commentedRe the firewall suggestion the thing is that it all worked fine before I updated to 6.x-2.2. Anyway does this help?
Thanks...
Comment #7
sunHm, your ping actually stated this:
I also double-checked that and you should get 100% results (no packet loss). So this pretty much looks like something is wrong in the networking layer on your server.
The upgrade to 2.x is not really relevant here. The only difference between 1.x and 2.x is that 1.x communicated over XML-RPC HTTP requests and 2.x communicates over RESTful HTTP requests. Both essentially talk to the same target Mollom servers, only the data that is transmitted in the HTTP request body is different.
I'd recommend to consult your hosting provider or server administrator with this information to have them investigate why so many packets are getting lost.
Comment #8
Juc1 CreditAttribution: Juc1 commentedOk but I have now pinged again about 5 times and it is 0% packet loss each time.
I guess it could be a coincidence but the problem seemed to start precisely when I updated to 6.x-2.2 so could I revert to the 6.x-1. version for now or will that cause a problem with my database?
Thanks...
Comment #9
sunThat appears to be coincidence from my perspective.
As with any other Drupal module, you can only upgrade - downgrading is never supported.
If you really want to, then you'd have to disable and uninstall the 2.x version, and afterwards, replace the module with the 1.x version and re-install + configure that from scratch.
I'd be very surprised if that would make a difference though.
I just tested connectivity from a few servers that are distributed across the globe, and all of them were able to verify Mollom API keys and communicate with Mollom servers correctly.
Comment #10
Juc1 CreditAttribution: Juc1 commentedOk so I uninstalled 6.x-2.2 and I reinstalled 6.x-1.6 and everything seems to be ok again.
There is no longer an error message on /admin/reports/status (it does not mention Mollom at all so maybe Mollom is only mentioned when there is an error).
I will get round to updating to 6.x-2.2 on a clone site.
Thanks...
Comment #11
sunYes, we should get to the bottom of this.
That is, because the 1.x series is effectively discontinued (and borderline unsupported) by now.
I do not understand why your site is able to make XML-RPC HTTP requests, but not pure/RESTful HTTP requests. As mentioned before, the requests are hitting the same servers. Only the parameters/data that is being sent is in a different format.
Please let me know of whatever you're able to find out! :)
Comment #12
sunHi @Juc1,
I'm planning to publish a new 6.x-2.3 release today, which contains some important bug fixes — unrelated to this issue. However, if there's anything in the current code that might prevent the module to connect to Mollom servers in certain environments or under certain circumstances, then we might be able to quickly fix that.
Were you able to test once more on a clone site, as you mentioned?
Thanks,
sun
Comment #13
Juc1 CreditAttribution: Juc1 commented@ sun sorry I have only just done the test. I installed a fresh install of Drupal 6.28 and Mollom 6.x-2.3 (no other modules) on a new domain on the same server. I go to admin/settings/mollom/settings and enter my Mollom keys. It tells me "The Mollom servers could not be contacted. Please make sure that your web server can make outgoing HTTP requests."
I will try some more tomorrow but if it is like the other domain mentioned above then Mollom will start to work if I uninstall 6.x-2.3 and install 6.x-1.6...
Comment #14
sunAny chance you could create an admin account for me, so I can look into the site? (Use my contact form to send credentials)
Comment #15
Juc1 CreditAttribution: Juc1 commentedTest domain =
Mollom 6.x-2.3 - "The Mollom servers could not be contacted. Please make sure that your web server can make outgoing HTTP requests."
Mollom 6.x-1.6 - "Mollom servers verified your keys. The services are operating correctly."
Comment #16
sunIf you don't want or cannot provide me an account, could you try whether the change in attached patch makes any difference?
Comment #17
sunHi @Juc1, were you able to test whether the change in #16 makes any difference on your site?
Comment #18
Juc1 CreditAttribution: Juc1 commented@ sun sorry, I got distracted. I applied the patch and it did not make a difference. I will contact you about the login.
Thanks...
Comment #19
sun@Juc1: I didn't receive a mail yet and hope it didn't get lost or something. Did you send it already?
Comment #20
sunSorry, without further information this issue can only be closed as not reproducible.
Feel free to re-open this issue if you want to provide further information. Thanks.
Comment #21
eporama CreditAttribution: eporama commentedI have this same problem. I think I have more information that might help diagnose.
Drupal watchdog shows:
but the reverse nslookup of that IP:
Gives the xmlrpc2.mollom.com name, but the forward lookup on this is the other address 173.193.242.189
Here's some more tests which show that I can curl glb.mollom.com but not rest.mollom.com in this scenario.
And I also verified that the timeout patch in #16 did not help.
Comment #22
eporama CreditAttribution: eporama commentedAnd... realized 10 seconds after posting that in troubleshooting mollom problems a while ago, we had manually set rest.mollom.com in /etc/hosts and I had never undone that.
Comment #22.0
eporama CreditAttribution: eporama commentedx