Date: Fri, 27 Jul 2007 15:02:48 +0200
From: Pierguido <pierg75@yahoo.it>
To: Debian User Lists <debian-user@lists.debian.org>
Subject: [lvs-users] Ldirectord problem
Message-ID: <46A9ECF8.9030505@yahoo.it>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Hi all.
I'm trying to build a little cluster (two hosts) to serve mail (smtp,
pop, imap) and web services.
At the beginnings everythings worked without many problems...but now i
see strange ldirectord behavior:
This is host 1:
srv-cluster-1:~# ./test_cluster.sh
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:e0:18:fe:35:7d brd ff:ff:ff:ff:ff:ff
inet 192.168.30.120/24 brd 192.168.30.255 scope global eth0
inet6 fe80::2e0:18ff:fefe:357d/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:50:04:37:76:95 brd ff:ff:ff:ff:ff:ff
inet 192.168.30.121/24 brd 192.168.30.255 scope global eth1
inet6 fe80::250:4ff:fe37:7695/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:19:5b:5d:41:6e brd ff:ff:ff:ff:ff:ff
inet 10.0.0.1/24 brd 10.0.0.255 scope global eth2
inet6 fe80::219:5bff:fe5d:416e/64 scope link
valid_lft forever preferred_lft forever
5: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
ldirectord is stopped for /etc/ha.d/ldirectord.cf
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
master stopped
version: 8.0.4 (api:86/proto:86)
SVN Revision: 2947 build by root@srv-cluster-1, 2007-07-23 18:48:08
0: cs:Connected st:Primary/Primary ds:UpToDate/UpToDate C r---
ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
resync: used:0/31 hits:0 misses:0 starving:0 dirty:0 changed:0
act_log: used:0/257 hits:0 misses:0 starving:0 dirty:0 changed:0
and this host 2:
srv-cluster-2:~# ./test_cluster.sh
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:1b:78:57:19:60 brd ff:ff:ff:ff:ff:ff
inet 192.168.30.122/24 brd 192.168.30.255 scope global eth0
inet 192.168.30.253/24 brd 192.168.30.255 scope global secondary eth0
inet6 fe80::21b:78ff:fe57:1960/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:1b:78:57:19:61 brd ff:ff:ff:ff:ff:ff
inet 192.168.30.123/24 brd 192.168.30.255 scope global eth1
inet6 fe80::21b:78ff:fe57:1961/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:1b:78:37:bc:49 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.2/24 brd 10.0.0.255 scope global eth2
inet6 fe80::21b:78ff:fe37:bc49/64 scope link
valid_lft forever preferred_lft forever
5: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
ldirectord stale pid file /var/run/ldirectord.ldirectord.cf.pid for
/etc/ha.d/ldirectord.cf
ldirectord is stopped for /etc/ha.d/ldirectord.cf
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.30.253:143 wlc persistent 600
-> 192.168.30.120:143 Masq 0 0 0
-> 192.168.30.122:143 Local 0 0 0
-> 127.0.0.1:143 Local 0 0 0
TCP 192.168.30.253:80 rr
-> 192.168.30.122:80 Local 1 0 0
-> 192.168.30.120:80 Route 1 0 0
TCP 192.168.30.253:25 wlc persistent 600
-> 192.168.30.120:25 Tunnel 1 0 0
-> 192.168.30.122:25 Local 1 0 0
master running
(ipvs_syncmaster pid: 3698)
version: 8.0.4 (api:86/proto:86)
SVN Revision: 2947 build by root@srv-cluster-2, 2007-07-23 10:45:53
0: cs:Connected st:Primary/Primary ds:UpToDate/UpToDate C r---
ns:0 nr:28672 dw:28672 dr:0 al:0 bm:12 lo:0 pe:0 ua:0 ap:0
resync: used:0/31 hits:1786 misses:6 starving:0 dirty:0 changed:6
act_log: used:0/257 hits:0 misses:0 starving:0 dirty:0 changed:0
If i try to restart heartbeat (that should restart also ldirectord) the
i get both of the nodes on the same situation:
ldirectord stale pid file /var/run/ldirectord.ldirectord.cf.pid for
/etc/ha.d/ldirectord.cf
ldirectord is stopped for /etc/ha.d/ldirectord.cf
master stopped
here my confs:
srv-cluster-1:~# cat /etc/ha.d/ha.cf
logfacility local0
bcast eth2 # Linux
mcast eth2 225.0.0.1 694 1 0
auto_failback off
node srv-cluster-1
node srv-cluster-2
respawn hacluster /usr/lib/heartbeat/ipfail
apiauth ipfail gid=haclient uid=hacluster
srv-cluster-1:~# cat /etc/ha.d/haresources
srv-cluster-1 \
ldirectord::ldirectord.cf \
LVSSyncDaemonSwap::master \
IPaddr2::192.168.30.253/24/eth0/192.168.30.255
srv-cluster-1:~# cat /etc/ha.d/ldirectord.cf
checktimeout=10
checkinterval=2
autoreload=no
logfile="local0"
quiescent=yes
virtual=192.168.30.253:80
real=192.168.30.120:80 gate
real=192.168.30.122:80 gate
fallback=127.0.0.1:80 gate
service=http
request="ldirector.html"
receive="Test Page"
scheduler=rr
protocol=tcp
checktype=negotiate
virtual=192.168.30.253:25
real=192.168.30.120:25 ipip
real=192.168.30.122:25 ipip
fallback=127.0.0.1:25
service=smtp
scheduler=wlc
persistent=600
protocol=tcp
virtual=192.168.30.253:143
real=127.0.0.1:143 masq
real=192.168.30.120:143 masq
real=192.168.30.122:143 masq
fallback=127.0.0.1:143
service=imap
scheduler=wlc
#login="test"
#passwd="test"
persistent=600
persistent=600
protocol=tcp
Obviously both nodes have the same configuration.
Thanks all
Pier
"I disapprove of what you say, but I will defend to the death your right
to say it"
Evelyn Beatrice Hall
LinuxVirtualServer.org mailing list - lvs-users@LinuxVirtualServer.org
Send requests to lvs-users-request@LinuxVirtualServer.org
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
Date: Fri, 27 Jul 2007 08:12:40 -0500
From: Ron Johnson <ron.l.johnson@cox.net>
To: debian-user@lists.debian.org
Subject: Re: searching for graphical torrent client
Message-ID: <46A9EF48.8060401@cox.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/27/07 05:07, Giorgos D. Pallas wrote:
> I tried google but can't seem to find something that both looks decent
> *and* is available for debian (testing) as a binary. For example I tried
> qtorrent, but it is so minimal that I don't like it... Or to put it in
> another way: Which client resembles most the windows utorrent? (I also
> tried ktorrent for KDE and it crashes often...)
I like freeloader. You need to find your own torrents, but once you
do, it actually works like a charm. (The only torrent app I've been
able to get working on a consistent basis. The other are too
complicated for my tastes.)
Description: A nice GNOME download manager supporting torrents
Freeloader is a nice GNOME download manager written in Python
and supporting torrents. Its main features are:
- Support for BitTorrent files
- Command line control
- File system monitoring
- Sorting by status or progress
- Preferences saved in GConf
- Drag and drop URLs or Torrents into main window or tray
- Support for retrieval from most URLs (ftp, http, etc)
- Support for hiding in system tray
- Interruptible downloads
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGqe9IS9HxQb37XmcRAiOhAKCYYf3EeOFu4ZJIRdMDxhv6Be5yugCgmDzk
hDpAYsNTom/oskO1kTJdc14=
=2CjF
-----END PGP SIGNATURE-----
Date: Fri, 27 Jul 2007 08:16:09 -0500
From: Ron Johnson <ron.l.johnson@cox.net>
To: debian-user@lists.debian.org
Subject: Re: minimal firewall computer
Message-ID: <46A9F019.5070608@cox.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/27/07 05:34, Ivan Glushkov wrote:
> Hi all,
>
> I have a 2 MBit DSL connection at home and I have more or less classical
> scheme ISP <-> DSL Modem <-> Router <-> home desktop & laptops. Since
> recently somebody hacked into my windowz computer I started thinking of
> adding a firewall. Since connecting my desktop between the router and
> the modem is not an option (it must run windowz due to other members of
> my family), I am thinking of buying the cheapest possible second hand
> computer which still has two free PCI slots on which to install minimal
> Debian (no graphics, only firewall), plug two 10/100 Ethernet cards and
> add it in my scheme like this:
>
> ISP <-> DSL Modem <-> Firewall <-> Router <-> home desktop & laptops
>
> The question is actually what is the minimal CPU/RAM/HDD requirement for
> this PC? And do you think this is the optimal solution for an intrusion
> protection of a small home LAN?
Most "home market" routers should also have built-in firewall and
dhcp functionality. US$50 at any big mail-order store like NewEgg.
- --
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGqfAZS9HxQb37XmcRAm0TAJ91lwB3KO+g50p3HSp0rwsmNt7xYQCZAWDV
edBmuBtweLR1PGkNIbVOKs0=
=XZZ3
-----END PGP SIGNATURE-----
Date: Fri, 27 Jul 2007 09:36:22 -0400
From: "Todd Troxell" <ttroxell@gmail.com>
To: "Wetzelaer, Volker" <Volker.Wetzelaer@qsc.de>
Cc: debian-user@lists.debian.org
Subject: Re: AIC-9410 problems during installation
Message-ID: <ca76dcdb0707270636n29c2fce3kf04e660ab4bf5f84@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="----=_Part_4054_1677428.1185543382690"
------=_Part_4054_1677428.1185543382690
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 7/27/07, Wetzelaer, Volker <Volker.Wetzelaer@qsc.de> wrote:
>
> No, sorry,
>
> no chance. I tried so many things but it did not help.
> Maybe you can try this
http://www.jimmy.co.at/weblog/?p=71
> (Did not work with my Controller...)
>
> Volker
>
I did some research on this and found that it is the result of missing
firmware blob in /lib/firmware/ in the initramfs. There is more info in
fixed ubuntu bug #82382
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/82382
It also mentions a patch to initramfs here:
http://help.lockergnome.com/linux/aic94xx-firmware-initramfs-ftopict394102.html
I will let you know if I can make a d-i image with this installed.
------=_Part_4054_1677428.1185543382690
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 7/27/07, <b class="gmail_sendername">Wetzelaer, Volker</b> <<a href="mailto:Volker.Wetzelaer@qsc.de">Volker.Wetzelaer@qsc.de</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
------=_Part_4054_1677428.1185543382690--
Date: Fri, 27 Jul 2007 09:40:17 -0400
From: Wayne Topa <linuxone@intergate.com>
To: debian-user@lists.debian.org
Subject: Re: searching for graphical torrent client
Message-ID: <20070727134017.GA6233@buddy.mtntop.home>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Giorgos D. Pallas(gpall@ccf.auth.gr) is reported to have said:
> I tried google but can't seem to find something that both looks decent
> *and* is available for debian (testing) as a binary. For example I tried
> qtorrent, but it is so minimal that I don't like it... Or to put it in
> another way: Which client resembles most the windows utorrent? (I also
> tried ktorrent for KDE and it crashes often...)
Don't know about a Winbloz look alike, but you might give the azureus
package a try. It is a 'big' package, 7Meg, but has all the eye candy
you would want.
Wayne
--
It said "Insert disk 3..." but only 2 fit.
_______________________________________________________
Date: Fri, 27 Jul 2007 08:41:07 -0500
From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: Debian User List <debian-user@lists.debian.org>
Subject: Re: Sarge: Lost # of failed logins
Message-ID: <46A9F5F3.3050006@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
On 07/26/2007 10:44 PM, Andrew Sackville-West wrote:
> On Thu, Jul 26, 2007 at 05:52:00PM -0600, Bob Proulx wrote:
>> Florian Kulzer wrote:
>>> I have been using Debian for about 5 years now. As far as I remember, it
>>> always had the "n failure(s) since last login" message (if n was greater
>>> than zero).
>> I have never seen that message.
>
> it works reliably on this particular up-to-date sid box, shows the
> proper number of failures. I think it must come from login, but I
> can't see what might cause to happen or not.
> [...]
And it works on my Etch box, but my main box is still this Sarge
computer. Nothing in /etc/profile, ~/.bash_profile or ~/.bashrc seems to
produce this message. Surely the message comes from the 'login' command,
but I can't see what feature of login enables that.
Date: Fri, 27 Jul 2007 08:50:46 -0500
From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: Debian User List <debian-user@lists.debian.org>
Subject: Re: Sarge: Lost # of failed logins
Message-ID: <46A9F836.1010809@earthlink.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
On 07/27/2007 05:57 AM, Florian Kulzer wrote:
> On Thu, Jul 26, 2007 at 20:44:49 -0700, Andrew Sackville-West wrote:
>> On Thu, Jul 26, 2007 at 05:52:00PM -0600, Bob Proulx wrote:
>>> Florian Kulzer wrote:
>>>> I have been using Debian for about 5 years now. As far as I remember, it
>>>> always had the "n failure(s) since last login" message (if n was greater
>>>> than zero).
>>> I have never seen that message.
>> it works reliably on this particular up-to-date sid box, shows the
>> proper number of failures. I think it must come from login, but I
>> can't see what might cause to happen or not.
>
> [...]
>
>> I do _not_ get this message over ssh, so it must come from that pair
>> -- login or getty...
>
> I think this is controlled in /etc/login.defs:
>
> #
> # Enable logging and display of /var/log/faillog login failure info.
> # This option conflicts with the pam_tally PAM module.
> #
> FAILLOG_ENAB yes
> [...]
Hmm. My /var/log/faillog was missing, but even when I 'touch' it, the
behavior doesn't change. My FAILLOG_ENAB is also "yes" in /etc/login.defs.
In my /etc/pam.d/login file, "session optional pam_lastlog.so" is enabled.
End of debian-user-digest Digest V2007 Issue #2039
**************************************************
Received on Fri Jul 27 10:11:59 2007