[opensuse-buildservice] Uploads cause 500 Internal Server Error
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Seems no one has reported it on the mailing-list yet, so.. ;)
Uploading files with osc cause 500 Internal Server Errors:
.../server:messaging/mcabber> osc commit
Sending mcabber-0.9.3.tar.bz2
Deleting mcabber-0.9.2.tar.bz2
Sending mcabber.spec
...
urllib2.HTTPError: HTTP Error 500: Internal Server Error
Could to be related to the size of the file, as I was able to upload the
spec, but not the tarball.
Complete osc trace is attached, might be helpful.
Using the web UI worked. Dunno whether it's spurious or only fails with
osc though.
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On 2007-06-20 00:34:14 +0200, Pascal Bleser wrote:
urllib2.HTTPError: HTTP Error 500: Internal Server Error
known. i am already working on a solution. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Jun 20, 2007 at 12:34:14AM +0200, Pascal Bleser wrote:
Seems no one has reported it on the mailing-list yet, so.. ;)
Thank you.
Uploading files with osc cause 500 Internal Server Errors: .../server:messaging/mcabber> osc commit Sending mcabber-0.9.3.tar.bz2 Deleting mcabber-0.9.2.tar.bz2 Sending mcabber.spec ... urllib2.HTTPError: HTTP Error 500: Internal Server Error
Could to be related to the size of the file, as I was able to upload the spec, but not the tarball.
Complete osc trace is attached, might be helpful.
A propos trace: running osc with -X will output a full trace of the HTTP traffic. It might be helpful here. It shows that the server replies with 401 Unauthorized after the upload, and with 500 Internal Server Error after retrying. (Which is strange.) Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development
On 2007-06-20 10:18:42 +0200, Dr. Peter Poeml wrote:
A propos trace: running osc with -X will output a full trace of the HTTP traffic. It might be helpful here.
i only saw -H in the help. does -X include the body?
It shows that the server replies with 401 Unauthorized after the upload,
why is this strange?
and with 500 Internal Server Error after retrying. (Which is strange.)
no. that is kinda expected if you know the server side. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Jun 20, 2007 at 12:30:10PM +0200, Marcus Rueckert wrote:
On 2007-06-20 10:18:42 +0200, Dr. Peter Poeml wrote:
A propos trace: running osc with -X will output a full trace of the HTTP traffic. It might be helpful here.
i only saw -H in the help. does -X include the body?
I actually meant -H.
It shows that the server replies with 401 Unauthorized after the upload,
why is this strange?
Because the upload should succeed??
and with 500 Internal Server Error after retrying. (Which is strange.)
no. that is kinda expected if you know the server side.
Ah, that explains it. Thanks. Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development
to conclude an IRC discussion with other words ... It seems osc does get the 401 only with large files. When retrying with full credencials (to satiesfy the "not authentificated" 401 error), the server returns a 500 (internal error). So, we should look on the server side, why it returns 401 with large files in first place, IMHO bye adrian On Wednesday 20 June 2007 12:37:35 wrote Dr. Peter Poeml:
On Wed, Jun 20, 2007 at 12:30:10PM +0200, Marcus Rueckert wrote:
On 2007-06-20 10:18:42 +0200, Dr. Peter Poeml wrote:
A propos trace: running osc with -X will output a full trace of the HTTP traffic. It might be helpful here.
i only saw -H in the help. does -X include the body?
I actually meant -H.
It shows that the server replies with 401 Unauthorized after the upload,
why is this strange?
Because the upload should succeed??
and with 500 Internal Server Error after retrying. (Which is strange.)
no. that is kinda expected if you know the server side.
Ah, that explains it. Thanks.
Peter
-- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N�rnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Jun 20, 2007 at 12:57:23PM +0200, Adrian Schröter wrote:
to conclude an IRC discussion with other words ...
It seems osc does get the 401 only with large files.
When retrying with full credencials (to satiesfy the "not authentificated" 401 error), the server returns a 500 (internal error).
So, we should look on the server side, why it returns 401 with large files in first place, IMHO
No. The sequence 401 -> 500 is not specific to large files. The 500 is specific to large files. Please use "osc -H ci" to reproduce and you'll see. Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development
On Wed, Jun 20, 2007 at 10:18:42AM +0200, Dr. Peter Poeml wrote:
On Wed, Jun 20, 2007 at 12:34:14AM +0200, Pascal Bleser wrote:
Seems no one has reported it on the mailing-list yet, so.. ;)
Thank you.
Uploading files with osc cause 500 Internal Server Errors: .../server:messaging/mcabber> osc commit Sending mcabber-0.9.3.tar.bz2 Deleting mcabber-0.9.2.tar.bz2 Sending mcabber.spec ... urllib2.HTTPError: HTTP Error 500: Internal Server Error
Could to be related to the size of the file, as I was able to upload the spec, but not the tarball.
Complete osc trace is attached, might be helpful.
A propos trace: running osc with -X will output a full trace of the HTTP traffic. It might be helpful here. It shows that the server replies with 401 Unauthorized after the upload, and with 500 Internal Server Error after retrying. (Which is strange.)
Somewhere in the returned javascript foobar there is something which might give a hint: <script type="text/javascript"> var err_stat = "500 Internal Server Error" var err_desc = "The origin web server encountered an unexpected condition which prevented it from fulfilling the request. Please try your request again." var err_code = ""; if ( err_desc.indexOf("Access to this page is restricted because of access control policies") > -1 ) { err_code = "403"; } </script> Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dr. Peter Poeml wrote: [...]
Somewhere in the returned javascript foobar there is something which might give a hint:
<script type="text/javascript"> var err_stat = "500 Internal Server Error" var err_desc = "The origin web server encountered an unexpected condition which prevented it from fulfilling the request. Please try your request again." var err_code = "";
Yeah, I'm regularely running into those lately, when I don't take any
action on the BS web UI page for a while (say, 15min or so).
The session isn't timed out though, I don't need to log in again.
When I go to another page in the web UI and come then come back, it
works again.
Maybe some sort of mismatch between iChain and BS session lifetime (just
a random thought) ?
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Thursday, 21. June 2007 01:06, Pascal Bleser wrote:
Dr. Peter Poeml wrote: [...]
Somewhere in the returned javascript foobar there is something which might give a hint:
<script type="text/javascript"> var err_stat = "500 Internal Server Error" var err_desc = "The origin web server encountered an unexpected condition which prevented it from fulfilling the request. Please try your request again." var err_code = "";
Yeah, I'm regularely running into those lately, when I don't take any action on the BS web UI page for a while (say, 15min or so). The session isn't timed out though, I don't need to log in again. When I go to another page in the web UI and come then come back, it works again.
Maybe some sort of mismatch between iChain and BS session lifetime (just a random thought) ?
No, the ichain and bs sessions are completely unrelated.
cheers
-- Andreas Bauer - Novell - SUSE Internal Tools --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Jun 20, 2007 at 01:16:22PM +0200, Dr. Peter Poeml wrote:
Uploading files with osc cause 500 Internal Server Errors: .../server:messaging/mcabber> osc commit Sending mcabber-0.9.3.tar.bz2 Deleting mcabber-0.9.2.tar.bz2 Sending mcabber.spec ... urllib2.HTTPError: HTTP Error 500: Internal Server Error
Could to be related to the size of the file, as I was able to upload the spec, but not the tarball.
[...]
if ( err_desc.indexOf("Access to this page is restricted because of access control policies") > -1 )
Reportedly, setting a different content-type on the PUT request fixes this issue. I have a fixed osc package ready, but cannot commit it, notably not due to this very problem, but due to another one: iChain has gone fishing today. Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development
participants (5)
-
Adrian Schröter -
Andreas Bauer -
Dr. Peter Poeml -
Marcus Rueckert -
Pascal Bleser