Project

General

Profile

Actions

Regression #13944

closed

PHP error in ``flock()`` during certain XMLRPC operations

Added by Jim Pingle almost 2 years ago.

Status:
Resolved
Priority:
Normal
Category:
XMLRPC
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.01
Release Notes:
Force Exclusion
Affected Version:
2.7.0
Affected Architecture:

Description

Certain XMLRPC operations generate a PHP error mentioning flock():

PHP ERROR: Type: 1, File: /etc/inc/util.inc, Line: 174, Message: Uncaught TypeError: flock(): supplied resource is not a valid stream resource in /etc/inc/util.inc:174
Stack trace:
#0 /etc/inc/util.inc(174): flock(Resource id #10, 3)
#1 /usr/local/www/xmlrpc.php(990): unlock(Resource id #10)
#2 {main}
  thrown

This does not get triggered from the base system XMLRPC calls in High Availability synchronization, but can happen with some third party code such as from the Home Assistant integration.

Christian tracked this down to a problem in the unlock() code.

This issue is for tracking purposes, a fix is already in place, 053f60e56d09ba711af245c7f0ce6a06673ccc89

Closing it as I was able to reproduce the error before, but not on a build with the fix in place. XMLRPC sync works before and after.

No data to display

Actions

Also available in: Atom PDF