Having just enabled the module, I moved the supercron.php file to the root of drupal and then tried to access the supercron interface only to be presented with a raft of errors all starting "warning: fsockopen() [function.fsockopen]: unable to connect to :80 (Connection refused) " relating to line 208 of 'sites/all/modules/supercron/supercron.inc' ( is obviously a substitue for the real URL). The list of errors now appears at the top of all pages. Any ideas? I have disabled the module in the meantime.

CommentFileSizeAuthor
#5 supercron.absolute-url.patch476 bytespillarsdotnet

Comments

jpcwebb’s picture

Status: Active » Closed (fixed)

Have mucked about with the config and it seems to have gone away - not sure what that was about...closing.

jpcwebb’s picture

Status: Closed (fixed) » Active

Sorry, reopening - having had problems with v2.x-dev I am reverting to 1.3 as it is too buggy. But this particular error seems to be related to supercorn.inc which seems to rely on opening a http socket to invoke tasks, but in my case and in others I suspect, my host blocks http loopbacks to the site to (presumably) stop scripts acting as proxies and loading the server. Thus the only way for me to run scripts is directly with the php binary. This option should be built in for users with shared hosting that has restrictions on opening sockets IMO.

sinasalek’s picture

Same for me. I think an alternative way in case of shared severs would be a nice feature.

sashainparis’s picture

Status: Active » Needs review

Make URL be absolute seems toresolve this issue

line 445s

        if ($this->multithread OR $forced_multithreading) {
            $url = str_replace('%', $this->module_name, supercron_registry()->get_external_invocation_url());
            $url = url($url,array(absolute => TRUE));
            _supercron_parallel_call($url);
        }
pillarsdotnet’s picture

StatusFileSize
new476 bytes

Patch.

pillarsdotnet’s picture

abandoned module?

pillarsdotnet’s picture

Status: Needs review » Closed (duplicate)