Project

General

Profile

Actions

Bug #11718

closed

XMLRPC Client does not honor its default timeout value

Added by Vincent Caron 4 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
XMLRPC
Target version:
Start date:
03/22/2021
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
21.05
Release Notes:
Default
Affected Version:
2.5.0
Affected Architecture:
All

Description

I have traced an XMLRPC problem where I got a systematic mysterious error when starting a sync between my firewalls (on a dedicated crossover link) :

"A communications error occurred while attempting to call XMLRPC method host_firmware_version: @ 2021-03-19 16:30:45"

First, it turns out that the XMLRPC exception is not properly printed out which did not help to diagnose the problem. I made this simple change in xmlrpc_client.php :

- $this->error = "A communications error occurred while attempting to call XMLRPC method {$method}: " . $errormsg[1];
+ $this->error = "A communications error occurred while attempting to call XMLRPC method {$method}: " . $e->getMessage();

With this patch things started to get more helpful, the error message turned into :

"A communications error occurred while attempting to call XMLRPC method restore_config_section: Request timed out due to default_socket_timeout php.ini setting"

It turns out that php.ini has no 'default_socket_timeout', and the internal default is 60s. As a quick test I added default_socket_timeout=240 in '/etc/rc.php_ini_setup' then restarted PHP-FPM. My sync finally worked, because it turned out that it took 107s to sync (I have 253 interfaces, maybe that's related).

I think that the XMLRPC client should at least call ini_set('default_socket_timeout', $timeout) before invoking a remote method in order for it to honour its default 240s $timeout.

Actions #2

Updated by Jim Pingle 4 months ago

  • Status changed from New to Pull Request Review
  • Target version set to CE-Next
Actions #3

Updated by Jim Pingle 4 months ago

  • Subject changed from xmlrpc_client.php cannot honor its 240s default timeout because default_socket_timeout is not defined and defaults to 60s (with patch) to XMLRPC Client does not honor its default timeout value

Simplifying subject for release notes.

Actions #4

Updated by Jim Pingle 3 months ago

  • Plus Target Version set to 21.05
Actions #5

Updated by Steve Beaver 3 months ago

  • Status changed from Pull Request Review to Feedback
Actions #6

Updated by Viktor Gurov 3 months ago

  • % Done changed from 0 to 100
Actions #7

Updated by Jim Pingle 2 months ago

  • Target version changed from CE-Next to 2.5.2
Actions #8

Updated by Marcos Mendoza 2 months ago

  • Status changed from Feedback to Resolved

This fix has resolved a couple of different setups where the 60s timeout was being hit. Afterwards, the xmlrpc calls completed successfully.

Marking as resolved.

Actions #9

Updated by Renato Botelho about 2 months ago

  • Assignee set to Viktor Gurov
Actions

Also available in: Atom PDF