Summary.Net Archives
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Summary-Talk] Re: Summary installed on one server, monitoring another



Thanks again Jason,

When I used your debugging method, my browser showed the httpd folder ( 
I thought CrushFTP was better then that ).  I will change the URL to
ftp://206.102.88.10/httpd/* to see if that works.

I'll keep you updated.

Thanks again - Vijay

On Wed, 16 Feb 2005 10:17:37 -0500, Jason Linhart <jason@summary.net>
wrote:

> Vijay-Kumar Solanki wrote:
>>
>>> You probably don't have the log downloading setup correctly.
>>
>> Enable Log Downloading is checked
>> URL: ftp://206.102.88.10/*
>> Username and password are filled in
>>
>> When I processed logs, I received one file in the Summary Logs folder
>> called "*" and nothng else.
>
> That would tend to happen when there weren't any files in the directory
> you have configured Summary to download from. The might still be
> directories in the remote directory, but Summary will only download
> files directly contained in the directory you have configured
> downloading for.
>
> A good way to debug log downloading issues is to try to go to the
> downloading URL in a web browser. In your case you would use the URL
> <ftp://name:pass@206.102.88.10/> in a browser and see what you comes up.
> You want to see a directory listing of log files, if you don't you
> should be able to explore around in the browser until you find where the
> log files are located.
>
>> When I looked
>> at the Summary Log folder on the main computer (.10) there were many sub
>> folders for each website or domain.  So what I tried was to mount the
>> .10 machine and copy everything from it's Summary Logs folder (
>> essentially an alias to the httpd folder ) to the Summary Logs folder on
>> the new machine (.17).  This morning I have reports.
>
> If you are able to mount the .10 machine on the .17 machine then you can
> just use that approach to access your logs, instead of log downloading.
> You need to setup the mount to be automatic on startup, and then make a
> shortcut/alias/symbolic link (depending on platform) to the location of
> the log files and put that in Summary's Logs folder.
>
> If you copied the actual log files then what you have done is only a
> temporary solution, since they won't get updated without manually
> repeating the copy. But if you copied shortcuts/aliases to the log
> files, or the directories containing them, then you are probably all set.
>
>> I would have thought that ftp://206.102.88.10/* would have downloaded
>> everything from the .10 machine.
>
> That FTP configuration will download all of the log files in the default
> directory for that FTP account, but it won't copy log files in
> sub-directories of that directory. Each downloading configuration copies
> files from a single directory. If your log files are located in many
> different directories you will need one downloading configuration for
> each directory. (Each sub-report has it's own log downloading
> configuration.)
>
> Jason
>



-- 
Vijay-Kumar Solanki
d'Vinci Ineractive
Vijay@dvinci.com
301.797.2386
-------------
Go to <http://summary.net/list.html> to update subscription info.