Urchin 6.6, 6.601, and 6.602 Known Issues

Urchin 6.6, 6.601, and 6.602 Known Issues

Urchin 6.602 - Revision: October 23, 2009

Administration

The Goal Configuration wizard uses site overlay technology that is unable to handle password protected pages and is easily confused by complex pages, e.g. those with frames, javascript, css, auto-redirects, etc.

Geodata

Due to the format of the new geodata database, it is no longer possible to import local IP-to-domain name mapping information.

Log Processing

Processing logs out of chronological order will likely result in very slow log processing for high-traffic sites.
Increasing the DB limit beyond the default 100,000 records may reduce log processing performance, especially for sites with large traffic volume.
The log processing engine allocates memory for each filter applied to a profile for each physical log file opened during processing. This can result in large memory allocation requests and possibly failure to allocate all required memory when a profile is configured with many filters and a large number of physical logfiles are matched by the log source(s), e.g. due to an excessively broad wildcard match.
Large lookup tables can result in large memory allocation and possible memory allocation failures, especially if a large number of physical logfiles are opened during log processing.
There are certain known issues while using UNC sockets. For details, please refer to Working with UNC log sources.

Schedulers

Urchin schedulers (profile and CPC) use the database to store and retrieve the timestamps to schedule various jobs. This means that the database, once configured, must not be moved around timezones (i.e. do not change the timezone of the machine running urchin db). In addition, it is strongly recommended that you not change the timezone of the machine running Urchin schedulers.

E-Commerce

Urchin can read e-commerce data that is either embedded directly in the Web server logs when the transactions are logged via UTM javascript calls, or via an explicit ELF2 e-commerce log created by the shopping cart. Urchin will create duplicate transactions if the same e-commerce data is present in both webserver logs and ELF2 logs, so it is important that ELF2 logs not be processed if the same data is embedded in the webserver logs.

Utilities

The "zero day" functionality in udb-sanitizer can be very slow for profiles with large amounts of data.

Reporting

Cross-segment reporting can be very slow (or timeout completely) for sites with large amounts of traffic and/or long date ranges.
"P/Visits" results differ between the "Medium Conversion" report and each sub-report under the "Analysis Option".

Integration with AdWords

Direct access to AdWords from Urchin doesn't work if Urchin 6.6+ is installed on the 64-bit version of Windows 2008.

PostgreSQL installation

During the installation of PostgreSQL server on Linux Kernel 2.6 and Windows, installer requires root/admin privileges to create system user "postgres".
On Linux, PostgreSQL Installer requires glibc 2.3.3 or higher.
CPC data import may not work if bundled PostgreSQL server is selected during Urchin installation on Linux Kernel 2.4. In this case, we recommend using an external PostgreSQL server.

Urchin 6.601 - Revision: July 23, 2009

Administration

In Data Center mode, Account administrators have only one privilege level, which is more restrictive than the Affiliate administrator privilege levels found in the Urchin 5.
The Goal Configuration wizard uses site overlay technology that is unable to handle password protected pages and is easily confused by complex pages, e.g. those with frames, javascript, css, auto-redirects, etc.

Geodata

Due to the format of the new geodata database, it is no longer possible to import local IP-to-domain name mapping information.

Log Processing

For performance reasons, the log processing engine loads the entire geodata database in memory during processing, resulting in a rather large memory footprint (~800MB minimum) even when processing profiles for very small sites. This also adds a small latency to the log processing initialization time for each profile, typically 2-5 seconds.
Processing logs out of chronological order will likely result in very slow log processing for high-traffic sites.
Increasing the DB limit beyond the default 100,000 records may reduce log processing performance, especially for sites with large traffic volumes.
The log processing engine allocates memory for each filter applied to a profile for each physical log file opened during processing. This can result in large memory allocation requests and possibly failure to allocate all required memory when a profile is configured with many filters and a large number of physical logfiles are matched by the log source(s), e.g. due to an excessively broad wildcard match.
Large lookup tables can result in large memory allocation and possible memory allocation failures, especially if a large number of physical logfiles are opened during log processing.

Schedulers

Urchin schedulers (profile and CPC) uses the database to store and retrieve the timestamps to schedule various jobs. This means that the database, once configured, must not be moved around timezones (i.e. do not change the timezone of the machine running urchin db). In addition, it is strongly recommended that you not change the timezone of the machine running urchin schedulers.

E-Commerce

Urchin can read e-commerce data that is either embedded directly in the webserver logs when the transactions are logged via UTM javascript calls, or via an explicit ELF2 e-commerce log created by the shopping cart. Urchin will create duplicate transactions if the same e-commerce data is present in both webserver logs and ELF2 logs, so it is important that ELF2 logs not be processed if the same data is embedded in the webserver logs.

Utilities

The zip/unzip utilities supplied with Urchin have a 2GB file size limit. This may affect Urchin's ability to create backups/archives of reporting data for large sites, or to use the "compress" option in the Log Destiny for log sources.
The "zero day" functionality in udb-sanitizer can be very slow for profiles with large amounts of data

Reporting

Cross-segment reporting can be very slow (or timeout completely) for sites with large amounts of traffic and/or long date ranges.

External Authenication

Urchin 6.6+ comes with external authentication modules, which includes LDAP. Currently the LDAP module doesn't work with LDAP providers that are running over "SSL/TLS".

Installation

Upgrading an instance of Urchin that is using a Demo license is not recommended and may result in login/licensing issues.

Cookies

To facilitate enhanced interaction in the reporting interface, Urchin 6.6+ uses client-side cookies. Proper viewing of reports requires that client-side cookies be enabled in the client browser.

Urchin 6.600 - Revision: May 29, 2009

Administration

In Data Center mode, Account administrators have only one privilege level, which is more restrictive than the Affiliate administrator privilege levels found in the Urchin 5.
The Goal Configuration wizard uses site overlay technology that is unable to handle password protected pages and easily confused by complex pages, e.g. those with frames, javascript, css, auto-redirects, etc.
Attempting to log in to an account that contains a large amount of data may result in the following error: Session Error - unable to call default routine. (2002) Please login again. This is caused when the data extraction for rollup reports exceeds the default APPLICATION_TIMEOUT of 45 seconds. To work around this problem, increase the APPLICATION_TIMEOUT in session.conf to 180 (or more).

Geodata

Due to the format of the new geodata database, it is no longer possible to import local IP-to-domain name mapping information.

Log Processing

For performance reasons, the log processing engine loads the entire geodata database in memory during processing, resulting in a rather large memory footprint (~800MB minimum) even when processing profiles for very small sites. This also adds a small latency to the log processing initialization time for each profile, typically 2-5 seconds.
Processing logs out of chronological order will likely result in very slow log processing for high-traffic sites.
Increasing the DB limit beyond the default 100,000 records may reduce log processing performance, especially for sites with large traffic volumes.
The log processing engine allocates memory for each filter applied to a profile for each physical log file opened during processing. This can result in large memory allocation requests and possibly failure to allocate all required memory when a profile is configured with many filters and a large number of physical logfiles are matched by the log source(s), e.g. due to an excessively broad wildcard match.
Large lookup tables can result in large memory allocation and possible memory allocation failures, especially if a large number of physical logfiles are opened during log processing.

Schedulers

Urchin schedulers, profile and CPC, uses database to store and retrieve the timestamps to schedule various jobs. This requires that database, once configured, should not be moved around timezones (i.e. don't change timezone of the machine running urchin db). In addition, it is highly recommended not to change timezone of machine running urchin schedulers.

E-Commerce

Urchin can read e-commerce data that is either embedded directly in the webserver logs when the transactions are logged via UTM javascript calls, or via an explicit ELF2 e-commerce log created by the shopping cart. Urchin will create duplicate transactions if the same e-commerce data is present in both webserver logs and ELF2 logs, so it is important that ELF2 logs not be processed if the same data is embedded in the webserver logs.

Utilities

The zip/unzip utilities supplied with Urchin have a 2GB file size limit. This may affect Urchin's ability to create backups/archives of reporting data for large sites, or to use the "compress" option in the Log Destiny for log sources.
The "zero day" functionality in udb-sanitizer can be very slow for profiles with large amounts of data

Reporting

Cross-segment reporting can be very slow (or timeout completely) for sites with large amounts of traffic and/or long date ranges.

External Authenication

Urchin 6.6 comes with external authentication modules, which includes LDAP. Currently the LDAP module doesn't work with LDAP providers that are running over "SSL/TLS".

Installation

Upgrading an instance of Urchin that is using a Demo license is not recommended and may result in login/licensing issues.

Cookies

To facilitate enhanced interaction in the reporting interface, Urchin 6.6 uses client-side cookies. Proper viewing of reports requires that client-side cookies be enabled in the client browser.