Project

General

Profile

Bug #6328

stale xmlrpc.lock can make config sync stop functioning

Added by Chris Buechler over 3 years ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Category:
XMLRPC
Target version:
Start date:
05/06/2016
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

If anything prevents unlock($xmlrpclockkey); in xmlrpc.php from being hit, the config sync will stop functioning until the lock is removed. In the case I saw, hitting #6177 while the primary was doing a config sync was adequate to make that happen.

When that happens, you're going to be stuck in a situation where you need to restart php-fpm, so that should clear that lock if it exists.

Associated revisions

Revision 96a399cb (diff)
Added by Chris Buechler over 3 years ago

Clear xmlrpc.lock when restarting php-fpm. Ticket #6328

Revision 8ad194c0 (diff)
Added by Chris Buechler over 3 years ago

Clear xmlrpc.lock when restarting php-fpm. Ticket #6328

History

#1 Updated by Chris Buechler over 3 years ago

  • Status changed from Confirmed to Feedback

fix pushed

#2 Updated by Chris Buechler over 3 years ago

  • Status changed from Feedback to Resolved

works

#3 Updated by Jim Pingle 4 months ago

  • Category changed from 62 to XMLRPC

Also available in: Atom PDF