HOWTO build and install HAProxy on Solaris 10 x86

SunOS 5.10 i86pc i386

Download HAProxy source from here

gunzip haproxy-1.3.17.tar.gz
tar -xvf haproxy-1.3.17.tar

The readme file contains instructions on how to build it.

cd haproxy-1.3.17
less README

Download GNU make and gcc from sunfreeware.com - search the list on the right

Install GNU make

Installs to /usr/local/bin

gunzip make-3.81-sol10-x86-local.gz
pkgadd -d make-3.81-sol10-x86-local

Install gcc:

gunzip gcc-3.4.6-sol10-x86-local.gz
pkgadd -d gcc-3.4.6-sol10-x86-local

Make and install HAProxy:

Make sure that GNU make is the first make in the path or specify path
i.e., export /usr/local/bin:$PATH
Make sure gcc can be found in the path
i.e., export $PATH:/usr/sfw/bin

make TARGET=solaris CPU=generic

Create a user and group:

/etc/passwd

haproxy:x:114:126::/home/haproxy:/bin/false

/etc/group

haproxy:x:126:

Create an config file, see docs and examples directory
/etc/haproxy.cfg

Install and link to startup / shutdown script
Start last (relative to range of numbers)
ln -sf /usr/local/util/haproxy/haproxy.init /etc/rc2.d/S100haproxy
Stop first (relative to range of numbers)
ln -sf /usr/local/util/haproxy/haproxy.init /etc/rc2.d/K00haproxy

Install and enable auto-start script
/etc/default/haproxy

Create a link to haproxy executable

ln -sf /usr/local/util/haproxy/haproxy-1.3.17 haproxy


Usage : .././haproxy -f  [ -vdVD ] [ -n  ] [ -N  ]
        [ -p <pidfile> ] [ -m <max megs> ]
        -v displays version ; -vv shows known build options.
        -d enters debug mode ; -db only disables background mode.
        -V enters verbose mode (disables quiet mode)
        -D goes daemon ; implies -q
        -q quiet mode : don't display messages
        -c check mode : only check config file and exit
        -n sets the maximum total # of connections (2000)
        -m limits the usable amount of memory (in MB)
        -N sets the default, per-proxy maximum # of connections (2000)
        -p writes pids of all children to this file
        -dp disables poll() usage even when available
        -sf/-st [pid ]* finishes/terminates old pids. Must be last arguments.


/usr/local/sbin/haproxy -f <cfg> -D -p <pid file>

Another HOWTO

Very thorough site

Comments

Post a Comment

Popular posts from this blog

Sites, Newsletters, and Blogs

BLOGS Java.net Weblogs Martin Fowler's blog Paul Graham Ruminations of a Programmer Form Follows Function Newsletters Core Java Tech Tips Enterprise Java Tech Tips JavaSpecialists.EU TheServerSide.com Sites Java.net Today Hot Java Sites CSS Zen Garden Evernote Hacker News Pragmatic Programmer
Read more

Oracle JDBC ReadTimeout QueryTimeout

If a query exceeds the oracle.jdbc.ReadTimeout without receiving any data, an exception is thrown and the connection is terminated by the Oracle driver on the client. Unfortunately the session will still be queued on the database and continue to wait for locks, hold any current locks, and complete any DML/PL*SQL procedures that are pending on the server-side of the orphaned connection. If an application, on a another connection, due to ReadTimeout exception, retries DML/PL*SQL  which requires locks, those queries will queue behind the initial DML/PL*SQL. This will increase the workload exacerbating the situation. On applications with retries, this can be observed by querying the v$session table  or gv$session on RAC and noting new sessions started periodically based on the ReadTimeout interval. The sessions may often have the same SQL_ID and/or SQL_HASH_VALUE. If stmt.setQueryTimeout(Seconds) is issued and the statement exceeds the timeout, it will atte...
Read more

Locks held on Oracle for hours after sessions abnormally terminated by node failure

If a session holds db locks and is abnormally terminated (no fin/ack), the locks will persist until the db session is closed, typically around 2 hours and 12 minutes with default network tcp_keepalive settings. Abnormally terminated does not include CTRL C or kill -9. The ojdbc6 driver apparently has a shutdown hook thread that closes the connections in graceful shutdowns. The OS apparently closes the connections when processes are killed. Abnormally terminated might include power failure, firewall failures, Out Of Memory, OS/kernel crash, network connection failure, JBoss or other server node failure, etc. This was easily reproduced by creating a  process that connected to the db and updated a record but did not commit. While the first process was waiting, a second process with a contending update was started which blocked on the first update. The first clients network cable was then disconnected. The second clients transaction waited for approximately 2 hours until the databa...
Read more