The most common causes of Urchin failing to update are due to one of the following: 1. The Urchin Scheduler is not running. 2. There is a problem with the log file location or configuration. 3. There is a problem with the Urchin database. Urchin Scheduler Unless you manually run Urchin to update your reports, they are updated according to the Urchin Scheduler configuration. The Urchin Scheduler daemon must be running for the reports to update on time. To check the status of the scheduler, you'll need to open a command shell to the Urchin server and CD to the ~urchin/bin directory. From there, run the following command to check the status: ./urchinctl status (note; omit the ./ if running this command on a windows server) If either the Scheduler or the Urchinwebd are not running, you can restart them as follows: ./urchinctl start Once the scheduler is running again, you may wait for Urchin to update according to its normal schedule or manually update it by selecting the "Run Now" option from the Urchin Administrative GUI. Log File Configuration If the location of the log file changes or if the format of the log file changes, Urchin may stop updating the reports. To determine if this is happening, scroll down to the section in this article titled "Task History Inspection." Database Problem If the Urchin database is corrupt or locked for any reason, the reports will stop updating for the effected profile. To determine if this has happened, see the following section titled "Task History Inspection." Task History Inspection Urchin keeps a record of every attempt to process logs for every profile. If you suspect there may be a problem with the processing, these logs will often provide information that points to the root problem. There are two ways to access this information: 1. Open the Urchin Configuration GUI and select the following window: Configuration; Scheduler; Task History. From this view you'll see a Status column. Each item in the "Status" column is a clickable link. The link will open a window that displays the process status when Urchin attempted to process the log file for that profile. They are listed by date/time/profile as indicated in the remaining columns in this window. Click "Next" if necessary to find the profile and date you are looking for. 2. These same files are available on the server Urchin is running on. They are organized by profile so that each profile has a unique directory with all the Task History files contained within. The path to the profile directories is: ~urchin/data/history/"profile-name" where "profile-name" represents the profile directory. The files are not date named but they are in order so that the oldest file is the first history file and the last file in the list is the most recent history file with the latest process data. The data in these files can be broken down as follows:
------------------------------------------------------
Urchin 4.1.03 (freebsd4x) starting: 20021109 11:20:02
------------------------------------------------------
Lists Urchin version, Operating system and the start
date/time of the job
Processing profile: www.exhausto.com (on inxs.124)
Lists the profile and Urchin server name
WARNING: (7029-646-331) Logtracking is disabled and it appears log
has already been processed.
Lists any warnings, the warning ID, and a description of any
possible problems
Logfile: /usr/home/powell/logs/exhausto/ex0210.log
Lists the current log file path and log name that is being
processed
.......done.
Lists the status of processing the current log
data proc: 12124160 bytes in 10 sec
Lists the total bytes "processed" (this is not always the
total amount of bytes in the log file) and time taken to
process
data range: 2002-09-30 16:04 - 2002-10-18 08:00
Lists the range of dates that were processed during this run
only
data lines: 76089
Lists the amount of data lines that exist in the full log
file
data hits: 75917
Lists the amount of data lines that were processed from the
current log (this number does not include data lines that were
excluded due to filters, or data already processed during an
earlier run of Urchin).
------------------------------------------------------
Urchin 4.1.01 (freebsd4x) finishing: 20021109 11:20:12
------------------------------------------------------
Lists the finishing date/time of the current job