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

    Latest snapshots (i386,full) DIOCADDRULE device busy+cannot define table bogons

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    24 Posts 8 Posters 7.5k 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
      clarknova
      last edited by

      2.0-BETA4 (i386)
      built on Mon Nov 15 17:03:26 EST 2010
      FreeBSD 8.1-RELEASE-p1
      nanobsd

      I get this from time to time:

      
There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy The line in question reads [ DIOCADDRULE]:

      db

      1 Reply Last reply Reply Quote 0
      • M
        mxx
        last edited by

        After upgrading to todays snapshot, I don't get the following error anymore:
        "/tmp/rules.debug:204: cannot define table bogons: Device busy pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [204]: table <bogons>persist file "/etc/bogons"

        I still get the same error as Clarknova though on boot.</bogons>

        1 Reply Last reply Reply Quote 0
        • M
          mxx
          last edited by

          Okay, unfortunately I got

          php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was '/tmp/rules.debug:198: cannot define table bogons: Device busy pfctl: Syntax error in config file: pf rules not loaded'

          4 hours after upgrading to that snapshot.

          Here's the snippet from rules.debug. Line 198 is in bold:

          SSH lockout

          block in log quick proto tcp from <sshlockout>to any port 65002 label "sshlockout"
          block in quick from <virusprot>to any label "virusprot overload table"
          table <bogons>persist file "/etc/bogons"
          # block bogon networks

          http://www.cymru.com/Documents/bogon-bn-nonagg.txt

          block in log quick on $UPC from <bogons>to any label "block bogon networks from UPC"
          antispoof for em3

          block anything from private networks on interfaces with the option set

          antispoof for $UPC
          block in log quick on $UPC from 10.0.0.0/8 to any label "block private networks from wan block 10/8"
          block in log quick on $UPC from 127.0.0.0/8 to any label "block private networks from wan block 127/8"
          block in log quick on $UPC from 172.16.0.0/12 to any label "block private networks from wan block 172.16/12"
          block in log quick on $UPC from 192.168.0.0/16 to any label "block private networks from wan block 192.168/16"

          $UPC is my first "WAN" interface.

          I now upgraded to Sun Nov 21 02:37:38 ..</bogons></bogons></virusprot></sshlockout>

          1 Reply Last reply Reply Quote 0
          • M
            mxx
            last edited by

            Any news about those DIOCADDRULE errors?

            Is this something to worry about?
            If someone could explain what this error is about it would be very nice to know ;)

            Thank you!

            1 Reply Last reply Reply Quote 0
            • E
              eri--
              last edited by

              Please wait for a snapshot to come after this post and try to see if it fixes the error.

              1 Reply Last reply Reply Quote 0
              • AhnHELA
                AhnHEL
                last edited by

                Using 2.0-BETA4 (amd64)
                built on Mon Nov 29 23:16:42 UTC 2010

                Error still exists

                AhnHEL (Angel)

                1 Reply Last reply Reply Quote 0
                • E
                  eri--
                  last edited by

                  Can you show me your system logs?
                  Possibly other info from the system?

                  1 Reply Last reply Reply Quote 0
                  • AhnHELA
                    AhnHEL
                    last edited by

                    I'm running in a ESXi virtualized environment but from what I've read its the same error others are seeing with full installs on dedicated hardware.

                    Nov 29 22:55:50 	kernel: VMware memory control driver initialized
Nov 29 22:55:50 	sshlockout[37131]: sshlockout v2.0 starting up
Nov 29 22:55:50 	sshlockout[37131]: sshlockout v2.0 starting up
Nov 29 22:55:50 	login: login on ttyv0 as root
Nov 29 22:55:49 	php: : Resyncing configuration for all packages.
Nov 29 22:55:48 	miniupnpd[21227]: Listening for NAT-PMP traffic on port 5351
Nov 29 22:55:48 	miniupnpd[21227]: Listening for NAT-PMP traffic on port 5351
Nov 29 22:55:48 	miniupnpd[21227]: HTTP listening on port 2189
Nov 29 22:55:48 	miniupnpd[21227]: HTTP listening on port 2189
Nov 29 22:55:48 	php: miniupnpd: Starting service on interface: lan
Nov 29 22:55:48 	php: : Creating rrd update script
Nov 29 22:55:43 	php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Nov 29 22:55:43 	php: : DynDns: Cached IP: xxx.xxx.xxx.xxx
Nov 29 22:55:43 	php: : DynDns: Current WAN IP: xxx.xxx.xxx.xxx
Nov 29 22:55:43 	php: : DynDns debug information: xxx.xxx.xxx.xxx extracted from local system.
Nov 29 22:55:43 	php: : DynDns: _checkIP() starting.
Nov 29 22:55:43 	php: : DynDns: _detectChange() starting.
Nov 29 22:55:43 	php: : DynDns: updatedns() starting
Nov 29 22:55:43 	php: : DynDns: Running updatedns()
Nov 29 22:55:43 	dnsmasq[56517]: read /etc/hosts - 2 addresses
Nov 29 22:55:43 	dnsmasq[56517]: using nameserver xxx.xxx.xxx.xxx#53
Nov 29 22:55:43 	dnsmasq[56517]: using nameserver xxx.xxx.xxx.xxx#53
Nov 29 22:55:43 	dnsmasq[56517]: reading /etc/resolv.conf
Nov 29 22:55:43 	check_reload_status: updating all dyndns
Nov 29 22:55:43 	dnsmasq[56517]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP
Nov 29 22:55:43 	dnsmasq[56517]: started, version 2.55 cachesize 10000
Nov 29 22:55:42 	dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Nov 29 22:55:42 	dhcpd: All rights reserved.
Nov 29 22:55:42 	dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Nov 29 22:55:42 	dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1
Nov 29 22:55:41 	php: : ROUTING: change default route to xxx.xxx.xxx.xxx
Nov 29 22:55:41 	check_reload_status: reloading filter
Nov 29 22:55:40 	kernel: ovpnc3: link state changed to UP
Nov 29 22:55:38 	apinger: Starting Alarm Pinger, apinger(25355)
Nov 29 22:55:38 	php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was 'pfctl: DIOCADDRULE: Device busy'
Nov 29 22:55:37 	apinger: Exiting on signal 15.
Nov 29 22:55:37 	php: : There were error(s) loading the rules: pfctl: Duplicate signature for AIX 4.3 : File exists pfctl: Duplicate signature for AIX 4.3 : File exists pfctl: Duplicate signature for AIX 4.3 2: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 2-3: File exists pfctl: Duplicate signature for AIX 4.3 2: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 2-3: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 5.1 : File exists pfctl: Duplicate signature for AIX 5.2 : File exists pfctl: Duplicate signature for AIX 5.1-5.2 : File exists pfctl: Duplicate signature for AIX 5.1 : File exists pfctl: Duplicate signature for AIX 5.2 : File exists pfctl: Duplicate signature for AIX 5.1-5.2 : File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4
Nov 29 22:55:37 	php: : New alert found: There were error(s) loading the rules: pfctl: Duplicate signature for AIX 4.3 : File exists pfctl: Duplicate signature for AIX 4.3 : File exists pfctl: Duplicate signature for AIX 4.3 2: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 2-3: File exists pfctl: Duplicate signature for AIX 4.3 2: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 2-3: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 5.1 : File exists pfctl: Duplicate signature for AIX 5.2 : File exists pfctl: Duplicate signature for AIX 5.1-5.2 : File exists pfctl: Duplicate signature for AIX 5.1 : File exists pfctl: Duplicate signature for AIX 5.2 : File exists pfctl: Duplicate signature for AIX 5.1-5.2 : File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate si
Nov 29 22:55:37 	php: : There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy - The line in question reads [ DIOCADDRULE]:
Nov 29 22:55:37 	php: : New alert found: There were error(s) loading the rules: pfctl: DIOCADDRULE: Device busy The line in question reads [ DIOCADDRULE]:
Nov 29 22:55:37 	php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was 'pfctl: Duplicate signature for AIX 4.3 : File exists pfctl: Duplicate signature for AIX 4.3 2: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 2-3: File exists pfctl: Duplicate signature for AIX 4.3 2: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 2-3: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 5.1 : File exists pfctl: Duplicate signature for AIX 5.2 : File exists pfctl: Duplicate signature for AIX 5.1-5.2 : File exists pfctl: Duplicate signature for AIX 5.1 : File exists pfctl: Duplicate signature for AIX 5.2 : File exists pfctl: Duplicate signature for AIX 5.1-5.2 : File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AI
Nov 29 22:55:37 	php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was 'pfctl: Duplicate signature for AIX 4.3 : File exists pfctl: Duplicate signature for AIX 4.3 2: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 2-3: File exists pfctl: Duplicate signature for AIX 4.3 2: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 2-3: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AIX 5.1 : File exists pfctl: Duplicate signature for AIX 5.2 : File exists pfctl: Duplicate signature for AIX 5.1-5.2 : File exists pfctl: Duplicate signature for AIX 5.1 : File exists pfctl: Duplicate signature for AIX 5.2 : File exists pfctl: Duplicate signature for AIX 5.1-5.2 : File exists pfctl: Duplicate signature for AIX 4.3 3: File exists pfctl: Duplicate signature for AI
Nov 29 22:55:37 	php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was '/tmp/rules.debug:59: cannot define table direct_networks: Device busy /tmp/rules.debug:85: cannot define table bogons: Device busy pfctl: Syntax error in config file: pf rules not loaded'
Nov 29 22:55:37 	inetd[59970]: Accessing /var/etc/inetd.conf: No such file or directory, continuing anyway.
Nov 29 22:55:37 	inetd[59970]: Accessing /var/etc/inetd.conf: No such file or directory, continuing anyway.
Nov 29 22:55:36 	apinger: Starting Alarm Pinger, apinger(35530)
Nov 29 22:55:36 	kernel: pflog0: promiscuous mode enabled
Nov 29 22:55:36 	check_reload_status: reloading filter
Nov 29 22:55:36 	check_reload_status: reloading filter
Nov 29 22:55:36 	kernel: Trying to mount root from ufs:/dev/da0s1a
Nov 29 22:55:36 	kernel: SMP: AP CPU #3 Launched!
Nov 29 22:55:36 	kernel: SMP: AP CPU #1 Launched!
Nov 29 22:55:36 	kernel: SMP: AP CPU #2 Launched!
Nov 29 22:55:36 	kernel: da0: 8192MB (16777216 512 byte sectors: 255H 63S/T 1044C)
Nov 29 22:55:36 	kernel: da0: Command Queueing enabled
Nov 29 22:55:36 	kernel: da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit)
Nov 29 22:55:36 	kernel: da0: <vmware virtual="" disk="" 1.0="">Fixed Direct Access SCSI-2 device
Nov 29 22:55:36 	kernel: da0 at mpt0 bus 0 scbus0 target 0 lun 0
Nov 29 22:55:36 	kernel: acd0: DVDR <vmware virtual="" ide="" cdrom="" drive="" 00000001="">at ata1-master UDMA33
Nov 29 22:55:36 	kernel: IPsec: Initialized Security Association Processing.
Nov 29 22:55:36 	kernel: Timecounters tick every 10.000 msec
Nov 29 22:55:36 	kernel: ppc0: cannot reserve I/O port range
Nov 29 22:55:36 	kernel: vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Nov 29 22:55:36 	kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Nov 29 22:55:36 	kernel: sc0: <system console="">at flags 0x100 on isa0
Nov 29 22:55:36 	kernel: orm0: <isa option="" roms="">at iomem 0xc0000-0xc7fff,0xca000-0xcafff,0xcb000-0xcbfff,0xdc000-0xdffff,0xe0000-0xe3fff on isa0
Nov 29 22:55:36 	kernel: psm0: model IntelliMouse, device ID 3
Nov 29 22:55:36 	kernel: psm0: [ITHREAD]
Nov 29 22:55:36 	kernel: psm0: [GIANT-LOCKED]
Nov 29 22:55:36 	kernel: psm0: <ps 2="" mouse="">irq 12 on atkbdc0
Nov 29 22:55:36 	kernel: atkbd0: [ITHREAD]
Nov 29 22:55:36 	kernel: atkbd0: [GIANT-LOCKED]
Nov 29 22:55:36 	kernel: kbd0 at atkbd0
Nov 29 22:55:36 	kernel: atkbd0: <at keyboard="">irq 1 on atkbdc0
Nov 29 22:55:36 	kernel: atkbdc0: <keyboard controller="" (i8042)="">port 0x60,0x64 irq 1 on acpi0
Nov 29 22:55:36 	kernel: atrtc0: <at realtime="" clock="">port 0x70-0x71 irq 8 on acpi0
Nov 29 22:55:36 	kernel: acpi_acad0: <ac adapter="">on acpi0
Nov 29 22:55:36 	kernel: pci34: <acpi pci="" bus="">on pcib34
Nov 29 22:55:36 	kernel: pcib34: <acpi pci-pci="" bridge="">at device 24.7 on pci0
Nov 29 22:55:36 	kernel: pci33: <acpi pci="" bus="">on pcib33
Nov 29 22:55:36 	kernel: pcib33: <acpi pci-pci="" bridge="">at device 24.6 on pci0
Nov 29 22:55:36 	kernel: pci32: <acpi pci="" bus="">on pcib32
Nov 29 22:55:36 	kernel: pcib32: <acpi pci-pci="" bridge="">at device 24.5 on pci0
Nov 29 22:55:36 	kernel: pci31: <acpi pci="" bus="">on pcib31
Nov 29 22:55:36 	kernel: pcib31: <acpi pci-pci="" bridge="">at device 24.4 on pci0
Nov 29 22:55:36 	kernel: pci30: <acpi pci="" bus="">on pcib30
Nov 29 22:55:36 	kernel: pcib30: <acpi pci-pci="" bridge="">at device 24.3 on pci0
Nov 29 22:55:36 	kernel: pci29: <acpi pci="" bus="">on pcib29
Nov 29 22:55:36 	kernel: pcib29: <acpi pci-pci="" bridge="">at device 24.2 on pci0
Nov 29 22:55:36 	kernel: pci28: <acpi pci="" bus="">on pcib28
Nov 29 22:55:36 	kernel: pcib28: <acpi pci-pci="" bridge="">at device 24.1 on pci0
Nov 29 22:55:36 	kernel: pci27: <acpi pci="" bus="">on pcib27
Nov 29 22:55:36 	kernel: pcib27: <acpi pci-pci="" bridge="">at device 24.0 on pci0
Nov 29 22:55:36 	kernel: pci26: <acpi pci="" bus="">on pcib26
Nov 29 22:55:36 	kernel: pcib26: <acpi pci-pci="" bridge="">at device 23.7 on pci0
Nov 29 22:55:36 	kernel: pci25: <acpi pci="" bus="">on pcib25
Nov 29 22:55:36 	kernel: pcib25: <acpi pci-pci="" bridge="">at device 23.6 on pci0
Nov 29 22:55:36 	kernel: pci24: <acpi pci="" bus="">on pcib24
Nov 29 22:55:36 	kernel: pcib24: <acpi pci-pci="" bridge="">at device 23.5 on pci0
Nov 29 22:55:36 	kernel: pci23: <acpi pci="" bus="">on pcib23
Nov 29 22:55:36 	kernel: pcib23: <acpi pci-pci="" bridge="">at device 23.4 on pci0
Nov 29 22:55:36 	kernel: pci22: <acpi pci="" bus="">on pcib22
Nov 29 22:55:36 	kernel: pcib22: <acpi pci-pci="" bridge="">at device 23.3 on pci0
Nov 29 22:55:36 	kernel: pci21: <acpi pci="" bus="">on pcib21
Nov 29 22:55:36 	kernel: pcib21: <acpi pci-pci="" bridge="">at device 23.2 on pci0
Nov 29 22:55:36 	kernel: pci20: <acpi pci="" bus="">on pcib20
Nov 29 22:55:36 	kernel: pcib20: <acpi pci-pci="" bridge="">at device 23.1 on pci0
Nov 29 22:55:36 	kernel: pci19: <acpi pci="" bus="">on pcib19
Nov 29 22:55:36 	kernel: pcib19: <acpi pci-pci="" bridge="">at device 23.0 on pci0
Nov 29 22:55:36 	kernel: pci18: <acpi pci="" bus="">on pcib18
Nov 29 22:55:36 	kernel: pcib18: <acpi pci-pci="" bridge="">at device 22.7 on pci0
Nov 29 22:55:36 	kernel: pci17: <acpi pci="" bus="">on pcib17
Nov 29 22:55:36 	kernel: pcib17: <acpi pci-pci="" bridge="">at device 22.6 on pci0
Nov 29 22:55:36 	kernel: pci16: <acpi pci="" bus="">on pcib16
Nov 29 22:55:36 	kernel: pcib16: <acpi pci-pci="" bridge="">at device 22.5 on pci0
Nov 29 22:55:36 	kernel: pci15: <acpi pci="" bus="">on pcib15
Nov 29 22:55:36 	kernel: pcib15: <acpi pci-pci="" bridge="">at device 22.4 on pci0
Nov 29 22:55:36 	kernel: pci14: <acpi pci="" bus="">on pcib14
Nov 29 22:55:36 	kernel: pcib14: <acpi pci-pci="" bridge="">at device 22.3 on pci0
Nov 29 22:55:36 	kernel: pci13: <acpi pci="" bus="">on pcib13
Nov 29 22:55:36 	kernel: pcib13: <acpi pci-pci="" bridge="">at device 22.2 on pci0
Nov 29 22:55:36 	kernel: pci12: <acpi pci="" bus="">on pcib12
Nov 29 22:55:36 	kernel: pcib12: <acpi pci-pci="" bridge="">at device 22.1 on pci0
Nov 29 22:55:36 	kernel: pci11: <acpi pci="" bus="">on pcib11
Nov 29 22:55:36 	kernel: pcib11: <acpi pci-pci="" bridge="">at device 22.0 on pci0
Nov 29 22:55:36 	kernel: pci10: <acpi pci="" bus="">on pcib10
Nov 29 22:55:36 	kernel: pcib10: <acpi pci-pci="" bridge="">at device 21.7 on pci0
Nov 29 22:55:36 	kernel: pci9: <acpi pci="" bus="">on pcib9
Nov 29 22:55:36 	kernel: pcib9: <acpi pci-pci="" bridge="">at device 21.6 on pci0
Nov 29 22:55:36 	kernel: pci8: <acpi pci="" bus="">on pcib8
Nov 29 22:55:36 	kernel: pcib8: <acpi pci-pci="" bridge="">at device 21.5 on pci0
Nov 29 22:55:36 	kernel: pci7: <acpi pci="" bus="">on pcib7
Nov 29 22:55:36 	kernel: pcib7: <acpi pci-pci="" bridge="">at device 21.4 on pci0
Nov 29 22:55:36 	kernel: pci6: <acpi pci="" bus="">on pcib6
Nov 29 22:55:36 	kernel: pcib6: <acpi pci-pci="" bridge="">at device 21.3 on pci0
Nov 29 22:55:36 	kernel: pci5: <acpi pci="" bus="">on pcib5
Nov 29 22:55:36 	kernel: pcib5: <acpi pci-pci="" bridge="">at device 21.2 on pci0
Nov 29 22:55:36 	kernel: pci4: <acpi pci="" bus="">on pcib4
Nov 29 22:55:36 	kernel: pcib4: <acpi pci-pci="" bridge="">at device 21.1 on pci0
Nov 29 22:55:36 	kernel: pci3: <acpi pci="" bus="">on pcib3
Nov 29 22:55:36 	kernel: pcib3: <acpi pci-pci="" bridge="">at device 21.0 on pci0
Nov 29 22:55:36 	kernel: em1: [FILTER]
Nov 29 22:55:36 	kernel: em1: Memory Access and/or Bus Master bits were not set!
Nov 29 22:55:36 	kernel: em1: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0x2040-0x207f mem 0xd8940000-0xd895ffff,0xd8910000-0xd891ffff irq 19 at device 1.0 on pci2
Nov 29 22:55:36 	kernel: em0: [FILTER]
Nov 29 22:55:36 	kernel: em0: Memory Access and/or Bus Master bits were not set!
Nov 29 22:55:36 	kernel: em0: <intel(r) 1000="" pro="" legacy="" network="" connection="" 1.0.3="">port 0x2000-0x203f mem 0xd8920000-0xd893ffff,0xd8900000-0xd890ffff irq 18 at device 0.0 on pci2
Nov 29 22:55:36 	kernel: pci2: <acpi pci="" bus="">on pcib2
Nov 29 22:55:36 	kernel: pcib2: <acpi pci-pci="" bridge="">at device 17.0 on pci0
Nov 29 22:55:36 	kernel: mpt0: MPI Version=1.2.0.0
Nov 29 22:55:36 	kernel: mpt0: [ITHREAD]
Nov 29 22:55:36 	kernel: mpt0: <lsilogic 1030="" ultra4="" adapter="">port 0x1400-0x14ff mem 0xd8820000-0xd883ffff,0xd8800000-0xd881ffff irq 17 at device 16.0 on pci0
Nov 29 22:55:36 	kernel: vgapci0: <vga-compatible display="">port 0x10d0-0x10df mem 0xd4000000-0xd7ffffff,0xd8000000-0xd87fffff irq 16 at device 15.0 on pci0
Nov 29 22:55:36 	kernel: pci0: <base peripheral=""> at device 7.7 (no driver attached)
Nov 29 22:55:36 	kernel: pci0: <bridge>at device 7.3 (no driver attached)
Nov 29 22:55:36 	kernel: ata1: [ITHREAD]
Nov 29 22:55:36 	kernel: ata1: <ata 1="" channel="">on atapci0
Nov 29 22:55:36 	kernel: ata0: [ITHREAD]
Nov 29 22:55:36 	kernel: ata0: <ata 0="" channel="">on atapci0
Nov 29 22:55:36 	kernel: atapci0: <intel piix4="" udma33="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x10c0-0x10cf at device 7.1 on pci0
Nov 29 22:55:36 	kernel: isa0: <isa bus="">on isab0
Nov 29 22:55:36 	kernel: isab0: <pci-isa bridge="">at device 7.0 on pci0
Nov 29 22:55:36 	kernel: pci1: <acpi pci="" bus="">on pcib1
Nov 29 22:55:36 	kernel: pcib1: <acpi pci-pci="" bridge="">at device 1.0 on pci0
Nov 29 22:55:36 	kernel: pci0: <acpi pci="" bus="">on pcib0
Nov 29 22:55:36 	kernel: pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
Nov 29 22:55:36 	kernel: cpu3: <acpi cpu="">on acpi0
Nov 29 22:55:36 	kernel: cpu2: <acpi cpu="">on acpi0
Nov 29 22:55:36 	kernel: cpu1: <acpi cpu="">on acpi0
Nov 29 22:55:36 	kernel: cpu0: <acpi cpu="">on acpi0
Nov 29 22:55:36 	kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
Nov 29 22:55:36 	kernel: Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
Nov 29 22:55:36 	kernel: acpi0: Power Button (fixed)
Nov 29 22:55:36 	kernel: acpi0: [ITHREAD]
Nov 29 22:55:36 	kernel: acpi0: <intel 440bx="">on motherboard
Nov 29 22:55:36 	kernel: padlock0: No ACE support.
Nov 29 22:55:36 	kernel: cryptosoft0: <software crypto="">on motherboard
Nov 29 22:55:36 	kernel: kbd1 at kbdmux0
Nov 29 22:55:36 	kernel: wlan: mac acl policy registered
Nov 29 22:55:36 	kernel: ioapic0 <version 1.1="">irqs 0-23 on motherboard
Nov 29 22:55:36 	kernel: MADT: Forcing active-low polarity and level trigger for SCI
Nov 29 22:55:36 	kernel: cpu3 (AP): APIC ID: 3
Nov 29 22:55:36 	kernel: cpu2 (AP): APIC ID: 2
Nov 29 22:55:36 	kernel: cpu1 (AP): APIC ID: 1
Nov 29 22:55:36 	kernel: cpu0 (BSP): APIC ID: 0
Nov 29 22:55:36 	kernel: FreeBSD/SMP: 4 package(s) x 1 core(s)
Nov 29 22:55:36 	kernel: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
Nov 29 22:55:36 	kernel: ACPI APIC Table: <ptltd apic="">Nov 29 22:55:36 	kernel: avail memory = 1014796288 (967 MB)
Nov 29 22:55:36 	kernel: real memory = 1073741824 (1024 MB)
Nov 29 22:55:36 	kernel: TSC: P-state invariant
Nov 29 22:55:36 	kernel: AMD Features2=0x1 <lahf>Nov 29 22:55:36 	kernel: AMD Features=0x20100800 <syscall,nx,lm>Nov 29 22:55:36 	kernel: Features2=0x80082201<sse3,ssse3,cx16,sse4.1,<b31>>
Nov 29 22:55:36 	kernel: Features=0xfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss>Nov 29 22:55:36 	kernel: Origin = "GenuineIntel" Id = 0x1067a Family = 6 Model = 17 Stepping = 10
Nov 29 22:55:36 	kernel: CPU: Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz (2665.84-MHz K8-class CPU)
Nov 29 22:55:36 	kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Nov 29 22:55:36 	kernel: sullrich@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64
Nov 29 22:55:36 	kernel: FreeBSD 8.1-RELEASE-p1 #1: Mon Nov 29 23:14:41 UTC 2010
Nov 29 22:55:36 	kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Nov 29 22:55:36 	kernel: The Regents of the University of California. All rights reserved.
Nov 29 22:55:36 	kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Nov 29 22:55:36 	kernel: Copyright (c) 1992-2010 The FreeBSD Project.</fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss></sse3,ssse3,cx16,sse4.1,<b31></syscall,nx,lm></lahf></ptltd></version></software></intel></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></pci-isa></isa></intel></ata></ata></bridge></vga-compatible></lsilogic></acpi></acpi></intel(r)></intel(r)></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></ac></at></keyboard></at></ps></isa></system></generic></vmware></vmware>

                    AhnHEL (Angel)

                    1 Reply Last reply Reply Quote 0
                    • A
                      andrew0401
                      last edited by

                      Running latest version - updated about 20 mins ago

                      Dec 1 08:00:22 php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was 'pfctl: DIOCADDRULE: Device busy'
                      Dec 1 08:00:17 inetd[23098]: /var/etc/inetd.conf: No such file or directory
                      Dec 1 08:00:17 inetd[23098]: /var/etc/inetd.conf: No such file or directory
                      Dec 1 08:00:16 check_reload_status: reloading filter
                      Dec 1 08:00:16 check_reload_status: syncing firewall
                      Dec 1 08:00:16 check_reload_status: reloading filter
                      Dec 1 08:00:15 php: /pkg_edit.php: Reloading Squid for configuration sync

                      Still here - but everything seems to be running OK?

                      Regards

                      Andrew

                      1 Reply Last reply Reply Quote 0
                      • E
                        eri--
                        last edited by

                        Are these errors still there if you upgrade to one of the latest snapshots?

                        1 Reply Last reply Reply Quote 0
                        • M
                          mxx
                          last edited by

                          Hi Ermal,

                          Unfortunately the error is still present on snapshot Sat Dec 4 01:44:52 EST 2010 (i386) and pops up directly after boot.

                          Sorry :(

                          1 Reply Last reply Reply Quote 0
                          • E
                            Efonnes
                            last edited by

                            When the snapshot that is currently building is done, try that one.  There's something in there that might fix this.

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

                              2.0-BETA4 (i386)
                              built on Sun Dec 5 07:23:23 EST 2010
                              Platform nanobsd (1g)
                              uptime  00:06

                              So far so good :)

                              db

                              1 Reply Last reply Reply Quote 0
                              • AhnHELA
                                AhnHEL
                                last edited by

                                Yes, looking good here as well.

                                AhnHEL (Angel)

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