Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Config.xml failed to open stream…etc/incxmlparse.inc, no xmp input

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 1.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      conservctionnw
      last edited by

      Hello, I am not a regular user or networking expert; I work for a small non-profit that had a pfSense firewall set up on a Soekris net4801. The person who set it up has disappeared. When moving our office today, I attempted to log on via a console cable to change the IP addresses, which I sort of know how to do, but it froze up and had to be hard-rebooted. Now, while it manages to boot all the way to the console setup menu, I receive the error:

      Warning: fopen(/conf/config.xml): failed to open stream: No such file or directory in /etc/inc/xmlparse.inc on line 149. Error: could not open xml input

      Only the shell (#8), PfTop (9), and traffic logs (10) from the menu work; the rest return same error

      The only thing I can see in the bootup that might be an issue is a line reading: pci0 <bridge>at device 18.1 (no driver attached)
      and then later the same error for device 18.5, but I don't know if that was all there before the disaster

      If you have any ideas, please let me know. RIght now I am sleeping on the new office floor (don't live here)
      into tomorrow so I can try again in AM

      THANK YOU and YOU ALL ROCK!!!</bridge>

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob
        last edited by

        The only thing I can see in the bootup that might be an issue is a line reading: pci0 <bridge>at device 18.1 (no driver attached)
        and then later the same error for device 18.5, but I don't know if that was all there before the disaster</bridge>

        A lot of chipsets include devices like sound which are of little use in a router/firewall. This is probably a report of such a device.

        Warning: fopen(/conf/config.xml): failed to open stream: No such file or directory in /etc/inc/xmlparse.inc on line 149. Error: could not open xml input

        I suspect this is telling you the main configuration file (/conf/config.xml) is missing OR its badly formed. It may have been "corrupted" when the system "froze" while you were attempting to change the IP addresses. Do you have a backup of the configuration file?

        On my system in /conf/backup there are a number of files that appear to be backups of the config.xml file. Someone else who knows the details better tham I do may be able to advise if such a file can be used to restore the config file.

        Once you get a config file you could reboot then use the web GUI to change the IP addresses and save the new config file. (This is often a lot easier than connecting the console port to something suitable.)

        You said the system "froze up". Maybe you didn't wait long enough. (The CPU in the Soekris is not fast by modern PC standards but still fast enough for many applications.) I think I've seen at least a few cases of reboot/startup when it has looked as if my system (VIA C3 800MHz CPU) had frozen but a bit more patience revealed it was still making progress. On reboot or startup if you don't see anything happen for 10 seconds you probably need to wait a bit longer before deciding its frozen. If you see 10 minutes go by without seeing any change there probably isn't much point waiting any longer. If you have ongoing responsibilities for this system it might be worth doing a few reboots and configuration changes to get a feel for the timing.

        1 Reply Last reply Reply Quote 0
        • C
          conservctionnw
          last edited by

          Thanks so much.  I found those backups,  looked up the unix commands, took a deep breath, and replaced the bad file with my fingers crossed and eyes closed. Nice to know being brave every once in a while pays off.  :)

          All is well now…with that part anway; getting the cable company to set up their end correctly is a post for another board.

          And you are right, I probably was impatient while on that console set up (and by using it at all instead of waiting for the wiring in the office to be done). Hard enough to figure all this out as I go along without the whole staff breathing down your neck because they haven't had email for 12 hours--I should have slowed down. I have learned my lesson! My staff and the wild critters we work so hard to protect thank you too.

          Barbara
          Conservation Northwest
          www.conservationnw.org
          Keeping the Northest wild!

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.