Re: spreadlogd 1.4.2, spread 3.16.2, FreeBSD 4.6-RELEASE

On Mon, Sep 09, 2002 at 10:58:49AM -0400, George Schlossnagle wrote:
> Mike Parson wrote:
>
>> On Mon, Sep 09, 2002 at 09:54:25AM -0400, George Schlossnagle wrote:
>>
>>> Can you ty out a hunch of mine and only use machine names in you 
>>> spread.conf which are below the MAX_PROC_NAME define in spread_params.h 
>>> (it defaults to 20).  
>>
>> Woo!  That works!
>>
>> At least, nothing is dying off now.
>>
>> Next question...
>>
>> I'm using the $#vhost in the Customlog directive, now, what is the
>> magic for spreadlogd.conf to let this all work?  My error_log is
>> being filled with
>>
> No magic per se, just set the VhostDir directive in your spreadlogd.conf

Basically, my spreadlogd.conf looks like:

Spread {
        Port = 4803

        Log {   
                Group = apache-0001
                VhostDir = /usr/local/apache/logs/
        }
}

How many Groups and what should the groups be set to?  I don't
really understand the description in the sample config.

>> [Mon Sep  9 09:16:12 2002] [error] (61)Connection refused: Could not 
>> connect to spread 4803 with private_name ap55984. Error -2
>>
>> With a bunch of different numbers for apXXXXX.
>
> Those are individual apache children failing to connect to spread.  Make 
> sure there is a spread ring they can attach to (i you changed the names 
> in the spread.conf from the hostnames, you will need to start spread 
> with a '-n <name>' flag.  My usual approcah to this is to use just the 
> nodename in the file, and to use a wrapper which converts `hostname` 
> into the nodename and runs spread with that flag.
>
> If spread is running, there may be other problems.  How many httpd 
> children do you have per server (per spread instance specifically).

I've got spread running on the web server and the log gathering (spreadlogd) system.

They've got identical config files.

They're now each started as the user spread with the flags 

-n $nodename -c /usr/local/etc/spread.conf

($nodename is not a variable in the file, it's hardcoded to the
nodename).

All that is in the spread.conf is the 5 lines defining the spread segment:

web2# grep -v ^# spread.conf

Spread_Segment  208.187.213.63:4803 {
        mysql2          208.187.213.32
        web1            208.187.213.10
        web2            208.187.213.31
}

(yes, we're on a /27, hense the smaller bcast)

I *think* my problem is in the spreadlogd configuration, like I
said, I don't fully understand the examples in the sample config.

-- 
Michael Parson
[email protected]