skip to content »

ik-kem.ru

Mysql manager of pid file quit without updating

If the realserver is the final delivery target, then the mail will arrive randomly at any one of the realservers and write to the different filesystems.This is the many reader/many writer problem that LVS has.

(an nfs.monitor is in the works.) Each realserver will have to be configured to accept mail for the virtual server DNS name (say lvs.domain.com).If instead you want the client to be presented with one virtual machine, you will need each machine to have its hostname being the name associated with the VIP, the sshd will have to listen to the VIP (if LVS-DR, LVS-Tun) and the hostkeys will have to be generated for the name of the VIP.The user must exit cleanly from their ssh session, or the realserver will be left running the ssh invoked process at high load average.I now use Net App filers on which my maildirs live, and I have multiple IMAP/POP (and Horde/IMP webmail) servers living behind a pair of LVS directors.Using maildir format [0], I export the mailboxes via NFS to the frontend servers and it works a treat - generally because maildir saves files using filenames derived from the hostname, so the frontend servers don't hit race conditions when trying to manipulate files.I'm using ipvs to balance ssh connections but for some reason ipvs is only using one real server and persists to use that server until I delete its arp entry from the ipvs machine and remove the virtual loopback on the realserver.

Also, I noticed that connections do not register with this behavior.

Surprisingly (considering that it negotiates a secure connection) nothing special either.

You do not need persistent port/client connection for this. The director will timeout an idle tcp connection (e.g. You'll get "Connection reset by peer" independently of LVS.

Since the client will be displaying a prompt with the name of the realserver (rather than the name associated with the VIP) this will work just fine.

However the client will get a different realserver each connection (which is OK too) and will accumulate keys for each realserver.

Shivaji Navale On our realservers, after the users have logged out of their ssh session, zombie processes run at high load average in the background. The ssh connection to the director doesnt get closed even after ctrl-D. I use ipvs to load balance ssh and I do use persistence (and my users are happy with it -- in fact they asked me to do so).