Making sure the postgres system user has a real shell - needed to perform command line execs
Fix autoinstall script to handle prompt change in f9f03d6
made --install == --upgrade
sourcing sub-scripts in their own sub-shell
removed commented out --update switch instructions left over from 90a85d393588a1 (commit before last)
Put in support for --policy-check flag
arg shift when checking policy..
updated security version to install 2.1.4
raised dashboard version to 1.1.0
Merge branch 'devel' of esgf.org:esgf-installer into devel
Merge branch 'devel' into gavin-proposed
raised LAS to 7.3.8
Merge branch 'proposed' of esgf.org:esgf-installer/gavin into gavin-proposed
Bug fix, was writing new csr with multiple Owner entry DNs gotten from keystore local cert and root cert combined - now will only get first one, which is local cert DN
Keep dashboard as it was... will unveil later.
make sure that the publisher_home is there before attempting to chown it
don't hardcode dbsuper user or esgcet databasename
Make sure that publisher_home directory is set before calling esgsetup --config (bob will put in publisher code later...)
Make node admin password be at least 6 characters long - this is so that if it is used for truststore/keystore password that it meets that criteria as well and not fail there
Trying to fix the CLOSE_WAIT problem....

So I have scoured the net looking for why the heck we keep getting a
ton of CLOSE_WAIT connections off board apparently to verisign.

jsvc      5641   tomcat   37r  IPv6 43389545       TCP 198.128.245.149:80->204.121.6.104:52369 (CLOSE_WAIT)
jsvc      5641   tomcat   40r  IPv6 44146898       TCP 198.128.245.149:80->192.43.239.242:39293 (CLOSE_WAIT)
jsvc      5641   tomcat   46r  IPv6 43397801       TCP 198.128.245.149:80->204.121.6.104:54353 (CLOSE_WAIT)
jsvc      5641   tomcat   48r  IPv6 43390413       TCP 198.128.245.149:80->204.121.6.104:58082 (CLOSE_WAIT)
jsvc      5641   tomcat   49r  IPv6 43391464       TCP 198.128.245.149:80->204.121.6.104:45878 (CLOSE_WAIT)
jsvc      5641   tomcat   50r  IPv6 43391239       TCP 198.128.245.149:80->204.121.6.104:48295 (CLOSE_WAIT)
jsvc      5641   tomcat   51r  IPv6 43392432       TCP 198.128.245.149:80->204.121.6.104:55672 (CLOSE_WAIT)
jsvc      5641   tomcat   53r  IPv6 43393252       TCP 198.128.245.149:80->204.121.6.104:38455 (CLOSE_WAIT)
jsvc      5641   tomcat   78r  IPv6 43394641       TCP 198.128.245.149:80->204.121.6.104:58812 (CLOSE_WAIT)
jsvc      5641   tomcat   81r  IPv6 43396987       TCP 198.128.245.149:80->204.121.6.104:33926 (CLOSE_WAIT)
jsvc      5641   tomcat   82r  IPv6 43401440       TCP 198.128.245.149:80->204.121.6.104:42746 (CLOSE_WAIT)
jsvc      5641   tomcat   83r  IPv6 43399225       TCP 198.128.245.149:80->204.121.6.104:42405 (CLOSE_WAIT)
jsvc      5641   tomcat   84r  IPv6 43399898       TCP 198.128.245.149:80->204.121.6.104:58584 (CLOSE_WAIT)
jsvc      5641   tomcat   85r  IPv6 43400222       TCP 198.128.245.149:80->128.115.57.69:52504 (CLOSE_WAIT)
jsvc      5641   tomcat   87r  IPv6 43402317       TCP 198.128.245.149:80->204.121.6.104:33189 (CLOSE_WAIT)
jsvc      5641   tomcat   88r  IPv6 43403030       TCP 198.128.245.149:80->204.121.6.104:57269 (CLOSE_WAIT)
jsvc      5641   tomcat   94u  IPv6 43451043       TCP 198.128.245.149:80->128.115.57.69:53233 (CLOSE_WAIT)
jsvc      5641   tomcat  110r  IPv6 43452287       TCP 198.128.245.149:80->128.115.57.69:53271 (CLOSE_WAIT)
jsvc      5641   tomcat  111r  IPv6 43456135       TCP 198.128.245.149:80->128.115.57.69:53334 (CLOSE_WAIT)
jsvc      5641   tomcat  117r  IPv6 43552802       TCP 198.128.245.149:80->134.157.176.115:39751 (CLOSE_WAIT)
jsvc      5641   tomcat  120r  IPv6 44044436       TCP 198.128.245.149:80->204.121.6.104:52117 (CLOSE_WAIT)
jsvc      5641   tomcat  122r  IPv6 44048557       TCP 198.128.245.149:80->204.121.6.104:55990 (CLOSE_WAIT)
jsvc      5641   tomcat  127r  IPv6 44052022       TCP 198.128.245.149:80->204.121.6.104:45886 (CLOSE_WAIT)
jsvc      5641   tomcat  128r  IPv6 44061972       TCP 198.128.245.149:80->204.121.6.104:43315 (CLOSE_WAIT)
jsvc      5641   tomcat  148r  IPv6 44347050       TCP 198.128.245.149:80->128.115.184.51:42257 (CLOSE_WAIT)
jsvc      5641   tomcat  163r  IPv6 44317960       TCP 198.128.245.149:80->128.219.49.13:32377 (CLOSE_WAIT)
jsvc      5641   tomcat  172u  IPv6 44327289       TCP 198.128.245.149:80->204.121.6.104:52346 (CLOSE_WAIT)
jsvc      5641   tomcat  174u  IPv6 44341286       TCP 198.128.245.149:80->128.115.184.51:42009 (CLOSE_WAIT)
jsvc      5641   tomcat  175u  IPv6 44341402       TCP 198.128.245.149:80->128.115.184.51:42078 (CLOSE_WAIT)
java      6004     root    4r  IPv6 44407526       TCP 127.0.0.1:44452->127.0.0.1:8984 (CLOSE_WAIT)
java      6004     root  153w  IPv6 44407527       TCP 127.0.0.1:35566->127.0.0.1:8984 (CLOSE_WAIT)

When I "dig" the destination IP I get:

%> dig 192.43.239.242

; <<>> DiG 9.3.4-P1 <<>> 192.43.239.242
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59854
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;192.43.239.242.			IN	A

;; AUTHORITY SECTION:
.			10800	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2012050801 1800 900 604800 86400

;; Query time: 9 msec
;; SERVER: 128.115.249.1#53(128.115.249.1)
;; WHEN: Tue May  8 23:09:04 2012
;; MSG SIZE  rcvd: 107

So looking around the internet I found this in a few locations:

http://www.java.net/node/663567
"I found a topic with the solution. Setting the jvm option
com.sun.enterprise.server.ss.ASQuickStartup to false solved the
connect timeout issue."

(and info at: http://mariosgaee.blogspot.com/)

Hopefully this will fix this issue.
-gavin