IPSEC widget error
-
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-p24And 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[29816]: /index.php: XML error: no leases object found! Dec 9 16:35:51 php-fpm[16176]: /index.php: XML error: no leases object found! Dec 9 15:10:08 php-fpm[78110]: /index.php: XML error: no leases object found! -
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.
-
Chris,
Do you need more samples to narrow down this error? I can duplicate it on every 2.1.5 system.
Thank you.
-
I can duplicate it on every 2.1.5 system.
Sure like hell noone's going to be fixing anything in 2.1.5.
-
My apologies. I meant to say every 2.2.5 system. Sorry for the confusion.
Thank you.
-
This is on 2.2.6 as well… I just noticed it
-
2.3 is not affected :)
