SAWMILLFORUM

I also wonder if you could tell me a few things about your Sawmill install and how you've set up your profile.

Have you set the log source to the local directory? or are you using FTP to get the data?

Are the log files you are processing compressed? or flat ASCII text files?

Hopefully with 7.1.10 you may see the progress error report, however, you should be able to dismiss it and carry on with processing.

But anyway, to answer your questions, David (keep in mind that I'm not very Unix-savvy):
>Have you set the log source to the local directory?
>or are you using FTP to get the data?

My log source is local to my Mac. It's a folder within my Sawmill folder.

>Are the log files you are processing compressed?
>or flat ASCII text files?

The folder has files in a .gz format.
The log data format is "Apache/NCSA Combined Log Format".
Did that answer the questions?

Problem while displaying progress, the node volatile.progress.step is missing. The debug_output node shows volatile.progress at the time when the step node was missing in build_progress_page.cfv.
debug_output = {
. exists = (string) "false"
. label = (string) ""
} # debug_output

Is the profile you are creating a brand new profile? Or are you using an existing profile and trying to update the database?

I wonder if for some reason maybe the issue is with updating the database vs. trying to rebuild the database. Though this should not matter it sounds like possibly something happened to the original database which has caused it to be in a corrupt state.

I'd like it if you could try to rebuild the database after creating a new profile and see if you continue to see the same issues.

Please let me know if what I've suggested is possible, and if you continue to get the error. IF you can send us in the sample of log data that causes the issues you are seeing, and it repeats, then possibly we can get to the bottom of what's going on.

In the most recent report, I was creating a brand new profile. As far as I know, I have never tried to update a database. We did wonder about corrupted databases before, though (when Sawmill 7.1.7 would claim to be working but report no progress for hours at a time).

I gave up on the folder of 7 log files, and instead had Sawmill 7.1.10 process 1 file with all 7 days. That worked. Here's the snapshot for that 7 day period:

Page views 596,040
Visitors 46,669

But now, when i try to view the Years/months/days report, I see the 'churning' effect (where it stays stuck like this for hours):

Processing steps Complete Remaining time Elapsed time
1. Integrating collected data into table (1) 0.00% 00:00:00 00:00:00

>I'd like it if you could try to rebuild the database after
>creating a new profile and see if you continue to see the
>same issues.

I will try this today, with the database I was just able to created, and will report back.

>Please let me know if what I've suggested is possible, and
>if you continue to get the error. IF you can send us in the
>sample of log data that causes the issues you are seeing,
>and it repeats, then possibly we can get to the bottom of
>what's going on.
>

Last night I was able to build a database, and view reports. This afternoon I did as you suggested, and tried to rebuild that working database (from the config page). When I did this, Sawmill got into the state where it claims to be working, but doesn't report any progress (reports 3 seconds of elapsed time, 402 lines read in, for 20 minutes straight).

I will be sending some files to you.

Tricia Jones
Animal Diversity Web
University of Michigan
http://animaldiversity.org/

I'm wondering if this is more an issue with progress reporting problems, and the database is actually able to build. I wonder if you were to build from the command line, and then run the GUI would the reports display this way?

Building from the command line would be done as follows:

Windows OS:

Open a command prompt windows and move to the Sawmill Install directory. cd \Program Files\Sawmill 7\ (is the default path)

Then run from the command line:

SawmillCL.exe -p profilename -a bd

and let it run, substituting the "profilename" above with the name of your profile.

For Unix/Mac OS X/Linux:

./sawmill -p profilename -a bd

Try to run the database build from the command line and let me know if it completes as you'd expect.

David, I did as requested, and got this error message (MacOS X 10.3.8):

#### Unable to delete directory 'LogAnalysisInfo/Databases/july_week_combo'
Error occurred at: : /tulip1/sawmill/v7/production/src/make_directory.cpp:283

At that point, I went and changed the name of the directory/folder (from july_week_combo to something else). Then I reissued the command to build, and it worked. So perhaps the problem is not with reporting progress, but deleting the directory? (or maybe this is a red herring...)

Tricia

I think it might have been a permissions issue all along, hopefully from this point forward you'll get "better" behaviour. Possibly a red herring, though I would expect that this sort of thing would happen consistently.

Well, either way, I'm hopeful that you are back up and running and will be able to get the reports you need. Let me know if you have further questions, or see this behavior in the future.

This is exaclty what we experience with our install.
quitting and restarting the server helps. But restarting the server every day is not an option.
Reports send by email works fine though. So you can provide your clients with inf.

cheers,

Ton

If you run from the command line you get the same issue? Meaning - Sawmill seems to stall at the command line building?

i don't know what you mean by running from the command line.
I try to run a report in my webbrowser. Then Sawmill is prsenting me with a progressbar that does not show progress at all. Restarting the server and running a report again works ok.

cheers,

Ton

Cancelling the task.
Logging out of Sawmill.
Clearing my browser cache.
Quitting my browser.
Quitting Sawmill.
Closing all other open apps.
Shutting down my computer.
Waiting a few minutes.
Restarting my computer.
Launching Sawmill.
Starting Sawmill, which launches my browser.
Logging in to Sawmill.
Clicking on 'Reports' and trying the same thing again.

Obviously, this gets to be a pain after a while. Also, when I get near a GB worth of logs, I can't get the "churning" to stop. (Good term for it!)

Good luck finding the fix!

just upgraded to 7.1.11 and looks like all is okay now.
I don't have to restart the server again to get my reports.
The only nasty bit is that I lost my schedules after upgrading.
Minor problem though.

There's only 1 thing I would like to change.
How can I change the text 'Search phrases by search engine" on the left hand side?
I tried to edit the prefs but that didn't work.

Cheers,

Ton

You can change the name of a report in Config->Manage Reports->Reports/Reports Menu. Change the Report Name, and it will change what appears in the bar above the report. To change how it appears in the sidebar (the Reports Menu), click Edit Reports Menu in the upper right of the Reports/Reports Menu page.