<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Upgrade 22.05 to 23.01 fails on FreeRADIUS XMLRPC Sync]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">We have four Netgate 7100's with PFSense Plus which we mainly use for OpenVPN user access. First three of them we upgraded from 22.05 to 23.01 without any issues, worked like a charm.  But on the fourth I ran into trouble.</p>
<p dir="auto">This fourth is used a bit differently than the other three. On this one we maintain the users in freeradius, which it syncs to the other three using the FreeRADIUS XMLRPC Sync.</p>
<p dir="auto">After the upgrade the system booted, but the freeradius daemon didn't start.  In the GUI there was a crash report:</p>
<hr />
<p dir="auto">Crash report begins.  Anonymous machine information:</p>
<p dir="auto">amd64<br />
14.0-CURRENT<br />
FreeBSD 14.0-CURRENT #0 plus-RELENG_23_01-n256037-6e914874a5e: Fri Feb 10 20:30:29 UTC 2023     root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/obj/amd64/VDZvZksF/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBS</p>
<p dir="auto">Crash report details:</p>
<p dir="auto">PHP Errors:<br />
[26-Mar-2023 10:34:52 Europe/Amsterdam] PHP Fatal error:  Uncaught TypeError: Cannot access offset of type string on string in /etc/inc/xmlrpc_client.inc:47<br />
Stack trace:<br />
#0 /usr/local/pkg/freeradius.inc(2505): pfsense_xmlrpc_client-&gt;__construct()<br />
#1 /usr/local/pkg/freeradius.inc(2453): freeradius_do_xmlrpc_sync('10.20.66.18', 'admin', 'qTEDrc5HiLsE9zF', '443', 'https', '150')<br />
#2 /usr/local/pkg/freeradius.inc(794): freeradius_sync_on_changes()<br />
#3 /etc/inc/pkg-utils.inc(715) : eval()'d code(2): freeradius_users_resync()<br />
#4 /etc/inc/pkg-utils.inc(715): eval()<br />
#5 /etc/rc.start_packages(66): sync_package('freeradius3')<br />
#6 {main}<br />
thrown in /etc/inc/xmlrpc_client.inc on line 47</p>
<p dir="auto">No FreeBSD crash data found.</p>
<hr />
<p dir="auto">After some investigation I found that the xmlrpc  sync-config seems to be the problem:</p>
<hr />
<p dir="auto">PHP ERROR: Type: 1, File: /etc/inc/xmlrpc_client.inc, Line: 47, Message: Uncaught TypeError: Cannot access offset of type string on string in /etc/inc/xmlrpc_client.inc:47<br />
Stack trace:<br />
#0 /usr/local/pkg/freeradius.inc(2505): pfsense_xmlrpc_client-&gt;__construct()<br />
#1 /usr/local/pkg/freeradius.inc(2453): freeradius_do_xmlrpc_sync('1.2.3.4', 'admin', '*******', '443', 'https', '150')<br />
#2 /usr/local/pkg/freeradius.inc(794): freeradius_sync_on_changes()<br />
#3 /etc/inc/pkg-utils.inc(715) : eval()'d code(2): freeradius_users_resync()<br />
#4 /etc/inc/pkg-utils.inc(715): eval()<br />
#5 /etc/rc.start_packages(66): sync_package('freeradius3')<br />
#6 {main}<br />
thrown @ 2023-03-26 10:34:52</p>
<hr />
<p dir="auto">When I remove that piece from a saved config.xml and import that config, the freeradius daemon starts, and seems OK.<br />
Then I tried to add the sync configuration, thinking it might help to make a fresh configuration. Adding seemed to work, but when I tried to enable the sync (tick enable, en save) another PHP error appeared in the GUI (3 of these):</p>
<hr />
<p dir="auto">Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /etc/inc/xmlrpc_client.inc:47 Stack trace: #0 /usr/local/pkg/freeradius.inc(2505): pfsense_xmlrpc_client-&gt;__construct() #1 /usr/local/pkg/freeradius.inc(2453): freeradius_do_xmlrpc_sync('1.2.3.4', 'admin', '********', '443', 'https', '150')</p>
<hr />
<p dir="auto">Uninstalling freeradius package and installing it again doesn't help.<br />
Also extra reboots won't help.</p>
<p dir="auto">So it looks freeradius seems to work for me on the three boxes which don't use the FreeRADIUS XMLRPC Sync, but it's broken on the one which uses the Sync.</p>
<p dir="auto">Luckily I could rollback easily using Boot Environments (hurray for ZFS!!!).  I can out of time and had to roll back to 22.05, we have a working setup again.</p>
<p dir="auto">Is this a known issue?  Any solution availabled for this?</p>
<p dir="auto">Kind regards,<br />
Jos Andel</p>
]]></description><link>https://forum.netgate.com/topic/179059/upgrade-22-05-to-23-01-fails-on-freeradius-xmlrpc-sync</link><generator>RSS for Node</generator><lastBuildDate>Fri, 10 Apr 2026 12:05:36 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/179059.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 27 Mar 2023 08:20:09 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Upgrade 22.05 to 23.01 fails on FreeRADIUS XMLRPC Sync on Sun, 02 Apr 2023 13:28:55 GMT]]></title><description><![CDATA[<p dir="auto">The filed bug gave a good hint about not having an empty HA-Sync configuration under 'System'. I've put a username and password in that configuration to make sure it's not empty.</p>
<p dir="auto">This results in a working upgrade, and working Freeradius after upgrade. XMLRPC also works fine after the upgrade.</p>
]]></description><link>https://forum.netgate.com/post/1097616</link><guid isPermaLink="true">https://forum.netgate.com/post/1097616</guid><dc:creator><![CDATA[jos-andel]]></dc:creator><pubDate>Sun, 02 Apr 2023 13:28:55 GMT</pubDate></item><item><title><![CDATA[Reply to Upgrade 22.05 to 23.01 fails on FreeRADIUS XMLRPC Sync on Mon, 27 Mar 2023 11:06:40 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/jos-andel">@<bdi>jos-andel</bdi></a><br />
<a href="https://redmine.pfsense.org/issues/14182" target="_blank" rel="noopener noreferrer nofollow ugc">Bug filed by Netgate Support </a>:  https://redmine.pfsense.org/issues/14182</p>
]]></description><link>https://forum.netgate.com/post/1096572</link><guid isPermaLink="true">https://forum.netgate.com/post/1096572</guid><dc:creator><![CDATA[jos-andel]]></dc:creator><pubDate>Mon, 27 Mar 2023 11:06:40 GMT</pubDate></item></channel></rss>