Attached is the request being made and the response before the zeros.
Here are the publishers I have configured. I don't believe I am using
any mirrors.
r...@factory:~# pkg publisher
PUBLISHER TYPE STATUS URI
ipkg (preferred) origin online
http://ipkg.sfbay.sun.com/release/
opensolaris origin online
http://pkg.opensolaris.org/release/
Thanks...
--joe
[email protected] wrote:
On Wed, Jul 08, 2009 at 02:38:58PM -0700, Danek Duvall wrote:
On Wed, Jul 08, 2009 at 02:31:51PM -0700, Joseph Mocker wrote:
I'm still a little uncertain that the "pkg fix" problem I am having
is related to the other recent problems with pkg.opensolaris.org.
For one, I get the same problem going to ipkg. It sounded like one
of the problems with pkg.opensolaris.org was volume, which I would
assume is not a problem for ipkg.
Also, the error I am getting is "Read error on tar stream." To me
this indicates its getting a response from ipkg, just not the right
one.
So I did a quick snoop and took a look at the response coming back.
From what I see, the payload of the HTTP response is the normal
header fields, then just several packets of 0x00 bytes.
Thoughts?
This really needs to go to pkg-discuss (install and website bcc'ed).
This was what I mentioned to Danek earlier in the week, but I guess he
didn't pass this along when he bounced your e-mail back to the list.
For a problem like this:
I responded to a similar thread last week, but received no follow-up.
http://mail.opensolaris.org/pipermail/pkg-discuss/2009-July/014893.html
Basically, we need to figure out why you're getting a read error on the
tar stream.
a. Do you have mirrors configured? If so, you may be requesting a file
from a mirror that doesn't have the content
b. Your tar stream may be getting corrupted/truncated
c. The server may not have the file you requested.
d. Something else is wrong
If you're getting 0x00 bytes back, it's likely that you're getting an
empty tar stream as a result (a or c). This means that the client has
requested a file that the server doesn't have. Can you snoop again and
capture the headers (and content) of the request that the client is
making to the server? This will give us a chance to figure out what
file is being requested that's absent on the server.
-j
*** Request ***
POST /release/filelist/0 HTTP/1.1
Accept-Encoding: identity
Content-length: 2041
Connection: close
Content-type: application/x-www-form-urlencoded
Host: ipkg.sfbay.sun.com
User-agent: pkg/26c3e2407c53 (sunos i86pc; 5.11 snv_111a; full; pkg)
File-Name-29=60d5a62bb44295eb439eaf79cf8edf2fe2ca769d&File-Name-28=bfb616aad4e09df13f4ef588fb4d0969bbaac455&File-Name-21=a3aa6a31403e0c53eac422f61d9c50242ce926f2&File-Name-20=3dd7f4309e0dd401bee2f7eba961b54adc7e8c5c&File-Name-23=85019c74071f33a9f1c160d615450f6cd01208de&File-Name-22=37c9b6ee28f43203fe4aea984ef63f8e8de7fb7f&File-Name-25=913bbd7053190a15061147f59d8acd5bac4cf386&File-Name-24=73f111638e6a779443854f87af95a84614701314&File-Name-27=fccd9bfbc80a717b355a1a5d761744de9cfc3deb&File-Name-26=f2f1c9d8443e10d9df0bf152ab0b3eaf919d9d73&File-Name-8=20b0ebf9985415496f52378185a6e6d0c3a77430&File-Name-9=51a928a75f6c3bc299a7c3a52320bd6b652bd481&File-Name-6=8fe7b2a02ec616be1277fbaa38bb4d942129b4a2&File-Name-7=45f468c207e9746134f9b2ee3a20a47ee113a184&File-Name-4=337c2be253f937752df118933ef075c1416b772e&File-Name-5=3d5c180aa6cb83cc484c5ed6ce155d000a03f744&File-Name-2=4ee4309f48ab5eee5e4eb983c30b6a535d9b7f16&File-Name-3=4438a33e142bc405dcef34c3ac091ace6fb5f7cc&File-Name-0=ddc803d598bdfc8d0f41ba9b53049e699d56cb7b&File-Name-1=35f8d4a1528d5485fff5a690b7c4070f113709c9&File-Name-36=7c15ce565e041bf6259b703e6a82820e7fe2f886&File-Name-37=0ecc83952d7daca9965477b4f4b13d644d9389b0&File-Name-34=959c7b36b3d0e287d4fe19c63907faa1ca28cceb&File-Name-35=57fc1c7f0e644ab0d35ff83cdd7b1b42829f3505&File-Name-32=fcf28f40e101c4bb336b3590c44e2983f6c1a918&File-Name-33=06cf3c6858883fe9f0a9edc6ee22b2dd3afd24ea&File-Name-30=dd826159efb136fb4e2c4a5e91e1b54db41d19d0&File-Name-31=fbf9471b8994ee528da228f5a8a8b58d481feb98&File-Name-10=624043d4e902b8d47d1d3b69fd4056246c19a631&File-Name-11=4d595df5a7a2f95fada7efc46dca56d4d24d5901&File-Name-12=4f7112c2bf6c965b1f63480cc90b88dbccb9711f&File-Name-13=5b3838e96cd20841d904b7fa1dc578e588f48e7b&File-Name-14=d5bfd9592851863159646d108f5db6c604b2d72a&File-Name-15=6e7a5da4991ca01e59b96af65a1cfe5b3ac95d67&File-Name-16=9c2927f1d31037835215cb140bf087b5e65272c6&File-Name-17=123f9363faffad6d05574224f360d3edfc7d21ec&File-Name-18=6f02b52fbbcc049120a38d147bc0f1c51d398583&File-Name-19=5aeea7e9fc8b97d1877fee0bbb2ea83cac8f4767
*** Response ***
HTTP/1.1 200 OK
Date: Wed, 08 Jul 2009 21:22:17 GMT
Server: CherryPy/3.1.1
Content-Type: application/data
Vary: Accept-Encoding
Connection: close
Transfer-Encoding: chunked
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
