7;m very interrested.
Regards
2012/7/24 Julien Cornuwel :
> Hi,
>
> Fixed! The problem comes from the squid ocf script
> (/usr/lib/ocf/resource.d/heartbeat/Squid) that doesn't handle IPv6
> addresses correctly.
> All you have to do is modify the line 198 as such :
Hi,
Fixed! The problem comes from the squid ocf script
(/usr/lib/ocf/resource.d/heartbeat/Squid) that doesn't handle IPv6
addresses correctly.
All you have to do is modify the line 198 as such :
awk '/(tcp.*[0-9]+\.[0-9]+\.+[0-9]+\.[0-9]+:'$SQUID_PORT'
|tcp.*:::'$SQUID_PORT' )/{
Source:
http://w
2012/7/18 Jake Smith :
> With the "status=Timed Out" I'm thinking that you're setting of 60s for start
> timeout might be too short? How long does it take to return if you start
> squid from the LSB script? How long after starting until the squid.pid is
> created (is it even created?)?
>From t
Hi,
I'm setting up a proxy cluster on OpenSuSE 12.1. Squid starts OK on
both servers when called from the lsb script. I stopped it and here is
the configuration I set up :
# crm configure show
node corsen-a
node corsen-b
primitive Proxy ocf:heartbeat:Squid \
params squid_exe="/usr/sbin/sq
2012/4/6 Dejan Muhamedagic :
> Hi,
>
> What probably happens is that radiusd does a fork later, as all
> unix daemon programs do. From the RA meta-data:
>
> binfile* (string): Full path name of the binary to be executed
> The full name of the binary to be executed. This is expected
> to k
Hi,
I have a working cluster on which I decided to go further and manage
the radius process with corosync instead of just the IPaddr.
And there comes the troubles...
The radius server is actually started and the monitor_hook (nagios
check) says it works fine...
Reading the logfile (full log here:
2012/4/4 Lars Marowsky-Bree :
> You can just use the LSB init script if one is provided.
Well, it is OK for 'start' and 'stop', but the status is clearly
lacking: it just checks if the process is running, not if the service
is delivered.
I think I'll write a simple wrapper around the LSB script b
Hi,
I'm quite new to Corosync/Pacemaker but I managed to get my cluster to work:
I have 2 nodes on CentOS5.8 (therefore Pacemaker 1.0.12 and Corosync
1.2.7) running samba-winbind-radius.
The cluster is running fine, but it only knows about one resource, the
failover IP address.
Now, I would like
