Home > Xml Error > Xml Error No Pfsense Object Found

Xml Error No Pfsense Object Found

Pressing "Apply Changes" seemed to work, and the filter reload reported no problems. News: pfSense Gold Premium Membership!https://www.pfsense.org/gold Home Help Search Login Register pfSense Forum» pfSense English Support» Packages» XML error: no packagegui object found! « previous next » Print Pages: [1] Go Down com> Date: 2006-03-15 21:58:49 Message-ID: 823e9f970603151358p6a6a2f48na4f5866f3e7ee525 () mail ! Dec 19 10:10:07 php-fpm[43633]: /index.php: XML error: no leases object found! have a peek at this web-site

This must be why replacing the config.xml with a backup doesn't help. History #1 Updated by Jim Thompson 9 months ago Assignee set to Steve Beaver #2 Updated by Steve Beaver 9 months ago Status changed from New to Feedback Assignee changed from Shellcmd-0.5 The shellcmd utility is used to manage command... Next, I rebooted the firewall, and discovered that the new config was correctly applied.

TheresultPost by Paul Peziolis the message below. A detail list of instructions forthis would be much appreciated as I know I'll probably run into it again. Strip out the section for that package, save and reupload it again (pfSense will reboot). Edit it with a texteditor that can handle the unix specific textfile (like http://pspad.com).

Thank you for your quick reply. Do not die when parsing config since we know how to recover. As an example, I have an alias that needed updating; one IP address needed to be added. Powered by Redmine © 2006-2015 Jean-Philippe Lang [prev in list] [next in list] [prev in thread] [next in thread] List: pfsense-support Subject: RE: [pfSense Support] "XML error: no pfsense object found!"

Status:ResolvedPriority:LowAssignee:-Category:IPsecTarget version:2.2Start date:12/19/2014Due date:% Done:100% Affected version:2.2Affected Architecture:All Description Whenever I go to the index.php page, it produces the a system log entry like this: Dec 19 10:17:29 php-fpm[43222]: /index.php: XML Reload to refresh your session. I have tried to repeat this in a VirtualBox VM, but it does not fail -- applying the old configuration simply leads to the machine starting up happily with the new to Status: Dashboard - index.php: XML error: no leases object found! (IPsec Widget) Category changed from Web Interface to IPsec Status changed from New to Confirmed Affected Architecture set to All

By the way, there is another problem with sync_package. copied a backup copy and then tried to edit it again and got another error message on another line. So i recopied the backup copy and then did a factory reset \ from the console and have it back up to the webconsole. gmail !

I'll try to explain the situation using the following exceprt of sync_package: 320 if($sync_depends == true) { 321 $depends = get_pkg_depends($pkg_name, ".xml", "files", 1); // Call dependency handler and do a The resultis the message below. com> Date: 2010-02-13 5:09:07 Message-ID: 6afe4a1f1002122109q439657cfne708c4bf845a8b3b () mail ! If yes where? #6 Updated by Chris Buechler over 6 years ago Status changed from Feedback to New Target version set to 2.0 #7 Updated by Scott Ullrich over 6 years

Thinking out of the box! http://downloadmunkey.net/xml-error/xml-error-no-element-found.php I can pull up the shell from theconsole but am lost what to do from there. Status:ResolvedPriority:NormalAssignee:-Category:-Target version:2.0Start date:03/17/2010Due date:% Done:0% Affected version:AllAffected Architecture: Description In pfsense-mainline: $ git grep '\bdie\b' etc/inc/xmlparse.inc etc/inc/xmlparse.inc: die(sprintf("XML error: %s at line %d cannot occ etc/inc/xmlparse.inc: die("Error: could not open XML gwled-0.2.1 Allows you to use LEDs for gateway status on s...

Does this mean a package is corrupt? From withinteraterm past that is where I am lost.XML error: OPTXXXX at line 115 cannot occur more than onceIn vi, type::115which will take you to line 115. Otherwise its not possible to distinguish between - and -style files near pkg-utils.inc:255. #3 Updated by Ermal Lu├ži over 6 years ago Status changed from New to Feedback I think for Source Logged hoba Hero Member Posts: 5837 Karma: +7/-0 What was the problem to this solution again?

System Patches-1.0.2 A package to apply and maintain custom system ... From the posts I need to edit the config.xml file butunfortunately am not very good at CLI. I also proceeded to Reinstall the package GUI Components, same error.

What packages do you have installed?

I can pull up the shell from theconsole but am lost what to do from there. Terms Privacy Security Status Help You can't perform that action at this time. Edit it with a texteditor that can handle the unix specific textfile (like http://pspad.com). Logged Perry Hero Member Posts: 1152 Karma: +1/-0 Re: XML error: no packagegui object found! « Reply #2 on: April 19, 2008, 12:41:21 pm » Strange, did you try a reboot

In my opinion it would be better to return false or an error instead of killing the whole script - at least when a recoverable error occures (like in the last Thanks! Also make sure your pfSense is on the latest version when working with packages.This makes complete sense and is the solution to my problem. have a peek here Logged Print Pages: [1] Go Up « previous next » pfSense Forum» pfSense English Support» Packages» XML error: no packagegui object found!

Dec 19 10:04:16 php-fpm[36053]: /index.php: XML error: no leases object found! Since it is seen in 2.2.x I'll leave it for Chris. #5 Updated by Chris Buechler 9 months ago Status changed from Feedback to Resolved already fixed in 2.3 as it Later on Line 331 parse_xml_config_pkg is called with "packagegui" as the expected rootobj. Service Watchdog-1.6 Monitors for stopped services and restarts them.

Ifound the config.xml file and pulled it up with vi config.xml. the real hardware has vr[012]|ath0 and the virtual machine has em[0123] instead). Exactly where do you observe that error? #3 Updated by Alex Vergilis 9 months ago Steve, The error is observed in the system log every time index.php is loaded. Adding the IPsec widget it starts logging it in the main system log.

I went back several versions then as far back as they went (about 6 days previous to the screwup, but same result. At this point, the /cf/conf/config.xml file contained the correct changes, but the GUI didn't reflect them, and when I downloaded the configuration from the GUI, I got the old values. That should suffice to solve this. #13 Updated by Chris Buechler about 6 years ago Status changed from Feedback to Resolved Also available in: Atom PDF Loading... Ermal, please read my original proposition.