I'm still getting my same timeouts, but this time when installing from
ipkg.sfbay. This seems to eliminate any issues with my own repo server's
repo/apache set-up:
----
% pfexec pkg install system/openjdk7/runtime
DOWNLOAD PKGS FILES XFER (MB)
system/openjdk7/runtime 0/1 563/564 14.1/30.2
Errors were encountered while attempting to retrieve package or file
data for
the requested operation.
Details follow:
1: Framework error: code: 28 reason: Operation timed out after 30000
milliseconds with 5954837 out of 16900743 bytes received
URL: 'http://ipkg.sfbay/dev'.
2: Framework error: code: 28 reason: Operation timed out after 30000
milliseconds with 5962793 out of 16900743 bytes received
URL: 'http://ipkg.sfbay/dev'. (happened 2 times)
3: Framework error: code: 28 reason: Operation timed out after 30000
milliseconds with 5946881 out of 16900743 bytes received
URL: 'http://ipkg.sfbay/dev'.
----
It always starts with trying to download the last file (563 files
already had downloaded successfully). I'd like to remove the parts of
the package that have been downloaded so far, and try to replicate the
problem from the beginning. Any way I can remove what's been downloaded
so far and start again?
-- Alan
Alan Steinberg wrote:
Dan's correct in that the real use of the repository was pretty much
limited to 2 people doing a few installs, mostly at different times.
-- Alan
Dan Price wrote:
On Wed 08 Jul 2009 at 04:11PM, Dan Price wrote:
On Wed 08 Jul 2009 at 02:27PM, [email protected] wrote:
On Wed, Jul 08, 2009 at 02:10:31PM -0700, Alan Steinberg wrote:
Our pkg.depotd is running with 50 threads and a 60-second timeout.
Our apache2 httpd.conf file contains:
ProxyTimeout 30
ProxyRequests Off
AllowEncodedSlashes On
ProxyPass /dev-private http://oursystem.domain:10800 nocanon
disablereuse=On
Do we have a bad setup somewhere, or is there a bug in the new
transport code?
There are likely problems in your setup. Setting disablereuse=on will
cause performance issues with the new transport. It performs better
when it's able to take advantage of connection re-use. I'm not an
Apache expert, but perhaps someone else can offer more guidance about
your other choices.
Sure-- it's not ideal to disable reuse, but doing so will only cause
performance to be lower than the optimum. It shouldn't cause the
timeout issues Alan has seen.
Umm, yeah, except in the case that your apache workers overwhelm your
total depot threads.
But it seems odd to me that RE would wind up in that scenario. You
sort-of need internet scale deployment to see that happen.
-dp
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
