forwarded 502193 http://projects.reductivelabs.com/issues/961
tags 502193 upstream
thanks
Doing some more research, I found
http://projects.reductivelabs.com/issues/961
and cannot help but notice a lot of CLOSE_WAIT connections on all of the
clients experiencing the problem, all held by the da
found 502193 0.24.7-1
thanks
The problem persists with the experimental packages installed on
server and client, both locally (server/client) on the same machine,
as well as remotely.
--
.''`. martin f. krafft Related projects:
: :' : proud Debian developer http://debian
I reproduced this running both server and client in debug mode.
Please see the attached files. The following lines are the
corresponding apache access.log lines:
130.60.75.74 - - [10/Feb/2009:09:56:34 +0100] "POST /RPC2 HTTP/1.1" 200 131
"-" "XMLRPC::Client (Ruby 1.8.7)"
130.60.75.74 - - [10/
also sprach martin f krafft [2009.02.09.0826 +0100]:
> I am now seeing the warnings quite often on lenny hosts talking to
> the lenny puppetmaster. I've now removed the record from the
> puppetmaster DNS name to make sure this isn't IPv6-related. Other
> than using three mongrel instances for
I am now seeing the warnings quite often on lenny hosts talking to
the lenny puppetmaster. I've now removed the record from the
puppetmaster DNS name to make sure this isn't IPv6-related. Other
than using three mongrel instances for the 8 machines I am currently
testing with puppet, I don't kn
5 matches
Mail list logo
