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

    Dansguardian Fails to start

    Scheduled Pinned Locked Moved pfSense Packages
    5 Posts 2 Posters 2.1k 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.
    • T Offline
      tj.krause
      last edited by

      Hi Guys,

      We recently switch from a Cisco PIX 535e to a pfSense box running on an Ivy Bridge core which is working quite nicely with a bit of tuning. We also have dansguardian 2.12.0.0 pkg v.0.1.6_1 (latest release) and squid 2.7.9 pkg v.4.3.1 installed which was running without any issue. We then reboot our main firewall to test out CARP which worked correctly however when the main box came back up Dansguardian would not start with the follow error in the System Log. We've tried removing the package including deleting the Dansguardian files in /usr/local/etc/dansguardian, /usr/local/pkg still without any luck. Any help would be appreciated.

      Jan 14 11:26:50 root: /usr/local/etc/rc.d/dansguardian.sh: WARNING: failed to start dansguardian
      Jan 14 11:26:50 dansguardian[47865]: Error parsing the dansguardian.conf file or other DansGuardian configuration files
      Jan 14 11:26:50 php: /pkg_mgr_install.php: Starting Dansguardian
      Jan 14 11:26:50 php: /pkg_mgr_install.php: The command '/usr/local/etc/rc.d/dansguardian.sh start' returned exit code '1', the output was 'kern.ipc.somaxconn: 16384 -> 16384 kern.maxfiles: 131072 -> 131072 kern.maxfilesperproc: 104856 -> 104856 kern.threads.max_threads_per_proc: 4096 -> 4096 Starting dansguardian. std::bad_alloc Error parsing the dansguardian.conf file or other DansGuardian configuration files /usr/local/etc/rc.d/dansguardian.sh: WARNING: failed to start dansguardian'

      Thanks!

      1 Reply Last reply Reply Quote 0
      • T Offline
        tj.krause
        last edited by

        Oh, I also forgot to mention both pfSense servers are running on version 2.0.1-RELEASE (amd64) built on Mon Dec 12 18:16:13 EST 2011 FreeBSD 8.1-RELEASE-p6

        1 Reply Last reply Reply Quote 0
        • T Offline
          tj.krause
          last edited by

          UPDATE: I believe I just found the issue, it looks like the pfSense interface for Dansguardian doesn't work correctly with many version of PCRE. We installed snort after Dansguardian and rebooted our server today expecting it to work however the issue described here http://forum.pfsense.org/index.php/topic,50688.15.html is the same issue we are having.

          1 Reply Last reply Reply Quote 0
          • T Offline
            tj.krause
            last edited by

            Solved by installing Snort then Dansguardian. Hopefully this will be fix in a future update or both our boxes will break on update to pfSense 2.1 once stable.

            1 Reply Last reply Reply Quote 0
            • marcellocM Offline
              marcelloc
              last edited by

              this is the pcre issue on dansguardian 2.12.0

              dansguardian patches are already submited to freebsd ports.

              After it, a pcre issues-free version of dansguardian package version will be released.  :)

              http://www.freebsd.org/cgi/query-pr.cgi?pr=175341

              Treinamentos de Elite: http://sys-squad.com

              Help a community developer! ;D

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