Free error detector software for linux

Unicode Error Detector is a product for Plone used to pinpoint errors in your application leading to UnicodeDecodeErrors.

Do not use this product unless you are actively debugging a Unicode Error. Never use this product in production sites.

UnicodeDecodeErrors typically occur when you try to add a Unicode string to a non-ascii string. This product patches StringIO used by page templates to check if the appended string is a Unicode string, and if it is, it replaces the string with an error marker.

As there is some overhead associated with inspecting the strings instead of just appending to the output, this product is meant for debugging purposes only.

Usage

Put the product in your Products directory and restart Zope. Load the template causing the UnicodeDecodeError, and this tool will indicate the location by printing THIS IS WHERE THE ERROR IS in the rendered template.

You can then inspect the template and/or code more closely to figure out where the decode error happens.

DNS Flood Detector was developed to detect abusive usage levels on high traffic nameservers and to enable quick response in halting (among other things) the use of ones nameserver to facilitate spam.
DNS Flood Detector uses libpcap (in non-promiscuous mode) to monitor incoming dns queries to a nameserver. The tool may be run in one of two modes, either daemon mode or "bindsnap" mode. In daemon mode, DNS Flood Detector will alarm via syslog.
In bindsnap mode, the user is able to get near-real-time stats on usage to aid in more detailed troubleshooting.
Usage: ./dns_flood_detector [OPTION]
-i ifname specify interface to listen on (default lets pcap pick)
-t n alarm when more than n queries per second are observed
(default 40)
-a n wait for n seconds before alarming again on same source
(default 90)
-w n calculate statistics every n seconds
(default 10)
-x n use n buckets
(default 50)
-m n mark overall query rate every n seconds
(default disabled)
-A addr filter for specific address
-M mask netmask for filter (in conjunction with -A)
-Q monitor any addresses (default is to filter only for
primary addresses on chosen interface)
-b run in foreground in "bindsnap" mode
-d run in background in "daemon" mode
-D dump dns packets (implies -b)
-v detailed information (use twice for more detail)
-h usage info
Sample Output:
dopacki:~$ sudo ./dns_flood_detector -v -v -b -t10
[15:14:56] source [192.168.1.45] - 0 qps tcp : 24 qps udp [8 qps A] [16 qps PTR]
[15:14:56] source [10.0.24.2] - 0 qps tcp : 15 qps udp [15 qps A]
[15:15:06] source [192.168.1.45] - 0 qps tcp : 24 qps udp [8 qps A] [16 qps PTR]
[15:15:06] source [10.0.24.2] - 0 qps tcp : 15 qps udp [14 qps A]
[15:15:16] source [192.168.1.45] - 0 qps tcp : 23 qps udp [7 qps A] [15 qps PTR]
Enhancements:
- Address filtering options are now available, as are fractional query rates for better precision.
- This update also fixes several crashes and segfaults that affected overall reliability.

Plone Error Reporting is a project which facilitates the submission of useful bug reports to Plone.
PloneErrorReporting replaces default_error_message and prefs_error_log_showEntry with pages that facilitate the submission of useful bug reports to Plone.
It is designed with the goal of improving the information provided by bug reporters.
To see PloneErrorReporting in action, first install the product, then create a python script called imabug in the ZMI that contains the single line
raise AttributeError, bad attribute
Now, while still authenticated, load the page http://mysite/imabug. You should see a step-by-step procedure for reporting bugs at the bottom of the error page as long as you are logged in as a Manager. Similarly, when you view bugs in the Plone error log, you will see the bug submitting procedure.
Enhancements:
- Moved the product to use its own translation domain. This fixes an issue were half-translated sentences showed up in the templates.

libgpg-error package contains common error codes and error handling functions used by GnuPG, Libgcrypt, GPGME and more packages.

Installation:

Please read the file INSTALL!

Here is a quick summary:

1) Check that you have unmodified sources. You can find instructions how to verify the sources below. Dont skip this - it is an important step!

2) Unpack the archive. With GNU tar you can do it this way:

"tar xzvf libgpg-error-x.y.tar.gz"

3) "cd libgpg-error-x.y"

4) "./configure"

5) "make"

6) "make install"

Apache::ErrorControl Perl module is an Apache Handler for Templating Apache Error Documents.

This mod_perl content handler will make templating your ErrorDocument pages easy. Basically you add a couple of entries to your httpd.conf file restart apache, make your template and your cruising.

The module uses HTML::Template::Set (which is essentially HTML::Template with the ability to use TMPL_SET tags). So for help templating your error pages please see: HTML::Template::Set and HTML::Template. Also check the OPTIONS section of this documentation for available TMPL_SET/TMPL_IF and TMPL_VAR params.

By default when an error 500 (internal server error) is encountered an error email is sent about it. the addresses emailed depend on the options specified. please see the OPTIONS section for help configuring this. you can also extend the system to send error emails on more than just internal server errors, please see the EmailOn option for how to do this.

Templates are looked up in the following order: the document root is scanned for allerrors, allerrors.tmpl, error code or error code.tmpl. if no templates are found the TemplateDir is scanned for the same files. if no templates are found the DefaultTemplate is used and if its not set the system dies.

Because so many places are checked for the templates its possible to have one global error handler and have different templates for each virtual host and also allow for defaults. It also means you can have a general catch-all template (allerrors/allerrors.tmpl) as well as single templates (i.e. 500.tmpl). Generally I just use allerrors.tmpl and use TMPL_IFs to display custom content per error message, but you can set it up any way you want.

errhdl is a small C library that offers error handling methods similar to the exception handling in C++.
In the event of errors, no exception objects are thrown, but an error class name and an error message are set, and execution continues at the next "OnError" statement.
The library can be seen as a nice frontend to setjmp/longjmp. It is thread safe and supports the use of POSIX threads.
Enhancements:
- A bug has been fixed that caused ignored errors in a called function to be raised again in the calling function under certain circumstances.

Progress is a utility used in a pipe to report progress of data transfer to standard error. Command-line arguments tells to specify how frequently to report, what character to use to report, and how much buffering to do.
Enhancements:
- February 9, 2003
- progress 1.0
- Initial announcement

Mail::ListDetector::Detector::Onelist is a ONElist message detector.

SYNOPSIS

use Mail::ListDetector::Detector::Onelist;

An implementation of a mailing list detector, for ONElist mailing lists. ONElist was eaten by eGroups which became Yahoo! Groups so this detector is really only useful for historical mail.

METHODS

new()

Inherited from Mail::ListDetector::Detector::Base.

match()

Accepts a Mail::Internet object and returns either a Mail::ListDetector::List object if it is a post to a ONElist mailing list, or undef.