IPSEC widget error
SoloIT last edited by
I'm getting the following error when the IPSec dashboard widget is on:
php-fpm: /index.php: XML error: no leases object found!
I see there was a bug filed (https://redmine.pfsense.org/issues/4130) and fixed for the same issue. Any guidance would be appreciated.
I also came upon this issue and noticed the bug fix SoloIT highlighted. Was this not merged into the main branch?
morrisasapmsp last edited by
Saw the original bug request while searching, and then fell upon this thread. I've just received this as well while running trace routes to various locations. GUI would not load for about three minutes.
Dec 9 12:08:43 php-fpm: /index.php: XML error: no leases object found! Dec 9 12:17:10 php-fpm: /index.php: XML error: no leases object found! Dec 9 12:17:10 php-fpm: /index.php: XML error: no leases object found!
There are multiple reasons you can get that message. The one in the linked bug ticked was fixed before 2.2.0 release and hasn't been a problem in any release version. The other reasons it can be encountered no longer exist at all in 2.2.5 as the IPsec status no longer uses the strongswan SMP plugin. So, upgrade.
@cmb, I'm already running latest stable release 2.2.5
"no leases object found" does not exist anywhere in the code of 2.2.5.
Interesting… seems like we've entered the Twilight Zone on this one....
2.2.5-RELEASE (i386) built on Wed Nov 04 15:50:18 CST 2015 FreeBSD 10.1-RELEASE-p24
And here it is again, a couple minutes ago after I refreshed the Dashboard with the IPsec widget shown (as noted in the reported bug)
Dec 9 16:37:26 php-fpm: /index.php: XML error: no leases object found! Dec 9 16:35:51 php-fpm: /index.php: XML error: no leases object found! Dec 9 15:10:08 php-fpm: /index.php: XML error: no leases object found!
dotdash last edited by
I'm getting this on a 2.2.5 full (amd64) install that had the config from a 2.1.5 nano (i386) box loaded on it. Remove the ipsec widget from the dashboard and it goes away, add it back and the error returns.
I see where it's happening, it's not the same as previous (that code doesn't exist anymore), just something the XML parser spits out when trying to read empty XML and it fills in the tag it's looking for.
I'll either fix it when I have a moment later, or open a new bug ticket. It's just harmless log spam where you have no connected mobile users in this case.
vergilis last edited by
Do you need more samples to narrow down this error? I can duplicate it on every 2.1.5 system.
doktornotor Banned last edited by
I can duplicate it on every 2.1.5 system.
Sure like hell noone's going to be fixing anything in 2.1.5.
vergilis last edited by
My apologies. I meant to say every 2.2.5 system. Sorry for the confusion.
luckman212 last edited by
This is on 2.2.6 as well… I just noticed it
maverick_slo last edited by
2.3 is not affected :)