Urchin hasn't been updated since 2012.
If you're ready to replace Urchin,
Check out Angelfish Software

Urchin Support Plans

Urchin 6 Installation Requirements

Urchin 6 is available for a variety of operating systems. Urchin must only be installed on a single server to process logs and serve reports. All reports may be viewed through a web browser on the client's end.

Operating Systems

Windows (32-bit)
  • Windows XP
  • Windows 2000
  • Windows Vista
  • Windows 2003 Server
  • Windows 2008 Server


  • Linux 2.4/2.6 (generic for most flavors)
  • FreeBSD 5.3+/6.2+

Anticipated OS Support

  • RedHat Enterprise 4 - Try Linux kernel 2.6 for time being.


  • MySQL 5.x
  • PostgreSQL 8.2.5

Browsers for administration and viewing reports

  • Internet Explorer 6.x+
  • Firefox 2.x+
  • Chrome 1.x+


Urchin 6 has no set hardware requirements, however for optimal performance, the following specifications are recommended:

Single-Multiple small-scale websites
  • 2GHz or greater processor
  • 2GB RAM
  • 250GB+ Hard Disk Space

Enterprise / Service Provider

  • 2.5Ghz Pentium dual-core / 2Ghz UltraSPARC / similar CPU speed range PPC/MIPS/etc
  • 3GB+ RAM
  • Mass Storage Solution (NAS/SAN)
  • Backup System

Memory/System/Disk Usage

  • Urchin Memory(RAM) usage can be configured to use between 20-500Mb (20 - 1024Mb for Urchin 6.5+)
  • Urchin process priority may be modified.
  • Data storage will use approximately 10% of raw log file size.

Important Note to FreeBSD users

FreeBSD has a hard-coded process datasize limit of 500MB. This limit is exceeded because of Urchin's geodata that must be memory resident during log processing. As a result, you will see the following runtime error:

ERROR: (8011-323-1057) Failed to allocate memory

To address this, you'll need to increase the FreeBSD system's default process datasize, which you can do by editing the /boot/loader.conf file and adding the following lines (reboot after).

# Increase max process data segment size to 1GB

WARNING!!! Be very careful when changing system limits like this. If you set kern.maxdsiz to be too large, your system may become unbootable. We strongly recommend that you read the FreeBSD documentation before making this modification, and assess the potential risks as they apply to your site-specific configuration.