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

RESOLVED: SNMP configuration yields error in logs

Scheduled Pinned Locked Moved SNMP
2 Posts 1 Posters 2.3k 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
    cs1
    last edited by Jan 22, 2016, 7:19 AM Jan 21, 2016, 12:21 PM

    Dear all,

    we're currently deploying pfSense at our university as our new primary guest access solution. Everything works smoothly. Thanks to all developers and contributers for all the hard work you put into this project!  :)

    The only problem we have right now is SNMP. When we activate SNMP in "Services: SNMP", no matter what interface we bind the SNMP daemon to, the configuration fails and we get a log entry of the following kind:

    php-fpm[54501]: /services_snmp.php: XML error: Undeclared entity error at line 147 in /conf/config.xml
    php-fpm[54501]: /services_snmp.php: pfSense is restoring the configuration /cf/conf/backup/config-XXX.xml
    php-fpm[54501]: /services_snmp.php: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-XXX.xml
    

    I haven't found any clues via the search function regarding whether or not this is a known issue. Do you have any idea why we see this message? After pfSense restored the old config, all SNMP functionality is deactivated again. Any ideas? Thanks for your help!

    1 Reply Last reply Reply Quote 0
    • C
      cs1
      last edited by Jan 22, 2016, 7:18 AM

      I found the cause of the problem. I used a special character ("ß") in the SNMP location field which is not valid (I simply overlooked that error). However, I was able to enter it on the "Services: SNMP" page and it caused a hick-up in the configuration. I think it might be a good idea to check that only USASCII characters are used for sysLocation and sysContact.

      1 Reply Last reply Reply Quote 0
      2 out of 2
      • First post
        2/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received