I setup Urchin 5 to run every day at 04:00 and it had been working fine for about a week, until two days ago when this started:

------------------------------------------------------
Urchin 5.0.01r2 (redhat72) starting: 20031008 04:00:01
------------------------------------------------------
Processing profile: www.domain.com (on ensim.32563)

[04:00:01] Logfile: /home/virtual/domain.com/var/log/httpd/access_log
data lines: 0 (0%)
WARNING: (7063-54-63) Unable to open database for writing since it has been archived

------------------------------------------------------
Urchin 5.0.01r2 (redhat72) finishing: 20031008 04:00:01
------------------------------------------------------


access logs look fine - error indicates the Urchin database has been archived? I didn't see an option in the Urchin configuration to archive the Urchin db...

# pwd
/home/virtual/domain.com/var/log/httpd
# ls -lah access*
-rw-r--r-- 1 admin2 admin2 4.5M Oct 8 09:34 access_log
-rw-r--r-- 1 admin2 admin2 11M Oct 5 03:42 access_log.1
-rw-r--r-- 1 admin2 admin2 5.6M Sep 28 04:01 access_log.2
-rw-r--r-- 1 admin2 admin2 135k Sep 20 22:32 access_log.3
-rw-r--r-- 1 admin2 admin2 186k Sep 13 19:25 access_log.4

ok found the urchin report for this domain. Just not sure what to do next. I see the .zip files and I have no idea how files are timestamped 3/10/2007 here

# pwd
/usr/local/urchin/data/reports/www.domain.com
# ls -lah
total 2.9M
drwxr-xr-x 2 nobody nobody 4.0k Oct 8 04:00 .
drwxr-xr-x 3 nobody nobody 4.0k Sep 21 02:31 ..
-rw-r--r-- 1 nobody nobody 228k Mar 10 2007 200309-archive.zip
-rw-r--r-- 1 nobody nobody 719k Oct 5 04:00 200309-hdata.und
-rw-r--r-- 1 nobody nobody 57k Oct 5 04:00 200309-hdata.uni
-rw-r--r-- 1 nobody nobody 42k Oct 1 04:00 200309-hdata.uns
-rw-r--r-- 1 nobody nobody 660 Oct 5 04:00 200309-ldata.und
-rw-r--r-- 1 nobody nobody 152 Oct 5 04:00 200309-ldata.uni
-rw-r--r-- 1 nobody nobody 329k Oct 5 04:00 200309-pdata.und
-rw-r--r-- 1 nobody nobody 82k Oct 5 04:00 200309-sdata.und
-rw-r--r-- 1 nobody nobody 116k Oct 5 04:00 200309-tdata.und
-rw-r--r-- 1 nobody nobody 1.6k Oct 5 04:00 200309-udata.unf
-rw-r--r-- 1 nobody nobody 18k Oct 5 04:00 200309-vdata.und
-rw-r--r-- 1 nobody nobody 18k Oct 5 04:00 200309-vdata.uni
-rw-r--r-- 1 nobody nobody 160k Mar 10 2007 200310-archive.zip
-rw-r--r-- 1 nobody nobody 579k Mar 10 2007 200310-hdata.und
-rw-r--r-- 1 nobody nobody 47k Mar 10 2007 200310-hdata.uni
-rw-r--r-- 1 nobody nobody 36k Mar 10 2007 200310-hdata.uns
-rw-r--r-- 1 nobody nobody 440 Mar 10 2007 200310-ldata.und
-rw-r--r-- 1 nobody nobody 152 Mar 10 2007 200310-ldata.uni
-rw-r--r-- 1 nobody nobody 215k Mar 10 2007 200310-pdata.und
-rw-r--r-- 1 nobody nobody 54k Mar 10 2007 200310-sdata.und
-rw-r--r-- 1 nobody nobody 116k Mar 10 2007 200310-tdata.und
-rw-r--r-- 1 nobody nobody 1.6k Mar 10 2007 200310-udata.unf
-rw-r--r-- 1 nobody nobody 12k Mar 10 2007 200310-vdata.und
-rw-r--r-- 1 nobody nobody 10k Mar 10 2007 200310-vdata.uni
# date
Wed Oct 8 11:06:40 EDT 2003


anyone see this before or know how to go about fixing it? any assistance would be appreciated.

thanks
Jason

I have the same problem. Did you resolve this?

no i never figured out how to fix it.

I just deleted the report and re-created it. it has been working fine for over a month now.

simpel solution:

cd /usr/local/urchin/
chmod -R 0777 data

and you're on again

I ran into this problem tonight and did a version of this:

http://www.google.com/support/urchin45/bin...8527&topic=7393

ow do I recover from 'Unable to open database for writing since it has been archived' error?

When attempting to run a profile, you receive this error:

WARNING: (7063-54-63) Unable to open database for writing
since it has been archived

This error occurs since the log tracking databases are stored on a per month basis with Urchin 5. During processing, Urchin reads the first couple of lines from the log file, determines which month this log belongs to and attempts to open the databases for that month. Since the databases for that month have been archived, an error is returned since Urchin will not allow reading/writing to databases that have been archived.There are several workarounds:

1. Turn off the archive feature and uncompress the *-archive.zip files for the affected profiles and remove the *-archive.zip files.
2. Change the log wildcarding to include a date matching string (perhaps YY* or YYYY* can be used to identify files only for this year).

P.S. The easiest way I found was to turn off the archiving...use the remove all files for the particular profile and re-run stats letting it do it's magic.