Hi Louis, Yes it has been updated, but not from very old releases. It was originally installed with pf 5.1.0, in july.
Here is violations.conf: [defaults] priority=4 max_enable=3 actions=email,log auto_enable=Y enabled=N grace=120m delay_by=0s button_text=Enable Network snort_rules=local.rules,emerging-attack_response.rules,emerging-botcc.rules,emerging-exploit.rules,emerging-malware.rules,emerging-p2p.rules,emerging-scan.rules,emerging-shellcode.rules,emerging-trojan.rules,emerging-worm.rules # vlan: The vlan parameter allows you to define in what vlan a node with a violation will be put in. # Accepted values are the vlan names: isolation, normal, registration, macDetection, inline, voice # and all the roles names you defined in the node_category table. (see switches.conf) vlan=isolation # if you add a role/category here, nodes in these roles/categories will be immune to the violation whitelisted_categories= template=generic trigger= desc=defaults MJ On 10/28/2015 10:16 PM, Louis Munro wrote: > Was this system updated from a previous release? > > I remember seeing that error in such a case. > Can you post the definition of your “default” violation in > conf/violations.conf please? > > -- > Louis Munro > [email protected] <mailto:[email protected]> :: www.inverse.ca > <http://www.inverse.ca> > +1.514.447.4918 x125 :: +1 (866) 353-6153 x125 > Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu>) > and PacketFence (www.packetfence.org <http://www.packetfence.org>) > >> On Oct 28, 2015, at 17:11 , mourik jan heupink <[email protected] >> <mailto:[email protected]>> wrote: >> >> ok, that sounds simple. :-) >> >> Tried adding a violation, but: >>> Oct 28 22:08:55 httpd.admin(9509) WARN: database query failed with: >>> Cannot add or update a child row: a foreign key constraint fails >>> (`pf`.`violation`, CONSTRAINT `0_61` FOREIGN KEY (`vid`) REFERENCES >>> `class` (`vid`) ON DELETE CASCADE ON UPDATE CASCADE) (errno: 1452), >>> will try again (pf::db::db_query_execute) >>> Oct 28 22:08:55 httpd.admin(9509) WARN: database query failed with: >>> Cannot add or update a child row: a foreign key constraint fails >>> (`pf`.`violation`, CONSTRAINT `0_61` FOREIGN KEY (`vid`) REFERENCES >>> `class` (`vid`) ON DELETE CASCADE ON UPDATE CASCADE) (errno: 1452), >>> will try again (pf::db::db_query_execute) >>> Oct 28 22:08:55 httpd.admin(9509) WARN: database query failed with: >>> Cannot add or update a child row: a foreign key constraint fails >>> (`pf`.`violation`, CONSTRAINT `0_61` FOREIGN KEY (`vid`) REFERENCES >>> `class` (`vid`) ON DELETE CASCADE ON UPDATE CASCADE) (errno: 1452), >>> will try again (pf::db::db_query_execute) >>> Oct 28 22:08:55 httpd.admin(9509) ERROR: Database issue: We tried 3 >>> times to serve query violation_add_sql called from >>> pf::violation::violation_add and we failed. Is the database running? >>> (pf::db::db_query_execute) >>> Oct 28 22:08:55 httpd.admin(9509) ERROR: unknown error adding >>> violation 1500002 for e8:91:20:0f:ee:92 (pf::violation::violation_add) >> >> Yes, the database appears to be running, the complete system seems to >> work fine. This is pf 5.3.1 on wheezy. >> >> Any ideas? > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users > ------------------------------------------------------------------------------ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
