From: http://vps05.hangarservers.net/admin/reports/event/74

From watchdog: "Failed to request next test: Server error. Requested method pifr.next not specified."

Nothing in the webserver error logs. Manual testing of HEAD works fine with no errors: http://vps05.hangarservers.net/pifr_client.php

Quick grep shows "sites/default/files/checkout/includes/xmlrpcs.inc: return xmlrpc_error(-32601, t('Server error. Requested method @methodname not specified.', array("@methodname" => $methodname)));"

PHPInfo show xmlrpc libraries are included.

Any ideas?

CommentFileSizeAuthor
#3 516966-check-url.patch1.91 KBboombatower

Comments

Amazon’s picture

Title: Failed to request next test: Server error. Requested method pifr.next not specified. » Better error message if the master URL in the configuration is not valid

I had the incorrect URL for the master. A better error message if a bad master URL is used would be great.

boombatower’s picture

hmm...basically that is handled at the xmlrpc level.

Only thing that could possibly be done is when you enter the url have it call the server via XMLRPC and see what methods it provides...and make sure they are pifr methods. That way if invalid URL or server that doesn't have PIFR server installed (like pointing to self) then it will fail.

boombatower’s picture

Assigned: Unassigned » boombatower
Category: bug » task
Status: Active » Needs review
StatusFileSize
new1.91 KB
boombatower’s picture

Status: Needs review » Fixed

Committed.

Status: Fixed » Closed (fixed)

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